ProppFrexx ONAIR User-Forum

Yes and you can change that to the last second. And yes you can also change the StartType to Manual up to the last second on the fly. That is what I am trying to say ;-) Just allow it in the overlay options that is all (since others do not want to allow these changes by default). However, if allowed...

I looked at it a bit closer... Actually the current scale is a logarithmic dB FS scale! The only difference is that I display possible values above 0 dBFS. And this because internally I process everything in 32bit floating precision. Which allows values above 0 dB. So a real dB FS would consider a m...

Yes, if a live show is planned you might change the start type of the overlay to Manual...you can also do this on the fly. If you allowed it in the overlay options you can click on the status bar in the overlay player to change the start type also during the waiting period, eg from Soft to Manual. I...

I am not sure why you feel offended so quickly. I just try to find a simple answer why it is working here on 3 different PCs, but not on yours.
Yes I am sure I tested the right keys. I tested all NumPad keys.
I am testing it on Win7 so may be it's an OS difference I have currently no clue.

Hmm, the topic was started about the confusing timer display...which I changed. Then you asked why the Delay button disappears, which I tried to explain as well. Then I explained how to change the StartType on the fly up until the second of the scheduled start time. And yes currently I understand 'u...

In fact I still can not understand why "Delay" button needs to disappear Assume we have an Overlay with StartType = Soft. This means, that at the scheduled start time, the remaining duration of the currently playing track will be evaluated and compared with the Max Delay time. The 'Delay'...

Yes, gosh! I am sorry - that happens when you are not at your real desk and try to fix things just by code without real testing!
I am really sorry!
A new v3.0.14.13 is now available, which should fix the issue - hopefully finally!

Is that may be a NUM-LOCK issue?
Here in my tests all NUM-PAD keys are just working fine.
What the key-codes you are using?

Hmm, that bug seems to be an internal bug of the UI lib I am using and is unfortunately out of my control.
It should however only happen sometimes when closing/updating the application and is very uncritical.

So what specific keys are NOT working?
I tested all regular keys and they seem to work here (as shown in the video)...