Transition Table

Transition Table 0.3.1

Download
Overview Updates (13) Reviews (38) History Discussion
Sorry, my mistake, everything is fine.
Don't know what happened but the old 0.2.6 installer must have been renamed 0.2.7 by mistake, instead of being overwritten by the new installer, I guess. So I had a file named 0.2.7 that was in fact a 0.2.6.
 
Hey i am on linux mint and trying to install the pluggin. When i was on windows it was working fine, but i cant seem to be able to install it now on linux. When i extract the files in the obs plugin_config folders, it does nothing. Any suggestions on how i can make it work?
 
Hello. Is there a way to write a RegEx, to target "all scenes starting by" in the "From" input, and the same for the "To" input ?
 
Exeldro said:
Exeldro updated Transition Table with a new update entry:

Version 0.3.0



Read the rest of this update entry...
Click to expand...
Hi @Exeldro ,

I use your plugins and greatly admire your work, congratulations!!!

I installed version 0.3.0 of the Transition Table plugin over version 0.2.7 on my Linux Mint 22.2 XFCE with OBS Studio 32.0.4 with a previously existing collection of scenes and transitions already defined in the Transition Table, and I experienced freezing when trying to switch scenes with a double-click in studio mode. I was using StreamUp Scene Organizer to manage the scenes. I reverted to version 0.2.7 and everything started working again. Thank you in advance.
 
Exeldro said:
Exeldro updated Transition Table with a new update entry:

Version 0.3.0



Read the rest of this update entry...
Click to expand...
FabioElizeu said:
Hi @Exeldro ,

I use your plugins and greatly admire your work, congratulations!!!

I installed version 0.3.0 of the Transition Table plugin over version 0.2.7 on my Linux Mint 22.2 XFCE with OBS Studio 32.0.4 with a previously existing collection of scenes and transitions already defined in the Transition Table, and I experienced freezing when trying to switch scenes with a double-click in studio mode. I was using StreamUp Scene Organizer to manage the scenes. I reverted to version 0.2.7 and everything started working again. Thank you in advance.
Click to expand...
Hey @Exeldro,

First, love your plugins, mate. Having the same issue as @FabioElizeu (though I'm on Windows), namely OBS is freezing when I trigger scene changes after updating to v0.3.0. There are no crash logs to share because OBS freezes (doesn't crash), but I noticed the following recurring entries in the "regular" OBS logs near or during scene changes that cause the freezing:

Code: 
Attempted to add Scene without specifying a canvas! Using default canvas instead.
Code: 
[obs-websocket 4.9.1-compat] GetTransitionData: duration is negative !

Not sure if either of these are relevant. Let me know if you want me to share the entire log file.
 
Hi, I just did a bunch of updates, and I've got an issue with the Transition Table. Previously the Scenes were all showing up in the drop menus in the order that they appeared in my Scenes dock, now they are seemingly random. Not only that, but there are also sources displaying in the drop menu, not just scenes.

I've tried uninstalling and reinstalling, and that hasn't fixed anything.

Has anyone encountered this before?
 
A heads-up, OBS Studio 32.1.0 + Aitum Stream Suite breakds Transition Table. It's also worth noting that any transitions defined by Advanced Scene Switcher are also affected. I was talking with one of the helpers on Aitum's Discord server; they say that it might have to do with OBS Studio 32.1.0's baked-in multiple canvas support. That support might have to do with this, apparently since neither plugin appears to be aware of multiple OBS Studio-handled canvases. I've already given Warmuptill a heads-up on this matter for stuff related to Advanced Scene Switcher. Until any solutions are offered, I'm keeping all my plugins updated but I'm not upgrading OBS Studio beyond 32.0.4.

--Katt. =^.^=
 
I’m seeing a bug. (Using Transition Table 0.3.1 on OBS 32.1.1 for Silicon Mac). If you exit a scene before the transition is done playing, you get stuck in the scene you exited from prematurely. In the Scenes panel, it highlights the correct scene, but it continues to display the scene you exited early. If you switch back and forth between those two scenes (the one you exited from and the one you exited to) it continues to display the scene you left prematurely. You must enter a third scene to escape this.

I asked Claude to analyze what might be causing the bug. It said this…
I see the issue. Look at lines 107-116:
Code: 
  obs_source_t *scene = obs_canvas_get_channel(canvas, 0);
  if (scene && obs_source_get_type(scene) == OBS_SOURCE_TYPE_TRANSITION) {
      obs_source_release(scene);
      scene = obs_transition_get_active_source(scene);                                                                                                                                             
  }

The bug: On line 109, scene is released, then on line 110, the released pointer is used to call obs_transition_get_active_source(scene). This is a use-after-release — the reference is dropped before it's used.

During a transition, obs_transition_get_active_source returns the scene being transitioned TO. But when you switch scenes mid-stinger, the transition's "active source" might still be the previous target, not the new one. Combined with the use-after-release, this could return stale data.

But more importantly, line 176-182 shows that transition_start calls set_transition_overrides which reads the "from" scene using obs_transition_get_active_source. During a mid-transition switch, this returns the WRONG "from" scene (the one being transitioned to, not the one you're currently on), causing the override table to set the wrong transition for the next switch.

The fix would be: After obs_source_release(scene) on line 109, the released reference shouldn't be used. And during mid-transition, the "from" scene detection needs to account for transitions that haven't completed.

However, this is a tricky fix that could break other things. The safest approach: report this specific finding (use-after-release on line 109-110, and stale "from" scene during mid-transition) to Exeldro on GitHub. He'd know the intended behavior and the safest fix.
 
rusty1 said:
I’m seeing a bug. (Using Transition Table 0.3.1 on OBS 32.1.1 for Silicon Mac). If you exit a scene before the transition is done playing, you get stuck in the scene you exited from prematurely. In the Scenes panel, it highlights the correct scene, but it continues to display the scene you exited early. If you switch back and forth between those two scenes (the one you exited from and the one you exited to) it continues to display the scene you left prematurely. You must enter a third scene to escape this.

I asked Claude to analyze what might be causing the bug. It said this…
I see the issue. Look at lines 107-116:
Code: 
  obs_source_t *scene = obs_canvas_get_channel(canvas, 0);
  if (scene && obs_source_get_type(scene) == OBS_SOURCE_TYPE_TRANSITION) {
      obs_source_release(scene);
      scene = obs_transition_get_active_source(scene);                                                                                                                                            
  }

The bug: On line 109, scene is released, then on line 110, the released pointer is used to call obs_transition_get_active_source(scene). This is a use-after-release — the reference is dropped before it's used.

During a transition, obs_transition_get_active_source returns the scene being transitioned TO. But when you switch scenes mid-stinger, the transition's "active source" might still be the previous target, not the new one. Combined with the use-after-release, this could return stale data.

But more importantly, line 176-182 shows that transition_start calls set_transition_overrides which reads the "from" scene using obs_transition_get_active_source. During a mid-transition switch, this returns the WRONG "from" scene (the one being transitioned to, not the one you're currently on), causing the override table to set the wrong transition for the next switch.

The fix would be: After obs_source_release(scene) on line 109, the released reference shouldn't be used. And during mid-transition, the "from" scene detection needs to account for transitions that haven't completed.

However, this is a tricky fix that could break other things. The safest approach: report this specific finding (use-after-release on line 109-110, and stale "from" scene during mid-transition) to Exeldro on GitHub. He'd know the intended behavior and the safest fix.
Click to expand...
Never mind. This was an OBS bug, probably having to do with Fixed scene list selection lag. It is now fixed with the recent update to 32.1.2.
 
You must log in or register to reply here.
Back
Top