Author Topic: mythv issues 810 beta2  (Read 1656 times)

klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
mythv issues 810 beta2
« on: December 14, 2009, 09:38:37 am »
Good Morning All

Installed 810 beta2 dvd, ran the /usr/pluto/bin/Diskless_CreateTBZ.sh, to allow diskless creation. Did not have to edit the this file /usr/pluto/bin/files.d/fstab-diskless - and my MD created successfully.

Set up mythtv, on the hybrid, and it works fine, attempted to play tv on the MD, this is where I encounter a little hickup, see excerpt from 44_MythTV_Player.log on the MD, the attempt to send the liveTv command seem to keep failing.
Quote
== ATTEMPT FRESH START ==
1       12/13/09 20:51:47       Spawn_Device.sh 44 (spawning-device)    16304 Dev: 44; Already Running list: 37,38,40,

== FRESH START ==
1       12/13/09 20:51:47       Spawn_Device.sh 44 (spawning-device)    device: 44 ip: 192.168.80.1 cmd_line: MythTV_Pl
ayer
0       12/13/09 20:51:47       44 (spawning-device)    Entering 44
========== NEW LOG SECTION ==========
1       12/13/09 20:51:47       44 (spawning-device)    Starting... 1
1       12/13/09 20:51:47       44 (spawning-device)    Found ./MythTV_Player
05      12/13/09 20:59:44.519           MythTV_Player::LaunchMythFrontend - ready to launch! <0xb77e1b90>
05      12/13/09 20:59:44.523           Changing mode: live <0xb77e1b90>
05      12/13/09 20:59:44.622           Going to send command jump livetv <0xb77e1b90>
05      12/13/09 20:59:45.630           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:46.634           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:47.634           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:47.634           ClientSocket::Connect() not successful <0xb77e1b90>
05      12/13/09 20:59:47.634           void ClientSocket::Disconnect() on this socket: 0x826fd18 (m_Socket: 8) <0xb
77e1b90>
01      12/13/09 20:59:47.634           Unable to connect to MythTV client <0xb77e1b90>
05      12/13/09 20:59:47.635           MythTV_Player::pollMythStatus no jump livetv  <0xb77e1b90>
05      12/13/09 20:59:47.734           Going to send command jump livetv <0xb77e1b90>
05      12/13/09 20:59:48.734           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:49.735           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:50.734           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:50.734           ClientSocket::Connect() not successful <0xb77e1b90>
05      12/13/09 20:59:50.734           void ClientSocket::Disconnect() on this socket: 0x829d5e0 (m_Socket: 8) <0xb
77e1b90>
01      12/13/09 20:59:50.734           Unable to connect to MythTV client <0xb77e1b90>
05      12/13/09 20:59:50.734           MythTV_Player::pollMythStatus no jump livetv  <0xb77e1b90>
05      12/13/09 20:59:50.834           Going to send command jump livetv <0xb77e1b90>
05      12/13/09 20:59:51.834           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:52.834           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:53.834           Connect() failed, Error Code 111 (Connection refused)) <0xb77e1b90>
05      12/13/09 20:59:53.834           ClientSocket::Connect() not successful <0xb77e1b90>
05      12/13/09 20:59:53.834           void ClientSocket::Disconnect() on this socket: 0x829d5e0 (m_Socket: 8) <0xb


Pluto log, indicated that it had to restart the mythv backend several times and doing /etc/init.d/mythbackend status, showed it not running. Rebooted the MD and this seemed to have fix that issue, but although the backend was running on the MD, tv was not working.

Tried the solutions from the following posts:
Quote
http://forum.linuxmce.org/index.php?topic=9117.msg62458;topicseen#msg62458
http://forum.linuxmce.org/index.php?topic=9232.0

The first one, as I was seeing multiple versions of mythtv, frontend and backend thus attempted that fix, was seeing a prompt to install mysql when I did apt-get install pluto-mythtv*, thus cancelled, this was on the MD in question. Rebuild the MD and tried the second topic after uninstalling mythv, this did not fix the issue, as still could not play tv on the MD.

Also tried the fix listed below, initially, as this had fix my issues in the initial beta, that is, including forcedirectio in the mount options.
Quote
http://forum.linuxmce.org/index.php?topic=3203.0

Questions
Is the output of apt-cache showpkg mythtv-frontend correct? Please see attached file mythtv errors.txt

When I ran the /usr/pluto/bin/Diskless_CreateTBZ.sh and created an MD, I am seeing the errors show below, what are the correct entries for the /etc/apt/sources.list?

Is this error contributory to the issue?

Quote
Get:12 http://packages.medibuntu.org intrepid/free Packages [3530B]
Err http://archive.ubuntu.com universe/main Packages
  404 Not Found [IP: 91.189.88.46 80]
Ign http://www.avenard.org intrepid Release
Ign http://deb.linuxmce.org replacements_debian/main Packages
Err http://archive.ubuntu.com universe/non-free Packages
  404 Not Found [IP: 91.189.88.46 80]
Get:13 http://www.avenard.org intrepid/release Packages [110kB]
Ign http://deb.linuxmce.org replacements_ubuntu/main Packages
Get:14 http://deb.linuxmce.org intrepid/beta2 Packages [32.2kB]
Get:15 http://packages.medibuntu.org intrepid/non-free Packages [7533B]
Err http://archive.ubuntu.com universe/contrib Packages
  404 Not Found [IP: 91.189.88.46 80]

What have I missed?

Thanks

klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
Re: mythv issues 810 beta2
« Reply #1 on: December 14, 2009, 02:00:03 pm »
Forget to mention, I had also changed the slave backend from 172.0.0.1, to the IP of the MD, which could have been the reason on checking the logs, why the backend successfully started.

This did not fix the issue describe in my previous post.

This morning, before heading to work, I configured a pvr 150 on the MD, but live tv still did not work; will look at it some more once I could leave work today.


klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
Re: mythv issues 810 beta2
« Reply #2 on: December 14, 2009, 11:11:36 pm »
I just tried from the following, from a post I found today, see below. This seems to be another solution to adding forcedirectio, which allows to stream directly from the backend.

http://forum.linuxmce.org/index.php?topic=8861.0

Got the live tv to show, but you have to actually click watch tv, same errors as in my earlier post in the 79_MythTV_Player.log. Even with the tv working, you cannot change any  channels, pause tv or use the guide, which works on the hybrid and after a while the process simple crashes.

Note, all worked well in the initial beta, only having to add forcedirectio to the home directory. It also worked when I did the upgrade to beta2. I decided to do a clean install using beta2 dvd, it seems this is where I encountered this issue.

Still fighting, planning to try an online install and see if I get the same results.

klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
Re: mythv issues 810 beta2
« Reply #3 on: December 16, 2009, 08:45:02 am »
I scratched the DVD beta2 install and did the online install; created an MD and all seems to be working well, livetv cam up on the MD, no cannot connect to client errors in the mythtv log; only had to change the mount option to add forcedirectio or set to stream directly from backend.

Will test some more a bit later, but so far all seems well, I can watch livetv on the MD, change the channel, and pause livetv, none of these things worked previously.

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: mythv issues 810 beta2
« Reply #4 on: December 16, 2009, 11:17:11 am »
Hi,

I can confirm that Live TV on the MD only works with "Allways stream from backend". I did not try "forcedirectio" yet.
So one of the solutions should be implemented.

Viking

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3062
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: mythv issues 810 beta2
« Reply #5 on: December 16, 2009, 01:54:55 pm »
Could you please open up a trac ticket and supply the information what is changed in the mythconverg database when you do the changes.

thanks

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: mythv issues 810 beta2
« Reply #6 on: December 18, 2009, 10:37:33 pm »
Hi pos,

will look into it when I find time.

@klanmce
Where do you setup forcedirectio ?

Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: mythv issues 810 beta2
« Reply #7 on: December 18, 2009, 11:03:22 pm »
I have another issue with Dolby Digital audio and MythTV in the newest beta2.

EDIT: I have an SPDIF conection from the mainboard to my reciever.

For some reason MythTV thinks that audio is AC3 2 channel and therefore not plays at all :(

MythTV general options:
Audio output device is ALSA:default
Speaker configuration 5.1
upmix disabled
DD and DTS is enabled.
Advanced audio disabled.

I have found out that if I activate "Use Internal volume control" below general options, setup Mixerdevice to ALSA:default and mixer-control PCM. It plays AC3 5.1 again even if the Spawn_mythfrontend_* logfile states that it is 2 channel audio !?
Not sure at which mythtv update that happened.

But interestingly enough Xine does also not play the AC3 audio on those recordings either - it plays only the stereo audio. How can I switch audio track in linuxmce xine_player ?
Normal DVD's are OK in Xine, playing AC3 5.1 or DTS.

Mplayer tells me that it contains AC3 audio :
#  mplayer -ao null -vo null 18501_20091025201300.mpg
VIDEO MPEG2(pid=511) AUDIO A52(pid=515) SUB Teletext(pid=33)  PROGRAM N. 1
VIDEO:  MPEG2  720x576  (aspect 3)  25.000 fps  15000.0 kbps (1875.0 kbyte/s)

Tested on recordings from Pro7 and livetv Pro7 right now. And the latest Beta2 + a MD from the 10.dec.

Greetings
Viking

klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
Re: mythv issues 810 beta2
« Reply #8 on: December 20, 2009, 02:49:01 pm »
Sorry I was working, we had issues, not good during the season.

I changed that in the mount options for the /etc/fstab, see the quote

Quote
//192.168.80.1/home                             /home                   cifs iocharset=utf8,forcedirectio,credentials=/usr/pluto/var/sambaCredentials.secret 1 1

I want to test, to see what ramifications if any(if it would break anything), it may have on the linuxmce system, haven't seen any so far.

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: mythv issues 810 beta2
« Reply #9 on: December 22, 2009, 12:28:09 pm »
Hi klanmce,

I will test if there is any problems with forcedirectio. And give some feedback.

I assume that is the better way to play TV as it will allow for more MD's in parallel - or what do others here think ?

Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: mythv issues 810 beta2
« Reply #10 on: December 22, 2009, 12:35:14 pm »
Could you please open up a trac ticket and supply the information what is changed in the mythconverg database when you do the changes.

thanks

It is a per MD setting and is called "AlwaysStreamFiles". "1" means stream, "0" means don't stream.

Same place as "BackendServerIP" is found for the MD.

Viking

klanmce

  • Veteran
  • ***
  • Posts: 133
    • View Profile
Re: mythv issues 810 beta2
« Reply #11 on: December 22, 2009, 11:16:32 pm »
Yes the stream options works, I have tried it in a effort in dealing with the issue I initially posted on.

I have one question though, to resolve a particular issue.

What is the MythTV client, as I am continually getting an error on a newly created MD, see below:
Quote
void ClientSocket::Disconnect() on this socket: 0x9a72768 (m_Socket: 8) <0xb6742b90>
01      12/22/09 18:09:00.746           Unable to connect to MythTV client <0xb6742b90>
05      12/22/09 18:09:02.514           Going to send command jump livetv <0xb7744b90>
05      12/22/09 18:09:03.517           Connect() failed, Error Code 111 (Connection refused)) <0xb7744b90>
05      12/22/09 18:09:04.517           Connect() failed, Error Code 111 (Connection refused)) <0xb7744b90>
05      12/22/09 18:09:05.517           Connect() failed, Error Code 111 (Connection refused)) <0xb7744b90>
05      12/22/09 18:09:05.518           ClientSocket::Connect() not successful <0xb7744b90>
05      12/22/09 18:09:05.518           void ClientSocket::Disconnect() on this socket: 0x9a72768 (m_Socket: 8) <0xb7744b9