Closed GoogleCodeExporter closed 8 years ago
The errors do suggest that mdd isn't running but MDD doesn't attempt to start
mythlcdserver when it's running in backend-only mode so this shouldn't be the
problem. Try running mdd in debug mode (mdd.pl -d) and then have a look at
/tmp/mdd.log. Attach the logfile here if the problem isn't obvious.
Original comment by foobum
on 26 Nov 2011 at 2:34
OK - mdd certainly wasn't running correctly, but...
chris@mythmaster:~$ sudo service mdd stop
mdd stop/waiting
...it kinda was running!?!?
chris@mythmaster:~$ sudo mdd.pl -d
Can't locate Image/Imlib2.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10
/usr/local/lib/site_perl .) at /usr/share/perl5/MDD/HTTPServer.pm line 30.
BEGIN failed--compilation aborted at /usr/share/perl5/MDD/HTTPServer.pm line 30.
Compilation failed in require at /usr/bin/mdd.pl line 41.
BEGIN failed--compilation aborted at /usr/bin/mdd.pl line 41.
chris@mythmaster:~$ sudo nano /usr/share/perl5/MDD/HTTPServer.pm
So, I installed libimlib2 & libimage-imlib2-perl
& the install script did its magic, and I now get 'mdd.pl' as a service.
I was under the impression that the Imlib2.pm error during the ./Build test did
not matter, but it seems it does. (I'll go fix it on the frontends as well,
just in case)
Thanks for your help foobum- at least mdd is now working as it should, just
scheduled a program using the guide - off to sort out the vlc streaming errors
now (may be back later).
ps- fantastic app, will go a long way to improve the WAF - she'll be able to
control all the frontends with the same remote, and she should NEVER lose it ;-)
Original comment by minidroi...@gmail.com
on 26 Nov 2011 at 9:40
OK problem with videos (not the recording issue - I think that's a vlc problem)
chris@mythmaster:~/mdd$ sudo mdd.pl -d
MDD: Debug mode is on
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
Use of uninitialized value $_ in concatenation (.) or string at
/usr/share/perl5/MDD/MythDB.pm line 162.
That was the o/p when I selected 'Videos' on the phone.
When I select a video, no o/p in log.
When I hit play, I get a popup "Connection refused to 192.168.xx.xx:16546"
and Mythdroid politely tells me "Sorry, this video cannot be played"
O/p in log at this point is:
sh: Syntax error: "(" unexpected
Any pointers?
Original comment by minidroi...@gmail.com
on 26 Nov 2011 at 9:49
Could you attach logs please? mdd's log can be found in /tmp/mdd.log. If
possible, the relevant logcat output from the device would also be useful.
Thanks.
Original comment by foobum
on 26 Nov 2011 at 6:45
Hopefully, this should be what you're looking for.
Not sure if it matters, but Im running a Samsung Galaxy mini with CM7 firmware
and the master backend is ubuntu 10.04 server (minimal install, with bits added
as needed).
Cheers.
Original comment by minidroi...@gmail.com
on 26 Nov 2011 at 7:40
Attachments:
Thanks for the logs. Easily fixed by escaping shell meta-characters in video
file names. Commit imminent..
Original comment by foobum
on 26 Nov 2011 at 11:19
This issue was updated by revision r579.
Original comment by foobum
on 26 Nov 2011 at 11:21
[deleted comment]
This issue was updated by revision r580.
Original comment by foobum
on 27 Nov 2011 at 12:40
So, I installed the patches (thanks) and installed ffmpeg & codecs from
medibuntu repo, and we seem to be making grand progress. I can stream videos to
the handset - audio perfect - video bit suspect! - what is recommended backend
spec for streaming to android?
Only problem (think its still related) is streaming recordings to handset -
get the popup as with videos "Connection refused to 192.168.xx.xx:16546" - was
sure it politely told me again "Sorry, this video cannot be played", but can't
reproduce that.
Logs attached again.
Thanks again for all your hard work and excellent app.
Original comment by minidroi...@gmail.com
on 27 Nov 2011 at 2:29
Attachments:
You do need a reasonable cpu on the backend. I use a dual-core Athlon64 and can
happily encode 448 kbps but not 1024 kbps. The more cores the better. An atom
is unlikely to cope. Lower bitrates require less horsepower..
So the problem is that the RTSP connection to VLC is being refused, which
suggests that VLC has had a problem or is just being very slow to start the
stream.. Could you post one more log please? /tmp/vlc.out should tell us what's
going on..
Original comment by foobum
on 27 Nov 2011 at 2:44
OK - to get this log mythdroid DID tell me "Sorry, this video cannot be played"
as well as the popup.
MBE is 2.66ghz celeron with 512MB. :-o
Only trying to stream 192 to handset - hopefully its not the hardware causing
problems.
Original comment by minidroi...@gmail.com
on 27 Nov 2011 at 3:00
Attachments:
This issue was updated by revision r590.
Original comment by foobum
on 27 Nov 2011 at 3:30
The VLC output looks ok. So, I guess it's that VLC is taking a long time to
start the stream (we already wait for a rather long time before accessing it).
I've just committed a potential fix, which causes us to attempt the RTSP
connection three times before giving up. Perhaps you could test the trunk
version of MythDroid?
Original comment by foobum
on 27 Nov 2011 at 3:33
No problem - how is the best way to go about that?
I guess I can use adb to push the file to the device? Where is it located in
the file system? I have no 'locate' in the adb shell!
I am currently sat with a windows laptop, but can use a linux box if it's
easier.
Cheers.
(I also wonder if this may help issue 53)
Original comment by minidroi...@gmail.com
on 27 Nov 2011 at 3:43
See http://code.google.com/p/mythdroid/wiki/BuildGuide
Jump on IRC (#mythdroid on freenode) if you run into any difficulties..
Original comment by foobum
on 27 Nov 2011 at 3:56
Looks like r580 & r590 has solved the problem.
Thank for all your help with this, foobum.
Original comment by minidroi...@gmail.com
on 27 Nov 2011 at 8:52
Thanks for all your help identifying and fixing the issues.
Original comment by foobum
on 27 Nov 2011 at 9:06
Original issue reported on code.google.com by
minidroi...@gmail.com
on 25 Nov 2011 at 11:21