Zynewave's Forum Page

@Conquistador wrote:

A question for you Frits…

The master chain is just the effect chain that is present on the master track. You have that docked on the right edge of the mixer. If you want to show the mixer strip for the zPEQ effect you added, just disable the “hide mixer strip” option in the zPEQ track menu.

I’ll get round to revamping the mixer. Some of the “spreadsheet” like behaviour of the effect headers is a leftover from the old expanded track mode. With that mode gone in 2.20, I can now start cleaning up some stuff.

Before the mixer, I will be looking at the tracks region. For 2.21 I’m trying out a new feature that will make navigation easier. I’m not quite ready for a preview topic on that yet.

After that, I’ll be looking at the track header contents. I’m not entirely happy with the current design. I think it tries to cram too much functionality into the small space of the header. It can be confusing at times with all the controls, menus and different mouse actions. I’m thinking about a solution where the contents in the header is mainly information, and then add a single button on each header. Clicking this button will show a larger popup panel to the right of the track header (semitransparent overlay on the track lanes) with easy controls for managing the effect chain etc. That’s beyond 2.21 though.

This is not a small UI thing to implement, so this is far into the future.

@Markus wrote:

So Frits, makes this topic anything sense?

So far not much new has come to light in this topic. I already knew that Darcy wants a Mac version of Podium. I need to grow a second brain to make that happen though 😉

@bladerunner wrote:

the ongoing cpu spike issue which can be clearly be seen in frits own video here

http://www.youtube.com/watch?v=Jv39dX7NP_Q

its reassuring to know that it happens on the devs own computer as i thought it might be an issue with my own particular set up. it really makes podium almost unusable for me. i haven’t seen behaviour like it in any other host. the spiking seems to be directly linked to the asio buffer size which has to be set at 2048 samples to tame the spikes. in reaper i have no such problem and can run many more softsynths at 512 samples. i have read through all of the cpu related threads in this forum and played around with all of the recommended tweaks etc. but the issue still very much remains.

i have also mentioned timestretching as an issue but i could just rewire reaper for that duty if i needed it so the cpu issue being addressed is my one wish.

i can regularly bounce tracks as a workaround but i think there is an issue that needs addressing here. do others find this is still a problem or are you bouncing tracks to get around it?

Sigh! 😥

If it leaves the impression that Podium suffers from CPU spikes, then I guess I have to redo the video with some tracks bounced. The spikes you see in the video are not random. They occur at places in the song where a lot of notes are playing simultaneously. I shot the video with a buffer size of 2048. As I’ve explained in previous topics, Podiums CPU indicator is deliberately sensitive, to give a clear warning of where there may be problems. Other hosts may use a slower updating CPU indicator, but that does not mean that CPU spikes are more likely to occur in Podium. As you can hear in the video, the spikes does not produce an audible degradation of the audio output.

That you find that Reaper produces lesser CPU spikes at low ASIO buffer sizes can be due to the anticipative mode, which has been discussed here:

http://www.zynewave.com/forum/viewtopic.php?p=13556&highlight=anticipative#13556