Jump to content


Photo

Transcoding issue on Raspberry PI


  • Please log in to reply
51 replies to this topic

#41 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 21 September 2019 - 10:58 AM

Ah ok, this is something I've already tested in a way!

 

The issue with transcoding doesn't only when transcoding has been running for 1h. It also occurs if the media starts stuttering, I stop it, (+ optionally restart the server/clear temporary files) and then resume. 

 

When I resume and it's ~1hr in, you get exactly the same stuttering. And the number of files at that point can be very low (in the 10s for example) so shouldn't be hitting that limit



#42 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 06:05 AM

Posted 21 September 2019 - 11:40 AM

The issue with transcoding doesn't only when transcoding has been running for 1h. It also occurs if the media starts stuttering, I stop it, (+ optionally restart the server/clear temporary files) and then resume. 

 

When I resume and it's ~1hr in, you get exactly the same stuttering. And the number of files at that point can be very low (in the 10s for example) so shouldn't be hitting that limit

 

Even after restarting the OS?



#43 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 21 September 2019 - 01:04 PM

Even after restarting the OS?

 

Correct!



#44 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 06:05 AM

Posted 21 September 2019 - 03:25 PM

And in the stuttering case you're always seeing lots of ffmpeg logs generated while it's just a single (long) ffmpeg log when it's working?



#45 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 06:05 AM

Posted 21 September 2019 - 04:14 PM

Those ffmpeg processes are always crashing returning error code 139 (which means SEGFAULT).

Unfortunately I got no idea why.



#46 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 22 September 2019 - 04:54 AM

And in the stuttering case you're always seeing lots of ffmpeg logs generated while it's just a single (long) ffmpeg log when it's working?

 

Yes, exactly.

 

 

Those ffmpeg processes are always crashing returning error code 139 (which means SEGFAULT).

Unfortunately I got no idea why.

 

Sounds like installing the beta with the newer ffmpeg version is the best bet then.



#47 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140105 posts
  • Local time: 12:05 AM

Posted 22 September 2019 - 11:56 AM

Let us know how things go. Thanks.

#48 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 23 September 2019 - 04:27 PM

@softworkz I just upgraded to the Beta server (4.3.0.9) but still seeing the same behaviour I'm afraid  

 

I've uploaded a sample of the logs in case that's useful, but looks like the same as before to me. 

Attached Files



#49 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 06:05 AM

Posted 24 September 2019 - 02:50 PM

Unfortunately I'm running out of ideas. The current installation doesn't allow testing ffmpeg commands from the command line, and we don't have any diagnostic options in the server yet, which would allow to try some more things. I hope we will have better ways for diagnosing problems in the future.



#50 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 24 September 2019 - 03:06 PM

Doh, ah well. Thanks for investigating - I appreciate the effort!



#51 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140105 posts
  • Local time: 12:05 AM

Posted 02 November 2019 - 07:23 PM

@Sock are you still running into this?



#52 Sock OFFLINE  

Sock

    Member

  • Members
  • 25 posts
  • Local time: 05:05 AM

Posted 03 November 2019 - 08:59 AM

Hi @Luke, yes, just double checked and still seeing this with the latest Beta unfortunately (4.3.0.18). I basically have had to stop using emby with the Fire stick because of this

 

Luckily I twigged that the Xbox one app doesn't have the issue, as it rarely has to transcode






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users