Comments about DIKO 2.45

[vmesquita]

Post your comments here.

[MASE]

I cant say anything bad about it yet...
Made my firts svcd with it, smoothly!

[MASE]

When trying to convert a dvd into a svcd, this is the error :

Code:

16:02:07: Error: Can not enumerate files in directory 'C:\Program Files\DIKO 2.45\Batch\' (error 3: system cant find path/directory.)
16:02:07: DIKO GOLD 2.45
16:02:07: --------------
16:02:07: *************** Getting movie info **************
16:02:07: ----------------Processing Movie 0----------------
16:02:07: Script Template: .\scripts\dvd\kwagOptimalSKVCD.avs
16:02:07: Parsing D2V File... L:\Big Stan\VTS_01_1.d2v
16:02:07: First VOB is...Stan\VTS_01_1.VOB
16:02:07: NTSC Film: 100.000000
16:02:07: Error: 9
16:02:07: Unable to Open first VOB
16:02:07: DIKO was not able to open the first VOB file. This error             generally happens when the VOB is
read-only.
Please remove the              read-only attibute and try again.

So that problem hasnt beeen solved   


My guess is to tell DIKO to use the demuxed m2v instead of the vob files...one has to demux with DGIndex first.

[bbez]

appears to be a stable release, i've done a few bsvcd's without error, although i use vcd easy to author the .mpg file to cue/bin

[Tobster]

So far it seems to work perfect and stable. I've done 2 conversions....

The only think I change with every release is the subtitles...
I change them to 'Tahoma 13' and the color white...
I'd like this to be standard, but I know there are different preferences...

But GREAT work again vmesquita !!!! 
I'm glad I bought the the GOLD edition, so I can support you in your hard work...
I'm sure that I would be happy with the free edition but I want to show you some respect.

[vmesquita]

@MASE
Sorry, I couldn't figure this problem out yet.

@bbez
Nice to know it's working for you 

@Tobster
Yes, people have different subtitle preferences...
Thanks for supporting DIKO! 

[Mr Pig]

Have to say great software but i have the same problem as mase.

Code:

15:51:57: DIKO GOLD 2.45
15:51:57: --------------
15:51:57: *************** Getting movie info **************
15:51:57: ----------------Processing Movie 0----------------
15:51:57: Script Template: .\scripts\dvd\simple.avs
15:51:57: G:\VIDEO_TS\VTS_05_0.VOB
15:51:57: Extracting selected PGC using VSTRIP...
15:51:57: vstrip\vstrip.exe @"D:\Diko Working\VOBList" -p0 -$1024 -o"D:\Diko Working\movie0\VTS_01.VOB
16:02:29: Creating D2V Project using DGINDEX...
16:02:29: dgmpgdec\DGIndex.exe -AIF=[D:\Diko Working\movie0\VTS_01_1.VOB] -OF=[D:\Diko Working\movie0] -TN=1 -Exit
16:03:27: Parsing D2V File... D:\Diko Working\movie0.d2v
16:03:27: First VOB is...Working\movie0\VTS_01_1.VOB
16:03:27: NTSC Film: 100.000000
16:03:27: Error: 9
16:03:27: Unable to Open first VOB
16:03:27: DIKO was not able to open the first VOB file. This error             generally happens when the VOB is
read-only.
Please remove the              read-only attibute and try again.

[rickydavao]

With regards to the problem experienced by both MASE and Mr Pig. I think the problem may have to do with the directory name that your VOB files are stored in.  I was storing mine in my Documents folder (Windows Vista) and having the same problem, but then remembered that some programs have a problem accessing files when the directory name is convoluted (ie: C:\My Computer\My Documents\My DVD Rips\My Movie ... you get the idea).  So I had the idea of putting my VIDEO_TS folder in a folder simply called \dvd in the root directory of my drive C: and that did the trick ... it worked fine.  I think DIKO may be having trouble accessing the VOBs if the folder names are longer than 8 characters or if there are unusual characters in the folder name (even spaces) ... in both MASE and Mr Pig's examples, there are spaces in the directory name.  Anyways, whether this is the root of the problem or not, perhaps only vmesquita can tell, but as I mentioned, it did work for me, so you might want to try renaming your rip folders to something less than 8 characters long and no spaces and see what happens.

Hope this helps!

[Mrmscorp]

Try.....

not work......


very bad for me.......

[Prodater64]

Maybe ripper program puts or keeps vob's read only flag active.
All of you have checked that vob's read only flag is not active?