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??

Okay, that's true that as a script is already involved, this operation can be done by the script. I agree with that.

BUT ! The problem here is that I didn't wan't to do a "non anamorphic" target, but an anamorphic one (that means that even if the box has been enabled, I wouldn't have checked it).

The problem is : as the source was identified as 4:3, the target was done without the anamorphic flag set on. And when I put it into DVDLab, the file was identified as 4:3 and not 16:9 !

:arrow: I had to parse all the m2v via dvdpatcher to activate the anamorphic flag befor to author the DVD. :-(

That is why I thought the box should be activated anytime. To tell if you want to set the anamorphic flag on or off in the target.
But perhaps your idea of this box differs from mine!

A "Override Automatic Settings" check box, perhaps :?: :idea:

-kwag

I don't know if it was posted before but ich I choose on Pack-Shot 5.1 AC3-Sound the Output File is a MP2 Stream with 128kbps. If I look with the Editor in the Command lines the AC3enc is choosen. 8O I don't know what it is.
Is it a bug, inc.???

Hi EM ,you should wait to hear from INc but in the new version of pack shot there is a message about there being a problem with AC3 or something did you read that because maybe it defaults to Mp2

Just a guess though

OK, thanx. I wait for the new version. :wink:

Hi sorry for beeing that late.
The issue was a bad " -f1 " parameter in azid( ) and thats fixed now.
New Version 1.02.3 is online.

According to the warning window. Thats an agrement with DSPguru, so it clearyfies that ac3enc is just a 3rd parity filter and so DSPguru will not be responsable for any ac3 issue which could happen.

Well in my case .. ype, mp2s sound louder but all my ac3s do sound even louder than the original VOB if auto Gain is choosen.

Inc.

Another little bug I've found. Not realy bad but a bug. If you choose the credits and again and again then the credits you can see first once then twice etc.

using PackShot_1.02.3+BeSweet

VIDEO:
source ntsc 720x480 AR 16:9
target : ntsc 704x480
GOP 18
FPS 23,976 NTSC FILM
2 pass
pulldown

in AUDIO:
track 1 stream 1: pt : ac3: 6 ch
track 2 no audio
audio track1 ac3 5.1 256 0db 48.000khz (would be wrote 48Khz or 48000Hz!)
audio track2 grayed

observations using win2K:
the windows run slow and if i try open the win explorer the system crash(freeze)...happen 2 times, was needed to reset the system(reboot) then i re stard and don't open the win explorer and PackShot run ok!
:arrow: feature request:...ink can we have a "process priority" option :?: (if is possible)

AUDIO result:
final size 0 bytes (ZERO) 8O :? why?

VIDEO result:
final size 1,06Gb :wink:
quality (powerdvd) 8) wow! very good image!

loading the video in tmpgencdvdauthor i got:
The video GOP is too long.
The video GOP is too long.
For a standard DVD it is necessary that the GOP fulfill the following condition:
Max 36 fields (18 frames) (NTSC format only)
Max 30 fields (15 frames) (PAL format only)
8O why if i was choosed 23,976 ntsc film ,GOP 18 and pulldown :?: :?

jorel,

if you want to change the process priority, start encoding as you normally would, then cancel it with CTRL+C, go to MS-DOS command prompt, move to the Packshot\engines folder. You should see the file called encode.bat, which is the one containing the command line for your last encoding work (the one that you cancelled).

In the command prompt, use this command line to restart your encode "start /belownormal encode.bat" (without the quotes). Now it will run in below normal priority. Use "start /idle encode.bat" if you want it to run in idle priority.

@ Boulder (always with shine hints)
(i'm using win2K)
i don't have a encode.bat in Packshot\engines folder.
i "found" ---> process.bat where are the command lines:
"mencoder.exe" -of rawvideo -sws 9 -nosound...."
"engines/BeSweet.exe" -core( -input "D:\..."
is that the right .bat :?:
have a way to do another .bat that call the process.bat
using "start /belownormal xxxx.bat" (without the quotes) ?
thanks in advance my friend! :wink:

@ ink and all:
about the audio..
maybe this is the reason:
i was ripped in dvddecrypter the main movie and the portuguese audio only in "file split"---> none and got a big vob ~3,18Gb.
when i load the ifo file in PackShot and choose the
:arrow: track 1 stream 1: pt : ac3: 6 ch
and in the process.bat command line was wrote: ...-substream 0x80..
:arrow: but the portuguese is the ---> -substream 0x82 :!:
then i change the command line to the right substream to the right audio !
....then i get the right audio.

i can't choose the right audio track in PackShot ripping the vobs like i did!
i did something wrong? :?
thank you!
:wink:

Yes, that's the file you should launch. I don't know if the 'start' command works from a bat file, that's something you'll have to try :wink:

Jorel I did tests on a NTSC VOB where both audios came out perfect, even in AC3!

So thers something wrong you did set.
Kwag also already did encodings and had no Probs with audio or EVEN GOP :?
As the Keinterval will be set in the process.bat as you choosed it in the encoding settings. So IF GOP 18 is choosen, the keyinterval in the commandline will have that value :!:

So my advice to you and ALL is ... if you got probs dont quote parts of the process.bat but do quote here the WHOLE generated process.bat of the engines folder! So I can clearly see what will be processed and where could be the problem! ;-)

So Jorel Post in here your process.bat content and I CAN SEE.
(sorry for confusing ... theres no "encoding.bat" but a process.bat in the engines folder.) ;-)

EVERY Time DO RIP ALL Audios from your DVD when using DVDdecrypter and Packshots IFO recognisng option!!
If not, do NOT load the IFO!!, and therefore use the Stream IDs in the Audio Track Combo List box instead!! That stream ID then will be then given to Besweets Commandline.
Because the IFO recognision will be corrupt if you do choose only the neded audio in DVDdecrypter, means the 0x82 will still be 0x82 but the IFO will tell packshot that the first audio is 0x80 !!

Inc, you didn't tell what you will do accordign to the "anamorphic" box.

Do you plan to change things or will I have to use dvdpatcher any time ?
It's stange that you dont suffer from this yourself. Am I the only one that use dvd2avi just to cut the credits ?

As I told you via PN ..... that will be implementated!
A "force 16:9" flag setting in the encode section ;-)

New Packshot is released!

Its beta, so please do report bugs, thanx!

The resizing engine of Mencalc is now included, means direct avi/mpeg4 support.
In case of a wanted cropping of the blackborders before (when adding noise on black borders containing sources) please in this beta state do use "commandline only" and do tweak the resizing parameters to your own needings. The final release will contain a "Film Pixel" cropping support where that will be no problem anymore.

http://www.kvcd.net/forum/viewtopic.php?t=10915

Read also the included Readme, as Packshot now comes including a codecs.conf file so users just have to install ffvfwmakeavis (if really needed for avs) and put the copy of mencoder.exe into the "packshot" folder, thats it.

hi Inc.,

I found a really HUGE problem- the filename is "1.0.50" but it should be "1.05.0" :lol:

Finally installed and ran this now and it is fantastic!!!!!! Lot's of features and the batch encoding is really great. Thanks a lot for making this :!:

ren

Hi incredible,
I tried packshot on my win98se machine and .. well... the command line is too long apparently and I see the command-line call to mencoder but the result is "Bad command or file name".
It seems the command-line is too long. Could you save some of the options to a temp.conf file which mencoder would read instead?

Thanks anyway.

Is that Win98 only related??


@ Ren

Yep! That should be fixed in the name ;-)

As in here at kvcd now many users do "try" to generate proper working KsVCDs/kDVDs ... I added a "Caution" Remark in that Packshot Download Thread.
Its a fact that everything which bases on mencoder.exe should be handled carefully and no author of a mencoder GUI can take the responsibilty as the main problem relates to the non proper working ratecontrol code of mencoder.exe :!:

So see that GUI only as a possibility for experienced users to get "tweakable" commandline outputs.

Well, a report :D . PackShot 1.05.0
1. The source is *.vob with 3 audio tracks. Audio 1 German 6ch, audio 2 German 2ch, audio 3 English 6ch. I want audio 1 English 6ch 256 kbps, audio 2 German mp2 128 kbps (from the 6ch track). I select the appropriate tracks after loading the *.ifo and click "Command line".
The generated command line is:

Well, I expected for the first track the output to be *.ac3, but it is *.mp2. Maybe this is in favor for mplex muxing I don't know.
2. I start the encoding, but had a feeling it is too slow. So I decided to reboot. Kill cmd.exe, save settings in PS, reboot. Launch PS, load settings. The source is loaded (vob), I specified the same target, but the ifo is not loaded, the field is greyed out (I cannot load it). First track is there (English 6ch)-OK, the second is also there(German 6ch), but greyed out. I clicked Command Line to see what for line it will generate. The Line:
Hmm, for some reason as input in mencoder line I have the expand settings. As expected only one audio is taken in consideration.
3. The last I will report only for fun and completion. I am sure and aware that THIS IS NOT PACKSHOT BUG. The mencoder used was from MPlayer-mingw32-1.0pre4.zip. The encoded *.m2v has NEGATIVE (Yes, yes, MINUS :D :D ) average bitrate, namely -235 Kbps (shown by VDubMod, and I seen it in cmd.exe, before the ecoding to complete). Nevertheless it played OK in MPC and the quality is also OK (av bitrate specified you can see in the command lines here above) :mrgreen:
So, that's it.