For whatever reason, I’ve started to get “conversion failed” errors again. Graphics Drivers haven’t been updated, and MCEBuddy is running from the command line vs as a service. Logs of the last failure: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Since downgrading to the 4.19 drivers above and running the command line engine, no issues. Thanks! Will.

I just got another - FWIW, if I transcode the file manually, it works fine. Here’s the log: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. I’m wondering if the script I’m using throws errors when it’s invoked from Plex. Here’s the script: @echo off C:\Progra~1\M…

Update - I think I’ve got it solved. Because I already had MCEBuddy running in Command Line mode, the “command=engine --action=start” was erroring out. When I remove that line, it works perfectly. Hope this helps someone :slight_smile:

Or not. Got another failed conversion. Logs: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. I’m stumped. Any help is appreciated!

Your graphics driver appears to be having an issue while initializing. Looks like there’s a memory leak: 2019-07-08T21:11:38 MCEBuddy.AppWrapper.FFmpeg → [hevc_nvenc @ 0000020a974c89c0] OpenEncodeSessionEx failed: out of memory (10) 2019-07-08T21:11:38 MCEBuddy.AppWrapper.FFmpeg → [hevc_nvenc @ 0…

I remembered I’d pulled a dev build of FFMpeg - I tried replacing it with the 4.13 release and haven’t run into any issues yet. I’m running the studio version of the NVidia drivers - they’re supposed to be more stable, but maybe I just need to find a config and stick with it! Thanks for the help!

After getting another round of errors, I downgraded to the NVidia 4.19x drivers - no issues since then. One thing that’s puzzling to me: I’ve run 90+ files through the UI and haven’t run into an issues using the same configuration and drivers. Why would using the UI not express the memory issue, w…

Do you have the link to the drivers so I can put it in the sticky? Did you change the running mode of the engine? The only time you may see a difference is if the engine is running as a service vs as a command line engine. This is because of the way windows starts ffmpeg. In kernel context the grap…

Still getting errors, but I think it might be due to switching back to the service model vs command line. Here’s the link to the legacy driver: NVIDIA Creator Ready Driver | 419.67 | Windows 10 64-bit | NVIDIA

Have you tried using 353.9? Win 7/8.1 - http://developer.download.nvidia.com/compute/cuda/7.5/Prod/local_installers/cuda_7.5.18_windows.exe Win 10 - http://developer.download.nvidia.com/compute/cuda/7.5/Prod/local_installers/cuda_7.5.18_win10.exe OR 376.51 [Bild] Hardware Ac…

Just a FYI note about Nvidia cards and multiple simultaneous conversions: [Bild] Will MCEBuddy use multiple NVidia cards in one server? Hardware Encoding NVidia limits their graphics drivers to only 2 concurrent transcoding streams at a time for most non quadro graphic car…

Erneut „Konvertierung fehlgeschlagen“-Fehler

Allgemeiner Support / Fragen Hardware-Kodierung

Goose (Goose) 13. Dezember 2019 um 13:00 12

Nur ein Hinweis zu Nvidia-Karten und gleichzeitigen Konvertierungen:

Thema		Antworten	Aufrufe
Conversion Failed Hardware Encoding	4	1426	12. Januar 2019
Will MCEBuddy use multiple NVidia cards in one server? Hardware Encoding	8	1448	13. Dezember 2019
MCE Buddy Fails to convert and remove comercials since last stable release Hardware Encoding	3	967	20. März 2019
Intermittent hardware encoding failure Hardware Encoding	16	3402	15. Februar 2018
2.4.9 HW encode Trouble Hardware Encoding	3	2547	15. Oktober 2018

Erneut „Konvertierung fehlgeschlagen“-Fehler

Verwandte Themen