A "Minimize" button, por favor

-kwag

@kwag
Not a bad idea my friend . Hint-hint, nudge-nudge .

__________________
AudioSlave

How about having the drop down list of 'max rates' editable - I use 1850 as max, this restricts me to 1150 or 2400 (i think theyr'e the values).

__________________
|
Meeow!

An option to select process priority would be very nice.

A very good tool, by the way

Adding a Mencoder version with native AVS support would also be nice...

__________________
j3llyG0053

Hi J3lly,
I completely agree that we should provide both GUIs with MEncoder or maybe with a link right next to it to the latest MPlayer/MEncoder links.
But then we're still "fighting" to include internal AVS support in MEncoder.
So I guess Inc. and VM should provide those as soon as we get it working
Cheers

__________________
Rui

1. "Minimize" button --- done!

2. Changing "Max Bitrate" from drop down list to a Text field where you can enter full individual values! ok? ---- done !

3. Process priority selection ... oh oh ... a new Checkbox will be done ... may you excuse that Ill do put that on my todo list ... it will be done soon!

4. avs support ---- shure if that will work!



Version incl. the changes will be available this afternoon (CET)

It would be nice a wav to mp2 audio encode option, even for todo list.

wav source ????

Whats your purpose?

Much more senseful would be if we get dts DECODING in besweet working ... that would be great ... as I had maaany issues according this.

As I posted in another thread, and even after what you explained there, I would like to have the possibility to mux within pack-shot...

It would also be useful when you load an avi, not generated with makeAVIS (like the avis I make when capturing), it demuxed the audio (BTW, in PCM-wav format) and the wav file was loaded in "audio". Asking too much?

For that reason, it would also be useful the chance of encoding mp2 from wav.

Inc,

the priority setting can definitely wait..it's not that hard to set manually every time

If you feel like adding something to the GUI, I'd like to suggest the possibility to use custom matrices.

Ah man!! Incredible.. you're ... ahh umm Incredible!!!

__________________
|
Meeow!

@ Digi doc

I will add the capability of individual AVI import WHEN I got the internal resolution calculator ready ... as now Templates from 720x576(480) to XXX x YYY are used which I had made by using FitCD.

I "could" add also Avi source resizing internal-templates incl. 768x576,704x576,384x576,352x576,384x288,352x888
+ ntcs 640x480 etc etc betc etc ...

see? It would be a damm lot of work and a real calculator makes more sense and so I better put focus on that = muuuch more elegand and that avoids a mega amount of internal IF/Then routines

Muxing ... shure ... sometime it will be added, but ... whats the problem, why dont you just take mplex.exe (frontend) and do the job?
Even if you follow the intention of the state of PackShot now .. means DVD in and DVD out ... you have to author the DVD later (and therefor muxing within the authoring appl.)

But I see .... you want me to release the "golden mpeg-job cow"
My answer: This is just the beginning ..... but ... poco a poco as I also should take sometimes time to get fresh breath from the "outside"


@ Boulder

YEP! Will be done ---- Matrix developing/comparing actually is a big subject on doom9 - as I catched the "bach" matrix is very favored there


Inc.

And the new kid in town, Jawor's 1-CD matrix looks very promising. I've been using it for my low-bitrate TV capture encodes and it looks very good both compressibility and quality-wise

Hi Boulder,

Zoom in about 300% on a still dark wall or similar object, on something encoded with Jawor, and compare the dancing DCT blocks agains the same encode with the Notch matrix.
Then tell me what you see (I already know )

Edit: From the developers at the Mplayer's group:

" The difference in bitrate was a big surprise. Using "-K kvcd"
with mpeg2enc the average reduction in bitrate (as reported by
mplex) was 20% (depends on the -q or quality setting - sometimes
the savings was closer to 12%, other times 25%). The TMPGEnc
tables split the difference between the default and kvcd tables -
usually around 10-15% savings over the default tables. Much
depends of course on the source of the material being encoded.

The claim that the kvcd tables reduce the "splotches" during
dark scenes is true - the dimly lit scenes do look better when
using the kvcd tables.

Cheers,
Steven Schultz"

http://zebra.fh-weingarten.de/~maxi/.../msg00537.html



-kwag

hi inc,

an entry for 544x576(480) in the target resolution combo would be great.
i used this successfully on some 300-360 min. encodes to one dvd-r...

a lot of tnx for your great packshot

regards, ***mfb***

Yes, friend of course, take your time. And look for time to enjoy life .

... and now back to wishes :
It's clear the actual intention of your tool, DVD in DVD out.
For future (future) releases, it would be nice also support for more than one DVD film. Yes, we can make the numbers, and feed PackShot with them. But we need the ac3 sizes for that, and that means encoding audio out of PackShot first... It would be nice to load 2 or 3 vobs in PackShot, leave it work several days (in my slow PC) and then author a KDVD with 2-3 films in.
And for future (future future) releases, also nice to load our captures (AVIs) and have the video and audio to author our home-made DVDs.

I see I don't let you breath. Take it as is, just ideas for PackShot v10.02.01

As we do encode our audio at a fixed CBR rate we can simply calculate at wich bitrates and which durations of thes movie what sizes would come out these sizes would be added to the calculation of the avgbitrate generally when several movies will be encoded.
That would then be possible "when" I get the Batch option working.
Is on the "list" As Im also a capturing maniac.

@incredible
Would it be possible to add 480x480/576 to the resolutions - for all of us poor folk, we who don't own a DVD burner... yet!

__________________
AudioSlave

Why ???

As any encoder on this poor Earth, the resizing shouldn't be done by the encoder but with an avisynth script !

If you really need to do other things than 704*480/576, use a script.

@inc
Is it possible to have a zone where we can edit the command line that will be launched ? That's would be the easiest way to improve the tool by tweaking the parameters you choosed to implement.