Zynewave's Forum Page

@Pigini wrote:

@Zynewave wrote:

The problem is that it is not implemented. Only the timing clock is transmitted, which can be used to sync e.g. external delay units to the Podium tempo. Start/stop messages are not transmitted. With my current todo list, it’s going to be a long time before I have time to add support for this.

Are Start/stop messages difficult to implement? It seems such a basic thing. I would have thought it was just overlooked at the time, but not that it was hard to do.

Not particularly difficult. It’s just that there are so many non-difficult things on my todo list. Lately it feels like that for every feature I implement, two new requests are added to the list. I’ll have to put some of the requests that are only relevant to a small percentage of Podium users on a todo-in-the-future list.

@Malcolm Jacobson wrote:

The only thing I still find confusing is the behaviour after bounce. If I enable Realtime Bounce (my preferred bounce method when jamming with VSTi’s) then enter Record, the audio file is displayed while recording – but disappears when I press Stop. I think this is very confusing behaviour, and the first couple of times I tried it I thought I had done something wrong. It took me a few goes before I found out I had to enable the playback of bounced audio after recording in order to view/listen to the bounced track.

Could this behaviour be changed (even if it’s something that can be enabled by preference) so that the audio is displayed and plays back automatically after creating a bounced recording?

I’m not sure what the best solution is to this. Suppose you have disabled the “deactivate record mode when playback is stopped” option: When you stop playback (with record mode still enabled), should the bounce record mode stay activated in case you want to continue recording, or should it switch to bounce playback?

Or should it be the deactivation of the transport toolbar record button that switches to bounce playback? And what if you switched record mode on/off without recording anything?

Suggestions anyone?

@ronin wrote:

There is another thing on my mind:
Personally I think the selected input should only be activated when the track is armed (no monitoring and no input metering while unarmed). The tooltip on the record button already implies this behavior.

Hmm, :-k . Doing that would mean you could not set up an audio input to act just as a live feed (perhaps from a talk-back mic in a booth). Once you start recording on other tracks, you would unintentionally record the live feed track.

Anyone have an opinion on this?

Beta3 is up. I managed to reproduce the silent recording bug with another soundcard interface I had. I’m 99% sure the bug is fixed now.

@thcilnnahoj wrote:

@Zynewave wrote:

The width of the meters in the mixer will resize according to the zoom setting.

Nice, but personally, I wouldn’t say no to even wider meters. 😉 It’s also a shame that the currently biggest meter size is only available when the strips are zoomed to 300%, because they would fit inside strips at a smaller zoom level already, and thus you could save some space.

The meters resized with the same percentage as the strip widths. This was to ensure that even a 32-channel input meter would not grow larger than the zoomed strip width. I’ve changed it so that mono/stereo meters increase at a larger rate, and 3-8 channel meters increase at a slightly larger rate.