HDMI support in MVPMCX2 client for NMT

[nycaleksey]

Hi,

I am trying to understand how to start using GBPVR client on my NMT and I am under the impression that the latest client doesn't support HDMI output. Is this correct? Could someone explain why HDMI support is problematic?

Thank you.

[mvallevand]

Maybe some clarification is in order. mvpmcx2 as installed following the "Dummies Guide" uses the standard NMT media player used by all the NMT applications (ie the NMT file browser, YAMJ and other jukeboxes, myiHome, SwissCentre, llink, UPnP). This is a professional grade player for all media types and all monitors and connections. HDMI is not an issue.

However because mvpmcx2 uses this external player, the integration is limited during media playback, pretty much the only function available is changing channels in livetv. To compare it to GBPVR on a PC, it would be like launching VLC, MPC, or WMP to play your media, you can certainly access the media reasonably well, but the functionality of GBPVR is lost.

Recently with the "Directors Cut" release sub and I coordinated an integrated native mode player for mpeg ps and ts files. It is focused on playing analog and digital broadcast captures and is nowhere near as powerful as the NMT player but at the same time it delivers on full PVR functionality (menus while video is playing, commskip, rewind, mp3 playback with the GBPVR screen, much faster loading of media). The NMT player will always be used for non-mpeg video files and if you use an HDMI connection to your monitor. In both releases, when media isn't playing you have complete PVR functionality so it still is pretty powerful.

Why wasn't HDMI included in the last release? Primarily because it is not easy stuff. Can you look at your PCH and program it to do anything at all other than maybe making a simple skin change or modifying html code like the jukeboxes do? That is how it was for me just over a year ago, I couldn't even control the screen or the remote, and there is no documentation on how to do this. Sub tried an interface that didn't use mvpmcx2 and while it was a great achievement, it suffered from too many of the warts of the NMT browser.

As my knowledge of the NMT continues to grow I am not saying HDMI from native mode is going to be impossible, in fact over the last couple of weeks I got a much better handle on how to program for it and I am actually optimistic that I have overcome the biggest obstacles. If started this first, the programming would have been impossible because I was introducing too many variables without the depth of knowledge I needed. My nature is to be conservative to manage expectations, I do this as a hobby so there is really zero value to marketing vapourware, especially as I have the most demanding clients to please, (read that as WAF).

Martin

[nycaleksey]

First of all I want to thank you very much for your efforts.

So in Director's Cut version of the client you developed a custom NMT software piece for the mpeg playback functionality that addresses the long-standing annoying issues it has (timeseeking, etc) and adds long-awaited functionality (comskip)? This is very cool. Hopefully HDMI version will come out and I will be able to use this client as well.

I don't understand why Syabas people can't fix this timeseeking bug - the MPEG TS playback is crippled on NMT and this makes it impossible to watch recorded broadcasts.

I'll try out the pre-DC version to see how it works on my setup. My TV doesn't support component input unfortunately.

Thanks again for a very cool software!

[martint123]

Thanks also for that clear explanation Martin, it helps me picture what is going on and the hurdles you have to leap.
From what you are saying, then I guess h264 .ts files as broadcast in the UK for HD are also passed onto the NMT player?.
I wish you success with your HDMI understanding and control as I look forward with hope to the possibility of forward skipping of in-progress recordings.

regards and thanks for your valuable contributions and time.

[mvallevand]

@nycaleksey you can also try svideo and composite too to see if your mpeg-ts files are handled. mpeg-ts file handling is tricky so Syabas isn't completely at fault, as you may note by the many posts in the PC based playback section and GBPVR doesn't report the timeline correctly either. The difference is I am trying to do something about the problem, so if the file doesn't play in the Director's Cut with a sample I might be able to figure out a workaround.

@martin123 h264 files are a problem because I don't support 1080i, 720p and 576p sample can work ok. The new client can be configured to either send all h264 ts files to the NMT player or selectively with the alter enter (which is the USB Eject key on the remote)

Martin

[pBS]

i must say you've done an excellent job with what does work, i only use mpeg2 ps [both sd and atsc-hd] and it works perfectly for me on a wireless g setup... [except for when the microwave is on! lol]
i'm saving up for a wireless-n stick so i can stream my blu-rays-turned-mpegs..but for all the atsc it handles it just fine even on with a lowly non-turbo g setup..

but i'm on component only with mpegps so i get all the benefits...