2012-10-01, 03:11 PM
I read that Timeshifting and Seeking support is back in master as of today, this potentially breaks current plugins, any news on status with NPVR plugin ?
2012-10-01, 03:11 PM
I read that Timeshifting and Seeking support is back in master as of today, this potentially breaks current plugins, any news on status with NPVR plugin ?
2012-10-01, 04:29 PM
KRA Wrote:My experience with other plugins is that it's sometimes troublesome to activate, in the live-tv section of xbmc there is a "reset database" option, I find that come handy when trying to get a plugin working. Alternative delete TV* database files. Very true, I always reset the database with every new build I install. You never know what changes took place from one build to the next. (unless you look at the commit log )
2012-10-01, 04:36 PM
KRA Wrote:I read that Timeshifting and Seeking support is back in master as of today, this potentially breaks current plugins, any news on status with NPVR plugin ?I've never seen how their timeshifting code works, so it's safe to assume it doesn't work with NextPVR. I'll check it out in the next few days though, and will add support for it.
Update, I try to test 4TR to compare. Unfortunatly the 4TR plugin doesn't seem 100% compatible with current GIT version, because when it's about to start playback TS file xbmc crash (nothin in log )
I did however compare backend response. I start to tune channel from xbmc. xbmc report "working" instant, within 2 seconds 4TR is writing TS file, normally it would start play the next second, but rather crash. Same test in NPVR. click on channel, instalt "working", but it takes about 10 seconds before NPVR device status report active tuner, at same instant TS file is created. Then an additional 5-10 seconds before xbmc start to play. "same test" with VLC http://serverip:8866/live?channel=33 9 seconds device status report active tuner, 10 seconds TS file shows up, 13-14 seconds VLC start playback. Unfortunatly none of my tuners work on linux, and I can't be bothered to install mediaportal to test. the slow tuning I can live with (channelchange is much faster than stop/start) But I need to fix the cpu hog issue. Gonna run xbmc in debug mode to see if anything pops up. EDIT: Just like to add my Terratec H7 dvb-c tuner cut the times in half, compared to the above on my Hauppauge Nova HD dvb-s2 tuner. Still cpu hog though. Now on to debug mode.
2012-10-01, 05:20 PM
It sounds like you're mainly referring to startup time here, rather than channel change time. ie, the time to build the directshow graph and start it running. Some apps leave the directshow graphs constructed, and just paused or stopped, so that it's quicker to start. Personally I dont care about startup time. When nextpvr no longer needs the device, it deconstructs the graph and releases the resources back to the operating system, which does mean next startup does require graph to be rebuilt etc.
The time to build and run a graph varies a bit from device type device. DVB-S tuners are also typically slower for some reason. Channel change times should be much quicker. ie, graph is already built and running, so just needs to submit new tuning. In my tests NextPVR was delivering data for the new channel to xbmc less than a second after the request to change channels. Its up to xbmc (and ffmpeg) how quickly it'll show it to the user though.
2012-10-01, 05:31 PM
You could see if this updated pvrclient-nextpvr.cpp helps your CPU usage in live tv.
2012-10-01, 05:32 PM
sub Wrote:I've never seen how their timeshifting code works, so it's safe to assume it doesn't work with NextPVR. I'll check it out in the next few days though, and will add support for it. In none developers speak: AFAIK it just adds some commands for pause and seek, so you just have to map those commands to talk to the backend.
2012-10-01, 05:38 PM
thanks for the patch, I will test it, please keep in mind I'm no programmer. Is the file a patch for the plugin, so I replace the file and re-compile ?
I've added a "small" xbmc log from a short trial of start xbmc, play a channel for a few seconds, stop. As you can se the log is flooded with messages as described here: http://forums.nextpvr.com/showthread.php...MC-plugin) If I read log correct, we are talking millions every second, starting when the plugin loads. But My cpu hog starts only at playback of live-tv, so I don't think it's related
2012-10-01, 05:40 PM
KRA Wrote:thanks for the patch, I will test it, please keep in mind I'm no programmer. Is the file a patch for the plugin, so I replace the file and re-compile ?Yes, just replace the file and rebuild.
No change as to cpu usage with new patch, but with dvb-c tuner I actually tune HD channel as fast as 3 seconds, SD however is slower to tune (probably due to cpu hog issue).
A few seconds after starting a channel cpu goes to 100% When changing channels, it cpu use goes down for a couple of seconds, then back to 100% So it's at 100% way before it actually start to play/show the channel. |
|