Tapedeck dropouts (GR 4, MacOS 10.6)

Hello!


I have troubles with the tapedeck on Guitar Rig 4 (and also Guitar Rig 3)... even with a buffer size of 512 samples (which is not really real time to me anymore), there are occasional drop outs in the audio recorded by the tapedeck - like 0.5 seconds dropouts, sometimes within the first 20 seconds, almust always before one minute. Else, the system doesn't have any apparent low-latency issues, recording with logic 9.02 works flawlessly even with a buffer size of 128.

I tried it on a mac mini 2.0 GHz as well as on a macbook pro 2.4 Ghz, same result. In both cases I used OS 10.6.2.

Is anybody else having this issue?

 

i have had this exact same problem with GR3 and 4 and it's very annoying. to the point where i don't use the TapeDecks at all for recording because if i come up with an idea i like, the popping makes it unusable and i have to re-record anyway.

i've searched on this issue before and was never able to find a fix. let me know if you hear anything more.

i'm using a MacBook and have had no other latency or popping issues, even down to 64 samples for recording in Logic. it's only the Tape Decks that are the problem.

-t

 

Hi!

Yeah it's annoying and renders the TapeDecks useless for me as well. I tried the latest beta version however and in my first test I managed to record more than one minute without dropout. Unfortunately I didn't have the time yet to do more experiments...

Have you written to NI about your issue? I already filed a bug report, so far without response.

 

Tape Deck glitch bug

i am signed up for the Public Beta, but have been leery about switching over because i have so many recording going right now that have very elaborate automation and GR4 presets.

i did file a bug report about the Tape Deck glitch months ago, but never heard anything back.

please post if you get more information.

thank you!

-t

 

I received a reply from NI, it's a known issue and they are working on a fix. And in fact I have been playing around with the GR 4.0.8 beta for a while, and it seems the problem went away!