Rayzoon Technologies LLC

[sonicviz]

Hi,
I'm getting some strange behavior from Beta7 when using audiom8 to drive it.

I'm getting periodic short freezes on the power knob, usually on playing power increases, which translate to spikes in the winxp performance monitor.

Say I'm playing a guitar riff low, I'll increase my playing dynamics, the power knob swings up, then freezes for what seems like 100-500 msec, causing a spike in task monitor, which also causes an audio dropout.

I minimised the whole reaper layout and it seemed to lessen the problem.

Using Reaper 3.04. Could this be an issue with the gui update?

or?

Cheers,
sv

[Ralph [RZ]]

Do you have another host to test this with?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[sonicviz]

I have cubase, but to replicate my entire live project would take to long at the moment.

I rolled back my winxp system a couple of times in case it was a conflict from recent install but I am still getting glitches, even after I optimised some other plugins.

I also found another bug/feature.

I have a nocturn, but am using a bidule patch to convert noteons to program changes so I can switch Jamstix live loops.

I had a song with one part, 200 repetitions, with both drum and percussion parts.

I copied that part to two other parts, and then try and modify them so I basically now have:
part 1 Drums/silent + percussion
part 2 Drums + percussion
part 3 Drums + percussion/silent

It was working for a short while, now the UI won't let me select parts anymore. It stays locked on one part no matter what I do.
If I reload the song it allows me to switch parts for a little while, them locks up again.

[Ralph [RZ]]

Can you replicate the part problem and then immediately send me the rzdlog.txt from My Documents\Jamstix2?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[sonicviz]

I figured out the parts issue.

When I now load the song originally, which has live loops already set, I can switch parts to edit with live loops set.

When I start/stop play and switch via PC midi messages, which works fine, when I stop the play I can no longer select the parts unless I turn live loops off.

Sent you file anyway.

ty!

[sonicviz]

I'm fairly certain this has something to do with Jamstix.

At times on the Reaper performance monitor I see JS2, which normally runs at about 2.5-3.4% cpu range spike up to ~20+% which coincides with the audio dropouts from sudden load. (dpc spikes)

I have not confirmed if this is only related to Drums + percussion songs, but I suspect this may be the case.

EDIT:
Less glitches with just drum song, but still there.

I guess this is either Reaper or Jamstix, or a conflict between the two.
Has been working fine till recent releases of both these.
But I can only roll back so far now, as both Reaper and Jamstix have implemented new file formats incompatible with older versions, so I'm now back to acoustic playing I guess.

[sonicviz]

Update:

Fingers crossed, but I think it may related to the full debug log option turned on by default in the beta.

I turned it off and am getting smoother performance now on the problem songs I have.

I have a gig tomorrow and will stress test it live again to see if I can nail it further.

I think a combination of heavy drum + percussion and full debug log is causing it to glitch...*knocks on head*

Could you please make another option to turn ALL logging off, and disable it by default?

ty

[Ralph [RZ]]

Yes, 'Full Debug Log' can cause these problems because it writes a ton of stuff to the log file during the entire session. Without it, only minimal information is written to the log that will not cause any performance hit.

Concerning liveloop part selection, I'll see what we can do there.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[sonicviz]

Yes, seems obvious in hindsight. I think you should add something to the manual about that actually, may save someone a lot of time in the future.
I have 24 tracks in my Live performance project with a number of support instruments and it took some hunting to eliminate the others.

edit (I see it's already there. I don't remember how this got enabled actually...):
FULL DEBUG LOG
This option causes Jamstix to write extensive debug data into its log file (rzdlog.txt). You should use this option only when directed to do so by tech supp ort and only for the duration specified since it can cause significant CPU and disk resources.


The good news is I did optimise some of the other vst's so have cut cpu by another few % as well.

I still think you should any logging optional to enable people to run things as lean as possible, especially in heavy use environments.

ty!