Should I support TMPGenc

I just tried the latest TMPGEnc using 2pass VBR and it looks nice. and I was wondering if I perhaps should start supporting it. I have looked a bit into it and I think I can fairly easy incorporate support for it. But in the first round I will only be able to support CBR and 2Pass VBR.

What do you guys think. Please vote.

if this means that we will have CCE and Tmpeg, and will be just a question of taste what encoder to use...

my vote is yes, why not?

btw: I made a test few days ago, and tmpeg 2passVBR took almost 2x the time of CCE 3passVBR encoding.

Oh, by all means if it is not going to cause a major rewrite with the associated bug hunt. This would give people an option.

I agree, the newest versions of tmpg are definately getting there, especially with 2pass.

I do not look forward to a bunch of questions caused by the try me placard or the expiration of the demo. I wonder if it might be possible to check the registry and inform them that they have expired and are SOL before beginning the encode.

@Mozart:

Yup, TMPGEnc is when using the best Motion Search Precision, extremely slow. But, I think that on a 2cpu system TMPGEnc could be quite faster because it supports Multiple CPUs.

btw, if I am to support TMPGEnc, I will use it as I use CCE today. That is the input will be from avs and not d2v.

If this can be done without endangering stability using CCE, I'd say YES please. It's always better to be able to choose.

BTW
before i discovered d2s i used flaskmpeg-avisynth-tmpgenc on a dual A1700+ system: i got approximately .7 RT

Yes, I would definitely use it if it was supported. Spent too much time on learning tmpgenc template tuning and I still use it for a 26 part tv_capture-gt;vcd project with moving menus (tscv). Slowness is not an issue for me because I regularly start coding at 10pm and can check it out next evening ;-(

P.S.: due to a forum errmsg I could not vote so pls yes++;

Thanks
Z

Yes please!!

During the last week I encountered nothing but problems with CCE (even tried the failsafe way with 2.50,2.62 and 2.64). If the quality is something like the CCE 3-pass VBR then yeah!! Your work is great DVD2SVCD, thanks a million!!

/Ivan

quot;If it aint broke, dont fix itquot;

But for some people, it is broken.  CCE refuses to run on my computer at all when doing multipass, even outside of DVD2SVCD.

Plus it's not free and mentioning the quot;other wayquot; would break the forum rules.

The problem with TMPGEnc is the 30 days limit.  Maybe you could support a (very) old version.

Still a bit of a newbie at this, but I have successfully created over 30 DVD to SVCD movies so maybe I am not that new anymore....
If it won't endager the stability of the current program and cause you major headaches to do, why not? If I understand all this correctly
we could use this instead of CCE to do some conversions on older systems not running an Athlon or PIII.  I know I have an older system sitting around that is mostly just used for email(wife), it could be very cheaply converted to use the program and save some wear and tear(and Time) on my system.....Great idea if it will work......

I would think you would have a fair amount of trouble predicting the actual filesize, wouldn't you? I never had much luck getting TMPEnc getting to meet the correct bitrate...

I would conjecture that only a cbr mode or two pass vbr could be used and have accurate file size. D2S may have told me that ... it is in my head from somewhere.

yeah sure add it

Although I don't like the ploicy they enforce... It´ll surely be a relieve for those who can´t get CCE to work (not my case...)

I am torn.  On the one hand it would be a great thing for the people that have problems with CCE.
On the other hand it will be more work for you, potentially add problems and increase the scope of the forum.
We really don't gain much on the CCE logo/TMPG time out issue.  Were we get many quot;how do I get rid of the logo in CCE?quot; questions now with TMPG we will get quot;how do I get rid of the 30 day limit for Mpeg-2?quot; questions.
If you could somehow sneek a registry cleaner into DVD2SVCD we would be set, but somehow I think this will irk the TMPG people.

I guess in the end if it's not to much work the ability for the people that have problems with CCE to use DVD2SVCD probably wins with me, but only if it doesn't take too much of your time and introduce many new problems.

Mark

My gosh, is it true?

An old quote from DVD2SVCD:

quot;3. And all the damn mails demanding new stuff. Why is it people think they can demand changes in dvd2svcd? What happend to a nice suggestions and a good reason to why exactly that new option would be good in dvd2svcd. For instance I have been getting mails demanding that I support TMPGEnc as an encoder. THAT WILL NEVER HAPPEN. Nor any other encoder will be supported. Well, not before I find an encoder which I think is better.quot;

Well, I shouldn't poke fun of the situation as adding TMPGEnc support would be really great.  I for one can confirm that TMPGEnc does a very good job at scaling over multiple processors having spent far to many hours with TMPGEnc and my dual processor P3 systems.  TMPGEnc scales well not only because of the encoding pipeline that can scale over multiple processors, but even moreso because it supports a seperate thread for video prefetch.  I just noticed that the new version even supports pipeline for motion search.

In my experience, TMPGenc sticks to the restricted bitrates.  I have heard in this forum that CCE does not.  In my experience, CCE actually does better at the lower bitrates, but this contradicts the opinion of others; perhaps DVD2SVCD will demonstrate with encoder is actually superior.  I have read the CCE tends to encode video that is slightly softer than TMPGenc, and maybe this gives CCE an unfair advantage.

I always click the 'Soften block noise' option to 'true' in TMPGenc and set the Intra- and Non-Intra- block values to 99 and 99.  I believe that people are parinoid that this will soften the video and thus lessen the video quality, but you see, TMPGenc only softens the video if a quot;bitrate shortage occursquot;, thus quot;ugly block noise will hardly appear.quot;  Maybe I should mention this over in the TMPGenc forum, but hey, since I started using DVD2SVCD, I have left TMPGEnc behind me.

blah blah.

Thanks again DVD2SVCD!

On one side,  one has to admit that CCE does not really fit with all the other pieces of software included into DVD2SVCD. It is quite strange to bring such a powerful free tool as DVD2SVCD and to force people to quot;buyquot; a very expensive product like CCE.
On the other side, CCE performs extremely well and for people who don't want to spend days for encoding, TmpgEnc is not a good choice.

Still,I understand that for people who have crashes with CCE, the TMpgEnc option would be nice.

On my personal point of view, if I may, I'd rather see the AVI2SVCD functions operational and bug-free before including TmpgEnc support (but it's just my personal need here).

There is also a risk when one keeps adding functions to a good piece of software, since it increases bugs probability, due to multiple possible combinations of parameters and so on. This might quickly become a real pain in the @55 for you to work on ! (like CCE crahs problems).(and maybe the AVI stuff will also be).So I don't want to look like I'm selfish or anything, nither do I want to offend people who have serious problems with CCE, but I'd rather say no to this TmpgEnc proposal. I think it is far too complicated for the real benefits it will bring (unless more than 50% people have crashes with CCE).

WaldokSure, but keep the CCE option because that one is the fastest and with the best results so far (at least for me)

i voted for the support of tmpgenc, but i still think that cce is the BEST encoder available, but with the support of tmpeg dvd2svcd will work for more ppl than now , but my quetion is the folowing ( please dont flame me ) will it also be possible to make vcd or xvcd ? . because if it will there will be a lot more of users that will be able to use this MASTER PIECE OF SOFTWARE, cause a lot of my freins gett a little disapointed when they find out that their dvd only reads vcd or xvcd. if it will not its ok for me but if it will,dvd2svcd will became a lot more popular !

TMPGenc is very promising. So, I vote to include it to DVD2SVCD.