ffmpeg maxing out CPU

[sub]

It wants to transcode most everything and it doesn't use GPU and only 32-bit.  So background usage of 60% doing other tasks doesn't leave much.  Source is 720p but wants to transcode live to devices capable of 1080p.  May not work for me if I can't stop the transcoding.  Waiting to see what happens when it records instead of live.

How are you trying to watch stuff? In the web app? NextPVR will only transcode for viewing in the web app (or if requested in the iPhone/Android apps). It does this because it has to - web application can't play broadcast streams, so it needs to be transcoded to a format that can be played by a browser. (v4 would also need to transcode in these same scenarios)

If you're watching in a client that can play native streams, like nextpvr.exe, or kodi, or other clients that support directplay, then it wont transcode the stream

[mvallevand]

Thanks Martin.  Got frustrated with v5 not knowing what features work and which don't.  So thought I'd fall back to v4 since I'm new to this app. It wants to transcode most everything and it doesn't use GPU and only 32-bit.  So background usage of 60% doing other tasks doesn't leave much.  Source is 720p but wants to transcode live to devices capable of 1080p.  May not work for me if I can't stop the transcoding.  Waiting to see what happens when it records instead of live.

Looking at your posts I don't really have a clue what your issue actually is. V5 for IPTV should be better all around.  You likely need to try a non transcoding client like Kodi to enjoy NextPVR if playback transcoding is the issue.  If recording transcoding is the issue you need a new thread with logs.

Martin

[markn62]

Thanks Martin.  Got frustrated with v5 not knowing what features work and which don't.  So thought I'd fall back to v4 since I'm new to this app. It wants to transcode most everything and it doesn't use GPU and only 32-bit.  So background usage of 60% doing other tasks doesn't leave much.  Source is 720p but wants to transcode live to devices capable of 1080p.  May not work for me if I can't stop the transcoding.  Waiting to see what happens when it records instead of live.

Yes, after further testing I see that only browser playback causes transcoding in v4. Also finding that;

• iOS TvGuide crashes with v4 but not with v5.
  
• iOS TvGuide is very slow to load and doesn't show all content that a browser session does.
  
• Appears v5 can do m3u8 but v4 can't.
  
• v4 doesn't record to a Nas drive even if smb format //address/folder is edited into the config.xml, v5 does.
  
• v4 doesn't take much CPU when not transcoding, yay!
  

Martin, what I'm trying to do is see how v4 behaves so I don't ask so many v5 questions on this board and frustrate you all instead of myself. ;-)  So long story short, going back to v5 to thresh out (test) what remains with a few issues there and be patient knowing more is coming.  I don't want to wear out my welcome.

[mvallevand]

Ok iOS issues are for sub, but I can tell you that v4 will record to a NAS I have done it for years, but you have to figure out how to do this for the service there are many posts on this. You will ahve the same issue if you run v5 as a service.

v5 takes almost no CPU when not transcoding either. If v5 is transcoding IPTV and v4 is not that is something that sub can look at separately (as I posted)

Martin

[markn62]

Ahhh, so it's the service that's causing the issue. Thanks mvallevand.  In passing I've read many of the posts on how to resolve this.  I just assumed since it worked in v5 that all permissions and such were satisfied.  I'll re-read the posts regarding service restrictions on external drives and try again.