PackShot bug report thread
 

Please do report bugs on "PackShot" here.
Questions about the usage in general have to be asked in the PackShot release thread, not here! ... thanx! :wink:

Hmm... sorry for being the first bug-reporter :oops: .
I tested in 2 different vobs from 2 different films...

Video encodes as we're used, OK.

For 1st audio track I chose Spanish ( :roll: ) and left default settings

For 2nd audio track I chose English, ac3 2.0ch, and left default settings.
When besweet encodes 2nd audio track, it displays azid parameters and then LAME ones (CBR, joint stereo and so). In the command window it appears the parameter OTA instead of ac3enc (or whatever).

So it looks that despite selecting ac3 it encodes mp2. But the file extension is ac3.
I loaded the 2nd audio stream in Headac3he and compalins about not finding ac3 header...

No prob, every hint to a bug is welcome! :)

Thats defenitely a bug then! Ill check that this evening.
Did that happen when you loaded a setting.ini incl. these options choosed or did you just tested it without any save/load settings workout?

Thx!
Inc.

PS: Was the engl. original source auido track already in 2.0CH? Or did you choose AC3 2.0 and downmixing lfe -3db out of an orig AC3 5.1 Audiotrack?

http://www.digitalfaq.com/archives/i.../2004/05/3.gif

1 - We can read "source " maybe better "Source" (First Letter = Capital Letter).
8 - We can read "sharpen" and "blurring" same as previous (First Letter = Capital Letter).
32 - It would be Available Soon.
33 - It would be Save Settings.

@ Prodater64

:lol: Totally agree with you!
Kwag and I yesterday just saw the "safe" has to be save" which ahs been fixed (look in the real appl. now) .... but for the rest of correct english it seems we where defenitely toooo tired :wink:
One time your head is FULLLLL of Variables and you dont think in words anymore .... so thanks for the hints! :)

@ DigiDoc .....

Audio 2 caused 6ch AC3 even if 2,0 AC3 is selected, that bug btw I did found! AND if a 5.1 downmix to 2.0 is choosen, then "surround2" was used in azid, where latest azid uses "dplii" .... also fixed that ... new vers. release will be tonight!
(BTW. Kwag told me he encoded an Ac3 to mp2 from 5.1 to 2.0 using the last release and so he didnt told me that he had probs! (even "surround2" was used in azid parameters and not "dplii" 8O )

The rest seems to be determined well:

First Track: AC3 5.1
Sec. Track: AC3 5.1
First Track: AC3 2.0
Sec. Track: AC3 5.1
First Track: AC3 5.1
Sec. Track: AC3 2.0
First Track: mp2
Sec. Track: mp2
First Track: AC3 5.1, max gain, delay -80, 384kbit
Sec. Track: AC3 2.0 no downmix lfe but surround flag set and stereo flag set, gain 5db, delay -20, 224kbit

Ok Inc, that would be OK. But in my process.bat it reads:
that's for second track (english ac3 5.1 ch, downmixed to ac3 2.0 ch)
Anyway, I think you already fixed it. :wink:

"MAJOR" Bugfixes have been made in the last hours where beside the other audio issues I also found a bug according to gain determination in the commandline!
Before I used the gain parameters using ota( -g ...) engine for gaining which gave even more quiet outputs when AC3 and auto "max" gain was choosen!
I did many tests and the way gaining via using the azid(-g ...) engine is the best and preserves full 5.1 digital separate channel sound .... you can hear the difference according to volume of the encoding. ALSO be shure you did set up AC3Filter in the system properly cause its set generally too low and thats why often AC3s do sound more quiet on Windows Systems.
Well when using the "max gain" a "klick" just at the veeeeery beginning of the AC3 encoding can be heard .... seems to be a ac3enc or azid issue, well maybe you all also recognise that?! And .. can it be heared when you play the authored DVD on your Tv or Surround set?

Also some Bugfixes according to the input and target file requesters have been made ... now the target AND the IFO first will open in the same Folder where the source was choosen as a) the Ifo of the source VOB everytime is in the same folder and b) odten people do save their encodings in the same folder as the source. But for shure you still are free to choose another location ... its just set as this when the requester opens.

Inc. :)

:!: There are big issues when performing a InverseTelecine on telecined sources --- no matter if "-fps 23.976 -vf IVTC=1, softskip" is used or "-fps 23.976 -vf pullup, softskip".

both do still end up in fieldshifted 23.976 output, so an adding of "Softpulldown," before the inversetelecining vf parameters solved at least that.

BUT the video is minimalst shorter than the audio = async!
(Same issue when trying that with MencodeME)

I do speak here of the case when telecined sources are used! Means a 29.97 out of a 23.976 i.E.

minor bug :

1/ open pack-shot, do all settings and save parameters. close the app.
2/ open it again, load the settings and try to go

:arrow: error saying that no target is selected even if there is something in the "target" field. You have to refill it to be abble to run the job.

And I would keep it that way :!:
Except erase the input and output file names :idea:
That way, you just load all parameters, but you prevent overwriting your previous encode, if you click START ENCODE after you've already done an encode ;)

-kwag

If it does so, okay, the feature should stay like this (I agree with you).
Currently there is a weird situation where the field has something but the tool tells the opposite.

Exactly :!:
I guess Inc just did set the text field to the file names, but forgot (on purpose?) to actually set the related variables :)

-kwag

FIXED!

:)

The variable in the safe settings mode was wrong written

outputfile$ would be correct

but a variable outputfilr$ was written to the ini file which doesnt exist and therefore contains "" and this interprets the "run" mode as -no target- :wink:

Thanks phil!

In what way :?:

-kwag

In the way that after loading a Setting you first have to determine again a Target path/file! Like you suggested ;-)

Also some people might think, why Packshot just displays the source file and not the whole path in the Source Field. Thats cause if you load the ifo, you can directly compare the right VTS track number ;-) wich you wouldnt see if the whole source path would clip out of the traget field/window.

@Inc
I have an error (didn't try to look which exactly as it is not very important) if I select mencoder matrix.
I have P4 1.6 GHZ. Which mencoder you suggest is better to use p4 optimized or generic build? Currently I am using the one from MencodeMe023 bundle.

If its not importand that it wouldn't be an error :lol:
Maybe the values count of the mencoder matrix is set wrong by Packshot, so specify THAT error.

P4 should run with a P4 build as "nomen est omen".
I did compile that build on an athlon! but I used a P4 cpu related confugration when compiling. So I couldn't test it by myself.

P4 - well,OK. Ah by the way if I rename an 720x576 MPEG-2 mpv-vob it works with packshot no problem :D . The only thing is mencoder internal denoising is not so good as avisynth filters, but it is not a problem of packshot.
I will look for the error (tried two sources - the same, DOS window appear for a second - clear sign for an error) and post it tomorrow.

The following point is just between a bug and a suggestion but I post it here :

I have a DVD anamorphic. If I load the VOB in packshot, it is identied as 16:9 and the "non anamorphic" box is enable.

The problem is that I need to cut the credits. Do I did a D2V project, and avs script, and a false avi with makeAVIs.

:arrow: this time the file is identified as 4:3 and I can't check the "non anamorphic" box.

THis box should be availaible any time IMHO.

Problem is:
Non-anamorphic means letterboxing in here and IF you already go via Avisynth, then you can set that in your script.

BUT! The incorrect thing of packshot in case of an anamorph avi input (which is in regular not the cas), he will set a 4/3 AR flag, even the image will be encoded anamorph --- so how do you want to end up? Anamroph or non- anamorph/Letterboxed??