by peter_h » Sun Jan 17, 2010 10:36 pm
My vote goes to using VLC as an external player. In fact, I don't see why it can't be added now to MM3 as a minor update, or script addon - double-click the entry and it passes the filename on to VLC to play. I'd be happy to use existing db fields even, so the db structure as it stands would do. At least for now while the video specific side of the db gets worked out.
Using VLC would save a heap of work for you guys as it plays anything, really efficiently. (For example, it plays back my h.264 SD movies on a 700Mhz celeron without maxing the CPU. Media Player Classic, FFmpeg, etc, can't do that.) I love it almost as much as the monkey.
VLC has a raft of interfaces/APIs to control a borderless, GUI-less playback window, so should be easy(?) to integrate into the MM interface...?
I'm all for leveraging the great work gone into tuning VLC's performance. Don't re-invent the wheel and waste resources, I say.
My vote goes to using VLC as an external player. In fact, I don't see why it can't be added now to MM3 as a minor update, or script addon - double-click the entry and it passes the filename on to VLC to play. I'd be happy to use existing db fields even, so the db structure as it stands would do. At least for now while the video specific side of the db gets worked out.
Using VLC would save a heap of work for you guys as it plays anything, really efficiently. (For example, it plays back my h.264 SD movies on a 700Mhz celeron without maxing the CPU. Media Player Classic, FFmpeg, etc, can't do that.) I love it almost as much as the monkey.
VLC has a raft of interfaces/APIs to control a borderless, GUI-less playback window, so should be easy(?) to integrate into the MM interface...?
I'm all for leveraging the great work gone into tuning VLC's performance. Don't re-invent the wheel and waste resources, I say. :)