DGIndex 1.3.0 beta 5

[Guest]

LPCM support is on the worklist. Its current absence is not an instability, in my view.

[planet1]

Originally posted by neuron2
... not an instability, in my view.


Your right of course, but you could mention in one of the htmls that lpcm-delays are not yet reported.

[BGane]

Tried 130b5 over the weekend. I'm having a strange problem. It could well be my problem, but I decided to post just in case someone can help.

I am trying to convert a purchased DVD that is PAL format to NTSC.

I have two machines. One works with DGMPGDEC. One does not. When I attempt to frameserve an AVS script through to TMPGEnc, I am getting an error message on one of the machines, from TMPGEnc as I press "Start", that the file cannot be opened or is unsupported.

Software configuration of both machines is as follows:

Windows XP Service Pack 2
TMPGEnc Plus 2.524.63.181
DGIndex/DGDecode 130b5
AVISynth 2.55
ReadAVS 0.11e
VirtualDub 1.65
Cyberlink PowerDVD5 (current patch level)

The machine that works is an older Intel mobo D850MV with P4 2Ghz. The second machine, which does not work with 130b5 is an ASUS P4P800SE with P4 3Ghz. Both have 1GB memory.

I have ripped the DVD, using SmartRipper 2.41, on both machines. I have loaded 130b5 on both and then used DGIndex to create a d2v on each. Then I have created an AVS script, which is as follows:

LoadPlugin("DGDecode.dll") - I do actually fully qualify path
mpege2source("VTS_01_1.d2v") - full path here too
LanczosResize(720,480)

I am frameserving to TMPGEnc, via the AVS script to load the VOB, processed by DGIndex.

On the Intel machine, everything works fine. My problem occurs with TMPGEnc on the ASUS machine. It gives me the error message, "file cannot be opened or is unsupported" when I try to start encoding.

Problem isolation attempts:

1. I tried VirtualDub, and it works fine on both machines. I gave VirtualDub the AVS script as input, pointing to the d2v created by DGIndex and it worked fine.

2. If I give TMPGEnc just the d2v file itself directly, VTS_01_1.d2v, then it works. TMPGEnc can read that file. Problem only occurs if I attempt to give TMPGEnc the AVS script.

3. If I build a d2v with DVD2AVI 1.77.3, then TMPGEnc can read either the AVS or the d2v created by that. It seems that it only has a problem with the AVS when the d2v was created by DGIndex.

4. I know that TMPGEnc is using the proper DGDecode.dll because there is only one on the machine - matching pair for the DGIndex used, and when I invoked TMPGEnc and gave it the d2v directly, DGDecode.dll could not be deleted because the file was in use.

So - why is it that this machine's TMPGEnc has a problem, only when the DGIndex-created d2v is being read via an AVS script?

[Guest]

What is ReadAVS and how does it figure in your process?

[BGane]

ReadAVS.dll allows TMPGEnc to read an AVS script.

[Nic]

It doesn't sound like a DGIndex/Decode problem, so I doubt neuron2 can help you. Could it be something like needing a YV12 codec installed on both machines? Try installing XviD on the Asus machine. Other than that I can't guess. But if it works in VDub, then it isn't DGDecode's fault i'm guessing.

-Nic

[Guest]

Just for fun, try toggling the I420/YV12 DGDecode option.

[guada 2]

How it is possible ?
I did not know that Tmepgenc could read a file AVS.
Could give me myself details.

Thank you.

[guada 2]

Neuron2,

A question:
The versions bêtas of DGindex are they compatible between them or not?

Thank you in advance

[Guest]

Originally posted by guada 2
The versions bêtas of DGindex are they compatible between them or not?
Sorry, I don't understand your question.

[Guest]

Originally posted by BGane
ReadAVS.dll allows TMPGEnc to read an AVS script. I don't need that to read AVS with 2.54. Isn't that needed only for earlier versions of TMPGEnc?

[guada 2]

I am sorry for the translation Neuron2.

Indeed, I tested DGindex bêta5 outside GK 0.34.8.
I thought that the file D2v was going to be read by GK. but was not it the case.
What return to my question the beta versions of DGindex (bêta3, bêta4, bêta5) are them any various.

Thank you

[Cyberia]

Originally posted by guada 2
The versions bêtas of DGindex are they compatible between them or not?

I think he's just asking if there are any d2v changes (or other compatability issues) between any of the 1.3 series betas.

I believe all the 1.3 series betas are cross-compatable.

[sunbeam]

Originally posted by guada 2
The versions bêtas of DGindex are they compatible between them or not?
Hi guada 2,
when I want to encode a whole bunch of files at once and some of them are prepared with DGIndex 1.3.0 beta 4
and others with DGIndex 1.3.0 beta 5 then I delete all the older .d2v files and prepare them All with his newest release.
I think its better when a beta 5 .dll can ride his beta 5 .d2v.
Is that what you meant?

sunbeam

[guada 2]

Thank you Cyberia,

It is astonishing Cyberia, I have make a test out of the last version of GK; and that is confirmed.
Is what it is normal.

[sunbeam]

Originally posted by Cyberia
I believe all the 1.3 series betas are cross-compatable.
When you`re right Cyberia, then the changes in the different betas would not disturb for example
a beta 2 .d2v encoded with a beta 5 .dll.
If this is true and there are changes in the newer betas how they can really
drive into a older .d2v and therefore take effect then?

sunbeam

[guada 2]

It is not really that sunbeam.

On the contrary, I puts on a side DGindex (for example:in my documents), and GK installed in my programs.

why then the D2V are not compatible DGindex Bêta3 and beta 5?

[Guest]

All 1.3.0 betas use D2V file format version 8. The D2Vs generated by, e.g., beta 3 and beta 5 are identical.

Whenever I make a change to the D2V file format, I bump the version number at the top of the D2V file. You can use that number to assess compatibility between different DGIndex versions.

[guada 2]

Tthank you for the advice.

Goodbye Neuron2 ;)

[guada 2]

Hello neuron2, :)

It would be possible to integrate into your software extension DV or rather "dvsd"?
It is perhaps dared.But as say the saying: "which does not try nothing has anything"

Thank you.

[Guest]

@guada 2

What would be the purpose? There are perfectly adequate DV codecs. What functionality are you trying to obtain that is not already available?

[guada 2]

Neuron2,

I understand to you by saying that.
But can you say to me how to make HDV, a manner of exploiting "Upscaling DV".
That appears strange but I think that that would be very useful for me…

[Backwoods]

Originally posted by guada 2
But can you say to me how to make HDV, a manner of exploiting "Upscaling DV".
That appears strange but I think that that would be very useful for me…

HDV = 1440x1080 MPG2
DV = 720x480 MJPEG(similar)

They aren't connected in anyway. If you want to upscale DV to HD resolutions, I think you should reconsider or try your luck with IIP or HybridFuPP.

[guada 2]

I thank you Backwoods.
But I always thought that there was a servicing cowling intermediate platform which would make it possible to make this task.

It is true that the method VDM or other + DV codec or Huffyuv or Logarith… make it possible to obtain Avi Lossless, but could not your step use DGindex as well as possible to exploit the quality of this format like one does it so well with the video DVD.

DGindex nowadays shows its capacities through several sources why not the DV.
My idea is not very with make finalized, I cannot speak about it.