Getting "A corrupt audio region was detected and padded with silence" message

Author
twisted6s
Max Output Level: -55 dBFS
  • Total Posts : 2001
  • Joined: 2007/08/21 21:10:33
  • Location: New York
  • Status: offline
2017/05/12 01:41:23 (permalink)

Getting "A corrupt audio region was detected and padded with silence" message

I get this message when opening a one specific project. But I can't locate the clip or "region" in question. All my audio files have the waveform drawn, there are no clips with just a line. The project is only 1:08 minutes long with only nine tracks of audio and about the same number of midi tracks. I wonder why Sonar doesn't tell you which clip or track this corrupt region is in. Anyone having a similar issue?
post edited by twisted6s - 2017/05/12 10:43:54

Core 2 Quad Q9650 3.0 ghz processor, 8 gig ram, 2.5Tb drives, Sonar Platinum, Lynx L22, FMR Audio RNP & RNC, Mackie HR824, Neumann tlm 103, Window 10 64
https://soundcloud.com/twisted6s/sets/tony-pruden

 
      
#1

4 Replies Related Threads

    andy_grahammer
    Max Output Level: -90 dBFS
    • Total Posts : 40
    • Joined: 2015/03/30 10:37:22
    • Location: Germany
    • Status: offline
    Re: A corrupt audio region was detected and padded with silence 2017/05/12 02:55:47 (permalink)
    Habe you checked the take lanes? Mabe the corrupted clip is under another clip and is hidden. Happend to me once.

    Sonar Platinum x64 - 23.8.0 BUILD 30 [2017.08]
    Windows 10 x64 (10.0.10586.633)
    Intel Core i7 4th gen 3.33 GHz
    16 GB Ram
    Roland Studio Capture UA-1610
    #2
    andy_grahammer
    Max Output Level: -90 dBFS
    • Total Posts : 40
    • Joined: 2015/03/30 10:37:22
    • Location: Germany
    • Status: offline
    Re: A corrupt audio region was detected and padded with silence 2017/05/12 02:59:55 (permalink)

    Sonar Platinum x64 - 23.8.0 BUILD 30 [2017.08]
    Windows 10 x64 (10.0.10586.633)
    Intel Core i7 4th gen 3.33 GHz
    16 GB Ram
    Roland Studio Capture UA-1610
    #3
    twisted6s
    Max Output Level: -55 dBFS
    • Total Posts : 2001
    • Joined: 2007/08/21 21:10:33
    • Location: New York
    • Status: offline
    Re: A corrupt audio region was detected and padded with silence 2017/05/12 10:42:45 (permalink)
    Hi Andy, I didn't use take lanes and I'd already seen the link above my friend. No success😞

    Core 2 Quad Q9650 3.0 ghz processor, 8 gig ram, 2.5Tb drives, Sonar Platinum, Lynx L22, FMR Audio RNP & RNC, Mackie HR824, Neumann tlm 103, Window 10 64
    https://soundcloud.com/twisted6s/sets/tony-pruden

     
          
    #4
    bvideo
    Max Output Level: -58 dBFS
    • Total Posts : 1707
    • Joined: 2006/09/02 22:20:02
    • Status: offline
    Re: A corrupt audio region was detected and padded with silence 2017/05/13 20:44:39 (permalink)
    There could be other audio data that is known to the project but doesn't appear on the time line. For example, slip-edited clips could represent audio data somewhere in the middle of a file, where the "corrupted" part of the file has been trimmed away from the track. Also, tracks that have been frozen have audio files standing by for unfreezing that doesn't show on the track.

    W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1