x264 configuration component

[stax76]

Well, I want to support x264.exe in my upcomming Stax Media Encoder as well, for XviD support I was able to invoke the XviD config dialog and save the settings in a hashtable and write it back to the registry before encoding. I'm afraid for x264.exe it won't be that easy because there is no dialog I can invoke unless somebody offer a .NET assembly or a automation server or something like that I can utilize. I could write my own but to be honest I would have more fun coding DVB...

[LigH]

You are using XviD as a VfW codec, am I right here?

And for x264, you prefer the standalone encoder over the VfW codec?

[Doom9]

no dialog I can invoke unless somebody offer a .NET assembly or a automation server or something like that I can utilizePut MeGUI's x264ConfigurationDialog, x264Settings, commandlineGenerator and MeGUISettings into a class library, create a MeGUISettings object and just fill in the x264.exe path, then launch the Dialog, get the x264Settings object back, send it to the commandlineGenerator along with the settings object and you have your commandline.

But to be consistent with how you use other codecs, you might want to use the VfW (there's no avi output in x264.exe after all, and hardly anything can handle raw avc streams.. you won't get it into an avi unless you use avc2avi, won't get it into OGM period (unless you're using VfW), won't get into matroska unless you use direct MP4 output).

[stax76]

You are using XviD as a VfW codec, am I right here?


exactly


And for x264, you prefer the standalone encoder over the VfW codec?


VfW comes for free as I've got already a abstract class to handle VFW but I would like to support also command line


Put MeGUI's x264ConfigurationDialog, x264Settings, commandlineGenerator and MeGUISettings into a class library, create a MeGUISettings object and just fill in the x264.exe path, then launch the Dialog, get the x264Settings object back, send it to the commandlineGenerator along with the settings object and you have your commandline.


thank you for the offer. It would be possible to make a component others can use as well. It could be a executable that is a standalone application but could also be utilized by other applications, managed or native. I could build it but I couldn't maintain it. I could translate it to any .NET language including C++/CLR in case somebody want's to maintain it but don't want to use C#. Ideally it would ship together with x264.exe to avoid versioning issues. I guess there is still people disliking .NET but I don't care. Maybe somebody can do it native, I would use Delphi.

[Doom9]

It would be possible to make a component others can use as well. It could be a executable that is a standalone application but could also be utilized by other applications, managed or native.Why a standalone? A commandline generator isn't doing you much good without a launcher, is it? You're obviously going to launch x264.exe on your own. And MeGUI has the logic to host the dialog and run x264.exe. And having an executable that just yields the commandline doesn't seem of much use.. those that want/need a GUI do not want to go to a commandprompt to launch encoding afterwards for obvious reasons.

I think once a dll template is set it, it could just be recompiled based on the MeGUI source whenever there's a new release. I plan to keep the dialog updated with x264.

[stax76]

a dll could be used easier, a executable demonstrating the the dll would still be a option however. There is a lot applications trying to achieve the same goal so possibly there could be more cooperation. We should however face our applications will compete against each other.