Post
by Quu » Fri Sep 10, 2010 12:53 pm
the interface to MPC-HC can't be changed (though the web interface might be), they don't support skins or the like... but they do support an IPC interface, so I could write a convention specific interface and control MPC-HC remotely... like i was planning on doing with mplayer's -slave mode. If i could not use MPC-HC to run the con's videos, i would not have tested it ^_^.
my disappointment is that MPC-HC is windows only, which means that if that ends up being the final solution, then I have cut out the linux and mac users. I have high hopes for mplayer under linux... I just need to learn linux gui crap.
I need a working video solution that can perform on two pieces of hardware... the acer revo, and one of AWA's existing playback computers. I don't care what OS i have to run to get it there, it is the minimal hardware targets I have. If i find a solution that is linux only on those two, i can require mac and windows to have more hardware and be happy.
So far, my working solutions are :
MPC-HC + Custom web interface
Advantages : Minimal code ownership by me, i just maintain the web code. Free
Disadvantages : Windows Only, Not as tight control on the play list as i would like. Would require local computer use web interface.
MPC-HC + Custom IPC interface
Advantages : basically total control over the interface. utilize MPC-HC as the render engine, taking advantage of it's sync correction and other tools. Could swap out vlc and mplayer for the render engines with minimal effort if UI is written in java. free
Disadvantages : Windows Only. More to code
DirectShow Custom Code
Advantages : absolute control over the interface and experience. could use the stand alone filters from mpc-hc or others, such as coreavc (free if using MPC-HC filters, cost otherwise)
Disadvantages : windows Only. allot of code to maintain and keep up to date, have to add in sync correction and everything manually.
Solutions yet to test under linux (and I hope work)
VLC + skin + custom web site
advantages : minimal code ownership
disadvantages : requires beefier computer for win32, untested under linux and vdpau
mplayer + custom IPC interface
Advantages : basically total control over the interface. utilize mplayer as the render engine, taking advantage of it's sync correction and other tools. Could swap out vlc and mpc-hc for the render engines with minimal effort if UI is written in java. mplayer is designed for an interface to sit on top of it. free
Disadvantages : only hardware accel is vdpau under linux, otherwise requires beefier computer. have to build copies from svn/git which means additional testing and support
Lead me not to temptation, for I have deadlines