Skip to main content
Miguel Salvador
Participating Frequently
January 19, 2023
Question

Error Rendering Selector 17 Error Code 19

  • January 19, 2023
  • 3 replies
  • 3370 views

Error constantly appearing when rendering.

There are someways to turn it around, if it's always a matter of trying again and again, which takes me a lot of time.

 

I even asked for a definitive solution, which they just couldn't give me, saying that it was an issue with the external server I'm using. Besides it was not true - even changing the device, the problem appeared again -, they suggest they blamed the server company (btw, it's a company server, used by hundreds of other people).

 

I guess I'll just have to wait for the next version...

3 replies

Warren Heaton
Community Expert
Community Expert
January 24, 2023

What type of file server is it?  

If you cannot work from a NAS specifically configured for video or a SAN, I'd work locally and copy files over as each project is completed.  If you work from a separate folder for each project where the Scratch Disk settings are all set to "Same as Project", it's pretty easy to put and get entire project folders - especially across a high bandwidth network.

 

Miguel Salvador
Participating Frequently
January 24, 2023

Thanks, I actually already did that - although it is not practical to copy hundreds of gb constantly from one place to another, I think it solves for now...

 

I didn't get what do you mean by "it's pretty easy to put and get entire project folders - especially across a high bandwidth network."

Legend
January 20, 2023

Unfortunately working with media and video editing on a network is not simple and makes demands very different than people trying to access a work processing file or spreadsheet.    This is why Avid still has something of a lock on people needing to work with shared media...    And I know that dealing with IT people is not always easy..  Can you set up your system to render to a local drive connected directly to your workstation to see if that makes a difference.  

Miguel Salvador
Participating Frequently
January 23, 2023

NOT AN IT/SHARED MEDIA ISSUE.

 

Unfortunately, I'm tired of several adobe specialists unsucessuflly dealing with this issue, and blaming it on my system.

Already cheked with my company IT team and there are much more complex programas - like autodesk revit - working well...

I even copied all files to my local pc and the problem maintains.

 

It's clearly an issue with your adobe version!

It's urgent that you solve it!

Legend
January 23, 2023

most of the participants are just users who are trying to help.  Never easy to troubleshoot from a distance.  And the demands a program like Premiere put on a network are very different than a program like autodesk. 

Please tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card.  There may be an issue there...  And could be an issue with the graphics card driver...

Sometimes the renderer in the project settings:general dialog will at least get you over the hump... 

 

Kevin Monahan who moderates this forum and is an Adobe employee.  He said that the error message indicates a video codec problem.  What are your source properties and sequence settings?   Working with heavily compressed formats can cause issues as can combining sources with various frame rates.  Premiere is pretty amazing how it can handle almost anything you throw at it, but sometimes your asking too much of your system.   By any chance are you working with material from a smartphone or screen recording.    If so, the problem can be cause by sources with variable frame rates..

Here's how to diagnose and fix this issue
use mediainfo to determine whether your source is variable or constant frame rate
https://mediaarea.net/en/MediaInfo/Download
if it's variable use handbrake to convert to constant frame rate setting the quality slider in the video panel to maximum
https://handbrake.fr
and here's a tutorial on how to use handbrake
https://www.youtube.com/watch?time_continue=34&v=xlvxgVREX-Y

 

And finally, gotta say my experiences over the years with clients IT departments is that often the culture is about how to deflect blame rather than working to fix the problem.    

Kevin-Monahan
Community Manager
Community Manager
January 20, 2023

Hi Miguel,

Your error is a video codec issue. Can you try changing it to another one? QuickTime > ProRes LT is a common one. Info on how to do so is here.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Miguel Salvador
Participating Frequently
January 20, 2023

That is one of the ways of turning it around - already did that -, but the issue always comes back...