Zauni.
PodianerHi,
I have a problem with Jamstix.. First of all, the cpu usage is at 25-30 percent, what is way too much, because Cubase or Tracktion both use about 15%.
Every fourth bar, always on the “one” the cpu goes to 60 and then suddenly falls back to 25-30. Is anybody here, who uses Jamstix? Frits? Any idea why Jamstix seems to dislike Podium? ❓
duncanparsonsDon’t know, but the other seq I use, NTrack, had some problems with JamStix when it came out. The 2 developers got on good speaking terms very quickly, and made small tweaks so that it works as it should.
Maybe if you post on the Jamstix forum as well as here, Frits and the other dev might have a chin wag?
DSP
ZynewaveI’ll download the demo, and try it out in the weekend.
Podianerthanks again, Frits!! ❗ 😀
PodianerOk, 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..
ConquistadorI tried Jamstix in Podium recently and I had spikes when looping over 4 bars, the CPU meter was constantly red or tinted.
I was having spikes with FL5 as well.
I was going to post my problems to this forum but decided to at least restart Podium as it is very reliable. So after restarting Podium the spikes in FL5 and Jamstix vanished.
PodianerRestarting 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.
Conquistador@Podianer wrote:
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.
Sorry to hear that. However, as I am sure you aware you are dealing with two products that have *highly* responsive developers. I am sure Frits and Rayzoon will have a fix very soon. 😉
PodianerThat’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?
Podianer:
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?
Zauni:
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.
ZynewaveI’ve tried the JamStix demo, with ASIO4ALL. I could run it with a steady CPU reading of ~15%. At one point though, after frantically clicking on various buttons (I had no idea what I was doing), the CPU suddenly went to 100% and stayed in the red. Unloading and reloading the plugin seemed to fix it. I think it happened when I activated the JamStix metronome, but I cannot reproduce it.
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.
PodianerI 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.. 🙄
ZynewaveIf you email me your project file, I can check if there are other things that causes the spikes.
PodianerHi Frits,
Did you find anything ❓ This bug is driving me crazy… ❗ Hope you can make Jamstix working for me…
ZynewaveI finally found a way to get a reproducable error. Do you have the metronome activated in JamStix? This could explain why you get spikes on ‘one’.
To fix it, I simply deselected the ‘enable plugin multiprocessing’ option in the Podium preferences dialog. It appears that JamStix is having problems with multiprocessing. Let me know if disabling multiprocessing cures your spike problems.
PodianerI 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….