MythTV PVR client Addon Developers Wanted - Developers Only! - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: PVR Development (/forumdisplay.php?fid=136)
+--- Thread: MythTV PVR client Addon Developers Wanted - Developers Only! (/showthread.php?tid=82015)
- outleradam - 2010-10-24 14:24
^^ Yeah, dunno what was up with that. It went away after reboot. I had been working on it all day. Something was bound to be screwey... I was hoping someone could tell me what that was.
This is a new log just to verify everything is working properly.
installed ppa:mythbuntu/0.24 under Maverick
Installed Dharma B3 LIVE iso
built source from SVN last night
removed Dharma XBMC binary from /usr/bin
replaced runXBMC line /usr/bin/xbmc to /usr/local/bin/XBMC
ON mythbackend computer:
1. restarted the computer
2. let mythtv boot up log here: http://pastebin.com/PMNx9eiS
ON my desktop
3. connected with VNC mythfrontend client (i tried ssh last night and had audio but no video)
4. Played video over VNC and verified everything worked properly
5. shutdown XBMC
on virtual machine running XBMC (hosted by my desktop):
6. selected pre-created mythtv-client source
7. navigated to recordings
8. failed attempt to play the same video as in step 4 log here http://pastebin.com/WXE4d5UL
9 shutdown XBMC VM
- outleradam - 2010-10-24 18:57
Any suggestions as to how to get this working?
This is what puzzles me:
- PhracturedBlue - 2010-10-24 21:19
outleradam Wrote:Any suggestions as to how to get this working?That message is normal. It just means that thie 1st connect failed (which it is supposed to). we use the output of the 1st connect to choose the correct protocol. If you are actually having an issue, turn on verbose debugging in xbmc and capture stdout (not xbmc.log):
- outleradam - 2010-10-25 00:48
^^ Yes. I think I am, Installed live cd, compiled binaries, removed the /usr/bin/xbmc binary and launched the SVN binary located in /usr/local/bin.
I can get information, but video won't come across.
Here is the information http://pastebin.com/M5MGwmAW
For completeness; I removed about 200 lines per second which stated
Also, I snipped a large portion in the middle. It's marked with SNIP
- wagnerrp - 2010-10-25 00:57
PhracturedBlue Wrote:That message is normal. It just means that thie 1st connect failed (which it is supposed to). We use the output of the 1st connect to choose the correct protocol.
Why not simply have it start with the current release version? Use '23056' for default now. Switch it to '63' next week. That should take care of most of those warnings.
Also, note that the protocol version is a string, not an integer. After the 0.23.1 release that resulted in '23056', all first party code was updated to treat it as such. Any future point releases that result in a protocol bump will likely be of the syntax '63a', '63b', ...
- outleradam - 2010-10-25 01:04
just to be sure of this, I made a copy of the runXBMC file, modified it to reference /usr/local/bin/xbmc, did a sudo apt-get remove xbmc-data xbmc-common xbmc, and then copied the runXBMC into the /usr/bin folder and added /usr/bin/runXBMC& to the /etc/rc.local.
So, It should effectively be running SVN, i mean it's got no data or common files from the live CD anymore. I rebooted the virtual machine and tested again. It still had the same thing and the same version information.
I must be doing something wrong... I want this to work and have been working to get this 1 out of 2 approvals for addition into Dharma for the entire weekend.
I'm willing to keep pushing it until I can get it to work. I'm just out of ideas.
- PhracturedBlue - 2010-10-25 01:23
wagnerrp Wrote:Why not simply have it start with the current release version? Use '23056' for default now. Switch it to '63' next week. That should take care of most of those warnings.
Well, you'd need to drop support for protocol versions 1-8 if you did that, since they use a different means of communication I believe. On the other hand, I can't imagine anyone still uses such an ancient version of myth.
Since we need to change the code every time they update the protocol, there's no reason to change the protocol from an int to a string until it is necessary.
- PhracturedBlue - 2010-10-25 01:47
What I was expecting was to see a bunch of stuff about 'ANN FileTransfer' which I don't see in your log, This is a message you would see from cmyth_conn_connect_file() which is the primary routine in xbmc to fetch a file from xbmc to play.
I do see this:
You do have this:
I'm not sure how to proceed, since I don't see anything obvious from your logs.
You could try this. maybe it would help:
start myrhbackend, and redirect output to a file
wait ~20secs for it to fully initialize
start xbmc, redirect stdout to a file.
go directly to vide->files->mythtv->tvShows->...>some show and play it.
immediately exit xbmc
supply the mythbackend stdout, xbmc stdout, and xbmc.log files.
Maybe with all 3 it will be obvious to me where things are breaking down.
FYI, I don't have any way to test Live-TV with my setup, so I am not sure it works. So let's start with recording playback which does work for me.
- PhracturedBlue - 2010-10-25 01:53
By the way, the failure seems to be here:
- outleradam - 2010-10-25 03:00
Video is somewhat laggy since I svn upped mythtv. Possibly related? I'm getting you the information you require.
I should clarify that I built from source and then installed the 0.24 repo later. Myth frontend runs slower then usual, but it works.