mtd not started by default -> dvd ripping not working

[Sylvain Defresne]

MTD is used by the DVD ripping facility of MythTV (see http://www.mythtv.org/wiki/index.php/MythDVD#DVD_Ripping ), however it is not started by mythbuntu even when the mythdvd plugin is installed. It should be started by default when the mythdvd plugin is installed.

[Sylvain Defresne (sdefresne)]

The attached script, when installed in /etc/init.d/mtd, and registered by 'update-rc.d mtd defaults' will start mtd (Myth Transcoding Daemon) when starting the computer, thus enabling the DVD ripping facility of MythTV.

I think it should be included in the mythdvd package.

[laga (laga)]

Is this really needed? You just hit "0" to start mtd.

Also, didn't we use to autostart mtd?

[Sylvain Defresne (sdefresne)]

Well, if I don't start MTD before-hand, I get the following error message : "Cannot connect to your Myth Transcoding Daemon. You can try hitting any number key to start it. If you still see this message, then something is really wrong."

If I hit "0", nothing seems to happen, I still get this error message. Thus my bug report. And even if pressing "0" were working, it does not seems to work in default configuration, thus giving an impression of unpolish (this is my impression) ...

[Nick Fox (nickj-fox)]

I would agree here. Unless there are reasons that prevent mtd from being a
background process, why should we not have this running so this message does
not appear for users not understanding this as a normal operation for
mythdvd?

-Nick

On Nov 11, 2007 3:00 PM, Sylvain Defresne <email address hidden> wrote:

> Well, if I don't start MTD before-hand, I get the following error
> message : "Cannot connect to your Myth Transcoding Daemon. You can try
> hitting any number key to start it. If you still see this message, then
> something is really wrong."
>
> If I hit "0", nothing seems to happen, I still get this error message.
> Thus my bug report. And even if pressing "0" were working, it does not
> seems to work in default configuration, thus giving an impression of
> unpolish (this is my impression) ...
>
> --
> mtd not started by default -> dvd ripping not working
> https://bugs.launchpad.net/bugs/162049
> You received this bug notification because you are a member of
> Mythbuntu, which is the bug contact for Mythbuntu.
>

[Mario Limonciello (superm1)]

It should be starting. Look at:

http://codebrowse.launchpad.net/~mythbuntu/mythbuntu/mythbuntu-default-settings/annotate/supermario%40portablemario-20071010184626-cmls9jupee2xwdzt?file_id=admin_session.sh-20070704025724-ke5marctr1h515o6-20

On Nov 11, 2007 8:55 PM, Nick Fox <email address hidden> wrote:

> I would agree here. Unless there are reasons that prevent mtd from being a
> background process, why should we not have this running so this message
> does
> not appear for users not understanding this as a normal operation for
> mythdvd?
>
> -Nick
>
> On Nov 11, 2007 3:00 PM, Sylvain Defresne <email address hidden> wrote:
>
> > Well, if I don't start MTD before-hand, I get the following error
> > message : "Cannot connect to your Myth Transcoding Daemon. You can try
> > hitting any number key to start it. If you still see this message, then
> > something is really wrong."
> >
> > If I hit "0", nothing seems to happen, I still get this error message.
> > Thus my bug report. And even if pressing "0" were working, it does not
> > seems to work in default configuration, thus giving an impression of
> > unpolish (this is my impression) ...
> >
> > --
> > mtd not started by default -> dvd ripping not working
> > https://bugs.launchpad.net/bugs/162049
> > You received this bug notification because you are a member of
> > Mythbuntu, which is the bug contact for Mythbuntu.
> >
>
> --
> mtd not started by default -> dvd ripping not working
> https://bugs.launchpad.net/bugs/162049
> You received this bug notification because you are a member of
> Mythbuntu, which is the bug contact for Mythbuntu.
>

--
Mario Limonciello
<email address hidden>

[laga (laga)]

I've just been able to reproduce this. Granted, it was on Beta 1, but the relevant lines in session.sh were there and mtd was _not_ started.

When I manually ran

     #If we have mtd around (and not running), good idea to start it too
       if ! `pgrep mtd>/dev/null`; then
           if [ -x /usr/bin/mtd ]; then
               /usr/bin/mtd -d
           fi
       fi

in a Terminal, it started (and stayed running).

What could cause this? Something missing in the environment, caused by the desktop environment not being running yet?

[Nick Fox (nickj-fox)]

This has been resolved in 0.21. No fix required I have verfied this working as it should.

[Nigel Stewart (nigels)]

Recently updated from 8.10 to 9.04 and noticed that mtd was no longer running.
Seems to be due to permissions issues:

-rw-r--r-- 1 29999 mythtv 158 2008-11-18 08:38 mtd.log

Changed this to:

-rw-rw-r-- 1 mythtv mythtv 158 2008-11-18 08:38 mtd.log

And mtd is able to launch via session.sh
Posting this in case this bites anyone else.
Can't say if the problem on my setup was self-inflicted, or not.

[Jeremy Nickurak (nickurak)]

Still getting this in lucid.

[Jeremy Nickurak (nickurak)]

Affects mythvideo via mythplugins.

[Nick Fox (nickj-fox)]

http://i-wikisport.com/product.php?topic=5fy

[Thomas Mashos (tgm4883)]

Marking incomplete as this release isn't supported anymore. Can anyone confirm that this issue is still present on a supported Mythbuntu/MythTV release?

[Thomas Mashos (tgm4883)]

Marking this bug as invalid, since upstream has removed dvd ripping from mythtv