Zynewave.
MarkusHi,
So, cause there is so much arguable, why we wont to this. Those who are active in here forum can make just ONE wish. That wish must be kinda easy/fast to do. When Frits is accomplish every wish, we start “new round”. How’s you think about that?
If Frits or you doesnt like my idea, say it. When we reach like 5 or more negative answers, Frits can delete this tread. However, i think this idea would be fair to all.
Anyway, i’ll start.
Markus wish that Selection Tool can strech notes. This way we would have “all in one” tool. Very welcome feature. Now, make your wish. LOVE AND PEACE!
darcyb62My one wish would be to have this ported to Mac. I have been using Logic since I went to the Mac and although I quite Logic, I yearn for the day when Podium will run on the Mac. Until then, Logic it is.
Markus@darcyb62 wrote:
My one wish would be to have this ported to Mac. I have been using Logic since I went to the Mac and although I quite Logic, I yearn for the day when Podium will run on the Mac. Until then, Logic it is.
Nice wish! However we talking about easy / fast things. Porting in Mac would be take alot time.. I think..?
darcyb62But that’s it. I don’t have any other wishes for Podium. If I recall correctly, the only thing I thought missing with Podium was the ability to route midi.
aMUSEdWell for me the really big question is the project management which I find hard to work with. My usual practice in other hosts is to save versions of my work-in-progress iteratively so I can always backtrack easily to an earlier version and start again and always have a pristine opening project so I can follow different paths from the same starting place. Most hosts have a “save as ” command to enable that to be done easily (like snapshots). However Podium doesn’t for Arrangements, only for Projects – imho it’s the arrangement level that needs the save as since its the individual work-in-progress level not the project level which is the container for arrangements (or at least should be). There is no way currently in Podium to save versions along the way without writing over previous versions (indeed you have to save the whole project if you don’t want to lose anything stamping in your edits when the whole point is not to for the whole project, just for each version) and the whole system is confusing and makes it too easy to lose work.
bladerunnerthe 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?
Zynewave@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
LiquidProj3ctJust delete it and don’t lose your time, the next time you’ll do it better 🙂
thcilnnahoj@Zynewave wrote:
As you can hear in the video, the spikes does not produce an audible degradation of the audio output.
Well, actually they do! Only very slightly noticable, though.
When I do MIDI only stuff I work at the same buffer size and I get a few spikes here and there, too. I don’t get the impression that Podium offers less performance than other sequencers – it’s just that Nucleum’s a bit hungry, given its Synthmaker nature. 😉
Incidentally, why not just delete the CPU indicator when recording demo videos in the future?
On the topic: I don’t have any wishes that are quick and easy to do at the moment.
MarkusSo Frits, makes this topic anything sense?
bladerunnerhi frits 🙂 sorry this subject makes you sigh. perhaps is it just taking me longer than everyone else to get my head around it 🙄 lol! i have just been playing around with reapers sychronous and anticipative modes and also with podium and i think i finally get it (i read through the linked thread)…
it seems to me that podium is reporting a more accurate cpu reading than other hosts and that podiums engine is based on real time performance (so, equivalent to reapers synchronous mode right? – forgive me if i am repeating stuff that has been mentioned in other related threads) and not the rendering ahead type ability of reapers anticipative mode. when reaper is in synchronous mode i get a similar performance to podium but when in anticipative i get more performance but the trade off is in a delay to real time performance tweaks to plugins etc. (right?!). hope i’m making sense
Zynewave@bladerunner wrote:
it seems to me that podium is reporting a more accurate cpu reading than other hosts and that podiums engine is based on real time performance (so, equivalent to reapers synchronous mode right? – forgive me if i am repeating stuff that has been mentioned in other related threads) and not the rendering ahead type ability of reapers anticipative mode. when reaper is in synchronous mode i get a similar performance to podium but when in anticipative i get more performance but the trade off is in a delay to real time performance tweaks to plugins etc. (right?!). hope i’m making sense
Exactly. I’ve spent a lot of time optimizing the performance of the engine, so I’m glad to hear that your performance test shows that Podium matches the synchronous mode in Reaper.