jono grant Posted January 22, 2020 Share Posted January 22, 2020 Remove it maybe Cakewalk or fix it? That's all.... thanks! J Link to comment Share on other sites More sharing options...
bitflipper Posted January 23, 2020 Share Posted January 23, 2020 You learn something new every day - I didn't even know that was an option during recording. It's not something I'd have even thought of doing, as I avoid any ITB processing at all while recording. Still, it's surprising that removing DC offset would actually corrupt files. Corrupt in what way? Dropouts, perhaps? Link to comment Share on other sites More sharing options...
Byron Dickens Posted January 23, 2020 Share Posted January 23, 2020 I once lost the better part of a day trying to troubleshoot distortion on some tracks I was trying to record. Finally discovered that I had somehow accidentally clicked on "remove DC offset during recording" and that was the cause. So, to the OP: uncheck that. Link to comment Share on other sites More sharing options...
David Baay Posted January 23, 2020 Share Posted January 23, 2020 40 minutes ago, bitflipper said: Corrupt in what way? It just causes a general distortion of the audio. I never looked into exactly what the nature of the distortion was. Link to comment Share on other sites More sharing options...
bitflipper Posted January 24, 2020 Share Posted January 24, 2020 It's possible what the OP is hearing are dropouts, which when numerous can sound like very bad distortion. It could be that the overhead incurred by real-time DC offset detection (basically a HPF set to a very low cutoff frequency) is simply pushing the CPU over the edge. If that's the case, then simply increasing the size of the record buffers may fix it. Of course, that'd also increase your latency, if that's a problem. Link to comment Share on other sites More sharing options...
David Baay Posted January 24, 2020 Share Posted January 24, 2020 Hey, Dave, you should just do a quick test yourself. I don't think it's related to streaming performance or buffer settings. It seems there's just some logic issue with the way offset corrections are applied when working on a pair of inputs. Looking back at old threads, it only occured when recording each side of a stereo pair to a separate mono track, not with a single stereo track, which was not made 100% clear in the OP. This was reportedly fixed in the Newburyport release but I don't think I ever personally verified it. Link to comment Share on other sites More sharing options...
Byron Dickens Posted January 24, 2020 Share Posted January 24, 2020 Have you unchecked "remove DC offset during recording" yet? Link to comment Share on other sites More sharing options...
David Baay Posted January 24, 2020 Share Posted January 24, 2020 53 minutes ago, Byron Dickens said: Have you unchecked "remove DC offset during recording" yet? OP is recommending others to do that, not asking about it. Link to comment Share on other sites More sharing options...
WalkerTalker Posted January 26, 2020 Share Posted January 26, 2020 Wow, this is an long standing issue, and surprising it hasn't been addressed since 2015! http://forum.cakewalk.com/Sonar-IpswichLexington-Users-Remove-DC-Offset-During-Record-Heads-Up-m3337455.aspx Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now