Tempo changes.. Tempo events… I tried them all out… But no positive effect…
Still spikes on every bar start?
Today I installed Podium 1.39, and tried the new “import plugIn button”. Before that I deleted Jamstix in my project. Now I have the correct device definition. I only use Jamstix once in an arrangement.. it’s quite hungry for CPU even in other hosts… but the spikes on the 1st beat only appear here.. (btw. 1.39 is nice!!)
I don’t even have a multiprocessing cpu.. 🙁 (could not disable)
Neither do I have activated or used the metronome of Jamstix..
But when putting more “drum beats” in Jamstix and thus increasing the simultaniously played samples, Podium’s CPU indicator stays red all the time….
Did you find anything ❓ This bug is driving me crazy… ❗ Hope you can make Jamstix working for me…
Thanks! Great bug fixes!! 8)
I could run it with a steady CPU reading of ~15%.
I increased the buffers. Putting them to 2048 made the spikes on the first beat go away, but my average cpu usage still lies at 40 %. Still wondering why the spikes occured only at “one”… ❓
Try to adjust some of the options in JamStix and see if the CPU usage is affected. Also try adjusting your ASIO buffer size and see if this affects it.
Didn’t change anything.. 🙄
That’s what Zauni wrote (Jamstix dev):
I just downloaded the latest Podium demo and ran Jamstix in it. The CPU usage did not spike (XP3000 1.5GB RAM ASIO4ALL 1. but stayed around 18% +/-4%
My best guess is that this may be ASIO-related. Could you try the ASIO4ALL driver or another driver?
Ok, I tried 3 different drivers.. My soundcard’s, Asio4All v2.6 and the ASIO driver of my PodXT-Live… same behaviour… always on the first beat there is a spike, with crackles in the engine’s output.. What am I doing wrong?
Since this doesn’t occur in T2 or SX on your machine nor in Podium on our (similar) machine, the problem is likely in your Podium configuration.
Unfortunately, we’re not familiar with Podium at all so we can’t give any pointers where to start looking but I’d look at audio I/O things such as buffers etc.
Restarting Podium didn’t help. It must at least have to do with Midi, ’cause when I activate “only midi out” (in Jamstix output settings), the internal sound enige of Jamstix is disabled, but the behaviour described above still remains. The fact that these spikes occur relating to the song tempo further contributes to this suggestion, imho.
Hey Super Crunchy,
Thanks for that, but buying another host/plugin is not what I can afford at the moment.. perhaps I have to record the midi output of Jamstix and feed that track into the sampler. Not that elegant… 🙄
Ok, I’ve posted in the jamstix support forum. When there is an answer, I will post it here for other users, who have the same problem..
thanks again, Frits!! ❗ 😀
Have you discovered other interesting bugs ?
Do you try me?? 😆
No, that’s it for now… 8) I only want to help making Podium a strong competitor to other hosts… Little contribution, I know!! 🙂
is it possible to disable the background-image (and only use a color for it)?
You can set the track image opacity to “0”. Or you completely disable the track image..
In both ways you only get the background color, that’s been already set for the panel, and not a certain color for the background of the arrangement…
No, I’ll get that fixed for the next 1.39 release. Thanks for reporting it.
Thanks for that.
There is another behaviour of Podium that I find a little strange.. When activating bounce on a bounce/group track, Podium gives error messages on those tracks that have plugins mapped, which are now unloaded.. So you have these red marked areas in your mixer although you already know that these plugins are’nt used at the moment. So it seems that Podium realizes that there is an error, but what it does not realize is, that this is a “wanted” error because of the bounce track. I hope I expressed it the right way.. What I want to say is: These red messages are wonderful, because you can realize any mistake in your arrangement very fast, but having bounce enabled a track, these messages don’t make sense to me.. Just my opinion… 🙂