Clicks that actually make it onto the recording!

Author
SvenArne
Max Output Level: -48 dBFS
  • Total Posts : 2719
  • Joined: 2007/01/31 12:51:29
  • Location: Trondheim, Norway
  • Status: offline
2017/03/09 11:12:40 (permalink)

Clicks that actually make it onto the recording!

Hi SONAR forum, long time no see! 
 
I'm having problems today with digital sounding clicks like I'm running out of CPU power. Only this time the clicks are actually printed to the track when recording! The project is a sketch with no plugs running apart from a few ProChannel compressors/EQ, so I got loads of CPU headroom. I've tried different recording chains and going both digital and analog into my BabyFace so it seems the clicks originate within either the interface/driver or SONAR. 
 
I've been a Cakewalk user for more than 20 years so I've had my problems with clicks, but I've never experienced them being recorded before! Any suggestions? I downloaded the update 2017.02 yesterday, is there any use trying to roll back?
 
Sven





#1

13 Replies Related Threads

    Rob[at]Sound-Rehab
    Max Output Level: -47 dBFS
    • Total Posts : 2819
    • Joined: 2011/02/03 04:31:35
    • Location: Sound-Rehab, Austria
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 11:36:31 (permalink)
    Probably no help to you, but I had similar issues in fall with Sonar & MOTU. Back then I contacted both companies: Cakewalk, well actually Noel himself, replied that they would help but they have no MOTU rigs in house, hence cannot follow-up.  MOTU eventually provided a much better driver, so the issue has gone here ...
     
    However, since you are now getting something similar with RME, which seems to be Cakewalk's number 1 interface for testing, you should have a fair chance that they can reproduce your issues ...
     
    My suggestion would be to see if you can reproduce that after a reboot and possibly also with a new project. If so, get Cakewalk involved. I wouldn't be surprised if Noel himself gets on the case as something like this is either very deep in the audio engine or in the audio driver (which with RME is let's say a lot less likely than with any opther company).
     
    Afterwards I would try to rollback and give it another try, should be quick. Also, what's the status with win10 updates? Are you current or some months behind?
     

    GOOD TUNES LAST FOREVER
      +++   Visit the Rehab   +++
     
    DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600
    Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture)   Control-Surface: VS-700C 
    VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really) 
    #2
    The Maillard Reaction
    Max Output Level: 0 dBFS
    • Total Posts : 31918
    • Joined: 2004/07/09 20:02:20
    • Status: offline
    . 2017/03/09 12:35:43 (permalink)

    post edited by Caa2 - 2017/03/11 12:47:50


    #3
    jpetersen
    Max Output Level: -61 dBFS
    • Total Posts : 1499
    • Joined: 2015/07/11 20:22:53
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 18:08:49 (permalink)
    Can you see them in the audio when you zoom all the way in?
    Are they gaps, clipping or waveform inversion?
    #4
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 18:35:38 (permalink)
    It's probably originating in the audio interface. Do you maybe have the clock source set to S/PDIF?


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #5
    konradh
    Max Output Level: -42 dBFS
    • Total Posts : 3325
    • Joined: 2006/01/16 16:07:06
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 19:16:36 (permalink)
    Caa2 mentioned the buffer and that occurred to me.  I set my ASIO buffer really low when tracking to avoid latency, and then high when mixing to avoid noises and other issues.
     
    That said, BitFlipper may have the answer for you.

    Konrad
    Current album and more: http://www.themightykonrad.com/

    Sonar X1d Producer. V-Studio 700. PC: Intel i7 CPU 3.07GHz, 12 GB RAM. Win 7 64-bit. RealGuitar, RealStrat, RealLPC, Ivory II, Vienna Symphonic, Hollywood Strings, Electr6ity, Acoustic Legends, FabFour, Scarbee Rick/J-Bass/P-Bass, Kontakt 5. NI Session Guitar. Boldersounds, Noisefirm. EZ Drummer 2. EZ Mix. Melodyne Assist. Guitar Rig 4. Tyros 2, JV-1080, Kurzweil PC2R, TC Helicon VoiceWorks+. Rode NT2a, EV RE20. Presonus Eureka.  Rokit 6s. 
    #6
    amiller
    Max Output Level: -73 dBFS
    • Total Posts : 876
    • Joined: 2006/01/28 19:54:49
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 19:41:34 (permalink)
    bitflipper
    It's probably originating in the audio interface. Do you maybe have the clock source set to S/PDIF?




    Yep, been there, done that.

    RAWK!!!

    . SONAR Platinum: 2017.10
    System specs:
    Purrrfect Audio:
    http://www.studiocat.com/open_cart/ 
    • Case Silent Mid Tower
    • Power-Supply 600w quiet
    • Haswell CPU 4790k @ 4.4GHz
    • RAM 32GB DDR3/1600
    • OS drive 1TB HD
    • Audio drive 2TB HD
    • Samples drive 1 3TB HD
    • Burner 24x DVD/RW
    • Video HD4600
    • Add TI chipset Firewire For all others
    • Operating System Windows 10 x64 Home Edition
    . MOTU 828 mkII
    . Lucid 9624 A/D
    . Millennia HV-3b pre
    . Dual 24" Widescreen Monitors
    #7
    tlw
    Max Output Level: -49.5 dBFS
    • Total Posts : 2567
    • Joined: 2008/10/11 22:06:32
    • Location: West Midlands, UK
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 21:08:08 (permalink)
    I've always found that clicks and pops related to the audio buffer not being large enough generally end up recorded. And not just with Sonar but other DAWs as well.

    Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
    ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
    Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
    #8
    SvenArne
    Max Output Level: -48 dBFS
    • Total Posts : 2719
    • Joined: 2007/01/31 12:51:29
    • Location: Trondheim, Norway
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 22:37:34 (permalink)
    Thanks for your replies guys!!
    Rob[atSound-Rehab]
    [...] My suggestion would be to see if you can reproduce that after a reboot and possibly also with a new project. If so, get Cakewalk involved. 
     
    I've tried different project files now and it's reproducible as in this is the state of my DAW at this point (cannot reliably do a take more than 20 seconds long with out getting a click)..!

    Also, what's the status with win10 updates? 

    Current!
     
    Caa2
    The only times I have had digital interrupts in my recording I found that using a larger sample buffer worked ok.
     

    ASIO buffer size doesn't seem to matter!
    jpetersen
    Can you see them in the audio when you zoom all the way in?
    Are they gaps, clipping or waveform inversion?

    Square clipping!
     
    bitflipper
    It's probably originating in the audio interface. Do you maybe have the clock source set to S/PDIF?


    Yeah, sync error is pretty much what it sounds like, but the issue arose while recording analog into the BabyFace using the interface clock. I then tried recording through my Audient (connected and clocked via S/P-DIF) but the result is the same!
     
    tlw
    I've always found that clicks and pops related to the audio buffer not being large enough generally end up recorded. And not just with Sonar but other DAWs as well.

    Sorry, but this is not my experience! I've never expected CPU/bus-related hiccups to end up on the audio file. 
     
    Sven





    #9
    SvenArne
    Max Output Level: -48 dBFS
    • Total Posts : 2719
    • Joined: 2007/01/31 12:51:29
    • Location: Trondheim, Norway
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 22:57:40 (permalink)
    Thank's for the replies guys!!

    I made big a post quoting and replying to each and one of you, but it disappeared after editing... So I'm boiling it down since I'm typing on my iPad now...

    -I'm on current Win 10 and the issue is persistent across projects, even running an empty project with only one track.
    -The waveform shows square clipping
    -ASIO buffer size makes no difference, but in my experience such buffer related clicks never get printed to file anyway!
    -Sync error is pretty much what it sounds like, but the problem arose while recording analog into my interface using the internal clock. I later tried recording through my Audient (connected and clocked via S/P-DIF) but that made no difference...

    I think I will try updating the RME driver tomorrow, haven't done that ina while...

    Sven





    #10
    jpetersen
    Max Output Level: -61 dBFS
    • Total Posts : 1499
    • Joined: 2015/07/11 20:22:53
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 23:26:58 (permalink)
    SvenArne
    -The waveform shows square clipping

    So it's in the audio waveform.
    Were you aware of hitting the limit whilst recording?
    Buffer adjustment will fix gapping, but not clipping.
     
    #11
    SvenArne
    Max Output Level: -48 dBFS
    • Total Posts : 2719
    • Joined: 2007/01/31 12:51:29
    • Location: Trondheim, Norway
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/09 23:43:09 (permalink)
    Definitely way below 0 dBFS. The clicks are not amplitude related. Unless I misunderstood your reply?





    #12
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/10 00:08:31 (permalink)
    Take a close look at the waveforms and describe the visual appearance of the clicks. That may provide a clue as to their source. Clocking issues will show up as narrow spikes, dropouts or sudden level changes. Overdriving the ADC may present itself as waveform peaks abruptly going to the opposite polarity. Both can sound the same. The latter is different than overdriving the interface's preamps, which won't result in clicks. The third possibility is buffer overruns due to too-small input buffers. That'll result in pretty obvious dropouts that last a millisecond or two. I guess a fourth (distant) possibility is a broken interface.
     


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #13
    Unknowen
    Max Output Level: -65 dBFS
    • Total Posts : 1276
    • Joined: 2014/11/07 11:27:09
    • Status: offline
    Re: Clicks that actually make it onto the recording! 2017/03/10 02:23:10 (permalink)
    Its a long forgotten option ;) a few weeks ago, and you didn't say what Win ver. you are using but a win 10 update had many reinstalling audio drivers. Also if you're on a laptop you will need to Re Deactivate your onboard sound card.
    *If you uninstall the onboard audio, reboot will reinstall them.
     
    Peace!

    Hay look,
    Somethings are not locked in stone... lol 3/18/2019
    #14
    Jump to:
    © 2024 APG vNext Commercial Version 5.1