Update 2025-04-05 (v13.6)


Hey everyone! I finally had time to sit down and actually add some new features I've been wanting to do. All it took was streaming it to keep me focused :D (You can watch that here: https://www.twitch.tv/videos/2424601074)

Changes:

  • Added LAYER CLIPPING! (properly this time!)
    • You can find the "Clip Layer" setting under the new "Compositing..." header in each layer's menu. "Scale Filter" and "Blend Mode" have also moved there.
    • Any layer can be the clip for any other layer (unless it's the same layer - can't clip yourself, silly). Folders aren't an option yet, but might be in the future.
    • The clip layer doesn't need to be visible to have an effect.
  • Renamed "Global Settings" to "Canvas Settings" and added presets
    • You can now add, edit and save these presets to easily switch between different sizes/rotations/positions for your canvas.
    • The presets are stored in your Layer Set - so if you don't save your layer set, the presets won't be saved either!
    • The active preset will be saved as "default" when you save your Layer Set, so each time you reload it you'll get that one on startup.
  • Made the highlighting optional when showing Layer Bounds.
    • Previously, when hovering over a layer's menu, the layer bound rectangle would get shaded with the UI theme colour.
    • I saw that some people didn't like this, so it's now turned off by default, but can be re-enabled in the advanced menu.
  • Set the default FPS limit to 60, and turned off VSync by default
    • VSync can cause some NVidia GPUs to eat a lot more resources than necessary. Since most people will likely be capturing their avatar at 60fps, I thought that made sense as the default.
    • This won't affect your existing settings if you've saved them, only new users.
  • Linux only: Re-enabled the Transparency option in the Advanced menu
    • This will still not make the window itself transparent, but it should appear transparent when captured through obs-vkcapture.

Thanks for using RahiTuber!


Edit - v13.611

  • Fixed an issue that incorrectly ignored the "scaleFilter" setting because it was expecting the wrong type

Edit - v13.62:

  • Fixed an issue where "Clip to Backdrop" would not actually clip any more due to new rendering changes
  • Added a "Premultiply Alpha" option to the advanced menu to allow more freedom with how your output blends to whatever you're using behind it

Edit - v13.621: 

  • Fixed an issue brought about by v13.62 which made the application background color additive to the windows behind it in some situations 🥴

Apologies if anyone got email spam from all these updates. I think that's the last one!  

Edit - v13.622:

  • Fixed an issue that would cause a crash if a clipped layer is duplicated or moved.

Apologies if anyone got email spam from all these updates. I think that's the last one! 

Files

rahituber-win.zip 2.6 MB
Version 13.622 10 hours ago
rahituber-linux-beta-x64.zip 2.3 MB
Version 13.622 10 hours ago

Get RahiTuber

Download NowName your own price

Comments

Log in with itch.io to leave a comment.

(+1)

Phenomenal update, love to see it!

(+1)

I found a bug again! (Why do I always break things? lol)

The software crashes if a layer that is clipped inside another is duplicated or re-arranged in the list.

(1 edit) (+1)

It's not you breaking things, trust me, I really need to write some extensive automated tests for this program and I'm paying the consequences 😅

Thanks for letting me know.  Just uploading a fix now!

Edit - Fixed in 13.622!

(3 edits) (+1)

Awesome!!!

PSA: Since the Scale Filter variable has changed from Boolean (true or false) to binary, those that used it before will find it defaults to "Nearest pixel" in this version. A workaround if you need to restore many layers is to edit your .xml file (must NOT have been saved with this version) with a text editor and replace :

Replace:With:
scaleFilter="false"
scaleFilter="1"
scaleFilter="true"scaleFilter="0"

^Fixed

(+1)

Oh no! That's entirely my fault with the settings loading. I'll fix that asap!

(+1)

With version 13.611 it should not have this issue any more (and hopefully still work if you'd saved it with the new numbers instead of booleans)

By the way - either "false" or "true" would have resulted in the program reading "0" because it was (incorrectly) expecting an integer value in the XML, not a boolean. So, scaleFilter=1 should have meant true and 0 should mean false.

Doesn't matter any more since the xml should now be back to saying "true" or "false" as intended!