6.0.9 issues

[daan.hzndnk]

Hi all,

First thank you so much for this update & the amazing Adobe exporter.
It works great.
Currently I'm working on a big theater production and the last 3 days (?) I've tested the new update quite intense. This are the bugs I've encountered. Right now I'm switching back to 6.0.6 so I won't be able to investigate it any further because I need these funtions to work properly.

1) as I mentioned in another post: OSC aboslute values are not working but 0 and 1.
So /positionx a 2 won't move it 2 pixels. Only 0 and 1 are working.

2) I just added the trails effect to a few clips who had some effects (tint, hue, levels) applied to it, and it only did want to work when it was set above the Transform effect, otherwise it just didn't work. I do not have time to nail this one down to the very core, hopefully others will.

3) I added a .mov with just 1 frame of ProRes422lt and this crashed the application. Didn't tested it twice, it could be a render mistake. Sorry no time to investigate this one further I'm on a extreme tight schedule.

4) !!! After some hours of programming I couln't trigger certain clips over OSC by using /connect 1 (either a column or clip). In the OSC monitor I did saw the message arriving(!!). After restarting Resolume the cues DID fire again. Only a few (or just one) clip was not able to fire over OSC, the others were still working. It might have something to do with the way we are replacing clips: we do it the dirty way: using chronosync we just overwrite files, then I switch decks, so Resolume loads the new files. Is it possible this breaks OSC cuing? I'm sorry but this one too: I do not have time to investigate any further and I'm downgrading to 6.0.6 from now.

5) LOW PRIO: the OSC monitor does not have sufficient space to show a whole incoming message (eg: /composition/layers/11/clips/5/video/effects/transform/positionx a 500
-> I can't see the ending of the message, and I can't see the actual float or int (or only just the first digit) because of the "a" string. It would be great if this one got a bit more space to nail down problems more quickly.

Working on OSX Mac Pro 10.13.5

Best, Daan
ps. I'm working on the "Pauperparadijs" theatershow in Carré Amsterdam, is going to be a great show

[Zoltán]

Thanks for these!

1) as I mentioned in another post: OSC aboslute values are not working but 0 and 1.
So /positionx a 2 won't move it 2 pixels. Only 0 and 1 are working.

Indeed it's broken, ticket created.

2) I just added the trails effect to a few clips who had some effects (tint, hue, levels) applied to it, and it only did want to work when it was set above the Transform effect, otherwise it just didn't work. I do not have time to nail this one down to the very core, hopefully others will.

I couldn't recreate this one yet, any pointers would be welcome.

3) I added a .mov with just 1 frame of ProRes422lt and this crashed the application. Didn't tested it twice, it could be a render mistake. Sorry no time to investigate this one further I'm on a extreme tight schedule.

We'd love to get our hands on this file

4) !!! After some hours of programming I couln't trigger certain clips over OSC by using /connect 1 (either a column or clip). In the OSC monitor I did saw the message arriving(!!).....
It might have something to do with the way we are replacing clips: we do it the dirty way: using chronosync we just overwrite files, then I switch decks, so Resolume loads the new files. Is it possible this breaks OSC cuing?

Hard to say, could break the clip's playback possibly.
If other clips still launched and the ones that were replaced did not, then that could be indeed the cause for this.

5) LOW PRIO: the OSC monitor does not have sufficient space to show a whole incoming message (eg: /composition/layers/11/clips/5/video/effects/transform/positionx a 500
-> I can't see the ending of the message, and I can't see the actual float or int (or only just the first digit) because of the "a" string. It would be great if this one got a bit more space to nail down problems more quickly.

Indeed it would be great to be able to resize the message inspector.