Hi Gary... I am going to post this to the list as I want people who have done this to review my comments...
Let me repeat just to be clear - HD bit rates are too high for the mvpmc. I don't know if anyone has had success with this. What people have done is to get VLC to transcode the MythTV videos. To do this, and I don't so use this as a guide line, you need to make symbolic links to the MythTV video files using an ".avi" suffix. You can copy and rename them as well. Then you can NFS export all these files and mount them on the mvpmc box. Note, I believe the path on both the sever and the mvpmc box need to be the same for this to work. Now you can browse the video files with the mvpmc file browser and select/play-back one of them. The VLC and mvpmc will think the .avi file is not compatible w/mvpmc and VLC will transcode the video for mvpmc. The transcoded video will be at NTSC like bit rates and will play back on the mvpmc box. See, that's why I would really like it if MythTV would do this auto-magically for you. In addition - I should point out that AC3 pass through is not expected to stay in sync with the video on the mvpmc box. Martin hit upon a initial starting point that makes my NTSC bit rate digitally recorded MythTV shows initially work. But I haven't tested anything longer than 15 minutes. Normal audio works fine. Yet another reason to make MythTV transcode the video before giving it to the mvpmc box. > Thanks for the reply. I wonder if you can rebuild the dongle without > setting up a PPC compile environment. (Gary is asking because I assumed the mvpmc start up script is only loaded as part of the initial tftp'ed dongle -and- I assume he wants to change the script w/o having to build the dongle from scratch.) Jon's make/scons stuff is top notch. That is, setting up a PPC cross compiler should be automatic. And trying other paths to build a dongle might cause more trouble than just typing "make mvp". That said I believe I was wrong. It's been a while since I set my dhcp and tftp up. Here is the way I have it set up on a Linux box. For my 1st mvpmc box my startup script is here: /tftpboot/dongle.bin.mvpmc.config and my dongle is here: /tftpboot/dongle.bin.mvpmc. My dhcp entry in /etc/dhcp.conf dictates the name of the dongle. This information, apparently, is used in forming the name of the configuration script. For my second box, I wanted to use a different configuration but the same dongle. So I symbolically linked a file called /tftpboot/dongle.bin.mvpmc2 to the original /tftpboot/dongle.bin.mvpmc. However, the configuration script is a new file called /tftpboot/congle.bin.mvpmc2.config. From these examples you can see how the names of the dongle and configurations scripts need to match. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mvpmc-users mailing list Mvpmc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
