Resolume Forum

Hello Bart and Edwin,

I have experienced some strange behavior and a application crash/hang when using the Forward / Backward / Pause-Play / Random buttons in the Transport controls when using keyboard mapped buttons.

It maybe related or similar to this issues but had different experiences so I though I would post a new topic.
http://www.resolume.com/forum/viewtopic ... =transport

I'm getting different behavior for mapped keyboard keys when clips have audio or are using a different playback modes (BPM sync vs. timeline).

After I map the arrow keys to the Transport controls (forward, reverse etc...) using the "application key map" using layer focus I have the following results.

a video clip with no audio in timeline mode has fully functioning forward and reverse play controls using the keyboard. When that clip is switched to BPM sync mode the mapped keys no longer work. however I can still click the buttons with the mouse and have an effect.

Funny enough a different video clip with audio embedded, will respond to the mapped keyboard keys in both Timeline and BPM sync mode.

Also when I click the mapped key for "Random" that is not available for clips with audio the application will hang. I get the pinwheel of death and can't click on anything with my mouse. However the application is still running and can respond to midi and keyboard commands for instance I can change clip opacity with a slider, but with midi only.

I am using a MBP with OS X 10.5 running Resolume 3.0.1 rev 1500

It would be great if anyone else can test this, to see if they can replicate the bug.


p.s. Also just a side questions. Why is it that only clips with audio can use the beat loopr? Its a great way to mess with the video in general. I have many of my non-audio video clips running in BMP sync mode and love to cut them up even if the audio is not an element. I guess I could get the beat loopr by adding a silent audio track to the clilp, but that seems silly. that would also solve my keyboard mapping issues since clips with audio respond to the keyboard mapping in BMP sync mode.

We found the "Random" bug as well and that has been fixed.
We will have a better look at the mapping and see why the keys don't work anymore when switched to Sync mode.

A video beatloopr is in the making and will be in the next release.

Just wanted to follow up and see if anyone has tested this or is also have this problem. I'm surprised it has not come up before it seems like it would affect most people using R3. Unless I'm the only one with this freak issue.

Let me try to sum it up in a different way.

I have midi mapped the transport controls. application layer mapping .

Clip with no audio in timeline mode = tranport controls work via midi keys
Turn that clip to BMP mode = transport controls no longer respond to midi mapped keys
Add audio to same clip in BMP mode = transport controls start to work again with mapped keys

It would be great if someone could give this a try see if they have the same result. The issue is driving me crazy.

gradek wrote:Clip with no audio in timeline mode = tranport controls work via midi keys
Turn that clip to BMP mode = transport controls no longer respond to midi mapped keys
Add audio to same clip in BMP mode = transport controls start to work again with mapped keys

Confirmed, listed as todo.

Thanks Bart.

Oh, cool, glad this is on the radar. I noticed that OSC mapping behaves differently too, if there is audio on a clip all the transport controls have to be mapped to the layer/clip/audio path, not the layer/clip/video path.

I,m glad to inform you that this is fixed and will be available in version 3.0.2.

Very Cool Bart, Any hint as to when we might expect 3.0.2?

Thanks Bart, Tested and working good in 3.1
OSC is hurting my brain though.
http://www.resolume.com/forum/viewtopic ... 385#p22385