Zynewave's Forum Page

@thcilnnahoj wrote:

I noticed a problem with changing time signatures… When you enable snap, the grid shifts, and not like it should! 😮 The weird thing is that it doesn’t happen at any point on the timeline… I haven’t found out what exactly causes it.

Here’s a video with a simple example: http://www.youtube.com/watch?v=NyjVoR6GrMQ (this is after restoring the default setup, I only changed the gridline color)

Thanks. Nice find. Fixed.

@thcilnnahoj wrote:

I had some fun with real-time bounce recording today… now I remember why I missed it. 🙂 It’s too bad you can’t record any automation on tracks that are bounce enabled, though, even when the effect to be automated comes after the bounce in the signal chain (probably due to the fact that you can’t record enable bounced tracks). It does work with the faders on parameter tracks, so perhaps something can be done? I didn’t try with a MIDI controller, just with VST editors.

Hmm, perhaps record enabling a bounced track should be possible. I’ll experiment with this at some point.

– It seems the highest level you can go to in the browser is a drive’s root directory. Am I missing something or is there no other way to change drives except using the browse dialog (double-click on the folder name bar)?

That’s the highest I can go with the Windows API function I’m using.

– When you drop files that are numbered like 1..20 in an arrangement, they’re not ordered the way you’d expect. 10 comes after 1, 20 after 2, and so on. Even Windows gets this right nowadays. 😉

I’ll have to search for a Windows API function that can help with a more intelligent sorting. I believe sorting behaviour is locale specific.

– If you uncheck “use as group track” for a track that has only one child track, the former group track is suddenly seen as an effect track… Maybe it should be impossible to uncheck this option (also for composite tracks?) when a track has child tracks.

I’ve noticed this too. I’ll fix this at some point.

@thcilnnahoj wrote:

If you delete things from a project, the project browser seems to have a problem displaying this:

Also, I’d prefer if the ‘Move bounced audio to new track’ command in the bounce menu would always create the new track directly below the one that got bounced. Objection, anyone?

Ouch 😯

Fixed. That was a bug that came with the UI changes in 2.36. I’ll probably release 2.37 within a day or two.

@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.