If I need to start broadcasting OSC to multiple changing targets I may change my mind but even then I may still only use it as a broadcaster rather than translator. I will second that in my workflow, max/msp is major overkill for the task at hand.
OSCULATOR ABLETON X32 MANUAL
I don't want them to appear every single video change so it will still be a manual call, but the selection, fade up, wait and fade out can all be automated by qlab so that I only need to call that I want it to appear.
OSCULATOR ABLETON X32 SOFTWARE
Also i did buy a few licenses for Qlab and i think financially i would rather buy a new camera then adding software on my bloated mac )Ĭan i ask what you are using for triggering lower thirds?Ĭan you clarify this question? You mean what will cause the 元 to appear? I haven't decided what the final trigger will be but my suspicion is a streamdeck button. Not that i think max8 couldn't do that but for me to switch or maybe learn them both is just to much i think, i'm not sure my knowledge of Qlab wil be surpassed by another program and thats fine for me for now. it has it's shortcomings but you learn to workaround i guess. And the apple-scripting osc audio video combo works great for me. I'm using ableton/ qlab/ jands vista (light) or grand ma2 and the x32 systems from Behringer/midas, and to be honest Qlab is the most useful for me mostly for the incredible fast workflow you can have with it and still be flexible. Yes you could do a lot and you can make a lot of custom things for your self, but it takes too much time for me to learn it and make everything i need. I have used Max 8 for a performance but to be honest it's a little bit too much hassle for me. Not only amazing but also fast work! Only here a few days but great response from !! This made me love my Atem a lot more. To be honest knowing this is working for me really made my week! I think it's just a matter of translating the right info from AtemOSC to your desired tally system right? It just makes it pretty easy to reroute osc to desired output. Of course you don't necessarily need osculator if your software can listen/learn osc commands (like qlab).
Maybe this could be made easier from within AtemOSC.) The disadvantage would be that you should make a start-up routine where al sources from USK/DSK & Pip would be reloaded for correct feedback on start but i could live with that. (In my case i would store changed-states of fill and key sources trough osculator and mark them tallied when ever the USK/DSK switches On-Air. So knowing this maybe it shouldn't be to difficult to make this possible. It also gives feedback on USK/DSK On-air status: 1 or 0, sadly not which source is used in it but if you change the source it wil give osc feedback which source is selected. So in qlab it launches cue: "preview number 3". So what i did in osculator is if preview "#" is higher than 0.5 send OSC > qlab cue "#" This is what AtemOSC sends back on a preview change (previewed camera 3): This works identical as the pgm program selection. With the help from osculator i managed to read and reroute the feedback OSC.
I was thinking, I need this!! Why isn't this implemented?!?!īut this is actually already implemented into AtemOSC how i see now! After reading this and #159 my mind was going to a feedback system for qlab cues/ obs scene's following selected camera (for different overlays per camera, or even different on-pc green screen background angels per camera) and also x32 switching audio scenes / mics
0 kommentar(er)
