Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
3

Error Compiling Movie I/O Error Selector 17, Error Code 14

New Here ,
Aug 02, 2023 Aug 02, 2023

Hello.

We've seen a number of systems hit with this error / issue recently when working on a particular project. Devices are able to edit and export other pieces of work fine, even export the same project successfully using different settings / presets. 

The preset we are trying to use chiefly consists of the following:
- MXF OPA1

- 1080p 

- 25fps | Upper

- 4 Channels of Audio

 

We believe it to be an issue with the content as a result of the above. We've seen consistencies with the timecode stated in logs that come back from Media Encoder (which we have been sending the exports to - but the issue persists using Premiere Pro as the sole exporter), but adjusting these suggested timecodes does nothing. 

 

It is a 6 episode series, and the issues have affected each one. We've tried amending the Seuqence Settings (Preview File Format switched from AVC to I-Frame only), exporting / rendering the aforementioned timecode areas first. Nothing seems to work. We're going to attempt to 're-wrap' the content, but I just wanted to check if this was common? I couldn't find anything specific for it online. 

 

It is also worth mentioning the primary machine we tested (before using others) has 128GB of ram (supposedly only using 10 so far as per Task Manager) - 300GB+ of free space to export to. It is a Windows 10 build, with everything up-to-date. 

 

Thank you.

TOPICS
Crash , Error or problem , Export
3.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Aug 03, 2023 Aug 03, 2023

Hi @Matt27801243432x,

I read your post. This is a "File I/O" Error Code. The advice is to delete disk space or choose a drive with more space. You also might check if a different HD might work for you. You may have issues with your current drive, even though it appears to have enough space. Drive initialization or corruption might be culprits. I hope that troubleshooting along these lines helps narrow down your problem. Let us know how it goes.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 06, 2025 May 06, 2025
LATEST

I was just working on a project off of an Amazon 256 GB thumb drive. It was a simple 10 minute project and so everything seemed to be working fine. After rendering about 75% of the project I kept getting an this and other errors. Just for giggles I tried rendering to a different drive and it rendered out fine. I then tried to copy that file back to the Amazon thumb drive it is gave some bogus error about the drive not being able to handle that size of file. There was over 80% of the drive still empty so the 5 GB rendered file would physically fit, but for some reason the drive was baulking at the size of the single file. I didn't know that was a thing, but that explains why the error kept coming up. I suspect that as the file was being created once the file size hit that limit, it forbade any more writing to the compiled file. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines