Rayzoon Technologies LLC

[T-Break]

Hi Ralph and all....

I must first say what a great new interface JS3 has and what useful new tools have been added to make the creation of songs that much easier.

However, I've been experiencing split second audio glitches like a needle going over a scratchy vinyl record (remember them) about every 10 or so bars, which renders the drum track unusable.

I have read the FAQ posted on this subject and have tried everything suggested in it - from reducing dynamic realism to min; increasing pre-buffer to max 128k and voice reduction. No improvement.

I've played through most all of the song pre-sets supplied and some of my own creation. The only thing I noted here is that those song pre-sets that mainly use Jamcussion don't glitch.

I've deleted the JS3 tracks in Sonar without closing the project and inserted JS2 instead to play the same songs - and NO glitches. So it's not the way I've set up the Sonar project.

The drain on CPU is exactly the same for both - no more than 4%, so my computer is hardly being taxed. It's a Pentium Dual Core Quad with 3Gb.

I've never had the problem with JS2, so this is definitely something to do with JS3. Could it be something to do with certain of the sound samples ?
I didn't use the migration tool because its name implied that it would move my JS2 packs and I knew I wanted to keep that intact in case I had problems with JS3. Instead, I copied and pasted sounds into JS3 folder.

I searched these forums without success. I'm hoping Ralph that you might have other suggestions or maybe other users with same/similar setup as mine is experiencing the same and just haven't posted.

My fingers are crossed and I'm going to stay positive.................. ?

[Ralph [RZ]]

Please use the 3.0.1 Beta from your download page and, if it doesn't fix it, please send me rzdlog.txt from My Documents\Jamstix3.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[T-Break]

Working on it now Ralph. Will advise outcome in a couple of days.

Cheers

[studio64]

Hi Ralph

I am still suffering similar problems in Cubase 4 and 5, each on a different partition.

I installed the new 3.0.1 dll, unfortunately, that made little difference.
I am on max 128 buffer

I also tried increasing the buffer size in my Steinberg MR816X, to an almost unacceptable latency, but that didn't improve things.

The red warning in Cubase shows every few bars, but with glitches only perhaps every 10.
This seems to improve slightly, when I play through the song a second time.


There is a big upgrade to Cubase 5,(5.5) in the pipeline, which claims to improve multicore usage, so that might change things.

regards
_________________
john-studio64
Intel i7-2600 3.4 16g Ram
Cubase6

[T-Break]

Just to updat...........

I've installed the JS3.0.1 Beta and regret to advise no resolution to the problem of audio glitches. I've e-mailed my rzd.log to you as requested.

The problem may be evident in some Quickstart songs and not others, or in a Quickstart song with default kit but not when kit is changed.

I'm hoping it's just a bad install. I'll wait to hear your findings.

Best wishes.

[T-Break]

Further update on my problem...........

On further evaluation, the installation of JS3.0.1 Beta does seem to have improved things somewhat. Audio glitches remaine apparent - but not as often.

Ralph asked me for an MP3 file so that he could hear for himself. Whilst working on that just now, I have discovered more .........

I bounced the JS3 track down to a new track in Sonar 7. Before exporting it to then send to Ralph, I played it back solo within Sonar. I heard the glitches and noted at which beat. I repeated several times and discovered the glitches at different places each time. I then took the track into Adobe Audition and played back from there. NO audio glitches.

This suggests to me that the glitching (like a needle over a scratched vinyl record) only occurs 'live' and within Sonar. If after further weeks of recording I find that my final exported files do not carry these glitches, then I can happily continue to record knowing I will have clean drum tracks although living with the inconvenience of hearing glitches whilst 'live' in Sonar.

The issue may be small incompatibility between Sonar 7 and JS3. I say this as I still do not have the problem with JS2 in Sonar 7.

It seems I won't be able to supply Ralph with an MP3 containing the problem. If at some point I do - then of course I will forward it.

Happy jamming all.........................

[Ralph [RZ]]

T-Break, try these things:

- turn LoD off in JS3 Options

and if that doesn't work:

- increase latency in Sonar to 256 samples
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[T-Break]

Hi Ralph........

Thanks for sticking with me on this. It's clear you care that we all have the best out of JamStix !!

LoD is off. With regard to increasing latency in Sonar to 256 samples, I find I can not. It is stuck on 222 (probably from when I first installed Sonar 7 and ran the wave profiler) and apparently won't let me alter it. I'll be the first to admit that I don't know the program inside out. Maybe something to do with my sound card (Emu 0404). It's set to ASIO. I've read Sonar's help files - which don't readily help. I've got to do some research elsewhere.

I'll stick with it and report later. Thanks !

[dke_music]

That is an odd buffer size. It should be 64,128,256, etc...

If you do have it set to ASIO, under Audio Options in Sonar you should see a button called Panel, to bring up the EMU control panel there you can set the buffer size.

If your running under WDM, you'll need to change the buffer sizes on the last tab under Audio Options, set them to 256

Dan

[studio64]

T-Break

I have similar problems in Cubase, but I found if I close the JS3 Gui totally, the glitches then go away.

Have you tried that?
I know it's not the total solution, but a work around for now in Cubase.

It may not work in Sonar, but worth a try.

I am sure Ralph will come up with the fix.

Regards
_________________
john-studio64
Intel i7-2600 3.4 16g Ram
Cubase6

[T-Break]

Hi DKE-Music........
Thanks for your advice. Before closing it last night I switched to WME which left me with different controls in Options>Audio compared to ASIO driver. Will try it now and see if it's made any difference. In the Advanced tab of Options>Audio, I did briefly notice a series of little boxes showing different sample rates. I've got a little time now to look into that. I'll also look into the small EMU ASIO window - but I seem to remember the slider only shows latency in m/secs. Under ASIO I get down to 4ms latency. Under WME, 10ms is lowest.

studio64..........
Thanks for your post too. I'll give your suggestion a go and report findings.

I guess the important thing is that bounce-downs of the JS3 track are seemingly clean.

I'll post again in the next day or two. Cheers.....

[Ralph [RZ]]

Have just released 3.0.1 Beta 2, which will further improve bar editor performance. Another thing you can do with this Beta, if you still get glitches, is to turn off the note display in bar icons. Simply add this line tothe [General] section in jamstix3.ini:

BarIconNotes=0
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[T-Break]

...........I do mean WDM driver............... !!!!!

[T-Break]

Hi guys..............

Things are looking up now (so far). Having switched to WDM driver with minimum 10m/sec latency in place of ASIO (with 4m/sec latency) the audio glitching was not apparent over a 15 minute run of various quickstart songs and 'rolling the dice' whilst in playback.

I then switched back to ASIO driver and increased from my 4m/sec latency that was always trouble-free with JS2 to 10m/sec latency as WDM and again no apparent glitches over a 15 minute playback.

Now, I might be splitting hairs, but I think one would obviously prefer 4m/sec latency rather than 10, yet I wonder in reality if the difference would be noticed.

This seems to be the solution for me at least, but could help others experiencing similar.

I've just picked up Ralph's post to say that 3.0.1 beta 2 has been released which could help my problem further. I'll load that and then try running JS3 through ASIO driver back at 4m/sec latency and see what happens.

I'll let you know................. hmmmmm, got Monday 'cracked' for this week, JS3 seemingly sorted and band practice this eve - yeah, things are looking up........

[jan]

T-Break , I also have this problem with glitches in Sonar 8.5 PE with only Jamstix running and after sending Ralph e-mail I found this thread .
Some cpu spikes also occured in Sonar but not on my system monitor .
I also did not have this problem in Jamstix ver 2 at lower latency .
I have done what you did and followed Ralphs advice conserning the baricon .
Jamstix 3 is the only vsti I have encounter this problem with .

All the best
Jan