RB
20th January 2003, 18:32
Hi,
I believe that the following is a bug in DVD2SVCD 1.1.0 build c:
Let's say we have two AVISynth scripts in dvd2svcd.ini where both use the same variables. Just for example:
[AVISYNTH_Script1]
0=BilinearResize(^Width, ^Height)
^Width=352
^Height=480
[AVISYNTH_Script2]
0=BicubicResize(^Width, ^Height)
^Width=480
^Height=576
Now when you select Script2 on the Frameserver tab and enter the values for Width and Height, they appear correct. But when D2S eventually creates the AVS file, the AVS actually contains
BicubicResize(352, 480)
The values are whatever you last put in for Script1.
That is, it looks like when D2S creates the AVS, it simply scans the INI file for the first occurence of the variable names and takes the values from there instead of reading them from the INI section for the currently selected script. I would be thankful if that could be fixed in a later release.
I believe that the following is a bug in DVD2SVCD 1.1.0 build c:
Let's say we have two AVISynth scripts in dvd2svcd.ini where both use the same variables. Just for example:
[AVISYNTH_Script1]
0=BilinearResize(^Width, ^Height)
^Width=352
^Height=480
[AVISYNTH_Script2]
0=BicubicResize(^Width, ^Height)
^Width=480
^Height=576
Now when you select Script2 on the Frameserver tab and enter the values for Width and Height, they appear correct. But when D2S eventually creates the AVS file, the AVS actually contains
BicubicResize(352, 480)
The values are whatever you last put in for Script1.
That is, it looks like when D2S creates the AVS, it simply scans the INI file for the first occurence of the variable names and takes the values from there instead of reading them from the INI section for the currently selected script. I would be thankful if that could be fixed in a later release.