cool new package DVD2DVDR ... !

[wayned16]

http://wayned1985.proboards17.com/index.cgi?board=DVDChat&action=display&num=1048045179

i downloaded the modded pulldown.exe, and the guy sounds genuine. I havent tested it yet. But we need some testers for it. And he only wants me to post the results on my board. If you lot want a copy i will put it on my site.

just check what he has to say on the link posted above. see what u think.

oh he also clames that IFOedit has not got a bug for NTSC films it is pulldown.exe what is causing incompatiblity.

[ArrogantBastard]

@wayned16

Thank you for the update on how to detect forced subs. I will check this when I get home tonight on my Attack of the Clones DVD. I know this one has forced subs.

For testing of the new pulldown. If you post it on your sight I have a verifiable test case I can run it through. It will only take me a half hour to verify what Bach is saying.

Let me know if you need assistance.

Thanks again,
AB

[wayned16]

ok i will post it up on there now, it will be in the downloads section. And no problem on the subs.

EDIT: sorry i need him to send it me again like a wolly i deleted the e-mail he sent me. So it should be up there tomorrow. sorry

[sfxwe]

I'm drooling at the mouth right about now.......are you trying to tell me that there is this possibility, although slight, that we could be looking at a full ripping, encoding, authoring DVD BU utility?

Someone pinch me!!!!!!!!!!!!

[defense]

oh he also clames that IFOedit has not got a bug for NTSC films it is pulldown.exe what is causing incompatiblity.

I'm gonna go out on a limb and say that guy is full of monkey shit. If i'm wrong then I'll eat that monkey shit. Pulldown isn't gonna fix the sync issues with DVD2DVDR because c'mon man..the issues have already been detected and scrutanized...it's the mpegencoder...that's why the issues regarding "sync" aren't prevalent in the newest versions.

Also, as far as pulldown rectifying the "IFOEdit" issue...Wayne....I have the Brooklyn Bridge at a discounted rate...just email me and I'll give you details.....c'mon....that is an IFOEdit issue and ONLY an IFOEdit issue...why do I say that? Because I've tested it thoroughly as well have many others. Let me give you the easiest method to test this out. Just "RIP" a movie..I don't care if you use SVCD internal routes..DVD DECRYPTOR...SMART RIPPER...DVD2DVDR...CLADXP...WHATEVER....who cares if it is a DVD5 OR DVD9..although DVD5 will be the easiest to test this on. RIP the movie....if you use Smart Ripper or DVD Decryptor..use stream processing so you have an .M2V file and a .AC3 track.

Now all you have to do is simply AUTHOR that "NTSC" ripped film with IFOEdit..and check out your results. Pulldown isn't even as much of a thought with that method of authoring and the issue is still VERY MUCH there. If you wanna waste the time I guarantee you'll come back saying your movie plays about 25% faster. I wonder where people like this really come from. Let me know how the magical version of pulldown works along with the other "backdoors" you probably have on your system by now.

@ robw, thank you for that information regarding the checksum issue. That is VERY interesting and now that you mention it, I also remember reading something about that issue somewhere..maybe doom9..but being that "at that time" I didn't encounter the issue...I didn't pay much attention to it. Thanks again for the info and I will do that google search and try and get that patch. I'm assuming you and others already have that patch installed already right?

Anyway, i'll do that search and hopefully this problem will be resolved. It just occurred again with "TRUE LIES" on the first PASS. I don't want to resort to DVD2SVCD because I know it is a great program as you mentioned...but it doesn't handle multi angle and seamless branching nearly as well as DVD2DVDR...not to mention it seems to always screw up the aspect ratio...meaning if a movie is 16:9, it seems to always select 4:3 encoded as 4:3. Maybe that is a SVCD default or something...but I just prefer DVD2DVDR for DVD's. Thanks again for the info on the "patch" i'll let ya know how it works out.

[sfxwe]

I thought the CheckSum Error Patch correction was for peeps running CCE on an Athlon? defense didn't you say yours was an Intel?

I think I have to agree with defense on the IFO Edit / pulldown problems / solutions. I don't think it is a pulldown problem. Just my 2 cents

[mosh]

@defense

It might sound that the pulldown issue isn't the problem it is the mpg decoder that was being used in dvd2dvdr that was causing headaches for NTSC users. If you read the post the person is claiming that there is a conflict with Pulldown and the original encoder dll that was being used in dvd2dvdr. Now if also this was the case it would now mean that you would now have a choice of encoders to use for NTSC so testing could begin to see what encoder is fastest and possibly better to use.

AB had changed the encoder and it worked, but it was a process of testing so if wayne is prepared to test the pulldown theory then fine it is only for the good of the NTSC users. If AB would have posted his theory before trying it would you have said the same about that.

[wayned16]

ok guys pulldownmod.exe is in my downloads section. I cant stress enough to post ur results on my forum, because he said if you find it work he wont release the source code. So please post all findings and results on my forum.

EDIT: oh by the way im gonna post my results shortly, using dvd2dvdr 1.4.6 and NTSC film with scenarist. once i know how to use it and got the right version

[wayned16]

results were sucessful no audio sync problems, scenarist 2.6 isnt that hard to use and yes it does create a MUX file then authours the dvd. But takes about the same time maybe quicker than meastro. As the script DVD2DVDR creates does all the work for u.

[sfxwe]

@wayned16

We need some more info bro........ what decoder did u choose? And Why?
Wasn't 1.4.6 working properly anyways? Like the audio was in sync? Cause if version 1.4.6 was ok prior, then what is the new pulldown doing for us.

PS. I did check your forum last night, but maybe I am missing something. Just what exactly is this new pulldown suppose to do for us, that the new version of DVD2DVDr isn't doing now? I am not asking this to be a smart a$$, so hope you all didn't take it that way

[wayned16]

sorry. i agree with you anyway, i asked on my forum to the creater of the new pulldown.exe that the problem has been fixed and the audio sync was due to the mpeg2decoder. But whats the harm in trying it out. If it works WICKED but if not, oh well....

i used CCE 2.50.01.00

yeah i know 1.4.6 works perfect now. I was just constrabuting to the forum of my results.

[wayned16]

@wayned16


For testing of the new pulldown. If you post it on your sight I have a verifiable test case I can run it through. It will only take me a half hour to verify what Bach is saying.

Let me know if you need assistance.

Thanks again,
AB

And i thought AB wanted to test out the new pulldownmod.exe as he says he has a verifiable test. So its on my site mate if you wanna go ahead.

[rob w]

I don't understand and don't like this big mystery. If the author of this new pulldown has something of interest then post it on Chatwalkers site. Provide a link for the source code. We're all in this together aren't we? If this author needs a ticker parade for his contribution and it works, I'll help to organize it.

Let's get on with making this software the best it can be!!

[sfxwe]

wayned16 wrote:

But whats the harm in trying it out. If it works WICKED but if not, oh well....

I agree, there is no harm......I am just trying to figure out what it is that this new pulldown is fixing? I am not upset at anyone or anything. I also appreciate your effort in trying to make DVD2DVDr a better program. More power to ya wayned16 ....... Please let us know your results and what options you picked in DVD2DVDr.

Hopefully AB will test it and give us his results too........ if it makes DVD2DVDr even faster than COOL .

[ArrogantBastard]

Hi All...

I ran a VERY QUICK test today with the new pulldown. In a nutshell it did not work, but here are the results:

DVD2DVD-R version: 1.4.3 (Known to have Sync issues without changing Decoder)

Source: NTSC copy of Chasing Amy Chapters 1 & 2
Parameters Checked: Progressive, ZigZag, Upper Checked
NTSC Parameters Checked: Force Film, Pulldown, Drop Frame

GOP Sequence M=3 and N/M=4

No other modifications were made. The pulldown included with DVD2DVD-R was replaced with the pulldownmod.exe and renamed pulldown.

Sequence ran without a problem. Authored in Maestro. Audio not in sync. It still looks like the decoder has problems with the interlaced video that is on cell 1 (total guess there though).

I will post this on wayned16's site as well... But initial feedback is negative. I will run one further test when I get home from skiing this weekend. It is my last time up for the year.

Have a good one everybody.
AB

[Vader443]

I believe this gentlemen has modified pulldown to fix the ntsc "time" bug. This bug shows up when one tries to author an ntsc with ifoedit. From reading his other posts, everyone thinks there is a bug in ifoedit when authoring an ntsc film. He claims that the bug is in pulldown, not ifoedit.

It might be worth trying to run the modified pulldown and author with ifoedit.

[rob w]

@Vader443

Ok, do the authoring and then open the IFO with IfoEdit. Look at the total number of frames in the movie and compare with the original DVD. Unless it is fixed, you will find that there are only 80% of the correct number of frames.

[ArrogantBastard]

Thanks Vader...

I will test the IFOEdit version on Sunday.

Thanks to all
AB

[Vader443]

@robw

I see your point. I will have to run a test file to see what this modified pulldown does and how ifoedit multiplexes the files with it. In some of his posts on Doom9, he claims there is a frame and timecode issue with pulldown. Apparently pulldown was written to be used with bbmpeg, and bbmpeg is not affected by the "bug" when multiplexing.

@AB

If you run a test, make sure you use the old mpeg decoder and not the new one. The new one seems to have other issues with ntsc film files.

[NYPlayer]

Vader443

It is an Ifoedit bug. If I were to use DVD2DVDr to remove audio and subs and there is no encoding required. It is still no good when authored with Ifoedit. The problem has nothing to do with pulldown. It has to do with Ifoedit authoring NTSC!!!!

[true0429]

There is a newer version of dvd2dvdr out. Last I checked yesterday version was up to 1.4.6 and the audio synch issues were settled and there have been upgrades to work with CCE 2.66

Also there is an english manual for this in pdf format. If anyone wants it let me know at true@tnt21.com

[defense]

Vader443

It is an Ifoedit bug. If I were to use DVD2DVDr to remove audio and subs and there is no encoding required. It is still no good when authored with Ifoedit. The problem has nothing to do with pulldown. It has to do with Ifoedit authoring NTSC!!!!

These people just don't get it. This "unknown" new author out of the woodwork is really doing a hell of a sell job on some people.


@robw, if what sfxwe says is correct regarding this bug for CCE and CRC errors being with Athlon processors, do you have any other ideas? I do have an Intel. What is more interesting is that version 1.3.2 to 1.3.5 NEVER had these errors, nor does DVD2SVCD ever have these errors. I disabled script processing and each time I get a CRC error with version 1.4.6 on the 2nd CCE pass and CCE just completely freezes. It has done this "three" times out of three times/..100% of the time. When I did all three movies with version 1.3.2, "PERFECT" as always. Any other suggestions?

[wayned16]

it happens on the P4 as well as AMD processors, it happens mainly if you have overclocked your processor. What version of CCE you using? have you applied the patch to stop CRC errors? have you got muiltiple versions of dvd2dvdr or avisynth installed?

[bhutchins]

DVD2DVDr 1.4.6 made a exelent backup of "Perfect Storm" NTSC, re-encode with CCE-basic, Burned with Nero 5.5.9.0. Audio in perfect synch Thank you Chatwalker.

[defense]

it happens on the P4 as well as AMD processors, it happens mainly if you have overclocked your processor. What version of CCE you using? have you applied the patch to stop CRC errors? have you got muiltiple versions of dvd2dvdr or avisynth installed?

interesting..I never heard about this problem being due to overclocking. I am definitely heavily overclocked but don't see why this would occur in version 1.4.6 and NOT any other version. I've just backed up the SAME three movies which the CRC error occurred with version 1.3.2 of DVD2DVDR and WHOALA!..no probz at all. Any clue "why" 1.3.2-1.3.5 work flawlessly and 1.4.6 doesn't? This error occurred when I did NOT have ANY other version of DVD2DVDR on my system, other then 1.4.6. I have since ALSO installed 1.3.2, which I am currently using. Any clue where I can download this "CRC PATCH" that kickme site doesn't have it.

I'll do a search like robw mentioned on google..but what I'm MOST curious about is how DVD2SVCD and version 1.3.2 and 1.3.5 all use the same version of CCE I currently have which is 2.5 SP and use it with no problems..but version 1.4.6 gives me these CRC errors each and EVERY time. Anyone have any ideas why that is? Even though it's CCE, it doesn't seem like it's a CCE problem..and moreso some conflict with 1.4.6 on my system because those other versions work perfectly fine.

[wayned16]

http://www.bath.ac.uk/~susajb/Cinema_Craft_Encoder_2_50_SP_CRC_Patch.zip

there ya go try that. CRC patch.

Its also on my site now just incase.

[defense]

@Wayne, thanks for the link to that patch...however, before I "patch" CCE, I was hoping someone would explain to me why this is happening to me with version 1.4.6, and not anyone else.

Also, why is 1.3.2-1.3.5 working perfectly along with CCE and "no" Checksum errors...as well as DVD2SVCD/CCE with "no" checksum errors? It those programs are using CCE without checksum errors, why isn't 1.4.6?

@robw I'm just curious if you ever installed this CRC patch yourself?

@sfxwe, did you ever install this CRC/checksum patch?

Did anyone ever install this CRC Patch?

Last but not least...this patch "disables" CRC32 checking in CCE..is there any reason why CRC checking should be "enabled" and NOT disabled? Thanks in advance for any info on this.

[wayned16]

-- just wanna say np for the link, and yes i always apply it. Does no harm to apply it does it, at least you dont get a nasty surprise 1hr 30 into ur encoding process.

Me personally have no idea why this is happening with 1.4.6 and not with other version. You mention u use 132 and 135 and works perfect, well since then all what has changed is the mpeg decoder and avisynth > avisynth 2.08 ...maybe got summat to do with avisythn but thats a guess.

[defense]

Me personally have no idea why this is happening with 1.4.6 and not with other version. You mention u use 132 and 135 and works perfect, well since then all what has changed is the mpeg decoder and avisynth > avisynth 2.08 ...maybe got summat to do with avisythn but thats a guess.

What is interesting is that i'm pretty sure sfxwe and rob w haven't applied this patch and they don't seem to be having this issue with version 1.4.6. I guess i'll have to wait to hear from them, but I don't think either of them have applied the patch. Until I know for sure I'll stick with version 1.3.2 which to me is the most stable and flawless yet. The ONLY thing for "me" that I can't do with 1.3.2 that I can with 1.4.6 is have pulldown with progressive frames run automatically after the encoding process. I don't mind that for now until I know for sure.

I am also wondering if CCE should have the CRC/Checksum enabled? What would disabling it do, if anything? IF the only thing changed is Avisynth, i'm not sure why that would cause this problem...but I guess something is causing it. I have NEVER had a single problem with DVD2DVDR 1.3.2 and the same holds true with all the movies 1.4.6 along with CCE failed to finish because of the freezing due to the checksum error midway through. Hopefully others can supply more info on this and their setups.

[ArrogantBastard]

@defense

I just installed 1.4.6 tonight and it ran smoothly on a small test without any patching. I use CCE 2.5 and Scenarist. I also have an Athalon XP 1800+ processor and have never had any problems.

Now of course that could change when I run it against the entire DVD. Backup is running now and I will update you in the morning.

Have a great night.
AB