Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro export error message / unable to create audio renderer

  • export error message / unable to create audio renderer

    Posted by Tom Adams on July 28, 2016 at 2:27 pm

    Not sure what’s going on but this just started happening with the new pp 2015.3 update…

    I’m thinking there must be something ‘wrong’ with the files that I downconverted from 1920 to 1280 in wondershare converter ultimate before I added into project … ?

    Leigh Miller replied 8 years, 7 months ago 8 Members · 9 Replies
  • 9 Replies
  • Ann Bens

    July 28, 2016 at 6:18 pm

    Why do you want to use Wondershare?

    ———————————————–
    Adobe Certified Expert Premiere Pro CS6/CC
    Adobe Community Professional

  • Jon Doughtie

    July 28, 2016 at 6:21 pm

    This may or may not resolve it, but try clearing all cache files.

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2015.02 (as of 6/2016)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from HD MP4 and P2 MXF.

  • Tom Adams

    July 28, 2016 at 7:19 pm

    the footage was shot in 1920 but, as I often do, I use wondershare to downconvert to 1280 before I bring into premiere because the video ends up going to dvd or more often- a very small window on a website. I have a 2008 mac desktop that can get a little finicky with with multiple layers of 1920 files but has no problem with 1280…

  • Tom Adams

    July 28, 2016 at 7:22 pm

    I tried clearing cache and preview files…and a whole bunch of other stuff…but what finally actually worked was changing the project file name and the sequence name… it turns out there were ” / ” marks because the file name had a date in it… and apparently this was the problem. I removed any strange punctuation and the problem was solved, exported just fine…

    must be a bug with the new update not liking some characters because I have dates in my file names before, many times…

    and onward we march….

  • Brad Sheffield

    September 26, 2016 at 11:51 pm

    I’m actually having same issue, but clearing cache and naming generic aren’t working to fix problem for me. I actually have a high school lab full of computers that this issue is occurring on nearly 75 percent of the machines. If my students remove the audio file, it exports just fine. Have never seen anything like it and can’t get any of my students’ projects to export. Please help…

  • Lee Lester

    November 1, 2016 at 9:47 am

    I had the same problem – the issue was that my sequence audio setting was 48000 Hz and my audio track was 44100 Hz – changing the sequence settings to match solved it!

  • Eric Bacus

    April 30, 2017 at 4:08 pm

    I know this is an old thread, but just FYI, I ended up saving the project to my desktop and then exporting to my desktop and it finally bypassed the error. One of those “If it’s stupid but it works, it’s not stupid” things…

  • C.v. Kalyan kumar

    July 16, 2017 at 8:40 am

    I Love you Bro!! It worked. I tried everything before this. Cleaned my media cache, changed by audio bitrate and nothing worked. Then I saw your post and I thought what the heck let me try saving the project file to my desktop and rendering the video in my desktop. And it worked like magic!! Thanks a Ton!!!!!

  • Leigh Miller

    September 19, 2017 at 12:50 am

    Check your naming conventions if all else fails!

    Had to login to lend my experience with the same issue.

    I was getting “Export Error Unable to create audio renderer.” Which was no help at all for the actual issue, and in-fact had me looking in the work direction for ages.

    I had named my project file through finder, not when saving out from premiere, which had a ” / ” in it. I opened and worked on the file no issue but then couldn’t render.

    Only when I was trying all these steps did I create a new project and try and save and name it through premiere did it tell me you couldn’t use certain characters.

    Good times.

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