Problem using link2/Procoder

[Happygolucky]

I've entered a bug report on this but thought I'd post it here to see if anyone else sees the same thing.

I have the latest release of DVD2SVCD installed, using Procoder 1.01.35 and Link2 frameserving (version 0.95). After extensive testing, it appears that DVD2SVCD is passing incorrect pathname to Link2. DVD2SVCD is passing ".\filename.avs" instead of the full pathname. Link2 is making the .avi file using ".\filename.avs" and when Procoder opens it, it is then trying to view C:\Windows\system32\filename.avs which of course does not exist. I have set all the directories correctly in DVD2SVCD, I checked the ini file and d2s file, all have the correct dirs. The problem is that DVD2SVCD isn't passing the full path name to Link2.exe.

I switched to using VFAPI and Procoder will get the correct file, but of course I'd prefer using Link2 with Procoder.

[dvd2svcd]

Well, it must be a problem at your end because the path .\something is the correct path. The reason is that Link2 is very sensible towards long pathnames. I have tested this and it works (well it works here anyway).

[DDogg]

Working here too. I do have a short pathname as my working files are in C:\maid Maybe that has something to do with it.

[Happygolucky]

Originally posted by dvd2svcd
Well, it must be a problem at your end because the path .\something is the correct path. The reason is that Link2 is very sensible towards long pathnames. I have tested this and it works (well it works here anyway).

Strange. No matter what I try, the ".\filename" comes out as "C:\Windows\system32\filename". Could it be because the aviwrap.dll is installed in that directory?

[DDogg]

Sorry for asking the obvious, but what happens if you try to manually wrap the same thing that d2s is trying to do?

[Happygolucky]

Originally posted by DDogg
Sorry for asking the obvious, but what happens if you try to manually wrap the same thing that d2s is trying to do?

Link2 gives me an error stating that the path is too long. It is like this:

C:\Movies2burn\movie\filename.avs

but DVD2SVCD has link2 use:

.\filename.avs

Which Procoder thinks points to:

C:\Windows\system32\filename.avs


Very odd, not sure what is going on. VFAPI works fine, though, so I guess I can forget about using link2.

[DDogg]

Just for the hell of it, do me a favor and put your output dir as c:\mov on your next encode or manual test.

[Holomatrix]

I had the same problem. It should work if you keep your directory structure 8 and under characters in length. Right now I would assume that Link2 is looking for your file in C:\Movies2~1\movie\filename.avs which does not exsist so is defaulting to you system path.

[Happygolucky]

I've renamed the folder to C:\Movies so I'll give it another try and see what happens. Thanks for all you guys help, it is very appreciated.

[Happygolucky]

Originally posted by Happygolucky
I've renamed the folder to C:\Movies so I'll give it another try and see what happens. Thanks for all you guys help, it is very appreciated.


OK, I renamed the folder and tried again. Running link2 manually, I can point it to the avs file and make the avi file (using the exact same names as DVD2SVCD does) and it works just fine. Using DVD2SVCD, however, it makes an avi file that points to the C:\Windows\System32 directory. I've checked in the ini file and d2s file for all the path names and everything looks just fine, so I'm not sure what is going on. I finally just gave up and did the job manually using TMPGEnc Plus and some creative editing of an avs file.