2013-02-28, 09:11
(2013-02-27, 04:55)ubuntu-xbmc Wrote: Great to see PVR functionality added to XBMC, thanks to all those who helped.
I've run into a problem. I had XBMC / Mythbackend set up with a digital tuner and it worked fine (I've seen the 100% backend issue) but recently I added an old analog MPEG2 tuner (e.g. NTSC). Since then, tuning an analog channel works fine in MythFrontend, but crashes XBMC completely. The digital channels still work fine. This appears nearly 100% repeatable (6 out of 6 times having tried tuning 7 times).
- I uninstalled / reinstalled the addon
- I recompiled the addon from the latest source and installed it
I have not wiped out cymyth's data, e.g. the addon didn't need to rescan all the channels, just the new ones that were added.
I have very little experience with the addon and want to make sure I'm not missing something basic. I assume mixing analog and digital is fine? Should I clear parts of userdata before adding channels? Anything else I am missing?
The last 4 crash logs all end with (or nearly end with) "Creating Demuxer":
Code:21:22:01 T:140338068870912 DEBUG: AddOnLog: MythTV cmyth PVR Client: OpenLiveStream: Opening new recorder 14
21:22:01 T:140338735445888 DEBUG: ------ Window Init (DialogBusy.xml) ------
21:22:01 T:140338735445888 DEBUG: Window DialogBusy.xml was already loaded
21:22:01 T:140338735445888 DEBUG: Alloc resources: 0.02m
21:22:02 T:140338102441728 DEBUG: NEWADDON PythonCallbackHandler construction with PyThreadState 0x7fa2f4005950
21:22:03 T:140336887596800 DEBUG: Previous line repeats 2 times.
21:22:03 T:140336887596800 DEBUG: AddOnLog: MythTV cmyth PVR Client: Process - Trigger PVR recording update: 2 recording(s)
21:22:03 T:140338085656320 DEBUG: CPVRRecordings - Update - updating recordings
21:22:03 T:140338102441728 DEBUG: NEWADDON PythonCallbackHandler construction with PyThreadState 0x7fa2f4005950
21:22:03 T:140336887596800 DEBUG: AddOnLog: MythTV cmyth PVR Client: Process - Trigger PVR recording update: 1 recording(s)
21:22:03 T:140338085656320 DEBUG: CPVRRecordings - Update - updating recordings
21:22:03 T:140338068870912 DEBUG: AddOnLog: MythTV cmyth PVR Client: SpawnLiveTV: Delay channel switch: 100
21:22:03 T:140338068870912 DEBUG: PVRFile - Open - playback has started on filename pvr://channels/tv/All TV channels/20.pvr
21:22:03 T:140338068870912 DEBUG: CDVDInputStreamPVRManager::Open - stream opened: pvr://channels/tv/All TV channels/20.pvr
21:22:03 T:140338068870912 NOTICE: Creating Demuxer
############ END XBMC CRASH LOG #############
I need more information: XBMC version, addon version, and a full debug log (please enable 'Include more debug information in the log file' in the addon settings and restart xbmc)
Also please try to build the addon yourself as explained here: http://wiki.xbmc.org/index.php?title=PVR...FromSource
and see if the current development version has fixed the problem already.
The interesting part - a stack trace - is at the beginning of the crash log. To include that you have to install gdb on your system (assuming you're on linux).
(2013-02-27, 02:19)sfrooster Wrote: The XBMC / Myth experience is really coming along. Along with commercial skip, once of the few remaining things I'd like to see addressed has to do with how LiveTv is handled.
In particular - everything seems to work pretty good for me if I set it on a channel and leave it, and I'm even able to skip around (back, then forwards, pause etc) within the stream, but there is a problem with trying to use PVR functions when I'm viewing a point in the recording which is prior to a show change / half-hour break, but it is temporally after one. That is:
-I'm watching LiveTv, Show X, which runs from 8:30-9:00
-It's 9:05, but at some point I paused for 10 minutes so I'm viewing what was recorded at 8:55
-A commercial comes along (or some other reason for skipping forward), I hit SkipForward (which normally pops ahead about 8 seconds)
-It jumps to 9:05, that is, the current point in the stream
Again, this is only with LiveTv where Myth uses the EPG (or every 30 minutes on the hour/half hour if there's no EPG) to break-up recording files. I haven't confirmed if this happens with all skipping (backwards or forward) done under this condition, but it does happen consistently enough that it seems to be related.
My questios are - Do others see this? Is there a fix available or planned?
On a related note - is anyone aware what the expected behavior is when hitting the record button/key while watching LiveTv?
@janbar: Any ideas?
