Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
On Mon, 14 Mar 2005 21:10:20 -0800, Ian Forde <[EMAIL PROTECTED]> wrote: > On Mon, 2005-03-14 at 21:49 -0700, Darren Richards wrote: > > Thanks for the suggestions. This will work in about 95% of the cases, > > but there are certain dvd's which require special options (like -aid > > 128). But specifying -aid 128 for all dvd's cause most of them to not > > play in dolby digital, even though I also specify ac=hwac3. So I need > > to specify separate options on a per-movie basis. > > > > I suppose I could make the script smart enough to supply different > > arguments based upon the filename. Perhaps I'll try that. > > No problem - what you could do is have a .desc file with the same > basename as the movie. Within that, you could specify the options that > you want to call mplayer with. From your script, you check for .desc > file for options. You would also need to configure mythvideo to > ignore .desc files the same way that .log files are ignored by default. > > Another (and probably smarter) way would be to give them a different > extension, so you could invoke mplayer on those particular files with > the -aid 128 option... The idea (for me, at least) is to avoid file- > specific options as much as possible and group movies into classes. > That's why I use .vob for avi files with AC3, and .avi/.mpg for the > others (with the exception of .dvdrip which is a straight iso that I use > xine for.) > > -I > Thanks, Ian. Great suggestions. I'll have to whip up a script to do something along those lines. -darren ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
On Mon, 2005-03-14 at 21:49 -0700, Darren Richards wrote: > Thanks for the suggestions. This will work in about 95% of the cases, > but there are certain dvd's which require special options (like -aid > 128). But specifying -aid 128 for all dvd's cause most of them to not > play in dolby digital, even though I also specify ac=hwac3. So I need > to specify separate options on a per-movie basis. > > I suppose I could make the script smart enough to supply different > arguments based upon the filename. Perhaps I'll try that. No problem - what you could do is have a .desc file with the same basename as the movie. Within that, you could specify the options that you want to call mplayer with. From your script, you check for .desc file for options. You would also need to configure mythvideo to ignore .desc files the same way that .log files are ignored by default. Another (and probably smarter) way would be to give them a different extension, so you could invoke mplayer on those particular files with the -aid 128 option... The idea (for me, at least) is to avoid file- specific options as much as possible and group movies into classes. That's why I use .vob for avi files with AC3, and .avi/.mpg for the others (with the exception of .dvdrip which is a straight iso that I use xine for.) -I ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
On Mon, 14 Mar 2005 20:08:33 -0800, Ian Forde <[EMAIL PROTECTED]> wrote: > On Mon, 2005-03-14 at 20:30 -0700, Darren Richards wrote: > > Upon double-checking mysettings, it seems that one frontend was > > pointing to /video/dvds, and the other was pointing to /mnt/hdb1/dvds. > > While physically they were the same place, they had two different > > names. Now that both are pointing to /video/dvds, the problem with > > the database getting overwritten has been resolved, but I have a new > > problem: I can no longer set unique player commands for each frontend. > > The settings I make on one frontend take affect on the other. This > > won't work for me because I have different hardware. On one frontend, > > I want to play the ac3 sound through my optical output (using the -ac > > hwac3 flag on mplayer), but I don't want this on my other frontend... > > > > How can I have different settings for the different frontends? > > Ah - that's an easy one. If the mythfrontend users on each box have > separate homedirs, you can set the ac option in ~/.mplayer/config for > each box. > > Example: > AC3-enabled frontend has ~/.mplayer/config with: > ac=hwac3, > > other frontend has ~/.mplayer/config leaves the option empty. > > Of course, if both frontend users share a homedir, you'll be better > served by using a script to autodetect on the fly. > >-I Thanks for the suggestions. This will work in about 95% of the cases, but there are certain dvd's which require special options (like -aid 128). But specifying -aid 128 for all dvd's cause most of them to not play in dolby digital, even though I also specify ac=hwac3. So I need to specify separate options on a per-movie basis. I suppose I could make the script smart enough to supply different arguments based upon the filename. Perhaps I'll try that. Thanks again guys, -darren ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
On Mon, 2005-03-14 at 20:30 -0700, Darren Richards wrote: > Upon double-checking mysettings, it seems that one frontend was > pointing to /video/dvds, and the other was pointing to /mnt/hdb1/dvds. > While physically they were the same place, they had two different > names. Now that both are pointing to /video/dvds, the problem with > the database getting overwritten has been resolved, but I have a new > problem: I can no longer set unique player commands for each frontend. > The settings I make on one frontend take affect on the other. This > won't work for me because I have different hardware. On one frontend, > I want to play the ac3 sound through my optical output (using the -ac > hwac3 flag on mplayer), but I don't want this on my other frontend... > > How can I have different settings for the different frontends? Ah - that's an easy one. If the mythfrontend users on each box have separate homedirs, you can set the ac option in ~/.mplayer/config for each box. Example: AC3-enabled frontend has ~/.mplayer/config with: ac=hwac3, other frontend has ~/.mplayer/config leaves the option empty. Of course, if both frontend users share a homedir, you'll be better served by using a script to autodetect on the fly. -I ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
Darren Richards wrote: How can I have different settings for the different frontends? make them run a script, which is different on each machine but on the path of both. Something like mplayer.sh Which internally calls mplayer with parameters supplied plus your customizations. Yan ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
On Mon, 14 Mar 2005 15:31:46 -0500, PAUL WILLIAMSON <[EMAIL PROTECTED]> wrote: > >>> "Darren Richards" <[EMAIL PROTECTED]> 03/14/05 3:22 PM >>> > >Thanks, everyone, for the suggestions. But I do have both frontends > >pointing to the same location. I guess the one difference is instead > >of creating a link from /mnt/dvds to /video/dvds (where I have them > >stored), I actually created the nfs mount directoy from /video/dvds > on > >my backend to /video/dvds on my second frontend. Maybe I'll try the > >more "correct" way of creating the mount point in /mnt and creating a > >symlink. > > Not a correct way really, just the way *I* prefer to do it. I get > confused easily, and I've been known to forget that a filesystem > is nfs mounted. No way I can do it this way... > > >But shouldn't the current setup work? Both frontends are pointing to > >/video/dvds. That never changes, and I can always watch the movies > >from either front end, but the database info keeps getting reset > >whenever I bring up the video manager... > > > >Thanks again, > >darren > > It should work. If both frontends (local and remote) are pointing > to the exact same path, all should be fine. What you described > certainly sounded like one was over-writing the other. > > Did you try to enter the IMDB stuff on the remote frontend, or > just the local frontend? When you did this, did you look in the > mythconverg database to see exactly how the video was > being seen by that frontend? > > Paul > > Upon double-checking mysettings, it seems that one frontend was pointing to /video/dvds, and the other was pointing to /mnt/hdb1/dvds. While physically they were the same place, they had two different names. Now that both are pointing to /video/dvds, the problem with the database getting overwritten has been resolved, but I have a new problem: I can no longer set unique player commands for each frontend. The settings I make on one frontend take affect on the other. This won't work for me because I have different hardware. On one frontend, I want to play the ac3 sound through my optical output (using the -ac hwac3 flag on mplayer), but I don't want this on my other frontend... How can I have different settings for the different frontends? Thanks, darren ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] MythVideo database resetting itself afteraddingsecond frontend
>>> "Darren Richards" <[EMAIL PROTECTED]> 03/14/05 3:22 PM >>> >Thanks, everyone, for the suggestions. But I do have both frontends >pointing to the same location. I guess the one difference is instead >of creating a link from /mnt/dvds to /video/dvds (where I have them >stored), I actually created the nfs mount directoy from /video/dvds on >my backend to /video/dvds on my second frontend. Maybe I'll try the >more "correct" way of creating the mount point in /mnt and creating a >symlink. Not a correct way really, just the way *I* prefer to do it. I get confused easily, and I've been known to forget that a filesystem is nfs mounted. No way I can do it this way... >But shouldn't the current setup work? Both frontends are pointing to >/video/dvds. That never changes, and I can always watch the movies >from either front end, but the database info keeps getting reset >whenever I bring up the video manager... > >Thanks again, >darren It should work. If both frontends (local and remote) are pointing to the exact same path, all should be fine. What you described certainly sounded like one was over-writing the other. Did you try to enter the IMDB stuff on the remote frontend, or just the local frontend? When you did this, did you look in the mythconverg database to see exactly how the video was being seen by that frontend? Paul ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
