[NZ][DVB-S][2013]Blu-Ray BD-F6500

[reven]

bugger.

[reven]

just been doing up some reading on the transcoding option in nextpvr

http://forums.nextpvr.com/showthread.php...+transcode

seems like its really not recommended and may cause more issues than it fixes.

[mvallevand]

there is a api call to transcode videos on the server and stream the transcoded files. I could add in an option to transcode files (off by default) and see if that helps. wont be tonight/today though (working on channel groups atm)

You can't skip transcoded files forward anyway.

Martin

[reven]

lol, i thought it was more advanced than what it was, somewhat on par with plex.

[reven]

i suppose a work around maybe to transcode all recordings in postprocessing.bat so they playback better.

[stustunz]

Tell Samsung to fix their player I reckon

[stustunz]

Transcoding all recordings would probably be ok but that means no skipping in process recordings

[reven]

I was trying on my 2012 bluray yesterday and skipping was working fine all except for 1 place in a 2 hour recording. I only seem to get the error in the same place of files, so seems like the file is somewhat corrupt at some point.

I also had the samsung screensaver kick in on the 2012 bluray, so I can test it locally to see if its disabled now. And with all my recent code changes the 2012 BR is running a lot faster that it previously did IMO.

I'm going to add a popup "Please wait while Live TV starts" like in the real nextpvr. playback does start slower on a 2012 than on a 2013.

[stustunz]

2012 is sweet it will play anything fine

The 2013 is shit
I transcoded (using handbrake to h264) tv3 news as I figure that's going to be a pretty bad recordings all joined together
once transcoded it played and skipped fine

[reven]

thats odd... The issue i experience with skipping (which is rare) happens on both the 2012 and 2013 models.

it is going to be out of my hands for the most part. There are a couple of things I can try, perhaps switching to a HTML5 video player (but that will prevent 2011 and below device from working), and no clue if it will be any better. But worth trying. If the HTML5 player works, I could always make 2011 device use the other player and 2012+ use the HTML5 one.

I won't get a chance to try this out for a few days at the earliest, probably realistically a week. Focusing on other areas still ATM (screen saver, volume keys are my current top priority, they're bugging me the most).