cool new package DVD2DVDR ... !

[Quigonsean]

Try this http://translate.google.com/translate?hl=en&sl=de&u=http://www.dvd2dvd-r.de/&prev=/sea...8%26oe%3DUTF-8 it is googles translation to english, what is cool as all links to other parts of the site ie faq are also translated.

Sean

[rob w]

AB
Thanks to you it looks like Chatwalker is about to release a new version 1.4.5 . His board gives the following information

We are testing 1.4.5 in which you can select between MPEG2DEC2.DLL and MPEGDecoder.DLL. I hope this will fix your problems with NTSC.

[ArrogantBastard]

@rob w

Wow... That would be great. Thanks for the update. I hope this solves our problems. I like to ease of the product.

Maybe we can get Chatwalker to do some Maestro customizations next. It would be great if the chapter information and subtitles were ready to be imported into Maestro.

Till the next release.
AB

[rob w]

It would be great if the chapter information and subtitles were ready to be imported into Maestro.


Yes, I agree, although Scenarist is better supported and also works very well. I would love to see support of subtitles in that program.

[wayned16]

i would just like to say nice work lads, keep it up.

but one problem if u use CCE 2.50, it does not like avisynth 2.08.

this is from DOOM9

2 days ago I wanted to test the speed of my new CPU in CCE. CCE 2.50 would always crash upon loading an AviSynth script. It turns out that AviSynth 2.08 and CCE 2.50 do not like each other and I had to use AviSynth 2.07. I also wanted to test AviSynth 2.51. In order to frameserve with the new version you need MarcFD's mpeg2dec3.dll rather than the usual mpeg2dec.dll. When using GKnot specify the new DLL as alternative mpeg2dec.dll in the Options. You also have to install a recent DivX5 or XviD codec (even if you're not going to encode to DivX/XviD.. for AviSynth to work in YV12 mode a WFV codec capable of decoding YV12 data has to be installed no matter what encoder you're going to use). Back to CCE another problem arose: CCE does not like YV12 data either - there goes the speed advantage - and you have to convert the video data to YUV2 by adding a ConvertToYUY2() at the end of your AviSynth script. But perhaps Cinemacraft will add YV12 support in the final version of CCE 2.67 - Cinemacraft, are you listening? - they seem to be taking AviSynth input rather seriously after all.

the fix for this is

On the issue I reported yesterday, sh0dan pointed out a way to make CCE 2.50 support both AviSynth 2.08 and 2.51. You have to replace the resampleaudio line with AddAudio.

thats also from doom9,
eg
To use the script, use:

AddAudio()

at the end of the script instead of the earlier ResampleAudio(44100).

so thats just incase chatwalker dont know about that little problem, best to get it out in the open, before his next release encounters problems.

[rdalcanto]

Changes didn't help me.... CCE still locks up when it starts. The script changes didn't help that part. I have an AMD processor, and tried with and without the audio line of the script (third line). Back to 1.3.2 or TMPGEnc....

Rick

[Chatwalker]

Hi folks

I've just released version 1.4.5.
Now you can select between MPEG2DEC2.DLL and MPEGDecoder.DLL. Also the problems with IfoEdit should be solved.

Regards
Chatwalker

[wayned16]

wohhooo thanks, did u get around the avisynth problem?

[sfxwe]

@chatwalker

What problems did you fix with IFO Edit, it must be for the pal users?

@AB

So which do we choose MPEG2DEC2.DLL or MPEGDecoder.DLL. If I read the posts correctly MPEGDecoder.DLL is the problem and we should choose to use MPEG2DEC2.DLL, right? LOL, or do I have it reversed?

@All

Has anyone tried this new version yet?

[sfxwe]

I just download the new version I figured I would just give it a shot myself. I must say this program is really coming along, and Chatalker is doing some nice things with it as far as the interface goes. I hope it works now for us NTSC users.

Keep up the good work chatwalker, it is looking nice bro.

I will post my results later tonight as I am just starting a BU right now.

[wayned16]

just think of it like this, use the old mpeg decoder for NTSC films (MPEG2DEC.dll)

and the new mpeg decoder for PAL films *MPEGDecoder.DLL*

i think i got that right


...i havent tried it yet.

[wayned16]

have a look at this for IFO edit fix in 1.4.5

http://www.dvd2dvd-r.de/modules.php?op=modload&name=eBoard&file=viewthread&tid=1962

[rob w]

If you downloaded 1.4.5, download again. The newest version is 1.4.5_2. It is not shown on the menus that this is a newer version until you actually get to saving the file. I looked in the history file to see what was different, but no information is given there.

[sfxwe]

Well 1.4.5 completed from start to finish . I still won't know if the audio is in sync till later as I am not at home, but I will post the results.

I also just saw rob w's post and I did not use version 1.4.5_2, it was 1.4.5 that I tested. Does anyone know what the difference was / is? Looks like we will have to test the newest one too, lol, the fun never ends, lol.

[sfxwe]

Well V1.4.5 completed for me as I stated above. I imported the files into maestro and the audio was in sync . I watched the pulldown process and it did pulldown / drop and progressive. Checking the video in DVD2AVI it showed progressive and did not flash from interlaced to progressive, it STAYED progressive.

Now, I also checked the video file in bitrate viewer and there were some slight differences here is the low down:

This is the info from the VOB off the original DVD:

Num. of picture read: 931
Stream type: MPEG-2 MP@ML VBR
Resolution: 720*480
Aspect ratio: 16:9 Generic
Framerate: 29.97
Nom. bitrate: 7651600 Bit/Sec
VBV buffer size: 112
Constrained param. flag: No
Chroma format: 4:2:0
DCT precision: 10
Pic. structure: Frame
Field topfirst: Yes
DCT type: Frame
Quantscale: Nonlinear
Scan type: ZigZag
Frame type: Progressive
Notes:

This is the info from the demuxed video:

Num. of picture read: 781
Stream type: MPEG-2 MP@ML VBR
Resolution: 720*480
Aspect ratio: 16:9 Generic
Framerate: 29.97
Nom. bitrate: 7651600 Bit/Sec
VBV buffer size: 112
Constrained param. flag: No
Chroma format: 4:2:0
DCT precision: 10
Pic. structure: Frame
Field topfirst: Yes
DCT type: Field
Quantscale: Nonlinear
Scan type: Alternate
Frame type: Interlaced
Notes:

Here is the info from the new encoded video (new.m2v):

Num. of picture read: 3331
Stream type: MPEG-2 MP@ML VBR
Resolution: 720*480
Aspect ratio: 16:9 Generic
Framerate: 29.97
Nom. bitrate: 9800000 Bit/Sec
VBV buffer size: 112
Constrained param. flag: No
Chroma format: 4:2:0
DCT precision: 10
Pic. structure: Frame
Field topfirst: Yes
DCT type: Frame
Quantscale: Linear
Scan type: ZigZag
Frame type: Progressive
Notes:

Now some questions:

1. So has anyone else tried the newer versions? So do we / I move up from 1.3.5 to 1.4.5 or 1.4.5_2? What do we do here guys, or girls ?

2. Also does anyone know what the diff is between 5 and 5_2?

3. Is this difference between video files in Bitrate Viewer something to be concerned with?

[wayned16]

hmm 1.4.5_2 there is a difference is file size

1.4.5 = 4,257,739

1.4.5_2 =4,257,399

i wonder what has been changed.

[defense]

@ AB, good job man. Identifying this problem with the MPEG plugins for our NTSC films allowed Chatwalker to incorporate it into this incredible program without having to spend countless hours trying to figure out what was causing the sync issues. Also, thanks for your time in posting a VERY INFORMATIVE response to how you changed the avisynth script. I didn't realize you were referring to changing it in DVD2DVDR with the expert options set. Before I could try it though, I saw an early X-MAS gift because ChatWalker released what now appears to be the absolute best version since 1.3.5. 1.3.5 didn't have the ability to take vobs from the hard drive, but this new version has that and MUCH MORE.

Also, I don't remember seeing in "ANY" version prior, and option for "progressive" frames with 2:3 pulldown. That's one less thing we'll have to do before authoring.

@ Chatwalker, just wanna say you are definitely DA' MAN! These last few releases have made huge strides and have rectified ripping speeds as well as more pulldown commands and the biggest gift of all for us NTSC people is that it now has the choice of the MPEG plugin. Not only does it have a choice, but even a newbie would know what plugin to select because you bold highlighted the newer plugin IS "NOT FOR NTSC. It is greatly appreciated that you took time to devote towards some of these NTSC issues, although the majority of movies you have to test are PAL. Like they used to say on the "Jefferson's" ...we're movin' on up! hahaha....Yep, time to say goodbye to 1.3.5 and move on up to 1.4.5.

Thanks again for the best backup program for DVD around and for all of the time devoted to NTSC films!


@ sfxwe, my advice to you is forget about what bitrateviewer says. That program is like a weather forecaster...they just predict one of two things..rain or sun. That tells you progressive or Interlaced, and when you run it from a VOB, such as the FIRST VOB of most NTSC films, because the opening credits/introductions are Interlaced, even if it scans through all progressive frames, it will STILl report Interlaced.

I succesfully got SYNC on my test movie as well and this is very, very PROMISING! It appears as though ChatWalker has gotten us up to date with the PAL users. Well, almost..except for the authoring with IFOEdit, but to me that's minor. I prefer Maestro for authoring anyway.

Last but not least, it definitely appears as though we can say goodbye to versions 1.3.2-1.3.5 and HELLLOOOO to 1.4.5, 1.4.5_2 and the newer versions to follow in the future!

[ArrogantBastard]

@All

Hi guys... I am travelling again, but it looks like you have all been testing the new version and it is looking good. YEAH! Please post if you have any issues. It will save me time when I get home and have a chance to start catching up on all the backups that I need to do.

Side note: Anyone using this version with CCE 2.5? I had heard there were problems with the 2.08 version of avisynth that Chatwalker uses. Please post if you have been successfull.

@Chatwalker

Thank so much for making the changes we NTSC users needed. It is very much apperciated. Please take a LONG break. You deserve it.

See ya soon,
AB

[defense]

Side note: Anyone using this version with CCE 2.5? I had heard there were problems with the 2.08 version of avisynth that Chatwalker uses. Please post if you have been successfull.

what's up AB...i'm using CCE 2.5 and there have been NO issues which I can tell from the newest version of DVD2DVDR and CCE 2.5. What problems did hear could be an issue with CCE v.2.5?

[sfxwe]

@AB

I was using V2.5 ........

@Defense

I didn't use the 1st VOB , I used the 2nd one, lol, for the reasons u had stated. I also agree that I don't think there is a problem.

@All.....

Has anyone tried V1.4.5_2 ? Should I stay with V1.4.5 or move on up?

Also is it even possible to get DVD2DVDr to automate the authoring process with Maestro? That would be so sweet .

[dreadogg]

Has anybody had the problem with the newer versions, since cce 2.50.01.00 is being controlled by EclCCE, that if the output folder has a space in the name, which it auto generated, that it fails to run CCE and CCE just hangs when it starts? Also higher versions of CCE give the error that they cannot find the ecl file. This is prevelent on the movie Bad Company. Any help would be appreciated. On a side note...if you use a version higher then 2.50.01.00 of CCE does it always ask to save to "noname" when run?

[rob w]

first try with 1.4.5_2 .....

in sync. Works great. will report soon on more experience.

[Chatwalker]

@all

It's nice to hear that 1.4.5 work for NTSC as well.
Thanks to AB for his workaround.

Why did you all use Maestro? Give Scenarist a chance!!!


Regards
Chatwalker

P.S.: In 145_2 i deleted a command in the authoringscript for IfoEdit. There is no need for an upgrade.

[wayned16]

Thankyou chatwalker great program (now NTSC works ).

one question, In expert mode what does Autostart mean next to the audio selection?

[sfxwe]

@wayned16

The autostart check box from what I understood, is for when you are authoring with IFO Edit (The PAL GUYS). The Can tell IFO Edit to make a certian audio and sub title track start when the DVD is played.

So for example if you used 2 audio (English and Spanish) tracks and wanted the Spanish version to start when the DVD is inserted you would check that audio track off in that box. When the dvd is played, the Spanish audio track would be the track you heard. Same with the subs check boxes......

Someone please correct me if I am wrong.

[wayned16]

ok thanks, another little question, ive just tried to backup a PAL movie with CCE 2.66.01.07 and it asked me to save changes to no name, i know why this is, but i was wondering what version of 2.66 does not ask you to do this?

[ArrogantBastard]

@defense and sfxwe

Thanks for letting me know you guys use version 2.5. During my usual surfing of Doom9 I came across some people who were having problems with CCE 2.5 and avisyth version 2.08. Specifically they were posts saying it was hanging.

BUT... You guys are great. You have alleviated my fears and I will be upgrading this weekend. Man I wish I didn't have to travel so much. Too many backups... Not enough time.

@Chatwalker...
Ok... You have convinced me... I am going to give Scenarist a try. I am not as familiar with it, but I love to learn.

Thanks everyone.
AB

[rob w]

Rest assured, DVD2DVD-R has made Scenarist exceptionally easy to use. You simply load the script file, select one check box and compile. There is no need to manually make chapters either - they're already taken care of. The only down side, for now, is that subtitles are not DIRECTLY supported by DVD2DVD-R; however, you can make your subtitles as usual and then import them manually into Scenarist before you compile.

[joepic]

Rest assured, DVD2DVD-R has made Scenarist exceptionally easy to use. You simply load the script file, select one check box and compile.

rob w

Since you seem to have some knowledge on Scenarist, I have a couple of questions for you:

1. Must Scenarist ALWAYS create a .MUX file which takes up 4.6GB?

2. Scenarist is slower compiling than Maestro, is this releated to the .MUX file creation? If not, then I would stay with Maestro because of the compile times.

3. Have you compared the CHAPTER times that DVD2DVD-r creates in the Scenarist script file vs the program Chapter Xtractor .chp file to see if they agree?

Thanks for your input...

[rob w]

Must say that I have not actually timed the process nor am I sure what the MUX file is about. When comparing times, however, do not just compare compile time.

In Maestro, assets are first checked. Then you must drop the video and audio on the timeline. You need to set the aspect ratio (easy to forget this too!). I usually set the 'first play' field to start the movie up automatically. Then you need to place a chapters file, created previously, on the timeline. Then you come to the compile step. This process is certainly not hard but it is very operator intensive.

With a DVD2DVD-R created script file, Scenarist does the entire job, through compilation without operator intervention and the total time seems fast to me. Given the simplicity I prefer it ... unless I want subtitles.