Can't Fast Forward Recordings

[perx 4]

Hi, I'm pretty new to Emby, using Emby and ServerWMC on a Windows 7 pc, and using Android/Chome clients to access.  I've got streaming/viewing Livetv working, and recordings work fine if I don't try to fast/forward or rewind.  But when I fast forward, the stream stops and I get a Playback error.  It seems to be reproducible with Android and Chrome.  I've attached the server and transcode logs, is there a setting I don't have correctly?

 

Cheers.

server-63592409725.txt

transcode-11533219-77ff-4799-9906-2d6f0afd4d38.txt

[DGMayor 90]

http://emby.media/community/index.php?/topic/32012-3058910-no-playback-in-webui-firefox-on-linux/

[Luke 42081]

try turning off quicksync and see if that makes a difference.

[perx 4]

I turned off quicksync and it doesn't fail, but fast forwarding just restarts the video. Should I attach the logs?

[Tester 45]

same exact setup and issue as Perx, foward/rewind do not work on android/chrome/theater.

quicksync OFF

[perx 4]

I attached the logs after QuickSync is off to see if that helps.  Is there some setting I need to be using to enable skip/back functionality of recordings?

server-63592646400.txt

transcode-285a8d4b-20e4-4efa-b6e7-0c6bf3a9a647.txt

[Luke 42081]

the stream coming is not seekable.

http://192.168.1.178:9180/serverwmc.stream/StreamRemuxFile?clientName=Emby%5ePERKINS-HP%5e0: could not seek to position 85.311

@@krustyreturns what do you think? this might be an example of where live broadcasts are better with http, but completed recordings are better with direct file access.

[perx 4]

Thanks for the response Luke, can you advise where that setting is?  Emby, not ServerWMC, right? Is it called something else?

[krustyreturns 191]

That is the default setup for serverwmc and emby:  http is used for live-tv. and file access for recorded tv.  @@perx go to the http tab in serverwmc and make sure you have 

'Use URLs for recorded tv' unchecked (I don't have the wording exact here)

 

Seems kind of drastic to kill the stream if its not seekable, Why not just, not seek?

Edited March 4, 2016 by krustyreturns

[Luke 42081]

Yea you're right. It's not that we're killing it by design, it's that ffmpeg throws an error. Right now we don't really look at what the error is, we just fail it altogether.

[perx 4]

Thank you both for the guidance.  I turned off the 'Use URLs for recorded tv' option in serverwmc and that seems to be the right direction.  I was able to skip forward once successfully.  That said, subsequent skip/back requests had no effect (no error, but no effect).  I attached the logs in case it would help to review.

 

Cheers.

partial_log.txt