#105 Making AviSynth portable

Next Release
closed
Internals (20)
5
2011-01-30
2011-01-30
No

AviSynth works great portable when converting all HKEY_LOCAL_MACHINE registry entries to HKEY_CURRENT_USER, except for the plugins. AviSynth only checks "HKLM\Software\AviSynth" for the "plugindir2_5" value. How about changing the following in avisynth.cpp:

if (RegOpenKeyEx(RegRootKey, RegAvisynthKey, 0, KEY_READ, &AvisynthKey))
return 0;

to:

if (RegOpenKeyEx(RegRootKey, RegAvisynthKey, 0, KEY_READ, &AvisynthKey))
{
if (RegOpenKeyEx(HKEY_CURRENT_USER, RegAvisynthKey, 0, KEY_READ, &AvisynthKey))
return 0;
}

Discussion

  • Ian Brabham

    Ian Brabham - 2011-01-30

    Last time I tested it, the AviFile interface would not reference the HKEY_CURRENT_USER tree for it's registration data. However a number of product, like x264, now directly access Avisynth, thus significantly helping the standalone cause without the need for the AviFile interface. There has also been the occasional request for per user specification for the plugin directory. In line with these requests it would seem prudent to search the per user data first.

    I will commit appropriate changes in the next batch of CVS commits.

     
  • Ian Brabham

    Ian Brabham - 2011-01-30
    • milestone: 269631 --> Next Release
    • assigned_to: nobody --> ianb1957
    • status: open --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks