Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Pro CC audio defaulting to “nan” db

  • Premiere Pro CC audio defaulting to “nan” db

    Posted by Rob Davis on July 31, 2013 at 1:15 pm

    here’s a strange “bug” that has reared its ugly head.
    After updating to 7.0.1 many, although not all audio settings are defaulting to “nan” db.
    It has happened to dozens of files, they can be movs, mts, or mpg.
    When they reset to “nan” db, the waveform representing levels in clips in the timeline simply flatline.
    I must adjust the levels to 0 db, match to clip, then drop into timeline.
    I can be working with no problems for many hours, saving, closing proj, closing app, opening app, working fine, then without warning, I’ve lost a days work. Bringing back earlier attic saves (ex Avid editor of 20 years) does not resolve the problem, the audio seems to be permanently “nan” db.
    I rolled back to 7.0.0, this did not help.
    I have lost 2 weeks in trying to get on top of this problem.
    The files themselves are fine, I’ve been using them for many weeks, until 13 days ago when things went pear shaped.
    I’ve spend many hours on the phone to Adobe, tried all the usual things, cache cleaning, Quicktime codecs moved, transcoded footage, but still no joy.
    I’ve not loaded any apps that could influence this.
    I’ve moved files to a portable drive and loaded onto my MacBook Pro laptop, and the levels are still “nan”db so I don’t believe the problem is computer based
    Anyone out there with this strange “bug”

    thanks in advance
    Rob

    Ben Helweg replied 11 years, 3 months ago 6 Members · 7 Replies
  • 7 Replies
  • Tim Kolb

    August 8, 2013 at 1:10 am

    Do you typically power down the computer and then have this happen, or does it happen during a day’s session when the computer hasn’t been power-cycled? Does the audio ever load properly after the computer has been power-cycled? It sounds like it could be Premiere Pro not getting access to its media cache files at the point it goes south. Sometimes it’s a strange drive permission/user account thing…I’ve heard the issue primarily from Mac users.

    If you moved the project however, I would think that Premiere Pro would be creating new cache files to replace the ones it can’t find.

    Odd.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Thomas Roebers

    November 11, 2013 at 10:47 am

    I am having this problem two and it seems to be quite serious…… After every restart of the project the audio is set back to NAN, and sometimes i have to just click the audio file and it works again…. Than after a while when i restart the project the audio is flatlined and seems to be gone al together…. Relinking didnt work and double clicking didnt work. I can replace the audio manually but after restarting the project its the same all over. Feels buggy and unsafe. Already redid the syncing in plural eyes and rebuild the entire project. Seems to be ok at first and the the problem appears… Could it be plural eyes? the casche? Been spending days already…. Need to really get to work but can’t…

    Also the image was gone and came back when removing all filters while i didn’t put any.

    please help!

    premiere pro 7.1
    plural eyes 3.1
    prorees materiall synced to wav audio
    Mac Pro 2010 mavericks

    excuse my English, thomas from Amsterdam Netherlands.

  • Michele Vee

    January 3, 2014 at 11:16 pm

    Help needed as well…same thing is happening to me…no audio waveforms on clips (though there was the last time I opened project); everything set to “nan”…even if you reset, rebuild, repaste attributes, restart still goes back to NAN. Made new proj & imported sequence–same thing…no audio playback just crackle here & there.
    Did you ever find a fix?
    Thanks,
    MV

  • Kara Herold

    January 4, 2014 at 3:26 am

    I am having this same problem.
    Let me know if you get any help.
    kara

  • Michele Vee

    January 6, 2014 at 11:09 pm

    Hi Kara:
    I spent 2 hours on phone w/Adobe. The support tech took remote control of my computer & it was a looong night–a lot of circuitous things transpired and was difficult to follow many of the steps. So, someone more expert with After Effects & PP than me would able to clarify what I’m going to try to explain. Basically, when I copied some audio levels and pasted their attributes on to other clips, something became corrupt. Thus no audio playback no waveforms, etc.
    So, he exported an FCPxml and opened it AfterEffects and then exported the sequence out of AE. He also did something with the audio because I saw an “extracted audio clip” created. But I’m not sure of the purpose or if this was useful in the end? The goal was to get a clean sequence back in Premiere (in a new project) and “Remove Effects” from all audio clips. That worked. Even though I had removed all effects from my audio in the first place, it was apparently too late in the corruption process so it just ignored me. In the end, I wound up with a sequence that has good audio but the playback & reaction time of the interface is much slower…so I know something is probably still not healthy, but I just need to get this project out the door and hopefully new projects will be okay. Very scary to lose a day of work running in circles on a deadline. Long live FCP 7:) Hope any of this is helpful.

    MV

  • Kara Herold

    January 6, 2014 at 11:14 pm

    Yikes, yes, long live Final Cut 7! Maybe someone from Adobe will take me up on my offer to meet in person!

  • Ben Helweg

    January 28, 2015 at 6:29 am

    If anyone out there is having this issue, I’d like to share how I worked around it.

    We were having trouble with a project that seemed completely normal, but no sound would play in any form.
    There was nothing in the mixer or project/sequence settings/renderer that would work it out.
    On a different workstation the same result was had.

    We sent the sequence out in XML, re-ingested into a new project and discovered that all the audio clips had an extra track volume filter and had ‘nandB’ listed for the volume.

    After creating a new sequence with a working video clip at the beginning, dropping in contents of the faulty sequence after it and deleting EVERY instance of nandB, did it finally start producing sound.

    I noticed that if you had multiple clips of audio on different tracks playing at the same time, if even one had ‘nandB’ on it, they all wouldn’t play and this was discovered after I realised our music track also had the nandB on it.

    Solved the problem for now, but doesn’t explain why it happened in the beginning, and why the video crossfades we had needed the renderer to be switched too…

    tl;dr – send your sequence or project via XML to a new project + sequence with working audio, delete all traces of volume filters displaying ‘nandB’.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy