Hi all,

what I will describe is happening in vMix 26.0.0, so please let me know if this no longer happening.
We are experiencing this in a "real" project, but I'll give a simple example.

Input 1: Slideshow
Input 2: Photo patched to External 2 SDI output. This can only be done with a pulldown menu showing the input NUMBERS, no name, no key (Input 2 -> External 2).

Whenever we trigger a refresh of the pictures in the slideshow, Input 1 DISAPPEARS for a split second.
Input 2 becomes Input 1 (because the slideshow disappeared), does no longer go to External 2 as it is no longer Input 2, and our SDI
output goes black. After the split second the refreshed slideshow input re-appears, takes its place as Input 1, the photo becomes
Input 2 again and re-appears on the SDI output. So with every slideshow refresh we are getting a dropout.

You can avoid this by making the slideshow the last input as only inputs behind the slideshow are affected,
but what the heck?! I would even expect the output of the slideshow staying available during refresh, but the
whole input DISAPPEARING because of a simple folder sync?!

What's your experience with this?

No, sorry, I mean what is also referred to as "Photos" input. In the settings it's all about 'Slideshow' then.
https://www.vmix.com/help24/index.htm?Photos.html

The described behaviour occurs when you right-click and select 'refresh photos' on the input.
Same when you trigger this via html.

It's not your fault, but seriously:
What kind of limiting and dangerous design is this on a broadcast software?
The input itself drops out and causes other inputs to loose their number and even assigned output?
And all this for a quick "what's new?" folder sync?

Why is this while on the other hand a list input is super tolerant.
You can add, move, remove, shuffle its files manually or from outside and it just keeps outputting.
It can even be auto-updated from outside with a little watchfolder tool.
Unfortunately it causes other major problems when stepping through its files.
https://forums.vmix.com/posts/t32293-Renderer-drops-caused-by-API---list

Hi Martin,

thanks for your reply and your suggestions.



TBH, when a function is available during production, I would expect it to work without causing negative side effects, especially on other inputs.



Maybe I'm naive, but...why?
This feels like I'm hitting F5 in Chrome and the browser is closing and re-opening just to update the page.



Yes, and I was wondering why the list can handle all kinds of changes without those side effects.
While it is much more flexible, other things are missing for me:
- There is no refresh functionality I can trigger via html
- It doesn't offer a slideshow function (and no transitions)
- Loop does not work on pictures
- It causes dropouts
Thanks for your response on this issue, I'll look into it, although reformatting incoming pictures would be additional hassle while Photos input
handles THIS part without problems.



I think you misunderstood me here.
While I was worrying why the Photos input had to completely disappear during refresh, the problem was not a different input taking the place of the Photos input
and maybe causing unwanted output. We can update the slideshow when it is not on air.
The problem is that a completely different input (for example #22) looses its output routing 'Input 22 -> External 2' when the slideshow is refreshed, because it becomes input 21 for a moment.
And THIS one is constantly on air.

I'm a bit puzzled as what I thought would be an super easy task caused so many unexpected problems including the workaround List causing
problems and neither Photos nor List delivering what I need - a (auto)updatable slideshow that does not cause negative side effects.


Rick

Yes, that's what we've done for now - we put the Photos input to the very end.
But as soon as we have two Photos inputs, refreshing one will impact the one behind.
Not our actual use case, just saying that this still feels like a problematic behaviour.

Anyway, thanks for your input!
I will further investigate our List problems as I would prefer to use a List.