Zynewave's Forum Page

@4mica wrote:

Sounds good now…is the midi quantize feature still going to be implemented?

The midi grooves, as discussed in the 2.41 preview topic, has not been implemented yet. It still is my intention to implement it at some point. I got sidetracked with other non-Zynewave stuff the last couple of months, and only recently started to work on Podium again. The first few releases will be about minor features and bug-fixes.

@thcilnnahoj wrote:

I don’t think two options are enough, though, if Trancit wants to only store the zoom level without song position. Likewise, I’d probably make a snapshot for editing that zoomed in vertically, but without binding it to a specific track (would this reset the view to the top, by the way?).

Ok, I’ll add an option for each of the four settings then.

A snapshot that only changes the track height zoom will not change the top offset. If you want it to reset to the top, you could create the snapshot when it was at the top, and then enable both the track offset and track zoom options on the snapshot.

The other suggestion, I think it was made by CQSD originally, was to make another feature for vertical zoom level recall (like “track height presets” in Studio One). This way you could combine separate your self-made zoom presets for the X and Y axis. Since you can only have one active snapshot, this isn’t possible at the moment. Honestly, though, I don’t know if this would be useful or just make it more confusing.

I don’t like the idea of introducing another type of zoom preset dedicated to track offset/height. It can be handled just as well by the current snapshot feature. Btw. there is no concept of an “active” zoom snapshot. The zoom snapshot buttons will light up (appear selected) if the current zoom settings matches those stored for the snapshot. So, if a snapshot is set to only affect track height zooming, then it will light up if that matches, ignoring the status of the other three zoom settings. That way there can be multiple snapshot buttons that appear selected.

Thanks for the feedback.

Edit: It probably is a good idea to add a fifth “First snapshot in a group” option on each snapshot. This will enable you to separate the snapshots into separate groups for e.g. timeline and track zooming. Sort of like it is done with the grouping of track tags.

The shop is now online again. All users with an expiring upgrade period should have received an email today, with a discounted offer for extension.

Difficult to please both of you, without implementing this as some sort of option

There are four settings stored for each snapshot: Timeline start, timeline size, track top offset and track height zoom percentage.

I could add options for these four settings in the snapshot button right-click menu. So each snapshot can be configured differently, meaning you could use some snapshots to position the timeline, and others to adjust zoom range, etc.

By default all four options would be enabled for new snapshots, so you would need to adjust the options for each snapshot, if you want them to affect only part of the zoom settings.

Is that the way to go? Should all four settings be available as individual options in the menu, or should it be reduced to two options, labeled “Horizontal timeline range” and “Vertical track range”?

@chase wrote:

I take it you are are the Programmer – Developer of Podium?

Yes. I am the only person behind Zynewave.

What would you like to see happen with Podium?
Were do you see Podium in say 5yrs?

Do you think you’l be taking it to a higher or the next level?
– staffing more people to handle the business side of things.
or help with programing etc etc

Do you see Podium growing as a company business and software is what I’m asking i guess.

or will Podium slowly stagnate or turn into more of a programmers hobby kinda thing?

Podium has always been a hobby of mine. The last 5 years I’ve been fortunate to be able to work full-time on Podium. I’m not making enough money from Podium sales to continue with it full-time though. In the future I will need to find a more dependable source of income, which inevitably means I will get less hours per week for Podium development. That means returning to the way I developed Podium for the first 15 years of its existance. So I see myself continuing with Podium development in-definitely.

I gather from the different questions you’ve been asking, in other topics as well, that you are requiring a lot of specific features within surround-sound processing, etc. You should perhaps be looking at products such as Nuendo, or some of the other big players that has a wider range of features than Podium currently offers.