New CCE-SP 2.64.01.10

[odwoh]

Is this new version going to supplant 2.5 in DVD2SVCD?

[Labersack]

Why not? read Q&A. Every version works with DVD2SVCD, but slow, only 2.50 work without VFAPI/2link.

[paul8883]

no Labersack, this version doesn't work with dvd2svcd right now. hopefully in the future version. the new version 2.64.01.10 can read avs file directly just like 2.50.

[chres]

Hi all,

yes paul8883 is right!
And that's why I'm wondering, if there's a possiblity to "patch" or get round the DVD2SVCD detection routine for CCE 2.50 SP.
I simply choose the .exe from 2.64.01.10, but that annoying message, we don't want to see ;), pops up.
So is there a way or do we have to wait for a next release?

chres

[M1ckey M0use]

You probably can skip the error message by patching byte at position 17F6A9 (hex) (version 1.0.9 build 3)

It says 75 there. And if you change it into E9, the nag won't display. Haven't checked it though. The program depends on sending keystrokes so it probably won't work with a newer version. You can always try.. (and let us know :) )

M.

[chres]

@M1ckey M0use

I just tried, but didn't work.
As you mentioned, the nag didn't appear, but there was also no further reaction and the "Go" Button stayed grayed out. Must be somewhere else.

chres

[M1ckey M0use]

Ok, another try then. It removes the nag, it enables the go button and you can start converting. I tested it that far. Can't test any further because if don't have the new app.

I'm still pretty sure that it won't work because of the keystrokes...

Here we go:

At position 17F69B (hex ofcourse) you'll find: FF 92 B4 00 00 00
change that into B0 01 90 90 90 90

This patch is for very advanced users only. Don't expect it to work...

M.

[chres]

It worked ... almost ;)

The encoder was launched, every file-dialog was filled out just like with the old version (so the keystroke macros seemed to work), .vaf file creation run through, but afterwards the actual encoding process didn't start.
More than you expected though...

btw: With the 2.64.01.10 I got a slower RT value (about 1.1) during the .vaf creation than with the 2.50 (about 1.25) (on Duron 900/512MB). I have hoped for further speed improvements with the new one, but actually it might be the other way round.

I think we do have to wait for the new version, where the new cce-encoder will be fully supported, as there seem to be some differences left. :confused:

chres

[seewen]

Hello,

i'm very intereted in your discussion.

Could you tell me what program i have to use to do your "tricks" (hex32workshop, or something like that ? ) .

And how do u know the right "bits" to change ? (i know that this is lamer's question, but just a little-quick answer will be really aprecciate ;-) )

Thank you

[chres]

Hi seewen,

a simple editor like ultraedit should do it. It opens the .exe in hex mode and you can make the necessary "patches" at the right position.

For finding the right places to patch, you have to ask M1ckey M0use, because I only do what I'm said to do *g* but would be interesting to know though. ;)

chres

[seewen]

Ok,

Thank you chres ;-)

[M1ckey M0use]

Actually it's not that difficult :-)

Too bad the first patch didn't work. That was just changing a conditional jump to a jump always to bypass the nag.

Something like:

If version_is_good then goto good_version

changed into

goto good_version

The second patch was in the version check function. So if the function is called somewhere else in the program, it makes sure the result is always true.

too bad that the conversion didn't start. What happens if you start it mannually?

[chres]

@M1ckey M0use

After beeing a few days on vacation, I finally could now rerun the test to be able to quote precisely.
When the cce 2.64.01.10 is used and I'm starting the encoding process manually (as you proposed and what I have done last time by myself ;)), after a few minutes there appears a popup saying: " is not a valid floatingpoint value. (which seems to be caused from DVD2SVCD)

Afterwards the CCE encoding window closes after a few furter minutes without any error message, but the main cce window stays open, though. DVD2SVCD seems to hang with the above mentioned message written in its log.

It's possible to close DVD2SVCD by ignoring the error message, that DVD2SVCD is still working.

With patched .exe, using cce 2.50 everything seems to work properly without any issues.

chres

[ch@@boom]

Originally posted by chres
@M1ckey M0use

After beeing a few days on vacation, I finally could now rerun the test to be able to quote precisely.
When the cce 2.64.01.10 is used and I'm starting the encoding process manually (as you proposed and what I have done last time by myself ;)), after a few minutes there appears a popup saying: " is not a valid floatingpoint value. (which seems to be caused from DVD2SVCD)

Afterwards the CCE encoding window closes after a few furter minutes without any error message, but the main cce window stays open, though. DVD2SVCD seems to hang with the above mentioned message written in its log.

It's possible to close DVD2SVCD by ignoring the error message, that DVD2SVCD is still working.

With patched .exe, using cce 2.50 everything seems to work properly without any issues.

chres

same happened with my encoding efforts

except that i get the error after the .vaf file is made (after 7-9hours)

CCE 2.64.01.10 ,, is not a floating blabla ..
CCE 2.50 working fine

AFAIK this is solved in the next version of DVD2SVCD
I haven't tried yet the unreleased version of next DVD2SVCD which is available on this board somewhere

[chres]

@ch@@boom

Yes, you are right. It happens after the .vaf file creation process, that's why I wrote "when I start the encoding process (better: transcoding process) manually" after that.

As you mentioned, I have tried the build 1 pre 22 version of DVD2SVCD 1.1.0, too, but didn't had luck with it.

So we really might have to wait for a next release, unless ...


@M1ckey M0use
Where are you? No futher ideas where and how to fiddle around ;):D?

chres

[M1ckey M0use]

I'm still here but i think we need to be patient :) It was worth a try to make a simple patch but unfortunatly it didn't work. I'm always willing to help people to help with my knowledge.

Version 2.5 is working fine for me so there's really no need to upgrade. Don't know if the new version is muuuuuuch improved since 2.5.

There's one bug thats bugging me at the moment:

http://forum.doom9.org/showthread.php?s=&threadid=32162

And i can't patch that either :) So lets hope we both get some attention from DVD2SVCD :)

[chres]

Yes, I agree!

Also I should have used the search function a bit more conscientious, because there's more to find! A bug concerning 2.64.01.10 is mentioned here (http://forum.doom9.org/showthread.php?s=&threadid=30816): This could have been the reason for aborting the encoding process?!?

Now we'll have to wait and see...
chres