Skip to content

1.1.6 Bug Fix and QoL Release

Latest
Latest
Compare
Choose a tag to compare
@t1stm t1stm released this 17 Sep 17:23
· 11 commits to master since this release
v1.1.6
9eddb47
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Some Bug Fixes and QoL improvements.

I've noticed some problems that were of medium severity but I still couldn't ignore them, so I made this release.
In this release I've also bundled some interesting stuff, which were meant to be included in the 2.0.0 version but are ready now, so I just included them to not worry about separating branches and other stuff.

Important Note

I've modified the GitHub repository to generate a new build every update I make to this project.
You can see the bleeding-edge releases here: ThirtyDollarTools GitHub Actions

What's Added? (in plain terms)

  • A higher quality resampler in the Converter. (Bandlimited Resampler)
  • A settings file for the Visualizer.
  • Ability to make the Visualizer's window be transparent. Documented below.
  • Support for using defined events in other #define events. Documented below too.
  • Fixed the scaling on displays bigger and smaller than 1x.
  • Performance improvements. (there can never be too many)

How to use the transparency.

First you need to open the Visualizer's settings file.
image

And edit the TransparentFramebuffer = False line. Set "False" to "True"
image
image

Open the Visualizer. The background won't be transparent unless explicitly being told to be.
image

You'll need to manually edit the !bg (background) events of your sequences so that they contain the transparency information too. Here's an example.

You have this file, which has a single !bg event followed by four pauses.
It looks like this: !bg@#2087ee,0|_pause=4.

When played in the Visualizer it looks like this.
image

Now to add transparency (alpha) to the background you can add two more hex letters after the color, with ranges from 00 (0) to FF (255). 00 is fully transparent and FF is fully opaque. By default all backgrounds have FF values unless manually set.

Let's say that you want the background to be fully transparent.
You can edit the line above to look like this: !bg@#2087ee00,0|_pause=4. The difference is the added 00 after ee.
The color doesn't really matter in this case since it's fully transparent, and even if it's black, it'll still be transparent.

Here's how the Visualizer looks like now.
image
Note: I am using blurring on all transparent windows, on my setup. On your setup you will most likely see it without any background blurring.

You can change the value to something in-between to use to your liking.

Now you can capture the Visualizer's window directly in OBS and put a source below the Visualizer's window and it'll be visible.
image

That's all for this section.

What do you mean defines in defines?

You can now use defined elements in other new defined elements. Note: The defined element used in the new define must be defined first. Otherwise it'll be parsed as a sound.

What's Changed (in GitHub terms)

  • Merge part of the abstracted events to master for the world to see! by @t1stm in #36
  • Rewrote the Audio Casting code. by @t1stm in #37
  • Change the solution's folder structure by @t1stm in #38
  • 1.1.6 Bug Fix and QoL release (miscellaneous stuff) by @t1stm in #41

I've taken a small break developing these tools but fear not, as I will be returning soon to developing them. When I am finished the result will be great. Thanks for reading this and I hope you have a nice day / night.

Full Changelog: v1.1.5...v1.1.6

Contributors

t1stm
Assets 6
Loading
0 Join discussion