What kind of error is this?

[aler81041643]

Hi, somebody can help me to understand what kind of problem is this [/PPro13.1/releases/shared/adobe/MediaCore/MediaLayer/VideoRenderer/Src/CutlistRenderer.cpp-839]

Premiere crashed several times, even after I unistalled and installed it again

Thanks

[rheaa25815583]

Downgrading the program entirely did help solve it. Thanks for this solution. Would not say it is the best one but it is a good fix for deadlines.

And what aclements said. Adobe, I expected better. @Abode / Nariman Sodeifi

[BlackwoodTennis]

I have the same issue... Ever since the update I can not render. I need to get a few projects done... Has Adobe put out any fixes for this?

This keeps coming up when I try to export... I can render it in the timeline and it works sometimes and sometimes it crashes. After many attempts and finally getting a timeline rendered out I tried to export and this is the message I get every time.... Please ADOBE help!!!!

[ricom48627488]

Please include me in the notification too. I'm working on a project with jpgs in it and it's at the point where Premiere is crashing within seconds of opening. I can't even work on it. Super frustrating.

[jamess22721693]

I'm having a nightmare with this error too... I can't even work on projects. Just crashes... re-opens... crashes! This is NOT GOOD ENOUGH ADOBE!

[/PPro13.1/releases/shared/adobe/MediaCore/MediaLayer/VideoRenderer/Src/CutlistRenderer.cpp-839]

Can you please fix this ASAP???

[sebrame]

Having the same problem with only one project, and it's close to costing me the job which will be $3K. Wonder if Adobe will reimburse??? Just kidding.

At least I think it's the same error - my error dialog box is cut off at '\Src\'

I see on the forum that there is a similar error that started occurring with 13.1 -

/PPro13.1/releases/shared/adobe/MediaCore/MediaLayer/VideoRenderer/Src/RenderFrameRequest .cpp-136

The crash and error message occurs at project startup. The file conform doesn't even complete.

I've noticed that I can create a new project, then import the problem project into it and edit. Then, if I close the newly created project and re-open it, I get the error, along with an 'Input Contract Violation'.

I've also noticed that when I import the problem project into the new one, no file conform is performed, yet when re-opening that new project, file conform starts, and that is when the error throws.

The 13.1.1 patch did not work.

Does not occur on other projects. BTW, these projects were created on Version 13.0.

Steps taken in futility -

Deleted Cache files and Previews.

Trashed Preferences

Changed MPE CUDA to Software Only

System Specs

Asus P6X58D Premium

Core i7 950

24GB RAM

nVidia GeForce GTX 770 4GB (425.31)

Windows 10 Home 64bit

System Drive(OS and Programs) - Crucial SSD 275GB

2nd Drive(Pagefile, Media Cache) - SSD 223GB

Media Drive(Media, Projects Files)  - Internal 2 Disk RAID0(onboard RAID controller) - 2TB

Premiere 13.1.1

[sebrame]

Well, as soon as I posted the above, I had a thought.

Tried running PPro as an Administrator, and the error has stopped occurring.

[sebrame]

Had no further occurrences of the error last night. Then, this morning I just happened to open my 'Graphics' bin, and it happened. At least this narrowed it down. I figured that there was an image or images in there that were causing the error. I moved the graphics folder to another drive, restarted PPro and started relinking one-by one. Got to an Illustrator file and on relink the error occurred. So, I opened that image in Illustrator, saved it out as .ai again with another name, and same thing. The image was an odd size - 100px by 800px, so I tried resizing the canvas to 1920 x 1080, and exporting to PSD, and that worked. Not certain whether it was the canvas resize or the conversion to PSD, but for some reason PPro didn't like that image.

[stevanb36262825]

I had this error, but only when exporting to Media Encoder (the export would freeze and spam this error message). For reference my Premiere Pro worked fine.

My project is heavy with JPG and Push transitions which I've seen referenced in this post so suspect there is a link with that.

If it helps anyone I reverted back to 13.0.4 and cleared the cache which worked.

[denise_sherman]

I have discovered that this issue seems to be related to using legacy titles. For me it would be a big workaround to do the titles another way since I am updating an old project with many legacy titles. Trying a pre-render now to see if this helps.

[denise_sherman]

I managed to get AME to work by pre-rendering (in premiere) the parts of the sequence that have legacy titles. I can't change away from software only render since I don't have any other hardware to render, so that would not have worked for me. It seems that the problem is caused by legacy titles in premiere pro (I have 13.1.2)

[denise_sherman]

The patch does not entirely fix the problem. It still happens with unrendered sequences containing legacy titles.

[johnf3399186]

Tengo el mismo problema, alguien podría ayudarme?

[javierg4648618]

A mí me tiraba el error cuando agregaba archivos .jpg, así que probé cambiar esos archivos por formato .tif y por ahora me funciona...