njumzs / mythdroid

Automatically exported from code.google.com/p/mythdroid
0 stars 0 forks source link

Problems installing on mythbuntu #98

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Which version of MythDroid were you using?
0.5.3
Which version of MDD?
0.5.3
Which version of MythTV were you using? (e.g. mythfrontend --version)
v0.24.1-112-g40f3bae (backend), Mythbuntu 11.04.

What steps will reproduce the problem?
1. install mythdroid
2. install mdd
3. start everything, then try to get a picture from recordings.

What is the expected output? What do you see instead?
Video. Instead I got port errors (16546)

Please provide any additional information below.
Needed to separately install libimlib2 and libimage-imlib2 first, then compile. 
Persisting Problem: 'sudo start mdd' does not return and produces no process 
although Upstart thinks it does.
Only manual start 'sudo mdd.pl -d' works. Reproducable.

Still no picture after that, then I figured out that vlc needed to be installed 
too (mythbuntu is a bit of a minimal install)
Now it sort-of works. My HTC Hero is probably a bit slow, only lowest selection 
of trancoding gives smooth picture. CPU usage on backend is quite low during 
transcoding (<0.4 on 2.5GHz Sandybridge dual core).

I would appreciate some help with the upstart script not working.

Original issue reported on code.google.com by frankd...@gmail.com on 8 Apr 2012 at 2:50

GoogleCodeExporter commented 8 years ago
IIRC the upstart problem has been fixed since 0.5.3 was released; could you try 
replacing your init/upstart file with the version in svn trunk 
(http://mythdroid.googlecode.com/svn/trunk/mdd/init/upstart), reinstalling mdd 
and letting us know if the issue goes away please?

Original comment by foobum on 13 Apr 2012 at 9:22

GoogleCodeExporter commented 8 years ago
As requested replaced the upstart file so using only 'respawn'. No change,
mdd.pl still doesn't return.
Then reinstalled from trunk (version 640). /etc/init/mdd.conf remained the
same. Problem too.

Only way to start mdd is via $sudo mdd.pl -b

Original comment by frankd...@gmail.com on 17 Apr 2012 at 10:08

GoogleCodeExporter commented 8 years ago
Hmm. If upstart thinks that there are mdd processes running do you need to 
address that? I've never experienced 'start mdd' not returning and I'm not sure 
what to suggest, except that you shouldn't run mdd as root!

Does upstart produce logs? Perhaps turn mdd debugging on in /etc/mdd.conf and 
see if mdd logs anything useful (to /tmp/mdd.log by default)? Maybe an strace 
of 'start mdd' might help?

Original comment by foobum on 18 Apr 2012 at 2:25

GoogleCodeExporter commented 8 years ago
I don't know if it helps, but if I start mdd.pl via the sysvinit script it does 
return.
Also, if I start it via sudo $nohup mdd.pl it returns and I can end the remote 
shell.

I'm working with an old htc-hero phone, which seems to be too slow anyway, vlc 
gives lots of missed frame errors and I almost never get to the point that I 
actually get sound/picture. I'm getting an atrix soon, that ought to work 
better.
Top says vlc is using 100% of it's slice of cpu time. System cpu use is 0.82 
(dual core sandy bridge 2600MHz), so probably something not right there either. 
I will report back when I have proper hardware to test with.

Original comment by frankd...@gmail.com on 22 Apr 2012 at 1:35

GoogleCodeExporter commented 8 years ago
Hi there,

Just reporting here that I have exactly the same issue on mythbuntu lts 10.04
service mdd start does not return. Tried changing the upstart conf in 
/etc/init, to contain fork instead of daemon and remove respawn, but it does 
not help. Do I have to do anything after changing that file before upstart 
actually uses it?

Furthermore I see that it is capable of reencoding SD video on the highest 
bitrate , so I can play it on my tab. However there is NO SOUND. HD recordings 
can not be reencoded real time, so 75% of my material can't be streamed to the 
TAB.

It's an athlon 5050E dual core.

Original comment by mellehol...@gmail.com on 24 Apr 2012 at 6:05

GoogleCodeExporter commented 8 years ago

Original comment by foobum on 26 May 2012 at 1:39

GoogleCodeExporter commented 8 years ago
Ok, so the problem is likely caused by the fact that with debug turned off, mdd 
will daemonise (so 'expect fork' would be correct). With debug turned on, mdd 
doesn't fork and so no expect stanza would be correct. I usually have debug 
turned on via the config file and so we've been seeing different things. I'll 
fix by making mdd fork in both cases.

Original comment by foobum on 16 Jun 2012 at 2:01

GoogleCodeExporter commented 8 years ago
Accidentally set to fixed.

Original comment by foobum on 16 Jun 2012 at 2:01

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r766.

Original comment by foobum on 16 Jun 2012 at 2:19