| Printable Version of Topic
Click here to view this topic in its original format |
| Unofficial VirtualDub Support Forums > Newbie Questions > "load Processing Settings..." Partly Fail |
| Posted by: Neremerus Feb 23 2015, 12:49 PM |
| I had to re-install my system and thus reinstall Virtual Dub 1.10.4 and the codes. I used this chance to update the used codecs. For example x264vfw 41 2525bm 41092 is used. This work as intended. But I have a problem with "Load processing settings...". Over time I created about 20 profiles for x264. If one of them is used, Virtual Dub loads the audio settings and most of the video settings. But it does not load the compression. It switch to x264vfw but the configuration of this is not loaded and remains unchanged. Virtual Dub does not complain about anything, it just does not change the configuration. I compared the old vdscript files and a new one and the only difference is in the line with "VirtualDub.video.SetCompData". The old files have 4720 as first parameter, the new one 9336. That the second parameter differs is obviously. Decoding the Base 64 and copying the old files over the start of the new one, reencoding and saving as a new file do not work. Thus it is maybe a value of a configuration that is not supported any more and Virtual Dub throws everything away. It took me a lot of hours to create the vdscript files. Is there a way to rescue the compression settings? Can Virtual Dub tell me what causes problems? Is there a way to let Virtual Dub load the remaining configuration values and ignore the defect ones? |
| Posted by: dloneranger Feb 23 2015, 12:57 PM |
| The problem is that you're using a different version of the same codec Virtualdub asks the codec for it's settings and base64 encodes them for saving in the script When loading the script virtualdub unencodes the data and gives it back to the codec as it's settings The different version of the codec goes 'nope the data's wrong' and ignores it Only fix is to use the same version of the codec or do all the codec settings again and resave them (you can delete the VirtualDub.video.SetCompData from your current settings if they're causing problems when loading) |
| Posted by: shekh Feb 23 2015, 12:57 PM |
| If you want to load old encoder settings you maybe need to find exact same codec version that wrote it. I bet x264 simply does not bother to track any versioning of settings. |
| Posted by: BugMaster Feb 23 2015, 02:41 PM | ||
Then you lose this bet because x264vfw have https://github.com/MasterNobody/x264vfw/blob/master/x264vfw.h#L69 exactly for the reason to https://github.com/MasterNobody/x264vfw/blob/master/driverproc.c#L174 from old/incorrect versions as dloneranger said. Version number is the first int in settings struct (current version is 4). P.S. kMods have separate version numbering. |
| Posted by: shekh Feb 23 2015, 02:55 PM | ||
Well, Ideally it could read every old format and apply all settings which are appropriate. Simply rejecting is of little help. |
| Posted by: BugMaster Feb 23 2015, 03:07 PM |
| If you want to backup settings between different versions than you should backup settings in registry: HKEY_CURRENT_USER\Software\GNU\x264 - for 32-bit version HKEY_CURRENT_USER\Software\GNU\x264vfw64 - for 64-bit version ICM_GETSTATE/ICM_SETSTATE messages are not purposed to be used between different versions because this private data which is driver specific. It mostly only useful to make automatic 2pass jobs. |
| Posted by: Neremerus Feb 23 2015, 04:15 PM |
| Thank you for the replies! After the first answers I looked into the source code of x264vfw and its revisions. Because there is nothing to backup and a downgrade is nothing in my mind, I think I will write a converter. The only difference between the versions is UTF-16 for the paths in the new files. Hopefully the conversion will have no side effects. |