(2012-04-22 20:01)cspack Wrote: Here's a full debug log from playing a recording through the myth:// protocol: Pastebin. If I play the same file from a samba share over the network it plays without stuttering.

EDIT: I noticed this message in the mythbackend log file on my backend server. Not sure if it's important but it comes up before selecting a recording for playback, not during playback:

Thanks for the log. Can you also post a log file with playback over SMB so I can compare. I might need to make some changes to CMythFile for some new caching stuff that seems to have been implemented. Have you been able to playback some of these recordings fine with Myth 0.24 or are these recordings fresh with Myth 0.25?

That error message in the mythbackend.log file is fine. We use a protocol version 8 message to determine what protocol the server actually supports - hence the error message.

Seeking within LiveTV has never been supported by the myth:// protocol (pausing playback is all that is possible). I believe that tsp42's implementation of the PVR Addon may have introduced time shifting (aka seeking in a live stream).

I'll be installing tsp42's addon at the weekend onto our HTPC and will continue to migrate all of XBMC's changes to libcmyth to the upstream location and work with tsp to also get any changes he had made put into the upstream repository for libcmyth.

From the testing done thus far:
- 1 person has a problem with playback of recordings. It's not clear why that is the case. A number of other people have not experienced problems.
- 1 person has had problems with some channels not appearing. I'll look into this at the weekend, but I suspect it's because either libcmyth or the myth:// implementation in XBMC assumes that channel numbers are integers and not decimals.
- There were a number of other issues that ended up being related to configuration in some way.

I have one change to make now that the code has been reviewed by another XBMC team member. Once I've made that change it will become a merge request for XBMC master and should go in early May.

(2012-04-27 01:14)dteirney Wrote: - 1 person has had problems with some channels not appearing. I'll look into this at the weekend, but I suspect it's because either libcmyth or the myth:// implementation in XBMC assumes that channel numbers are integers and not decimals.

Just some extra info.

I don't think it's the case of 13.1 overwriting 13 and I have no 16.x channel but 16 doesn't show. I wonder if it's to do with the channel type being flagged as something different. All my analog channels for instance use the same Frequency (as the pathetic cable box is modulated output only on VHF Ch 3)..

(2012-04-27 01:14)dteirney Wrote: Seeking within LiveTV has never been supported by the myth:// protocol (pausing playback is all that is possible). I believe that tsp42's implementation of the PVR Addon may have introduced time shifting (aka seeking in a live stream).

I'll be installing tsp42's addon at the weekend onto our HTPC and will continue to migrate all of XBMC's changes to libcmyth to the upstream location and work with tsp to also get any changes he had made put into the upstream repository for libcmyth.

From the testing done thus far:
- 1 person has a problem with playback of recordings. It's not clear why that is the case. A number of other people have not experienced problems.
- 1 person has had problems with some channels not appearing. I'll look into this at the weekend, but I suspect it's because either libcmyth or the myth:// implementation in XBMC assumes that channel numbers are integers and not decimals.
- There were a number of other issues that ended up being related to configuration in some way.

I have one change to make now that the code has been reviewed by another XBMC team member. Once I've made that change it will become a merge request for XBMC master and should go in early May.

I've made the code changes that were requested by one of the other XBMC developers. So there has been a change to the commit history for my myth-0.25 branch. There shouldn't be any functional changes but if anyone wants to update and quickly check that would be great.

(2012-04-28 13:07)dteirney Wrote: I've made the code changes that were requested by one of the other XBMC developers. So there has been a change to the commit history for my myth-0.25 branch. There shouldn't be any functional changes but if anyone wants to update and quickly check that would be great.

For anyone trying to update their branch you'll probably need to do a hard reset using git since the update was forced and there are probably conflicts with files already on the local system. Or just delete the local files in the libcmyth directory and then do a git pull.

For those people not seeing channels show up. Are they channels from the Live TV listing or the Guide.

If it's from the Live TV listing do you have any Tuner numbers > 16 in mythbackend. The source at the moment only enumerates Tuners up to number 16. Could be a problem for anyone that has a number of tuners using multiplexing.

Source ID is 13 for my missing channels, have deleted the git tree and starting again as I had the same problem described earlier. Should have it up and running in an hour or so..

As an aside, neither this version or the current pvr tree play my slingbox very well anymore. Lots of picture freezing. I know it's nothing to do with these additions and probably some decoding of the slingbox wmv codecs, but it's a showstopper until it gets resolved. Thankfully I have an old pvr tree on hand to get this working. I wrote a comment in the appropriate forum but appears to have falled on deaf ears. If someone wants to look at this I can PM them slingbox details.

Back up and running after downgrading to Myth 0.25 and restoring the DB. The latest git doesn't seem to want to play a channel, I get the filesize updates etc in the log but no picture. Old git still works as before (on remote frontend).

Just recompiled and tested.. The Guide shows those channels, it's live TV that doesn't. Although I get three lots of channel 27 instead of 27.1 WKOW_DT 27.2 METV 27.3 ThisTV etc.

Over here the frequency the channel used to appear on when it was analog is the first number, and the program number in the multiplex is the second. (So in DVB talk, it's the SID). MythTV when your entering channels (and a set top box) allows you to compress them, so to get 27.1 you type 271. That might be something you can check for? However, the second part can get long, especially when dealing with Clear-Qam, I have a channel that is something like 110.103.