Something I did back in the R5 days was always have a input layer for capture and then a second layer with layer routers referencing that camera layer. When triggering different effects and looks i'd trigger different layer routers.
I did this because I would have crashes making multiple inputs with different effects(Same source clip just copied over and over). We've come a long ways since then and I wonder if this safety layer is really required anymore.
If one of the resolume team wouldn't mind going into how inputs are handled in the back end and the best practice from treating said inputs, it might be a useful thing. I'm getting alot of questions about this recently and realize I've been doing it in a potentially outdated method.
Proper Input Treating
Re: Proper Input Treating
The capture inputs are opened only once.
This is why every capture clip that uses a given device needs to use the same input settings.
This has been the case in R5 and 4 too, and hasn't changed in R6.
I can't think of a reason why having these capture clips with different effect chains would cause any issues like you describe.
This is why every capture clip that uses a given device needs to use the same input settings.
This has been the case in R5 and 4 too, and hasn't changed in R6.
I can't think of a reason why having these capture clips with different effect chains would cause any issues like you describe.
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Re: Proper Input Treating
Just was a consistent series of crashes back in the early R5 day when cycling through blackmagic inputs with different effects. I'd use a layer router and the crashes would stop. It may of only been a particular release but i just made that a habit, and never really tested again.Zoltán wrote: Mon Jul 02, 2018 22:49 The capture inputs are opened only once.
This is why every capture clip that uses a given device needs to use the same input settings.
This has been the case in R5 and 4 too, and hasn't changed in R6.
I can't think of a reason why having these capture clips with different effect chains would cause any issues like you describe.
But i was really doubting the need for said habit the other day so thats kinda why i decided to make this post. Mainly sto
A. To confirm what i kinda suspected, ie. unnecessary.
B. For people asking me the same question to have a more official answer on the forums.
Re: Proper Input Treating
One reason could be mismatching capture settings between clips. When changing the port or resolution, the connection to the card has to be closed and re-opened, which is a pretty heavy task. Especially when you have multiple capture clips telling the card conflicting information, it could cause instability.I can't think of a reason why having these capture clips with different effect chains would cause any issues like you describe.
I'm not saying that you can always expect a crash. But it is a behaviour that would be avoided by using a single instance and multiple routers.
Re: Proper Input Treating
It’s likely I messed up something along those lines in this situation, I tend to evolve show files over time. Which also means small mistakes can be kept in after too many gig refreshments.
It sounds like if your looking for the best performance a single layer of captures(with copied settings) is the most efficient.
Buuuut if a user is a novice and may deal with different resolutions between shows having a capture source with a layer router(maybe in a dedicated group?) above could in small cases be safer. But that’s more for very green users.
This is great, I didn’t know about the settings, so that’s a big bit of info for me personally.
It sounds like if your looking for the best performance a single layer of captures(with copied settings) is the most efficient.
Buuuut if a user is a novice and may deal with different resolutions between shows having a capture source with a layer router(maybe in a dedicated group?) above could in small cases be safer. But that’s more for very green users.
This is great, I didn’t know about the settings, so that’s a big bit of info for me personally.