Re: [mythtv-users] frontend setup (NFS ?) need clarification
On 31-Dec-05, at 2:41 AM, [EMAIL PROTECTED] wrote: Deleting a movie from the drive doesn't remove it from the database, so it will continue to appear (with image) until you re-scan your media directory from the setup page. This behaviour is controlled by the by the "Newly scanned files browsable" setting in the video setup screen. When the flag is off mythvideo behaves as above and when checked it rescans the video directory to confirm the presence of each file and to add new ones that haven't yet been scanned. Personally I find it handier to have the flag checked although it costs a bit more in startup time. The rest of the post is correct. - George ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] frontend setup (NFS ?) need clarification
On Fri, Dec 30, 2005 at 08:01:43PM +0100, Franco wrote: > How should I set up things so that I can play all my video, music, etc. > from all the frontends? I believe the answer is "NFS", but should I setup > things so that the paths look the same from every machine? > I see that if I try to browse the videos from a frontend, I can see all > the video "covers" I had setup in the backend database, but when I try > to play them, I get a "file not found" (or similar) error. The thumbs and movies are in different directories. Deleting a movie from the drive doesn't remove it from the database, so it will continue to appear (with image) until you re-scan your media directory from the setup page. It will prompt for permission to remove the missing movie from the database. In any case, I think your original speculation is correct and MythTV expects all front-ends to use the same directory paths for the media. That's easily accomplished, and probably a good idea anyway as having a common configuration makes maintaining (or adding) machines easier. > And how do I should setup things, as I have my videos, music, etc., > split among the disks of the various machines? The directory you specify is deep-scanned, so it's possible to use multiple nfs mounts to aggregate various machines under that directory. For example, if box1 exports /home/franco/videos and box2 exports /var/lib/movies, you could mount them as /multimedia/movies/box1 and /multimedia/movies/box2 and then tell Myth that the videos are in /multimedia/movies. You could then aggregate your mp3s under /multimedia/music, thumbs under /multimedia/thumbs, etc. I would suggest using the nfs auto-mounter with the "ghost" option so that the mountpoints will be visible. That way, when Myth isn't playing a movie the nfs share will be unmounted, but when Myth scans the video directory it will know to check both box1 and box2 (which will cause them to automatically mount). > Last question: the only thing I found mentioned in the FAQ, was the > "myth://" URL... do I need to use that and where do I put it? You can probably ignore it. That url is used in MythWeb so that certain clients (which may not even exist yet) can access recordings via the web browser. -- Joke template: Three guys walk into a bar. One of them is a wee bit stupid, and the whole scene unfolds with a tedious inevitability. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] frontend setup (NFS ?) need clarification
On Dec 30, 2005, at 11:01 AM, Franco wrote: Hello, Hi How should I set up things so that I can play all my video, music, etc. from all the frontends? I believe the answer is "NFS", but should I setup things so that the paths look the same from every machine? I see that if I try to browse the videos from a frontend, I can see all the video "covers" I had setup in the backend database, but when I try to play them, I get a "file not found" (or similar) error. What's the purpose, then, of having the paths configurable in the frontend, if they need to be just the same as frontend ones? Your covers and video files need to point to the same path. Not specifically the same exact text. For instance, if you store your videos in /mythtv/videos on your backend machine, the frontend on that same machine should point to /mythtv/videos. However, if you NFS mount to /videos on your remote frontend machine, you should enter / videos in that setup. Another reason for this being configurable is that I have DVD's ripped on my backend machine, but I don't want my kids trying to stream that much data over wireless, so they keep their respective videos on their local machines (rip it on the backend machine, then copy it over the network to their local machine for viewing later). Their video directory is local, but the music/photos catalog is an NFS mount. And how do I should setup things, as I have my videos, music, etc., split among the disks of the various machines? I'd like to be able to watch/listen ALL my stuff from EVERY mythbox in the house... NFS mount wherever you have your data. I believe you can use colons to separate multiple paths. For instance, /mythtv/videos:/videos will look to both directories to populate your videos. I simplified my life by storing everything in a LVM on my backend machine (hooked right to my TV, so I use it as my main frontend machine, as well), then I just have a single location for all my data and can mount it on any other machine I please. Last question: the only thing I found mentioned in the FAQ, was the "myth://" URL... do I need to use that and where do I put it? Never used it before. Sorry I can't help there. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
