I’m unfortunately not as lucky, but I’m not sure it’s because of the Subtitle reason. Log is attached, . Totally unqualified to make this call but I think it got into trouble with the following: 2018-02-11T21:47:17 MCEBuddy.AppWrapper.FFmpeg --> Please use -b:a or -b:v, -b is ambiguous Here is t…

Completely unrelated to subtitles. You have a defective recording video stream 2018-02-11T20:52:13 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000021729d1a240] start time for stream 0 is not set in estimate_timings_from_pts 2018-02-11T20:52:13 MCEBuddy.AppWrapper.FFmpeg → [mpegts @ 0000021729d1a240]…

Thanks for looking at this. I have made so many changes to drivers, profiles, etc. since the video was recorded (to successfully do hardware encoding) that I’m not sure that I will be able to solve this mystery. Which is fine because I haven’t seen anything like it in subsequent recordings… A few…

[billede] BrianGGG: Is there anything useful about the error that I listed in my original post (“Please use -b:a or -b:v, -b is ambiguous”) or is this a red herring No consequence, ffmpeg has various types of inputs styles, we’re using an older more compatible one [billede] BrianGGG: I r…

Okay patched this up in today’s 2.4.9 beta build. Give it a whirl.

It’s quite possible that I didn’t understand what this patch would do, but I don’t think that this was successful. Two sample logs are below. I left the default profiles intact when I installed the 2-12 beta, thinking that the algorithm would eventually choose FFMPEG since the ideal case is hardwa…

This patch was to preserve the user selected order of the encoder if more than one encoder supports hardware encoding. In your case both handbrake and ffmpeg support hardware encoding capabilities so it made sure it didn’t reorder your preference. Your profile looked like: order=handbrake,ffmpeg,…

Thanks Goose. This solved the immediate problem. I changed the order, and I have verified that FFMPEG is being used for hardware encoding on my NVIDIA card (which was not the case in 2.4.8). This brings me to a few questions/comments: First…I think I misunderstood what was being done. Preservin…

[billede] BrianGGG: I’m suggesting that it would be ideal if MCEBuddy tried all hardware encoded routes first, followed by software. Yes that’s on our next to do list, this is one a little more complex so it’ll take some time to work out. [billede] BrianGGG: Custom User Profiles could be…

Thanks for the answers. It’s great to know that the “Hardware first” ordering is on the roadmap. Regarding the Custom Profile discussion above, I will put in a feature request because I think that the user profile is an “instead of” file rather than an “in addition to”. My suggestion is that if y…

Do open a feature request, this one is tricky for only one reason. Folks sometimes don’t rename the profile, so now you’ve got two profiles, once from the master and one from the custom, we’ll have to figure out which one takes precedence.

Konvertering mislykkes

General Support / Questions

BrianGGG (Brian) 13. Februar 2018, 20:04 12

I’ll open a separate request. My take on the duplicate issue is that you prefix a “USER_” on anything in the user file. That way “MP4 Normal” in the official Profile file will be separate from “USER MP4 Normal” in the User file.

Emne		Svar	Visninger
Hardware decoding failure due to invalid parameter Hardware Encoding	9	5718	18. December, 2023
2.4.9 HW encode Trouble Hardware Encoding	3	2513	15. Oktober, 2018
WMV High Profile - possible syntax error? Profiles	3	946	15. Oktober, 2017
2.4.8 Beta looks like FFMPEG is choking on me Video Stops Audio Continues not sure h.264 WMC Hardware Encoding	6	1778	19. November, 2017
Conversion Failed Hardware Encoding	4	1364	12. Januar, 2019

Konvertering mislykkes

Related topics