Hi ren,

Did you try the BETA 2a
That should be faster
I'll probably add faster prediction, but that will be for version 2.0, because I think we're pretty close now to Version 1.0 BETA 1
I just need more reports, before I release as version 1.0.

kwag

Kwag,

I think it would be easier to enter the length and fps instead of the average frame rate (average frame rate = length in sec / fps) since these are almost always known whereas average frame rate requires using a calculator.

When I use the large fonts display option the entry box titles are truncated. Placing the titles after the boxes, instead of before them, would allow both normal and large fonts to be used.

Let us know the final file size, so we can compare the accuracy

-kwag

You still need a calculator, because CQMatic needs to know the file size to encode, and that is only known with Moviestacker, FitCD, or other calculators that take into consideration the video size, number of CDs, etc. I haven't tried that

-kwag

I give CQMatic a try

I encode now the movie in CQ: 48,15

Hi Kwag..

I have a suggestion w/ reference to that suggest for a
dump of the LOG's contents, which was mentioned earlier.

I agree, there should be a feature for this, so that we
can help eather other out in determining the issues that
tapes place when using CQMatic

I don't think that its totally necessary to save it to a file,
unless really needed, or if CQMatic becomes more "meaty", but
it doesn't hurt to add in a feature, (a button) for this.

But, since we're all using this app, and in the testing stage,
as with all yours and other peoples "apps in development", it
would be more beneficial to add a dump of the listbox contents
to the CLIPBOARD, so that we can just PASTE it into our posts.
Actually, it's rediculously easy to implement

Please add this (right away) into your NEXT update (beta 3) you said ?? ( C++, Delphi, MSVC, C++ Builder ?? you didn't say)
Yeah, don't go another step w/out this. Don't have us all type
blindly, those lines ..as I said, it's rediculously easy to implement

Much needed feature !! hear, hear!!

Thanks,
-vhelp

Question:
How about a built-in average bitrate calculator
-----------------------------------------------------------
Answer:
Expect that for version 2
-----------------------------------------------------------

Nobody suggested it, so I did

-kwag

That will go on version 1.1
I just want to make version 1.0 as perfect as possible, before adding anything else
First priority is to verify that prediction is correct, then I'll add features

-kwag

>> Please add this (right away) into your NEXT update (beta 3)

OK pal,
-vhelp

I hope the final version of CQMatic and its planned bitrate calculator include functions for KDVD output into sized output files (i.e., 1400 as well as 1600).

Maestro kwag:

I believe that I have placed this request someplace else, so forgive for duplicatinf, but this is the right place for it:

Is it possible to place date and time for the encoding functions? That is the starting and ending time for such functions.

Thanks

Otto

maybe ice beers, whiskey(jack d.) and blondes?

It is, but for version 2 I just want version 1 to be as bug free as possible

Edit: I had posted that it would be in version 1.1, but because it will be a major revision, there probably won't be a version 1.1

-kwag

Hi Otto,

I'm testing that right now, for RC-3
I'm adding that, because it's no big deal, and it won't break any other code

-kwag

gracias Dom Kwag

Kwag:

I have a request, and this request is based on either my quick fingers (read anxiety to see what I had encoded), or stupidity on my part.
I encoded a movie last nght, it took about 7 hours to do, which is great, unfortunatelly it is over 1.1 gig without audio.(will post about it later on), but prior to checking everything, I did not save CQmatic's log. (I had just waken up and.. excuses, excuses eh?) Double
My request:
Is it possible to save the log automatically when CQmatic is turned off? Or perhaps trigger a "Would you like to save the log? type of question?
Sorry if this request is silly, I have read before that you are applying the KISS rule, well, in my case, it would be OPF (Operate properly fool)

Thanks

Totonho03

But that was not with 1.0 or 1.01 Release, right I'll do better than that. I'll save it to "CQMatic.[date+time here].log" when you double click to copy it to Clipboard, OR automatically when the process is done
This way, I'll never overwrite a log, and you can fill your disk with a log history It's not

-kwag

Hey Kwag would it be to much trouble to make the CQMatic window resizable or bigger?

That log area is pretty tiny and after a few sample runs the scroll list gets pretty long. I'd really like to use more screen real estate.

Thanks for all the hard work!!

For version 2, which will integrate the bitrate calculator, I'll widen the log window

-kwag

Hello kwag.

Sorry about this, here is the beginning of this morning's log, which is the same version as used last night:

and the end:
Perhaps I did something wrong last night while trying to fix the stretched output, but I am not sure that one is related to the other.

Thank you for your quick response.

Totonho03

Edit: Sorry Kwag, I should have posted this one in the "bug" thread