Fast forward gets stuck

[Mo3bius 0]

Hi,

when I fast forward the video, it gets stuck sometimes. If that happens, I can press start/stop and nothing happens. If I go back to the main menu and start it again, it works again.

I am using Firefox for video playback and hardware acceleration with a  nvidia 710 gt .

I dont see any problems in the logs except that it suddenly stops. So the line does not end properly. Something like: "21:20:12 [segment" and thats it.

[Carlo 4561]

If you are transcoding and FF are you waiting to give your 710 a chance to finish what it was working on and then prepare new segments at the point you just FF to?

[Mo3bius 0]

I encounter this problem with clicking to a random part of the video or ff with the arrow key. If I use the arrow key (right), I wait for the picture to appear and I hear the sound of the video. If I dont think I skipped enough, I skip again. So the skipping could be fast, but not faster than I see the result of the skip.

 

[Carlo 4561]

I think to dig into this we would need to see a specific example and have some log files to look at.

 

[Mo3bius 0]

Here are the logs for the timeframe. the embyserver.txt is shortened.

embyserver.txt ffmpeg-transcode-eed8cead-5ece-4fc6-ae2c-befb5f9dc31d_1.txt

[Mo3bius 0]

I checked the browser console. It just could be this:

 

HLS Error: Type: mediaError Details: bufferFullError Fatal: false

 

[Mo3bius 0]

Any news on this?

 

My best guess is that the frame buffer is not cleared fast enough by emby. So by skipping, I am just adding data until it is full. Other big commercial platforms like Netflix or Youtube seems to not have this problem so there must be a way around it. Maybe only load the new data after the old one is cleared?

[Luke 42086]

@Mo3bius we are looking into it. Would you mind trying our online web app and let me know how that compares?

http://app.emby.media

Thanks !

[Mo3bius 0]

The app had the same problem.

 

Did you change something in the last releases? (The release notes did not mention it).

 

I don't have this problem any more! So for me it is solved although no idea why.

 

[Luke 42086]

5 hours ago, Mo3bius said:

The app had the same problem.

 

Did you change something in the last releases? (The release notes did not mention it).

 

I don't have this problem any more! So for me it is solved although no idea why.

 

Thanks for the feedback.