m4l initialisation based on hidden status

Sep 17, 2013 at 7:20pm

m4l initialisation based on hidden status


Im using 4 potentially hidden menus in a m4l device. However, they’re all banging out a message when resuming from a saved live set. Do I have to create an initialisation routine based on what is hidden and what isnt? If so, is there any good way to do that?

Sep 18, 2013 at 2:19am

I don’t think that hidden objects behave differently regarding initialization. They are just not visible. So to prevent initialization messages from hidden objects you may need for example an output gate.

Sep 18, 2013 at 5:28pm

Thanks Broc, I’m starting to realise that gates are an essential part of initialisation :) Thanks to this I solved the problem, but it’s truly painful hunting down this stuff in a large patch :/


You must be logged in to reply to this topic.