PDA

View Full Version : Display Versions...


DD51
21st February 2005, 02:58
Is this right?

- Versions:
-- CCE SP Version: 2.67.0.27
-- ReJig Version: 0.3.0.0
-- QuEnc Version: 1.0.0.1
-- DECODER Version: UNKNOWN <--- Is this a problem?
-- AVISYNTH Version: 2.5.5.0

I installed DGDecode.dll in the avisynth plugins folder.
Actually I used Rockas DVDRebuilder_Installer_v0.72(D).exe
This is with DVD-RB 0.77

Only CCE SP 2.67.0.27 works for me.
If I try any other CCE SP above 2.67 It stops encoding before the end.
What I mean is CCE says remaining 2 minutes and then bam it goes to the next file...I have no idea why! :(

Is "-- DECODER Version: UNKNOWN" the reason why?

Any help or guidance would be appreciated

Regards,

DK
21st February 2005, 03:08
Is "-- DECODER Version: UNKNOWN" the reason why?

no it's not

the message is fine - same here with my setup

you should have directed rb to the eclcce.exe instead of cce.exe - did you do so?

DD51
21st February 2005, 03:31
Originally posted by DK


you should have directed rb to the eclcce.exe instead of cce.exe - did you do so?

I'm sorry for asking a stupid question...but...there's an eclcce.exe for CCE SP 2.70?

DK
21st February 2005, 04:04
no, there's not
(at least not yet)

2.70.x.exe will have to be directly addressed


++++++++++

and don't forget to check CCE TRIAL in rb 077 when you want to use 2.70

mrslacker
21st February 2005, 05:34
Originally posted by DD51
Is this right?

- Versions:
-- CCE SP Version: 2.67.0.27
-- ReJig Version: 0.3.0.0
-- QuEnc Version: 1.0.0.1
-- DECODER Version: UNKNOWN <--- Is this a problem?
-- AVISYNTH Version: 2.5.5.0
neuron2 has not put the version number into the dll. jdobbs and neuron2 have briefly discussed this issue. Don't worry about that. Just use the DGDecode version linked in the Rebuilder Forum.

neuron2
21st February 2005, 15:05
Originally posted by mrslacker
neuron2 has not put the version number into the dll. The version number is in the DLL! Enable the info=true param and see it display the version number. It's in a string in the binary. I asked if an API was needed to retrieve it, but nobody answered. Also, jdobbs can force use of particular versions by writing a defined format number in his D2V files.

mrslacker
21st February 2005, 16:58
Oh, I must have misunderstood this (http://forum.doom9.org/showthread.php?s=&postid=608315#post608315) conversation. So you won't see the version number with the Windows properties tab, but its there if you know where to look.

lamster
21st February 2005, 18:41
Originally posted by neuron2
The version number is in the DLL!
Perhaps, but it's not readily accessible. People expect to see it on the Properties tab.

The way it's typically included (at least, for VisualStudio-built projects) is via a VERSIONINFO (http://msdn.microsoft.com/library/en-us/tools/tools/versioninfo_resource.asp) entry in the resource file. See more about Version Information (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/resources/versioninformation.asp) on MSDN. (Sorry, I don't know how one would do it in Fortran...)

Here's a program I run when starting Rebuilder - I use it to capture version info and executable timestamps in the Rebuilder log (which I burn on the DVD), so I can always know what version of each tool was used to create the backup. (Both source and executable are included. I've also included the RB.bat that I use; this is typically configured to point to whatever movie I'm currently working on by a front-end batch file that updates both rb.bat and Rebuilder.ini.)

DD51
21st February 2005, 18:45
Originally posted by DK
no, there's not
(at least not yet)

2.70.x.exe will have to be directly addressed


++++++++++

and don't forget to check CCE TRIAL in rb 077 when you want to use 2.70

DK again thanks for responding...
I did chose CCE Trial in the setup and directed it to ccespt.exe (2.70) and put a check mark in the minimize checkbox in order for CCE to start. My problem is CCE stops the encoding way before the end. It's sparatic...it may jump to the next file at 23% done or could go to 56% and it imediately jumps to the next encode. Again this only happens with 2.70 and up...of course if I let it go through the whole process I get errors in the rebuild phase. It also finishes in like 30 minutes or less

It DOES NOT do it with 2.67 (NEVER)
I wish I new how to fix this :(

Many thanks again.

Regards

DK
21st February 2005, 20:08
maybe your cce version is *faulty*

try downloading the latest TRIAL and use it just for testing purposes and see if it makes a difference

btw: you did NOT touch any key while cce was doing its job, did you?


++++++++++++++++++++++++++++

just one more thought:

maybe the trail version is limited to a certain amount of frames/minutes?

DD51
22nd February 2005, 00:02
DK,

Many thanks for trying to help me but, no offense, but I don't think this is helping.

maybe your cce version is *faulty*
Yes that might be...I wouldn't even know how to tell.
I tried both CCE v2.70.01.05 and CCE v2.70.02.00 trial versions.
It's the same result.

try downloading the latest TRIAL and use it just for testing purposes and see if it makes a difference
I did try the latest trial version...no other "special" files used.
Pure Trial version.

btw: you did NOT touch any key while cce was doing its job, did you?
It's a shame u have to ask that kind of question! I know, I know some people don't understand why their TV doesn't come on all to find out that it was never plugged in!
Anyway...Of course I did not.

just one more thought:

maybe the trail version is limited to a certain amount of frames/minutes?
Maybe...I have no idea:(

Anyway...I can't thank you enough for trying...I don't want to bother with this anymore. I guess I'll stick with CCE 2.67. It works great!


Sincere regards,