EclCCE: Adds ECL support to CCE 2.66/2.67 trial

[RB]

Hi,

here is EclCCE, an utility that adds the load/save ECL (Encoder Control List) functionality and e few other useful new options to the CCE SP 2.66/2.67 trial versions. ECL support is added "seamlessly", you simply use the standard CCE menu items and toolbar buttons for loading and saving the ECL. There also is command line support for automatic ECL loading/encoding/exiting. Command line support only is available for earlier CCE SP versions. See the enclosed manual for more information.

Download EclCCE 1.81 (http://www.caranthir.de/files/eclcce.zip)
Mirror (http://www.weethet.nl/downloads/cceecl.rar)
Download EclCCE 1.81 Source Code (http://www.caranthir.de/files/eclcce_src.zip)

EDIT: Unfortunately my life has become too busy to continue development of EclCCE. Feel free to download and use the source code for your own enhancements to EclCCE. Good luck!

History:16/04/2004 v1.81

- Added support for CCE-SP 2.67.00.27

- Added VafFix INI parameter. Setting VafFix=1 in [EclCCE] section in
EclCCE.ini causes EclCCE to handle the create_new_vaf ECL option
the way it did in EclCCE v1.7b. Use this only for compatibility
with utilities such as BatchCCEWS that rely on the previously
"reverted" handling of create_new_vaf.


02/04/2004 v1.8b

- Fixed: compatibility issue with CCE-SP 2.50/2.62/2.64, jdobbs's
DVD-Rebuilder and command line ECL loading. No more AVIFileOpen
errors with DVD-Rebuilder generated ECLs for CCE-SP 2.50.

- Some internal code cleaning and small fixes.


31/03/2004 v1.8a

- Fixed: Cancel button could not be hidden via command line or INI
option for CCE-SP 2.50/2.62/2.64.

- Fixed: under rare circumstances, CCE unexpectedly closed when
loading or saving ECL.

- Added: Fix for "invisible CCE window" issue with CCE-SP versions
prior to 2.67.00.12 (see CCE-SP HISTORY.TXT).

- Added: sanity check on ECL files to display a reasonable error
message when trying to load an unsupported ECL format (CCE Basic).

- Added: -hideshutdown command line option. Global option to hide the
Shutdown checkbox in progress dialog, press Ctrl-Shift-S to
hide/unhide at any time.


25/03/2004 v1.8

- Added: ability to run CCE minimized. CCE will be automatically
minimized to tray if EclCCE.exe is run minimized and the –ecl
and/or –batch/-encode switches are used. Requires CCE-SP 2.66.01.07
or higher.

- Fixed: Video/Audio/VAF file extension specified in ECL was reset to
CCE default file extension when loading ECL.

- Fixed: create_new_vaf ECL option was reversed. Now create_new_vaf=1
really sets "Create new file" and create_new_vaf=0 sets "Use
existing file".

- Fixed: under certain circumstances, the ECL file was saved as the
last video file dropped into CCE, overwriting the video file.

- Fixed: Cancel button in Encode Progress Dialog was sometimes still
accessible although it was set to be hidden.

- Enhancement: shutdown timeout extended to 30 seconds. Also the CCE
window is now brought to the foreground when the shutdown sequence
is initiated.


17/12/2003 v1.7b

- Added support for CCE-SP 2.67.00.21 through CCE-SP 2.67.00.23


23/10/2003 v1.7a

- Added support for CCE-SP 2.67.00.18 and CCE-SP 2.67.00.20


16/10/2003 v1.7

- Added support for CCE-SP 2.67.00.17 and CCE-SP 2.67.00.19


25/07/2003 v1.6

- Added support for CCE-SP 2.67.00.12 and CCE-SP 2.67.00.13


10/06/2003 v1.5c

- Added support for CCE-SP 2.67.00.11


30/05/2003 v1.5b

- Fixed issue with Bitrate Tweaking feature that would sometimes
cause CCE to crash after the last pass.


26/05/2003 v1.5a

- Added option to prevent accepting multiple selections in the Open
Project dialog to make EclCCE compatible with DVD2SVCD again
(broken in 1.5).
- Fixed bug in command line support for CCE versions prior to
2.66.01.07


22/05/2003 v1.5

- Fixed: dragging and dropping ECL files into the CCE window was not
possible (trial version limitation)
- Added support for loading of multiple ECL files simultaneously
- It is no longer possible to accidentally select EclCCE.exe for the
CCE-SP executable when EclCCE runs for the first time.


12/05/2003 v1.4c

- Fixed the "CCE did not finish initializing in a timely manner"
error


02/05/2003 v1.4b

- Fixed: Advanced VBR Settings dialog was visible during automated
bitrate tweaking even though CCE was minimized to tray
- Fixed: Shutdown feature didn't work when using bitrate tweaking


25/04/2003 v1.4a

- Added support for CCE 2.67.00.10
- Added ability to minimize CCE to the system tray during encoding


16/04/2003 v1.4

- Added option to shut down system after encoding
- Added EclCCE settings dialog along with the ability to
specify the CCE process priority
- Added a manifest file for CCE to the distribution. Copy
cctspt.exe.manifest to the CCE installation directory to
apply Windows XP visual styles.
- Fixed: CCE window title was set incorrectly when ECL file
name contained a dash
- Fixed: in some cases Encoding did not start when clicking
Yes in the "Save changes....?" prompt and then
canceling the Save dialog.
- Fixed: in some cases you were not prompted to save changes
after modifying the Bitrate Tweak settings.
- Fixed: problem with hooking into CCE when EclCCE.exe was
run with process priorities above "Normal".


27/03/2003 v1.3a

- Fixed: Bitrate tweaking feature didn't take effect when
encoding was started by clicking the "Encode Now"
button in Encode Settings dialog.


25/03/2003 v1.3

- Added bitrate tweaking feature.


11/03/2003 v1.2

- Added command line support for earlier CCE SP trial versions
- Added support for CCE 2.67.00.09

05/03/2003 v1.1a

- Added -nochapterlist command line switch


26/02/2003 v1.1

- Added support for CCE 2.67.00.08


22/02/2003 v1.01

- Added support for CCE 2.66 retail -batch command line switch
- Added -nocancel command line switch


21/02/2003 v1.0

- First release. Supports CCE 2.66.01.07

[wmansir]

Nice! Thanks, I'm giving it a try now.

EDIT: unfortunatly it's not working for me.

When I try and save a .ecl nothing happens at all, except the program becomes none responsive (windows beeps when I try and click on it). I had to kill the program, but it did save the .ecl file.

When I tried to load the .ecl file nothing happens at all, but at least CCE doesn't freeze.

Using 2.66.01.07 trial on windows XP.

[RB]

Grr. It's working for me in XP.

Please do the following. It should have created an EclCCE.ini file in the directory where you put EclCCE.exe. Edit the [EclCCE] section to add an

Debug=1

entry. Run EclCCE again and try to save an ECL. You will have to click OK/Cancel now to get out of the dialogs. Let me know where it hangs.

Thanks.

[Redbacks]

Thanks, nice little tool....

[Redbacks]

Working fine for me using WinXP Professional and CCE SP Trial version
2.66.01.07

[wmansir]

It's weird, when I enabled Debuging it worked fine. I had to cancel out of the menues, but didn't encounter any errors or hangups on loading or saving. When I disabled debuging the same errors occurred.

Here is a copy of the .ecl file that was created when the process failed:
; CCE SP Trial Version -- Encoder Control List

[item]
title=starwars1.avs
vid_out=1
vaf_out=1
aud_out=0
aud_mode=0
vid_file0=e:\starwars1.mpv
vid_file1=e:\starwars1.mpv
vaf_file=e:\starwars1.vaf
aud_file=e:\starwars1.mpa
file_focused=0
video_type=4
timecode=0x1000000
tc_ref_frm=0
drop_frame=0
cbr_brate=6000
opv_q_factor=60
opv_brate_min=2000
opv_brate_max=9000
vbr_brate_avg=2257
vbr_brate_min=1194
vbr_brate_max=2565
vbr_bias=30
vbr_pass=3
create_new_vaf=1
pulldown_detect=0
letter_box=0
panscan=0
aspect_ratio=2
h_filter=1
h_filter_idx=8
use_filter=1
filter_val=4
dither=0
dither_max=8
quality_prec=16
intra_dc_prec=1
alternate_scan=1
non_linear=1
progressive=0
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
seq_endcode=0
dvd=0
all_closed_gop=0
fix_gop_length=0
fix_vbv_delay=0
top_first=0
half_width=0
half_height=0
lum_level=0
packet_size=2048
frame_rate_idx=1
qmat_idx=0
mpeg1=0
mpeg1_cps=1
brate_idx=7
stereo=2
samples_per_sec=44100
crc=1


It's incomplete by a few lines. When I loaded the complete .ecl, that I saved in debug mode, it loaded the file but resulted in the same unresponsive state as before.

I tried the Alt-F4 to close the program and it did respond with the normal "Save .ecl?" dialog, so the program is not totally unresponsive. When I selected "no", the program closed and windows played the "critical stop" sound.

EDIT: I also noticed that sometimes hitting Alt-F4 'unfreezes' the program, and allows me to continue using it as normal. I checked the .ecl after doing this and it appears complete. I'll have to play around with it later.

[RB]

OK, I think I found the problem and uploaded a new version (silly typo in code that would cause random failures like this). Please download again and let me know if this fixes it. Thanks.

[wmansir]

Looks great now, working flawlessly. Thanks again for this tool.

[RB]

I have uploaded version 1.01. The only changes are two new command line options: -batch combines /encode and /exit (added to be compatible with CCE 2.66 retail) and -nocancel hides the Cancel button in the encode progress dialog. Also command line options can now be indicated by either hyphen or slash.

I should also mention that right now custom 3:2 pulldown settings are not saved/loaded to/from the ECL, just the check state of the 3:2 Pulldown checkbox. Maybe I'll add support for the 3:2 pulldown settings in a later version if there is demand for it.

Oh, and in case you wondered: yes, it does load/save the VBR Bias setting from/to the ECL and applies it even if no VAF file exists yet :)

[RB]

CCE SP 2.67 trial is out: http://www.cinemacraft.com/jpn/download.html

I'm working on adding support for this version.

[rui]

Thank you for your efforts :)

I just can't wait to get home and try this baby. :)
To my sorrow, that will take some hours :(, i am at the begining of a monday work day :(

[rui]

Ok, i tested the latest version of EclCCE (1.01) and it's a HIT :)

It worked like a charm, with CCE 2.66.01.07 in WinXPSP1.

The test movie was "Saving Private Ryan". I loaded EclCCE, and after indicating the path to CCE, it opened it.

Then i feed it with the avs, and tried all sorts of configs, saving in between the ecl file, then exiting and opening it with notepad.
All seemed perfectly fine.

Then i made a one pass with Q60, and it went smoothly.

Thank you again RB for this great tool. :)

EDIT1: Now, when you add 2.67 support, i will be here to test it :D

EDIT2: I for one fell that this software is of such importance for the correct use of CCE (computer not powerfull enough to make all the passes in one stroke, so the capabilitie of saving ecl file is a great advantage for me), and it seems to work without bugs (at least for now :D , that the MODS should make this thread a sticky.

[RB]

Glad to see you like it :)

Support for 2.67 should be ready by tomorrow or so. I already verified that I don't need to make any major changes, I'm just fed up with something else right now.

[RB]

EclCCE 1.1 with support for CCE 2.67.00.08 is out. As usual, download from link in first post.

[Mikel]

Hi RB

Great software. I just have a problem. With every item loaded, i fills up memory with about 50-60 Mb.
What happens is that after 20-30 items loaded, I run out of memory.
The software reports some strange avi error and freezes.

I use version 1.1, with CCE 2.66.07

Any insight on this?

Cheers

Mikel

[rui]

Well, eclCCE 1.1 works very well with CCE SP 2.67.00.8

Mikel, when you say items, you mean AVIs', or other videos?

I tried to load a avs script of the full movie "Saving Private Ryan" (it has 243772 frames) and it only loads the memory till 26MB.

[Mikel]

... single movies
I try to put together some DVD with about 30 single movies.
I want to decode them all in one batch.

With every movie loaded, the memory decreases by at least 40 Mb.

Cheers

Mikel

[Mikel]

30 movies times 40 Mb is 1.2 Gb of memory...
Thats when the program freezes..

Mikel

[rui]

Mikel, i assume that each movie is small, right?

All together, they have how much time?

I tried again to load the full movie i mentioned above (it has 2 hours, 42 minutes and 30 seconds), this time by saving a ecl file, and then exiting the program, then opening eclCCE and loading the ecl file.

It increased the memory use by 24MB only.

[Mikel]

I find that the size of movies is not the problem, it's the number.
I get serious problems after about 20 or so movies.

Make a quick test to check if you get the same behaviour.

Cheers

Mikel

[Matthew]

Thanks for this tool, it kicks ass. In particular, the command-line support is great.

[ChrisBensch]

Edited: I have upgraded to 2.66.01.07 but once I saved my ecl, I tried to start encoding and CCE just froze. Now when I try to load an ecl, it just freezes, cannot use cce with eclcce anymore.



I am using 2.66.01.04 of CCE Trial, is it possible to add support for this version?

[RB]

Originally posted by Mikel
I find that the size of movies is not the problem, it's the number. I get serious problems after about 20 or so movies.


I very much doubt that EclCCE is the culprit here. Just perform this simple test: run CCE directly, not through EclCCE, add your many items. Does it give the same errors now?

[RB]

Originally posted by ChrisBensch
Edited: I have upgraded to 2.66.01.07 but once I saved my ecl, I tried to start encoding and CCE just froze. Now when I try to load an ecl, it just freezes, cannot use cce with eclcce anymore.
I am using 2.66.01.04 of CCE Trial, is it possible to add support for this version?

Before I start thinking about earlier versions, let's try to narrow down this problem.

- Are you using the latest EclCCE v1.1?

- When you saved the ECL and started encoding, where did it freeze? Did the encoding dialog come up at least?

- When you load the ECL, where does it freeze? When you click the CCE window, does it make this "bing" sound?

- You can start encoding without using EclCCE?

[vidcel]

So we use EclCCE to save ECL's in CCE 2.67 but what's the point when it has the CCE logo in it.
Haven't found a CCEPatcher for this one.

[unplugged]

here is EclCCE, an utility that adds the load/save ECL (Encoder Control List) functionality to the CCE SP 2.66+ trial versions
YEAH
what I can say, RB, nice Very nice!

[Mikel]

RB: When i run just CCE and add many movies, the problem does not occur.

I did some more tests regarding this:
The same problems also occurs when i Save a ecl-file.

Example:
I add 15 files by drag and drop
I save the project as a ecl file
The memory usage goes from 300 MB to 700 MB
I reload the project i just saved
The memory load rises again 400 MB over one GB

Really no one else with that problem?
Could it be some kind of driver problem?

Cheers

Mikel

[Tabriz]

I have just used ecl 1.01 with 266.01.07 with excellant results. I am truly delighted with this tool.
many many thanks.
Tabriz:)

[RB]

@Mikel:

Sorry, I can't reproduce this problem. I just did what you did here (XP SP1), added 16 small clips by drag & drop, saved ECL. Memory usage went from 311 to 321 MB. Exited CCE, ran it again and loaded ECL, memory usage went from 319 to 326. Just like without EclCCE.

What OS are you running? This is bizarre. EclCCE does not dynamically allocate/free any memory, so it can't be a memory leak in my code. Also, while you are dropping files into CCE, EclCCE just basically sits in the background and does nothing.

[Mikel]

Thanks for your answer...
I cannot understand the problem myself...

Here's my setup
Win XP Pro
P4 @ 1800 MHz, 512 MB Ram

I gave you some misleading information, it's the the memory that's running out but the page file beeing used up.

So when i start CCE, about 200 Mb of the Page File is being used.
(can be checked in the task manager)

With every movie opened or save, the page files grows about 40 MB.
With a max. Page file size, the error comes after about 20 Movies loaded or saved.

I have the impression that every time one item is loaded or saved during the flickering, the memory is used. It seems like another copy of CCE is started, but memory is not freed up. But thats just my impression.

I really hope someone else has the same problem and that it's not just my setup.

Cheers

Mikel

[ChrisBensch]

I beg forgiveness for even thinking this wonderful tool could be the problem! It was a bad AVISynth Script/M2V created by DoItFast4U. I reran DIFFU and everything is working fine.

Thank you so much for this tool!

[Chatwalker]

@RB

Congratulations to this wonderful tool. If you could add a small thing it is perfect!!!! In Batch-Mode EclCCE should only return when CCE has finished his work.

Regards
Chatwalker

[RB]

@Mikel:

I, too, was talking about the page file usage (monitored it in task manager). Let's do this test:

1. Run CCE without EclCCE
2. Bring up task manager, leave it open and watch memory usage during the following steps
3. Add your files
4. Double click on the first file in the CCE window
5. Click the Video, Audio and Quality Setting buttons (in this order) and close the dialogs immediately.
6. Click the "Setting" button to the right of the Input files combo box, double click the item in the new dialog with the listview.
7. Close the preview window that comes up, close the file settings dialog, return to the Encode Settings dialog, close it.

Repeat step 4-7 for each file. Do you see page file being used up abnormally at any time?

[RB]

Originally posted by Chatwalker

Congratulations to this wonderful tool. If you could add a small thing it is perfect!!!! In Batch-Mode EclCCE should only return when CCE has finished his work.


Well, it already does so, always. EclCCE.exe will not return until CCE has finished (just use WaitForSingleObject() on the EclCCE process handle).

[Mikel]

Hallo RB

I dont seem to have the problem on another machine with a similar setup. I really cannot understand that I have those problems with ECLCee at all.

I will some further tests.

I will PM you in the future with the results.

Cheers

Mikel

[shh]

I've the same problem as Mikel here.

W2k with 512MB RAM, EclCCE and CCE2.66.01.07.

I've loaded some avs-files (actually two, via avisynth v2.0.6, mpeg2dec2.dll) and everytime a new pass starts, CCE itself eats up additional ~64MB and the paging-file inceases about 128MB, too.
After a few passes all memory is gone and avisynth can't decode any further frames, passing an error-frame to the CCE (wich is then encoded)
CCE is keeping all the memory until I close it.

How could this happen? Is that maybe a "crack"-protection?

Is EclCCE *opening* the avisynth-file, when the ecl get's loaded? I'm asking this, because the file-length [frames] is updated after changing the length in the script and loading the ecl afterwords.
Perhaps that opening the problem. :confused:
I'm still searching for a maybe-bug in avisynth in conclusion with mpeg2dec, since sometimes after opening an avisynth-file, not all ressources are freed again (some part of avisynth hangs up)

Regards
shh

[RB]

shh, can you verify that this happens only when running CCE through EclCCE? Also, please follow the steps I outlined to Mikel to see whether this is actually related to EclCCE.

[mb1]

I've loaded some avs-files (actually two, via avisynth v2.0.6, mpeg2dec2.dll) and everytime a new pass starts, CCE itself eats up additional ~64MB and the paging-file inceases about 128MB, too.
That is a well known CCE bug !
Add ResampleAudio(44100) [for avisynth 2.0.x, not 2.5] to every avs you're loading into CCE and the memory hunger will be stopped.

[Mikel]

OK...there seems to be some kind of problem with ECLCCE.
By loading or saving (when running CCE through ECLCCE) huge amount of memory are eaten up.

I tried to exclude a driver problem, so i did some tests by rebooting into safe mode. The memory problem was still there.

So it's not a driver problem.

BTW, i am using Win XP Pro, SP1
Maybe the GFX-Card is related to it, its a TI4200 based card.

After detailed testings, the problem only occurs when CCE is running through ECLCCE. CCE alone works fine.

Because of the problems with ECLCCE, i went back using version 2.5 which runs fine and can load and save ECL-files.
I am looking forward though when the memory problem is solved.

Cheers

Mikel

[shh]

Some things to correct: I was using avisynth v2.07 and EclCCE 1.01. But you didn't change any major things in v1.1, did you?

Hmm... this is weird.
I've now done some tests without EclCCE, and no error occurs.
The program is still eating more and more memory, but after a time it is freed again. (paging-file is still increasing, though - must be the W2k caching algo)
So, perhaps there is no memory-leak with (or without) EclCCE, but there still seems to be a problem with the avisynth-scripts.
All works fine without the EclCCE, but with EclCCE after saving and loading a bit, avisynth can't decode anymore.
(I did some tests with EclCCE v1.1 too now)

I have absolutely no clue why this happens. Perhaps this is a general problem with avisynth-scripts in CCE.
But definatly CCE trys to get the number of frames when loading a src-file, so it must open the script(s).

RB,
could you perhaps add a delay (editable via .ini?) between adding file#1 of the ecl and adding file#2?
I guess avisynth has some problems with parallel frameserving of several files. (And parallel frame-serving would occour, if file#2 is opened before file#1 is closed).
This problems come up quicker, if you add some denoisers to the script. Perhaps a bug in avisynth of being not able to wait long enough for a frame... (internally throwing an exception instread of just waiting for the plugin to serve the frame)?

BTW, the memory-hunger seems to stop now: My 1.2GB pagefile is full all the time and CCE is kind of self-regulating it's memory to 380MB (of 512). So, I'm not quite sure if the ResampleAudio(44100)-line is necessary. (but I'll try that anyway)

Just doing the tests for Mikel (pagefile is full: 1.2GB and CCE-Usage:380MB):
"Unrecognized exception in line 3" <- That's the mpeg2dec-line. The plugin doesn't seem to have enough memory.
Same problem with all the other files btw, all cannot be decoded by avisynth (aka mpeg2dec).

I'll try, if this also occurs without EclCCE now.

Best regards
shh

[shh]

Update:
Ok, the same problem comes up without EclCCE, so your program is definatly innocent, RB. ;)
So, it must be avisynth what has a memory-leak.

Adding ResampleAudio(44100) doesn't help, btw.

CCE RAM-usage seems to be ok.
Pagefile increases on:
- ecl-saving (when using EclCCE), for each file a little bit
- ecl-loading (when using EclCCE), for each file a little bit
- generally when activating the preview (going to settings to add chapter-points etc.)

...and there seems to be no work-around.
Any ideas??
Should we post this problems at the avisynth-subsection of this forum? Perhaps the programmers there are already aware of that memory-leak.

Best regards
shh

Update 2:
The memory-leak does not occur in CCE v2.50! I've used the same avisynth-script.
After showing the preview under 'settings', the pagefile-usage goes up a little bit, but after closing the preview, it is freed again.
(In v2.66.1.7 the memory is not freed afterwords)
So this is a problem of CCE v2.66.1.7 (or perhaps the crack)

[RB]

Originally posted by shh

After showing the preview under 'settings', the pagefile-usage goes up a little bit, but after closing the preview, it is freed again.
(In v2.66.1.7 the memory is not freed afterwords)
So this is a problem of CCE v2.66.1.7 (or perhaps the crack)

I suspected something like that and that's why I asked you to perform the steps I suggested here (http://forum.doom9.org/showthread.php?s=&threadid=46664&perpage=20&pagenumber=2#post270526). The reason that you and Mikel thought it's related to EclCCE probably is that you never (or rarely) browsed through the CCE settings up to the chapter and encode range settings where this preview window comes up. But EclCCE always does this, it basically opens up all the CCE setting dialogs and reads/writes the controls in there and that's how the ECL is being read/written.

As for the source of this problem, I really think it's what you mentioned last ... I definitely do not have this problem ... :rolleyes:

Now what I could do about it is to provide a switch that will prevent EclCCE from opening this particular dialog. This would of course mean that encode range and chapter lists will not be read/written from/to the ECL. How does this sound?

[Ntsita]

Originally posted by RB
Now what I could do about it is to provide a switch that will prevent EclCCE from opening this particular dialog. This would of course mean that encode range and chapter lists will not be read/written from/to the ECL. How does this sound?
For me it's a good choice, because this two setting are typically performed in other manner (range with avisinth and chapters with authoring program)

[RB]

The chapter list in CCE of course does not really create chapters, this is a DVD, not an MPEG2 feature. It's there to, so to say, "serve" an authoring program like Maestro. Chapters can only be set at I-Frames and all the chapters list in CCE does is to tell CCE that it should create I-Frames at specific points so that authoring software can create a chapter break at this frame at all.

[Ntsita]

Yes, it's right.
But if a chapter is pointed to a not-I frame, what happens?
Surely, if you go to this chapter, you have a very slightly delay before the frame is displayed (it will be searched the next I frame after that point), or not?

[RB]

A chapter cannot point to a non-I-Frame. That means that if there's no I-Frame at the point where you want to set the chapter, the authoring software will set the chapter at either the previous or next I-Frame. IOW, your chapters will be off by up to size of GOP.

[Ntsita]

okay, then is it insignificant?

[RB]

Depends on your personal taste :) I'd say I'd surely like to keep the exact chapters from the original DVD (if we are talking about backing up DVDs). Anyway, I'll put that switch in and everyone can do as he likes.

[RB]

OK, new version 1.1a is out. You use /nochapterlist on the command line to work around this "bug". You can also make this setting stick by adding


ChapterList=0
to the [EclCCE] section in EclCCE.ini.

[rui]

Great. Thanks for your ongoing support :)

Just a sugestion: could you place the link for your wonderfull software in your signature, so one wouldn't have to go to the post in the first page of the thread to get it.

I know, it's a small thing, but i think your work is so good that it deserves to be mentioned in your signature :D

Thanks again.