Jump to content


Photo

Transcoding issue on Raspberry PI


  • Please log in to reply
59 replies to this topic

#41 Sock OFFLINE  

Sock

    Member

  • Members
  • 26 posts
  • Local time: 10:11 PM

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 ONLINE  

softworkz

    Advanced Member

  • Developers
  • 2571 posts
  • Local time: 12:11 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
  • 26 posts
  • Local time: 10:11 PM

Posted 21 September 2019 - 01:04 PM

Even after restarting the OS?

 

Correct!



#44 softworkz ONLINE  

softworkz

    Advanced Member

  • Developers
  • 2571 posts
  • Local time: 12:11 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 ONLINE  

softworkz

    Advanced Member

  • Developers
  • 2571 posts
  • Local time: 12:11 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
  • 26 posts
  • Local time: 10:11 PM

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
  • 152765 posts
  • Local time: 06:11 PM

Posted 22 September 2019 - 11:56 AM

Let us know how things go. Thanks.

#48 Sock OFFLINE  

Sock

    Member

  • Members
  • 26 posts
  • Local time: 10:11 PM

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 ONLINE  

softworkz

    Advanced Member

  • Developers
  • 2571 posts
  • Local time: 12:11 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
  • 26 posts
  • Local time: 10:11 PM

Posted 24 September 2019 - 03:06 PM

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



#51 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152765 posts
  • Local time: 06:11 PM

Posted 02 November 2019 - 07:23 PM

@Sock are you still running into this?



#52 Sock OFFLINE  

Sock

    Member

  • Members
  • 26 posts
  • Local time: 10:11 PM

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



#53 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152765 posts
  • Local time: 06:11 PM

Posted 21 January 2020 - 02:37 PM

@Sock are you still having an issue with this?



#54 Sock OFFLINE  

Sock

    Member

  • Members
  • 26 posts
  • Local time: 10:11 PM

Posted 21 January 2020 - 06:23 PM

Hi @Luke, I haven't tried again - I got a new TV recently and have been using the LG app, which works great. I gave it one last try before I disconnected the fire TV (I believe it was the stable 4.3.0.x I tried with) but had no luck. Thanks anyway



#55 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152765 posts
  • Local time: 06:11 PM

Posted 21 January 2020 - 10:40 PM

Ok there's lots of changes in the 4.4 beta so if you ever have a chance to try with that it would be much appreciated. Thanks.

#56 pgalbavy OFFLINE  

pgalbavy

    Advanced Member

  • Members
  • 102 posts
  • Local time: 10:11 PM

Posted 20 February 2020 - 12:16 PM

This may be irrelevant but the RPi can be very hard on, and sensitive to, the microSD card the OS is normally hosted on. Have you checked dmesg for any errors there and/or can you try another SD card with the OS on it?

 

Edit: Even if the transcode temp directory is in RAM!

 

Edit Edit: Another though; Is /tmp actually filling up a a RAM fs ? 


Edited by pgalbavy, 20 February 2020 - 12:18 PM.


#57 adriano_scorpions OFFLINE  

adriano_scorpions

    Newbie

  • Members
  • 1 posts

Posted 20 February 2020 - 08:38 PM

Please delete!


Edited by adriano_scorpions, 20 February 2020 - 09:01 PM.


#58 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152765 posts
  • Local time: 06:11 PM

Posted 24 February 2020 - 06:40 PM

@adriano_scorpions, what I would suggest trying is, mount your SMB network share to a local path using the mounting tools in the operating system. Then add the local path to your Emby library, rather than adding the SMB path directly. Please let us know if this helps. Thanks !



#59 eddiecc OFFLINE  

eddiecc

    Newbie

  • Members
  • 1 posts
  • Local time: 05:11 PM

Posted 28 February 2020 - 06:28 PM

Hi, I've been struggling with this issue for a few months, films that need transcoding (even if its just audio or new container) will start jumping back 1-2s every 10s, just over an hour into the film.

- happened when streaming to an apple tv, as well as to a browser

- also got lots of ffmpeg logs from the time when the stuttering started

- The logs would look normal until the stuttering, when it would show transcoding restarting `ProcessRun 'StreamTranscode 1ed06f' Execute:....` every few seconds. These would be followed by `ProcessRun 'StreamTranscode 1ed06f' Process exited with code 139`, but I also saw that same error further up, before the stuttering started, so not sure if it's related.

- It would persist after restarting emby or rebooting the Pi.

- Tried moving /tmp off the SD card into HDD with no effect

- Also thought it was just too much work for the Pi, but it wasn't running hot, and real video transcoding of short videos works fine.

 

However, I just downloaded the latest beta and it has been working so far, I'll report back if it starts up again. Or let me know if you'd like any more info.

I'm curious if there was a specific fix in there or was it just from updating ffmpeg?



#60 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 152765 posts
  • Local time: 06:11 PM

Posted 28 February 2020 - 10:10 PM

The beta has a lot of new development related to transcoding. Thanks for the feedback.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users