Skip to main content
Inspiring
November 27, 2016
Answered

Error when exporting 4K video as HD

  • November 27, 2016
  • 7 replies
  • 5992 views

I have projects with 4K mxf files that I am putting in a 1080p sequence. I am basically dropping the files into a sequence no edits or anything. They render fine at 1080P on my surface pro book and macbook pro. I decided to get a new desktop (MSI gaming computer, 7Gen intel chip, GTX 1080). Now I am having major problems. First the previous project wanted to create new peak files. Searched the forums and turned off generate audio waveform in preferences. Still could not render files (got error message). The clips will play on timeline for a few seconds and then they stop playing. Tried turning off intel acceleration and that didn't help. I can't even render video by creating a new project and add one mxf file to my sequence timeline. When I go to render I get an error message. Does premiere pro not work with the latest 7th generation chips? I also am having the same problems with clips from my Samsung NX1.

Changed title to more accurately reflect issue

    This topic has been closed for replies.
    Correct answer kitzj0

    Thanks for looking into it Jim! Last night reading through the MSI forums, someone had a problem playing 4k files. They thought the problem was from installing the updated NVidia drivers using their Geoforce application. So I did a fresh install of Windows again, installed only the driver from NVidia. Now I can export the mxf files properly. It is weird I only was having a problem with 4K xmf files and not the others. The exports are really fast.

    I appreciate everyone looking into my problem.

    Joe

    7 replies

    kitzj0AuthorCorrect answer
    Inspiring
    December 5, 2016

    Thanks for looking into it Jim! Last night reading through the MSI forums, someone had a problem playing 4k files. They thought the problem was from installing the updated NVidia drivers using their Geoforce application. So I did a fresh install of Windows again, installed only the driver from NVidia. Now I can export the mxf files properly. It is weird I only was having a problem with 4K xmf files and not the others. The exports are really fast.

    I appreciate everyone looking into my problem.

    Joe

    Bill Gehrke
    Inspiring
    December 5, 2016

    What specific nVidia driver version are you using for your GTX 1080?

    kitzj0Author
    Inspiring
    December 2, 2016

    Had better luck with chat tonight. I was on for over 90 min. The guy took over computer. The problem appears to be the GPU (GTX 1. He seems to think it will be fixed soon. I need to render without using the GPU. For now need to use MacBook Pro/ Surface Book because the render times without using the GPU are beyond astronomical.

    Brainiac
    December 2, 2016

    The problem appears to be the GPU

    I'm skeptical of that.  Like I said, I'm having no issue exporting with the 1070.

    What's your hard drive setup?  What software do you have installed besides the Adobe suite?  (List them all.)

    kitzj0Author
    Inspiring
    December 3, 2016

    Hi Kitz,

    I shoot in 4k and then place them on my 1080P sequence. Before the clean install I put some 4k footage from my Canon 5D mark IV on a 1080 sequence and the 3 minutes of clips exported fine.

    Interesting. The detected source in the error dialog box says the sequence settings is at 1440 x 1080 with non-square pixels. Why are you not using a 1920 x 1080 sequence with square pixels for your 4K footage?

    One thing I'd try is to ingest the 4K footage with proxies, cut the sequence with the proxies, output a 4K master, then create H.264 copies from the master.

    I don't usually export 4K footage scaled down in HD sequences, especially if they have GPU accelerated effects. With these processes (scaling, effects, and non-square pixels in your case), you are greatly taxing the GPU which I feel can upset the export process. 

    My feeling is that it's not the hardware or software, it's your workflow. It's somewhat non-standard and not optimized, in my opinion.

    Thanks,
    Kevin


    That was an error on my part with the sequence settings. However, I have corrected the sequences settings and have been able to replicate this issue several times. The Adobe chat representative looked through all my settings when he had control of my computer. I specifically asked if it was the computer or user error and he said the GTX 1080 has been problematic.

    I will try and see if using proxy files helps. I appreciate your input and suggestions Kevin.

    kitzj0Author
    Inspiring
    November 30, 2016

    Thanks Jim

    I think I might try and restore to Premiere Pro 2015 and see if that works for now. I have thought about starting fresh like you suggested.

    kitzj0Author
    Inspiring
    December 1, 2016

    I did as you suggested Jim, re-installed windows from scratch to  no avail. I am now into day 6 of wasting my time. Last night I did Adobe support chat. I gave the guy control of my computer. Premiere Pro 2017 wanted to generate the peak files and after a few minutes he gave up. Told me it was taking too long and to restart chat when it finished. So I restarted chat and the guy asked for my adobe credentials and then he immediately left our chat. This after waiting several minutes to get a live person.

    kitzj0Author
    Inspiring
    November 30, 2016

    I am wondering if I should take my computer back and try something else? Or is this an adobe issue? Seems like a few are having issue compiling. I have wasted 4 days trying to fix this issue to no avail. I can't export anything and am beyond frustrated.

    Brainiac
    November 30, 2016

    I just installed a 1070 into one of my machines.  A project created in an earlier version exported fine from 2017.0.1 without any issues.

    One thing you might try is starting fresh.  Purchased computers normally come with stuff installed that you may not want on a production machine, so I find it best to wipe the C: drive and reinstall Windows from scratch.

    kitzj0Author
    Inspiring
    November 29, 2016

    Thanks Jim,

    The problem isn't just with that one clip. I have the same issue with all previous projects I open, regardless of whether they contain .mxf, h264, or h265 videos. I can now start a new project, add a clip and export h264 clip. However, sometimes it takes a few tries at exporting before the export is successful. If I add a 2 min clip, the render will get through 50-75% of the export and then I get the same error. I try again and eventually it goes through the export process. All these clips and projects export fine on my surface book and macbook pro (windows 10). I bought a new desktop because I thought the GTX 1080 and faster processor would speed up the export process. I keep the NVIDIA drivers updated on all my computers.

    Brainiac
    November 27, 2016

    Give this a read.  It'll show what details we need.

    How To Ask For Help

    kitzj0Author
    Inspiring
    November 27, 2016

    Thanks Jim

    COMPUTER INFO

    • OS: Windows 10
    • Processor: Intel Core i7-6700k CPU @ 4.00GHz
    • Installed memory: 16.0 GB
    • System type: 64-bit Operating System, x64-based processor
    • Graphics Card: GTX 1080

    HARD DRIVE INFO 256GB SSD

    • Premiere Version: Premiere Pro CC 2017.0.1 v11.0.1 v6
    • Footage: PXW-z150 4K 3840x2160 50GB 51 min xmf format
    • TRT of timeline: 51 min
    • All production audio files are on a separate drive as the footage
    • Current project file size: 39 kb

    FAILED FIX ATTEMPTS

    Turn off accelerated intel h264 decoding in media preferences

    Turn off generate audio waveforms

    Media Cache database hit clean

      

    This is the error I get when rendering using h264 1080P setting with CBR set to 30

    kitzj0Author
    Inspiring
    November 27, 2016

    I can't even create a new project with new sequence and add clip onto timeline. I get the same error message and failed rendering. These clips will only play for a few seconds on my timeline before they start to stutter and not play. These files all played and renderered well on my surface book and macbook pro. I would have thought they would be even better on a new system.