Move

Move 3.2.0

Download
Overview Updates (105) Reviews (124) History Discussion
Just realized thats an old report from around last time I posted, apologies... Its not logging a report now, but its likely adv-ss crashing, I just thought the log was pointing to move, I usually work on this late, so I blame lack of sleep for missing the log date. Sorry.
 
I found a quirk where adding Two Move filters to a text object for animating the opacity in a scene was adding 2-3ms to my Frame Rendering time, and having this same effect done in 3 different scenes was causing my Render time to stick around 15-20ms causing lost frames sporadically.

Was a bit hell to nail down the issue to the Move Plugin, but I did eventually.
I figure I can reduce the total load by combining the Text sources into one and just changing the displayed text in the different scenes, but even with 1 source, 2-3ms of render feels expensive for a simple opacity shift, but let me know if I'm wrong thinking that.

Does this seem correct, or maybe there's a better way for going about this effect? Or maybe there's something else I'm missing.

Still very much appreciate the plugin and all the other work you do @Exeldro ! Thanks!
 
@MikeDeM the OBS text source has relative high rendering time on changes, that is not something the move plugin can change. Ways to make the OBS text source more efficient is using a smaller font, so don't take a 256 font and scale it down, but take a 16 font without scaling for example.
 
Exeldro said:
@MikeDeM the OBS text source has relative high rendering time on changes, that is not something the move plugin can change. Ways to make the OBS text source more efficient is using a smaller font, so don't take a 256 font and scale it down, but take a 16 font without scaling for example.
Click to expand...
Ah, copy! I'll try that. You called it perfect; the font I'm using is 275, so that could be a big factor and even just taking it down to 75 seems to make a significant difference. Thanks for the response!
 
For some reason when my sources move between scenes, they do it just fine, but they come in from a scene that didn't have them on before, they come in flickering. This didn't happen before and I'm on latest version to date. Happens on browsers, display captures, clones, everything.
 
This is more of a combined issue for Move and Soure Copy. I use the Source Copy "add_scene" vendor request to add a scene with a bunch of Move Value filters.

It used to work just fine and I managed to track it down to Move update 3.0.0. Not happening with the versions before that.

Essentially I am only changing the y position of the filters for the sources. Every source (1-5) has each position value once (y835, 650, 465, 280, 95, 1080). What happens now is that it doesn't apply those settings correctly, I attached a few screenshot for that. So Source1 (Bar1) is supposed to have one filter for y835, one for y650 and so on. Same for all other sources.

Since 3.0.0 however source 1 gets y835 for all filters, source 2 gets y635 for all of theirs etc. pp. The effect is also attached as gifs, how it looks like before 3.0.0 and after.

Also: if I import the scene from its json-file, it appears to work just fine. All settings are correct there. So I checked the "get_current_scene" response and it lists the settings there correctly as well (that's what I use for the add_scene request). Not only the transform_text but also the actual pos y value. The gif is also attached since I can't post large excerpts here.

I also re-adjusted the settings, refreshed "Get Values" for every single filter, with no success.


If you need more info or a better overview, please let me know.
 

Attachments

  • 1.png
    1.png
    138.4 KB · Views: 60
  • 2.png
    2.png
    144.4 KB · Views: 60
  • get_current_scene.gif
    get_current_scene.gif
    825.9 KB · Views: 79
  • before move 3.0.0.gif
    before move 3.0.0.gif
    734.8 KB · Views: 192
  • after move 3.0.0.gif
    after move 3.0.0.gif
    488.3 KB · Views: 156
For some reason the Move Value filter stops working when you close and start up OBS again
As in the filter isn't seen in the hotkey settings and manually triggering them in the filter settings doesn't work
You have to delete the old Move Value filters and make new ones every time you restart OBS
This is happening with 3.0.1
I went back to 2.9.7 because I used that version before where the problem didn't exist
 
I have an issue with Audio Move, I might just be being stupid but no matter what I try I can't see any of the Filters or Settings.
1719965013465.png
 
I'm sorry if this is a very basic question, but can the move plugin do this?

What I want to do is 'save' the position of a specified set of sources within a given scene, such that with a single hotkey press etc. while in that scene, all of those selected sources will move to those 'saved' positions. Essentially, I'd like to be able to 'save' the position of my webcam/chat overlay/etc. after I find good places for them to be when streaming a given game, so that if I stream other games and then come back to it, I don't have to 'find' those optimal spots all over again.

I'm trying to avoid having one scene for every single game I stream...as a variety streamer, that would get very chaotic very quickly...thanks in advance for any help! :)
 
So we're aware, the macOS pkg files, for all of the above arm64, Universal, and x86 versions, fail to install via the UI installer on my macOS Sonoma 14.5. I personally unable to find any way to get the proper libobs headers on my system, either, which means I can't build the plugin from source; something I've seen other plugins meet a similar fate with. I was however able to install it fine with sudo installer, so that might be something to keep in mind.
 
Hai all, I have an issue not sure if it's the plugin or my OBS version?
I recently reinstalled the plugin, using the latest version and OBS version 30.1.2
The plug in is lagging obs and dropping frames. It also flashes while the transition is in effect
I put a video on Twitter to demonstrate:

x.com

x.com x.com
 
xTerrene said:
So we're aware, the macOS pkg files, for all of the above arm64, Universal, and x86 versions, fail to install via the UI installer on my macOS Sonoma 14.5. I personally unable to find any way to get the proper libobs headers on my system, either, which means I can't build the plugin from source; something I've seen other plugins meet a similar fate with. I was however able to install it fine with sudo installer, so that might be something to keep in mind.
Click to expand...
Update; Turns out the installer package did NOT actually install it.
 
Exeldro said:
@Salberry it looks to me not all sources flashing. Is it only for a specific type of source or only for appearing or disappearing sources?
Click to expand...
It's wierd, some flash some times and then not other times, but all of them seem to flash in some capacity when appearing on screen for the 1st time. Haven't noticed flashing when they move off screen.
Aaaand after looking at the settings, I changed in the "appearing items" in the Transition drop down to None, it was previously also on Move, I think this is what was causing the issue.
 
egnever said:
Maybe something changed, but the setup I had before the last two updates is not working fully anymore. I use move value up and move value down for two audio sources to fade audio in and out. It moves the audio up and down for my music source but not my gameplay one. I have tried it a few times and it seems like nothing is fixing it. Been working for over a year like this and it just stopped.
Click to expand...
I am having the same issue, for almost 4 weeks, the move filters are just fully enabled, and do not turn off (get disabled) once the move value is completed.

I use Move Value - Source Volume on my audio sources in the audio mixer. Using Stream deck, I was normally able to do multiactions, change scener, fade music down, and fade mic up. The same in reverse when I switched to an scene like BRB or Ending Stream.

The current workaround is to manually go into the filter, change the "Source Volume" Setting to "None" and then back to "Source Volume".
Unfortunately, this bug makes the value default to something entirely different from what I had, so I have to set it again manually.
I've had to do this every time I start OBS.

I have tried renaming the filter. Removing it and creating it from scratch. Reconnecting my stream deck (removing and adding the stream deck plugin). Removing plugin and installing again. Issue comes back as soon as I close and start OBS again.

Got a Video of what I have to do to get it back to work, if anyone is interested.
 
You must log in or register to reply here.
Back
Top