[bug] OSC issues with audio and video

[gpvillamil]

Just a couple of quick ones:

When sending the direction to a clip, it seems that 3 = pause and 2 = random. Just a matter of updating the manual, I guess.

Another more bothersome issue:

When a clip has audio in it, it disregards any OSC messages sent to /layer/clip/video. I am writing a Max patch to remotely set playback modes, and of course I can't tell if a clip has audio in it.

Should I send all commands to /layer/clip/video AND /layer/clip/audio?

[glasshopper]

Looking inside a midi xml file - that is exactly how it works - but until we get an update it must be to a specific clip... layer[x]/active clip/ would be so so nice ... but as yet is not implemented.

[gradek]

This is very interesting that clips with audio are behaving differently then clips without audio. I have a feeling Resolume treats them differently some how. I have been having issues with midi and keyboard mapping the transport controls depending on if the clips has audio or not.

I talked about it here:
http://www.resolume.com/forum/viewtopic.php?f=13&t=4970

Just yesterday, I had the strange thing happen. I had mapped a slider to the playhead in the transport controls using composition mapping. At first it didn't seem to work, but upon more experimenting, I was able to scratch videos with audio, but not clips without audio.... ugh. so I deleted the mapping, and tried again this time on a clip without audio. after that it worked regardless if audio was present or not. This is the reverse problem I had before with the forward and backward controls in my other post.

[gradek]

It appears that 3.1 still has the same issue with OSC. The good news is that the issue with midi/keyboard mapping has been fixed. Transport controls, playhead, direction etc are all controllable by midi no matter if there is audio or not, or if the clips is in BPM or timeline mode. (discussed here: http://www.resolume.com/forum/viewtopic.php?f=13&t=4970 )

However the problem with OSC is frustrating. The beatloopr, playhead, and directional controls are no logner responsive as soon as a clip has audio.

The new /activelayer/ and /activeclip/ OSC commands are nice. but...

Its a bit strange that some commands (direction, beatloop, playmode) I have to send to the new /activeclip/ function, while others I have to send to the /activelayer/ function. This is odd because if I preview a new clip it becomes the activeclip, and I am no longer controlling the directional controls of the clip running in the active layer, instead the newly preview clip. Since all layers have direction controls, I'm not sure why I can't send a message to /activelayer/video/position/direction/ ???

Funny thing happened, I was able to stop a clips video track from playing yet the audio was still playing forward by sending a command /activeclip/video/position/direction 3 if I want to also pause the audio I have to use the /activeclip/audio/ prefix. /audio/direction commands affected both the video and audio, but /video/direction commands just affected the video layer independent of the audio. hehe

Bart, Edwin, Is there anyway in the future to allow video clips with audio or just audio clips to also respond to /activeclip/video/ OSC commands?

[edwin]

Bart, Edwin, Is there anyway in the future to allow video clips with audio or just audio clips to also respond to /activeclip/video/ OSC commands?

Audio and Video clips can be controlled independent of eachother, this is good for future features when someone might want to have a audio and video sample combined but not linked. Aka both clips will be played but video is not linked to audio. Or that a video is played backwards while audio is playing forwards....well you could probably think of some other things you might want to do.

Now the appliction sets the correct values but when you start using OSC you can actually override the behaviour of the application. You could probably set the video running backwards while the audio is playing forwards using OSC.
So maybe in the future we should have something like /activeclip/position/direction instead of /activeclip/video/position/direction or /activeclip/audio/position/direction.

[gpvillamil]

In general, I find that always sending the OSC command to both /layer/clip/video/position and /layer/clip/audio/position works OK, ie. just send exactly the same command to both addresses every time.

[phreakhead]

So I have this same issue with Arena 4 and TouchOSC:

Scrubbing back and forth with /activeclip/video/position on a clip that has an audio track is very jumpy and not nearly as smooth as a clip without audio. It seems that you send the new position to a clip that has audio, it will jump back to the previous position as soon as the message is done, making it impossible to "scratch" videos or jump to new positions.

One workaround for this is to pause the audio while scrubbing, then unpause as soon as you are done. However this is not ideal.

Another workaround is to send BOTH /activeclip/video/position AND /activeclip/audio/position messages at the same time, however not all OSC interfaces (e.g. TouchOSC) allow for sending multiple message from a single input.

Proposed solution: there should be some more universal "position" message that will control a clip no matter if it has audio or video - whichever one is there. Ideally, this would mean just fixing the /activeclip/audio/position and /activeclip/audio/direction messages to work with video if there is no audio track, so everything is standarized. This would really help me out a lot! Thanks!

[Joris]

Whenever a clip has audio attached to it, audio will become the master for the timing and playback of the clip. Any message sent to /video/ will be overruled again by the audio once you stop sending the message (as you've found out).

It's unfortunate that we distinguish between messages for video and audio, and that TouchOSC does not support multiple messages. But I'm afraid that's how it has to be for the time being.

[Rene]

It's unfortunate that we distinguish between messages for video and audio, ...

+1

What about "activeclip/videoandaudio/position" ?