mvpmcx2 and component output?

[NevOZ]

hi Martin,

Good news ... the second command you gave me works! Well done & thanks. I set the config.xml to 1920x1080 also, because at 1280x720 the picture was quite small on the screen. Still though, the picture is slightly too big and gets chopped off at the edges, I'm assuming I just need to adjust the config.xml entries a little more.

The first command didn't work, the error from telnet capture is shown at the bottom of this post.

Another problem I had was that it wasn't reading from the correct <MAC-XX....> section from config.xml, was instead reading from <MAC-DEFAULT>. I tracked down the reason being that I am using a wireless bridge between the PC and the PCH. This wireless bridge reports the MAC address of the PCH as being the MAC address that the wireless bridge has. So all I needed to do was use the MAC address of the bridge, and all was fine. This is obviously not a problem with your software, but with the wireless bridge (a known limitation of wireless bridge with DD-WRT firmware).

Anyway, heres the telnet capture of the command that didnt work:
/etc/mvpmc/mvpmcx2 -m 1080 -o component --display --frequency 50
post --frequency
killall: wget: no process killed
(*) DirectFB/Config: Active DTV standard hdtv60
(*) DirectFB/Config: Active DTV signal sdtv
(*) DirectFB/Config: Active DTV connector hdmi
(*) DirectFB/Config: Active Component standard hdtv60
(*) DirectFB/Config: Active Component signal sdtv
(*) DirectFB/Config: Active Component connector ycrcb
(*) DirectFB/Config: Active Analog standard ntsc
(*) DirectFB/Config: Active Analog signal ntsc
(*) DirectFB/Config: Active Analog connector cvbs
(*) DirectFB/Config: Driver options file /etc/smp8634rc
(!) DirectFB/Config: Unable to open config file `//.directfbrc'!
(*) DirectFB/Config: Active Component connector ycrcb
(*) DirectFB/Config: Active Component signal 1080i
hdtv60 --frequency
(!) DirectFB/Config 'mode': Could not parse mode!
dfb.c <169>:
(#) DirectFBError [DirectFBSetOption ("mode", display)]: Invalid argument!

Thanks again Martin,

[mvallevand]

Great. I gave you a bad command line for the first test it should be

/etc/mvpmc/mvpmcx2 -m 1080 -o component --frequency 50

You should set config.xml back to 1280x720 and retest when you have time.

How is the speed of at 1920x1080 over wireless? It is sort of the worst case scenario for sub and I. I still hope that 1280x720 will work.

Martin

Edit: Interesting note on the MAC address, thanks.

[NevOZ]

I tried your corrected command, and also config.xml with 1280,720 and this works. Thanks.

I have a dumb question for you. Should I be able to use the "Watch" command to watch TV? When I select this it seems to stall and nothing happens. I'm assuming this is because of my wireless performance. Because of the distance and walls between PC and PCH I'm only getting a 1.5 Megabyte/sec transfer rate, according to FTP transfers

[NevOZ]

Hmm, when I attempt to play back a Recording it seems to stall also. Nothing happens when I select "Play", and navigation slows to a big crawl.
When I run PVRX2 on my PC and Play the same recording it runs perfectly ... but not on the PCH.

[mvallevand]

I'm rushing getting for work, so a couple of quick comments.

- for livetv if you can get 1.5 MB constantly that will be about what the MVP is capable of and it works fine for SD television. Check to see that your live tv directory exists.

- go to telnet and run the command line and send the capture logs.

- if your recordings are on a share there could be a permissions issue so zip and upload your gbpvr logs.

Martin

[NevOZ]

Martin, thanks for your suggestions.
I was able to get it to work by changing the "BDA Multiplexer" option from DVR-MS to TS-Mux. That did the trick. It simply wont play any recordings in DVR-MS format.
Strangely it detects the audio stream of the recording as DTS, although I'm certain they aren't transmitted as DTS from the TV networks.
As you correctly said, SD streams come through perfectly fine. HD stutters, but that should hopefully change when Sybaas releases the new wireless-N compatible firmware. This will allow one to connect an Atheros-based wireless-N USB adapter.
Thanks again for all your help Martin!

[mvallevand]

I hate DVR-MS so much I forget it exists. I have added a note to not use it on the install guide.

Martin

[NevOZ]

I hate DVR-MS so much I forget it exists.
Martin

Agreed, it's proprietary rubbish!!
In your install guide, you may want to let people know that the setting is in the Config program under the Misc2 tab. The option is called "BDA Multiplexer". Just so users know where to find it.