anulação de tentativa de substituição de dados após várias tentativas

[marcusmendonca65]

Estou com problemas em renderizar o video desde a ultima atualização da versão, está dando o erro de anulação de tentativa de substituição de dados após várias tentativas, antes da atualização estava perfeito, isso está me impedindo de trabalhar. Ja tentei mudar para mercury saindo de cuda, mas mesmo assim continua o problema, estou com videos para entregar ao cliente e nao consigo de forma alguma trabalhar, estou com um note com placa Nvidia 4050 e processador Intel Core I7 e 16 gigas de Ram.

[Ann Bens]

Green frames usually indicate an issue with the gpu.

Make sure you have installed the most current nvdia studio driver.

[marcusmendonca65]

Yes I did, it was running ok until I updated. Now I received this error using media encoder.  - Arquivo de origem: C:\Users\marcu\AppData\Local\Temp\Asserpro-Rj Podcast_1.prproj
- Arquivo de saída: D:\Videos Canal\assespro-rj\04-12-24 - Marcos Neme e Professor Marco G10\Podcast 11 Assespro Final.mp4
- Predefinição utilizada:
- Vídeo: 1920x1080 (1.0), 23.976 qps, Progressivo, 203 (75% HLG, 58% PQ), Codificação de hardware, Nvidia Codec, 00:46:48:22
- Áudio: AAC, 320 kbps, 48 kHz, Estéreo
- Taxa de bits: CBR, Destino 11.14 Mbps
- Tempo de codificação: 00:08:40
12/09/2024 01:45:22 PM : Falha na codificação
------------------------------------------------------------
Anulação da tentativa de recursão de substituição de dados após várias tentativas no arquivo: D:\Videos Canal\assespro-rj\04-12-24 - Marcos Neme e Professor Marco G10\cam direita\REC_0001.MP4
Inserção de preto para o número de quadro 11620

[marcusmendonca65]

When I cleaned the cache I made the edit without problem, but when I started to export I received that error that I sent here.

[marcusmendonca65]

[Averdahl]

Don´t use the Game Ready driver, use the Studio Driver just as Ann wrote earlier. 

When you install, choose to do a clean install. 

By @marcusmendonca65

[marcusmendonca65]

Always worked with game ready, for many years, it's now a problem?

[Averdahl]

There has always been issues with the Game Ready driver, hence the recommendation to use the Studio Driver.

Always worked with game ready, for many years, it's now a problem?

By @marcusmendonca65

[marcusmendonca65]

doing the test now, but apparentilly will perform in the same way.

[marcusmendonca65]

Now 1 hour and 25 minutes and increasing, normally renders in 8 min

[marcusmendonca65]

Same error, even using studio drivers, stops at 12% and then give the error and starts to increase time, this started since the last \Adobe Update, before that was working withou problems. 

[marcusmendonca65]

[marcusmendonca65]

[Averdahl]

• What Premiere Pro version do you have, version and build number?
• What media do you use, what camera/s?
• Is it 1080 or 4K, or?
• What export settings do you use?
• Does it work if you export to ProRes LT? (Probably not but worth testing...)

As a test, what happens if you create a brand new project and import one of the source files that cause issues and place it on a matching timeline and export it? Same errors or none error?

[marcusmendonca65]

1) Adobe Premiere Pro 2025 

2) This is a Podcast in the 11th edition using the same camera and rendered in Adobe Premiere, Meevo (1080+)

3) 1080+ MEEVO

4) It's the 11th time that I used this export settings, first time with problem.

5) same problem

[Averdahl]

Thanks!

It seems that Pr 25.1 has issues with that footage so there is more or less two solutions.

The first is to stay in Pr 25.1 and use a third party app such as the free app Shutter Encoder - Encoder|Converter video FREE PC|Mac and either transcode the footage to another codec such as ProRes LT (or mp4) and use that as the source footage. Or, test to use Shutter Encoder to Rewrap the footage. This will create a brand new file lightning fast that you can use as your source file. Rewrapping mp4 files do often solve similar issues and since it is fast it´s worth trying first.

The second is to downgrade Premiere Pro to a version you know worked before. This can be cumbersome since one cannot open new projects made in Pr 25.1 in let´s say Pr 24. It is possible to export new project as xml and import that one in the older version of Pr, but some effects etc can be missed.

Regarding the render settings you provided, i would drop Render at Maximum Depth and Use Maximum Render Quality. They will not fix the errors, but it will decrease the render time. Both setting will not increase the quality from the cameras you have.

Do you by any chance have a file from that camera you can upload? It can be a short clip, maybe 1-2 minutes, filming the wall. It would be intersesting to test it out. You can send it via PM if you want.

1) Adobe Premiere Pro 2025 

2) This is a Podcast in the 11th edition using the same camera and rendered in Adobe Premiere, Meevo (1080+)

3) 1080+ MEEVO

4) It's the 11th time that I used this export settings, first time with problem.

5) same problem

By @marcusmendonca65

[marcusmendonca65]

This is a very complex project with many folders, captions and etc. So its is very dificult to export as a XML and import to previous version. In other case I'll try thew other solution that you recomended.

[Averdahl]

Thanks, that clip works here without issues.

Question:

That clip is 30 fps and i wonder why you are export is as 23.976 fps? For 30 fps footage, use a 30 fps timeline and export as 30 fps.

This is a very complex project with many folders, captions and etc. So its is very dificult to export as a XML and import to previous version. In other case I'll try thew other solution that you recomended.

By @marcusmendonca65

[marcusmendonca65]

I wil try another thing, I used multicam view, as I used in other projects here, I will try the old fashioned way to see if it will work, cut manually each clip.

[marcusmendonca65]

Apparentelly it's is working, the problem on this version, unfortenatelly resides on Multi cam view edition. Need to fix as soon as possible, this feature is very important. 

[marcusmendonca65]

found the problem, resides in one video, but something was wierd, other softwares like capcut were enabled to read and decode, but premiere didn't, and after I used the software to convert to MOV the export worked fine, but veru weird this behavior, because other softwares read it and processed without any trouble.

[Averdahl]

Great that it worked out!

Premiere Pro demand files that are flawless so a minor issue with the file do cause issues. Software players such as VLC, etc often playback those files without any issues.

...but veru weird this behavior, because other softwares read it and processed without any trouble.

By @marcusmendonca65

[marcusmendonca65]

[Kevin-Monahan]

This may be related to an Intel iGPU driver. If you have an Intel CPU and are having issues, check out the settings for the Intel GPU, not the NVIDIA one. See if this discussion helps: https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-25-1-igpu-stopped-decoding-my-f.... Let us know, please.

Thanks,
Kevin

[carlos_davi_5216]

eu estou com esse problema  no adobe premier alguem pode me ajudar?