Jump to content

Conversion tasks are failing in ffmpeg for recorded shows...any ideas?


jlficken

Recommended Posts

Hi, you customized some server transcoding settings. Try setting these back to default and see if that helps:

Warning EncoderParametersH264LibX.ConstantRateFactor: Original: 23 Actual: 18
Warning EncoderParametersH264LibX.Preset: Original: veryfast Actual: veryslow

 

Link to comment
Share on other sites

Can't actually read it as the things are to small. :)

Can you try something.  Turn off Hardware transcoding so it's using CPU and try a test conversion on a file and let's see what happens.

Link to comment
Share on other sites

jlficken
1 hour ago, cayars said:

Can't actually read it as the things are to small. :)

Can you try something.  Turn off Hardware transcoding so it's using CPU and try a test conversion on a file and let's see what happens.

Did you click on the image as it seems plenty big enough to read to me?

Also, I tried it with Hardware Transcoding disabled and it still failed.  Log attached...

Also, could you request that the Convert screen close once you click on the "Convert" button as right now it just stays open and doesn't give any confirmation that the conversion job has been set up.  I've had people create 10 of the same conversion jobs because there's no confirmation.

 

ffmpeg-transcode-350951ab-7fb2-41d9-a12e-62d7ac20af07_1.txt

Link to comment
Share on other sites

jlficken
8 minutes ago, Luke said:

As a test, you could try turning off hardware transcoding and see if that helps.

Tried that.  The log is in the post above yours.

Link to comment
Share on other sites

4 minutes ago, jlficken said:

13:16:56.269 [mpeg2video @ 0x693140] Invalid frame dimensions 0x0.

or 13:17:14.415 Too many packets buffered for output stream 0:1.

@softworkz do you have any insight on this?

Link to comment
Share on other sites

jlficken
Just now, cayars said:

or 13:17:14.415 Too many packets buffered for output stream 0:1.

@softworkz do you have any insight on this?

 

Yeah that's the one that I initially suspected but I saw the other error as well.

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...
  • 3 months later...
  • 1 month later...

@jlficken - The latest Emby Server Beta includes a new and updated ffmpeg where the error you were experiencing should finally be fixed.

If you don't mind trying a beta version, you could download Beta 4.7.0.6 (or later) and check whether it works for you.

Thanks,
sw

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...