NextPVR Android client now available

[sub]

IMHO it may not be worth looking into putting this in the Amazon app store until you sort out the deinterlacing issue I mentioned previously. The NPVR app on my shield looks great but the interlacing on Amazon devices was really bad. I am afraid if you put it in the Amazon store in the current state you may end up with a lot more complaints/support requests around this issue. Of course this is just my opinion based on my experience.

I have temporarily been using TVMosaic for my DVR and watching my OTA channels since it handles the deinterlacing in their Android client on the Amazon devices. I keep checking back here to see when you get this fixed, so I can switch back.

In this scenario, as long as you're not using direct play, you can set the ffmpeg command line parameters used for the transcode, so could use that to deinterlace the stream being sent to the Android device.

[mvallevand]

Deinterlacing on the ftv varies by device The original was bad but the 4k stick does mpeg2video fine and has trouble with deinterlacing h264 that is supposed to be fixed in current firmware.

I thought that the default transcode in NextPVR was -vf yadif.

Martin

[Maverick]

In this scenario, as long as you're not using direct play, you can set the ffmpeg command line parameters used for the transcode, so could use that to deinterlace the stream being sent to the Android device.

Yes I tried that but that causes a 15 second or so delay between selecting a channel and play actually starting. This becomes really painful when you just want to flip through channels. It is 100% up to you if you want to release it on Amazon or not. I was just pointing out a known issue that could cause you to have more complaints/support requests. If what mvallevand says is correct, then people with newer Amazon devices may not have this issue at all. I am not going to replace 3 otherwise perfectly good working devices though. All of my Amazon devices are Gen 2 devices.

[Maverick]

Deinterlacing on the ftv varies by device The original was bad but the 4k stick does mpeg2video fine and has trouble with deinterlacing h264 that is supposed to be fixed in current firmware.

I thought that the default transcode in NextPVR was -vf yadif.

Martin

It is good to hear Amazon is finally getting off their butts and fixing this basic issue on their end.

I have no idea what the default transcode is because the line in the config file is literally:
<TranscodeHLS>default</TranscodeHLS>
So it's impossible to tell what the default is, but it does NOT do deinterlacing.

I changed that line to:

<TranscodeHLS>-y [SEEK] -i [SOURCE] -map_metadata -1 -threads 0 -ignore_unknown -map 0:v:0 -map 0:a:0 -map -0 -codec:v:0 libx264 -vf yadif=1:-1:0 -pix_fmt yuv420p -preset superfast -crf 23 -b:v [BITRATE] -maxrate [BITRATE] -bufsize [BUFSIZE] -vsync vfr -profile:v high -level 41 -force_key_frames "expr:gte(t,n_forced*3)" -s [RESOLUTION] [SUBTITLES] -flags -global_header -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1" -hls_time 3 -start_number 0 -hls_list_size 0 -y [TARGET]</TranscodeHLS>

This does allow the server to deinterlace the signal before sending it, but it also adds a long delay when changing channels. Maybe this could be tweaked to remove that delay but I don't know what all those parameters mean. I copied that value from somewhere else in the config file.

I am not overly concerned about it right now because I have been using different solution but I am starting to think the other solution is not really being developed anymore. If that's the case I'll worry about fixing this then.

[sub]

I have no idea what the default transcode is because the line in the config file is literally:
<TranscodeHLS>default</TranscodeHLS>
So it's impossible to tell what the default is, but it does NOT do deinterlacing.

The default can be seen in the nrecord.log. It's currently:

Code:

-y [SEEK] -i [SOURCE] -map_metadata -1 -threads [THREADS] -ignore_unknown -map 0:v:0 -map 0:a:[AUDIO_STREAM] -map -0:s -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 [DEINTERLACING] -b:v [BITRATE] -maxrate [BITRATE] -bufsize [BUFSIZE] -vsync vfr -profile:v high -level 41 -force_key_frames \"expr:gte(t,n_forced*3)\" -s [RESOLUTION] [SCALE] [SUBTITLES] -flags -global_header -sc_threshold 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -hls_time [SEGMENT_DURATION] -start_number 0 -hls_list_size [SEGMENT_COUNT] -y [TARGET]

[mvallevand]

What control the passed parameter [DEINTERLACING]

Martin

[sub]

It's currently hard coded to always be "-vf yadif=0:-1:0"

[mvallevand]

So Maverick should be getting deinterlaced video. Those early Amazon device are basically crap so I wouldn't with about them

Martin

[HGset]

I have a new Amazon Fire TV Edition and would love to use your front end rather than setting up Kodi.  I've read it could be coming next in the Amazon app store, but am not the most patient guy. 

I've read that I can sideload the Google Play store (quite a lengthy process).  Any idea how the NextPVR Android client would work on the TV if I made it all the way to your apk? I'd be more than happy to pay for the apk if there's an easier way to get it!

Thanks in advance for your thoughts!

[sub]

I have a new Amazon Fire TV Edition and would love to use your front end rather than setting up Kodi. I've read it could be coming next in the Amazon app store, but am not the most patient guy.

I've read that I can sideload the Google Play store (quite a lengthy process). Any idea how the NextPVR Android client would work on the TV if I made it all the way to your apk? I'd be more than happy to pay for the apk if there's an easier way to get it!

Thanks in advance for your thoughts!

Amazon wouldn't ship them to New Zealand, so I haven't done anything further on that side of things.