VideoHelp Forum




+ Reply to Thread
Results 1 to 4 of 4
  1. Member vhelp's Avatar
    Join Date
    Mar 2001
    Location
    New York
    Search Comp PM
    Afternoon x264 (h.264) fans

    K, here's the scoop.. Using the command line version of x264.exe cli..

    Is there any way to incorporate the *same* param setups used in the virualDub
    default pop-up of it's "x264 encode setup screen" that it uses to encode pseudo
    x246 avi's, though they seem to not be True or Complete x264 ??

    The closest I found.., via searching around on my HDD, and finding this shortcut file,
    x264 configuration vfw, and then right-clicking it to open it's Properties,
    and in the one of the fields has a lable,

    Target: [C:\windows\rundll32.exe x264vfw.dll,Configure ]

    ..there is this "Configuration" file (no ext following it) and I don't know where it is.
    I'm guessing that the x264 configuration vfw (a separate .exe app) is calling *indirectly*
    and is using the param settings from there.

    Theory..
    It could quite possibly be that *only* the vdub psuedo method works with this
    Configuration file

    Anyway.

    I would like to use those settings in the *real* x264.exe command line tool instead, and
    refine the video attributes accordingly. fwiw, I'm using a batch file to incororate the
    long (though necessary) parameters. I'm currently working on a gui front-end to this,
    and I would like to have it default to the same param setup. It seems that when using
    the vdub route, the param settings are remembered in the next project. So, this tells
    me that vdub is saving a "configuration" file (the one above, perhaps) and I want to
    continue using that one, if possible.

    (sorry for the cryptic title, I couldn't think of the best way to word it)

    Thank you all for your support,
    -vhelp 4116
    Quote Quote  
  2. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    VfW stores the settings in the registry, not a config file. You could export them though. Not sure why you would want the VfW's defaults though. The cli version has its own defaults anyway.

    rundll32.exe x264vfw.dll,Configure is the same as opening the config in VDub or whatever.

    There are already plenty of GUI's available. Some have taken their basic design from the VfW GUI to.
    Quote Quote  
  3. Member vhelp's Avatar
    Join Date
    Mar 2001
    Location
    New York
    Search Comp PM
    ]VfW stores the settings in the registry, not a config file.
    registry, hmm.. hadn't thought of that. I'll give it some research.
    However, it is confusing, because, as i've posted above (again, here)

    Target: [C:\windows\rundll32.exe x264vfw.dll,Configure ]

    ..seems to include this mysterious Configure.


    There are already plenty of GUI's available.
    Well, it's not that I don't have interest in them.. I just do this for the
    hobby and stuff.

    Thanks for the interest, though.

    Cheers,
    -vhelp 4117
    Quote Quote  
  4. Member
    Join Date
    Dec 2004
    Location
    Australia
    Search Comp PM
    Configure is the entry point. Have a look at DriverProc.def in the source. There is no configure file.

    Speaking of source, if you also look at config.c you can get the registry names and default values.
    i.e.
    Code:
    { "bitrate",        &reg.bitrate,         800 },
    Like I said though you will want to look at the cli defaults since in alot of cases they will be the same anyway.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!