JS3 frquently crashes Reaper when loading (again w 3.1 beta)

XoechZ_at · Post by **XoechZ_at** » Wed Sep 15, 2010 11:34 am

Ok, I have tried ASIO4ALL drivers.

But they do not work at all!

First, the S/PDIF input of my soundcard does not work with ASIO4ALL and second, the output is crackling and popping all time. I have tried different settings with ASIO4ALL and read the manual. Did not help. This driver is not working here. Sorry.

XoechZ

Post by **Ralph @ Rayzoon** » Wed Sep 15, 2010 11:48 am

Please try the m-audio WDM driver in REAPER.

XoechZ_at · Post by **XoechZ_at** » Wed Sep 15, 2010 2:40 pm

Thanks for your pacience Ralph!

I tried the WDM driver in Reaper.

Result:
Seems to be more stable (no crashes when playing or saving projects or templates), but latency is too high for recording.

XoechZ

Post by **Ralph @ Rayzoon** » Wed Sep 15, 2010 3:34 pm

There should be an option to reduce latency.

Susan G · Post by **Susan G** » Wed Sep 15, 2010 4:05 pm

I've been having crashes with JS3 in REAPER as well, also while either loading or saving. Sometimes it doesn't happen until I actually exit REAPER.

I have a MOTU Ultralite. I've been using the ASIO drivers, but I'll see if WDM improves things.

Thanks-

-Susan

XoechZ_at · Post by **XoechZ_at** » Wed Sep 15, 2010 5:52 pm

Good to hear that I'm not the only one with this problem.

But as I said above, the official Jamstix 3.02 seems to be more stable concerning this problem than the new 3.1 Beta 1.

Also I want to mention that I'm not sure it is really driver related, because the crashes happen only when loading or saving projects containing Jamstix 3. There are no problems during playing, mixing, recording and all other stuff a DAW is for.
Funny enough, using WDM drivers really seem to cure this problem.

So, maybe it's more a Reaper related problem than a Jamstix related one. I don't know. I'm just a musician and want to make music in a stable environment.

Greetings,

XoechZ

Post by **Ralph @ Rayzoon** » Wed Sep 15, 2010 9:40 pm

I do understand these things can be annoying and we'll do our best to get this fixed. Can you send me a screenshot of your REAPER VST preferences?

XoechZ_at · Post by **XoechZ_at** » Thu Sep 16, 2010 3:36 am

Sure. Here it is:

www.xoechz.at/Screenshot.jpg

Greetings,

XoechZ

I_Wavne · Post by **I_Wavne** » Thu Sep 16, 2010 2:21 pm

I have crashing problems in Reaper 64 bit, but not in 32 bit. I just got Jamstix so I am busy learning how to use it instead of chasing the problem in the 64 bit version.

I am willing to try some fix's tho if you have any yet.

Regards,

Wayne

Sheppol_A · Post by **Sheppol_A** » Wed Sep 22, 2010 1:54 pm

Susan G wrote:I've been having crashes with JS3 in REAPER as well, also while either loading or saving. Sometimes it doesn't happen until I actually exit REAPER.

I have a MOTU Ultralite. I've been using the ASIO drivers, but I'll see if WDM improves things.

Thanks-

-Susan

I've just cured this problem on my system.It wasn't software.I had to replace the CMOS battery on my Mother board and didn't set up my RAM correctly.I build my own systems and when I bought another stick of RAM they sent me one that was 400Mhz when I wanted a 333Mhz stick.I forgot that I have to manually set the RAM speed to 333Mhz and not let the system BIOS Auto-detect the RAM speeds.

Note:Ram can also suffer from,"Board Creep".This means after a while the RAM sticks warp a little and make bad contact.Windows is very very sensitive to this hardware problem and can cause what appears to be software problems and BSODs.

It does not harm,if confident and taking anti-static precautions e.g ground yourself before touching RAM sticks or the mother board,to take them out and clean the contact edges of the sticks with some Electrical Switch Cleaner or clear alcohol(Vodka/Gin will do) plus lint free tissue and then reseating them correctly.

Warning!
If you are unfamiliar with the system BIOS do not enter it unless you have good knowledge otherwise making wrong changes can make the system un-bootable and require finding and correctly using the system BIOS clear jumper on the Motherboard.

HTH