Log in

View Full Version : AutoMKV 0.95 beta 21 NEED TESTER!


Pages : 1 [2] 3 4 5 6 7 8

delacroixp
13th January 2008, 05:09
*** EDIT_2 ***
Plays fine
I re-tried 0.95_Beta5 with Out of Africa (http://en.wikipedia.org/wiki/Out_of_Africa_(film)) and it also refuses to co-operate.
Extended log added.


:):devil::D
Pascal

buzzqw
13th January 2008, 09:36
@delacroixp

movie.h264 is a raw stream and so it's normal that not play

you should look for final muxed file

anyway looking at your log i saw that ar passed in muxing is wrong, on manual crop and resize no ar must be passed

http://www.64k.it/andres/data/a/AutoMKV095beta6.exe

BHH

Honeyko
13th January 2008, 11:03
Actually VLC will play it....which is very handy indeed.

Honeyko
13th January 2008, 11:11
BUG: Selecting manual-crop on the advance page grays-out Width setting on the general page.

buzzqw
13th January 2008, 14:39
@Honeyko

BUG: Selecting manual-crop on the advance page grays-out Width setting on the general page.

not a bug

or use manual crop AND manual resize

or use automatic crop AND specify only width

BHH

Aylwin
13th January 2008, 18:43
On Vista, everytime I run AutoMKV I get the message:

"AutoMKV need that libsndfile-1.dll (used for audio encoding) is copyed to your system folder. Allow copy?"

It doesn't matter if I click OK or Cancel. The file is already there in the System32 folder. Does it need to be in some other folder? Is this a bug?

There is no such error message with 0.93a.

buzzqw
13th January 2008, 19:45
the dll should be in your syswow32

when automkv say this message it also say the full path

please report here

thanks

BHH

Honeyko
13th January 2008, 23:32
BUG: If, after encoding is completed, there should insufficient space on the destination volume to copy/mux the video and audio files together into the chosen container, the string process will simply quit without any explanation. (I assume everything inside the Temp folder is "kosher" for manual muxing at such a point.)

Honeyko
13th January 2008, 23:40
BUG?: I have a test film clip whose VOB is 300 frames long at 29.97. (It is de-telecined to 240 frames during automatic processing.) The clip includes a gradual fade to black during the mid-section, and about fifty or sixty frames after that are just solid black; however, the very last frame, #300, is of a new, non-blank scene. -- This clearly non-progressive frame is always left out of every encode scheme I've tried.

Honeyko
13th January 2008, 23:55
BUG: Auto Crop butchers good pixel rows in order to achieve mod-8. Example: Crisp imagery with sharp divide between blackbarring and good film (i.e., no blurring) has 58 rows black bar above and 59 black bars below, for 363 good rows in a 720x480 canvas. Autocropping removes 60 from the top and 60 from the bottom.

This may (depending upon whether it's accounted for) slightly throw off aspect-ratio calculations.

Solution: Auto-crop preferences somewhere which permits the user one of three choices during auto-cropping: 1. crop to mod-8, 2. crop black only and encode slower if no mod-8 factor. 3. enlarge picture to next mod-8 factor during encoding. -- For the film above, 1 results in a 360 height encode without altering the pixel grid of the source; 2 results in a 363 height slower encode without altering the pixel grid of the source; 3. results in a 368 height encode as fast as 1 but which does alter the pixel grid of the source.

delacroixp
14th January 2008, 04:05
BUG: Auto Crop butchers good pixel rows in order to achieve mod-8. Example: Crisp imagery with sharp divide between blackbarring and good film (i.e., no blurring) has 58 rows black bar above and 59 black bars below, for 363 good rows in a 720x480 canvas. Autocropping removes 60 from the top and 60 from the bottom.

As far as I know MOD 2 is mandatory for cropping and MOD 8 is mandatory for width and height according to X264 specs. MOD 16, for width and height, by contrast, is merely beneficial to you as the user (In other words cropping should be [58 and 60] or [58 and 58] leaving 362 or 364... neither of which is MOD 8).
I guess there is no solution without a little lateral thinking (http://www.edwdebono.com/debono/lateral.htm).

The original movie was perfect... any transcoding involves a butchery of sorts.
Cropping without resizing is a logistical nightmare most of the time. Autocrop is inherently stuck between a rock and a very hard place. Of course, if there was an automatic preview system (http://forum.doom9.org/showthread.php?p=969913#post969913) showing AutoMKV's recommendation... the user could then take it from there.

Manual cropping should be used for complicated situations where the user has overiding preferences.


:):devil::D
Pascal


ps
I think MOD 8 affects time, quality and filesize.

Aylwin
14th January 2008, 07:44
the dll should be in your syswow32

when automkv say this message it also say the full path

please report here

thanks

BHH
The error message doesn't provide the full path. Attached is the screenshot.

http://cal-family.org/files/error.jpg

So where's the syswow32 folder?

buzzqw
14th January 2008, 08:43
@Honeyko

in next beta i added the possibility to do manual crop AND not manual resize. So you select the crops, but automkv will decide width/height according to ar

If, after encoding is completed, there should insufficient space on the destination volume to copy/mux the x264 video and audio files together into the chosen container, the string process will simply quit without any explanation. (I assume everything inside the Temp folder is "kosher" for manual muxing at such a point.)

i can lend you some spare gb :p

anyway in temp folder there are not to much "big" junk.. just audio and video files, other files are just some kb...

BUG?: I have a test film clip whose VOB is 300 frames long at 29.97. (It is de-telecined to 240 frames during automatic processing.) The clip includes a gradual fade to black during the mid-section, and about fifty or sixty frames after that are just solid black; however, the very last frame, #300, is of a new, non-blank scene. -- This clearly non-progressive frame is always left out of every encode scheme I've tried.

i think it's a B frame lag problem... try disabling b frames at all
(don't know...)

BHH

Honeyko
14th January 2008, 12:31
As far as I know MOD 2 is mandatory for croppingBUG: If odd numbers are entered, encoding proceeds, but the process eventually stalls without explanation. The user should either be warned, or odd numbers incremented to the next even (or whatever is done in AutoGK, where odd numbers are accepted).Of course, if there was an automatic preview system (http://forum.doom9.org/showthread.php?p=969913#post969913) showing AutoMKV's recommendation... the user could then take it from there.IMO, any such scheme that doesn't incorporate high-level zooming to the pixel-by-pixel level is not very useful for the user desiring to retain as much of the picture as possible, because it's virtually impossible to eyeball it otherwise. I.e., he'll either forfeit too much, or leave in some black. (I'd love see see an encoding tool permit me to bypass the tedious step of playing, screen-snapping, zooming it up in a picture viewer, and counting rows and columns. -- It's up there on my wish-list.)

==//==

@Honeyko
in next beta i added the possibility to do manual crop AND not manual resize. So you select the crops, but automkv will decide width/height....Neat! Thanks. I am really like the pace of development here -- several new betas in as many days. (Still looking for a decent "100%" setting that idiots like me can just pick. So far, High Performance w/filter LEM(ff="""HQDN3D(3)""",flem="""Removegrain(mode=2)""") and "100% quality" selected in Advanced selected yields very nice results, but the files are as big as the original VOBs (including black bars), so there's still work to be done)If, after encoding is completed, there should insufficient space on the destination volume to copy/mux the x264 video and audio files together into the chosen container, the string process will simply quit without any explanation.i can lend you some spare gb :p ....anyway in temp folder there are not to much "big" junk.. just audio and video files, other files are just some kb...Well, the audio and video could easily add up to three or four gigs for persons pursuing DVD5-sized output, meaning they'd need double that in order for everything to proceed. Suggestion: If space is lacking for the final mux, just move the files to be muxed into a new folder of the intended name+date, with a note added to the project's log.

buzzqw
14th January 2008, 13:17
update Automkv 0.95 beta 7
added manual crop possibility, without need to specify width/height (suggestion by Honeyko)
added par/ar/itu/anamorphic on xivd encoding (early beta)

http://www.64k.it/andres/data/a/AutoMKV095beta7.exe

LEM(ff="""HQDN3D(3)""",flem="""Removegrain(mode=2)""")

lem is a great adaptive filter!

just for your information

CRF Value for Quality Encoding = 40-(%quality_percent%/4)
so 100% = 40 -(100/4) = CRF 15 an overkill!
i suggest 88% = 40-22=18

Suggestion: If space is lacking for the final mux, just move the files to be muxed into a new folder of the intended name+date, with a note added to the project's log.

sorry pal.. where move ?

BHH

delacroixp
14th January 2008, 13:59
IMO, any such scheme that doesn't incorporate high-level zooming to the pixel-by-pixel level is not very useful for the user desiring to retain as much of the picture as possible, because it's virtually impossible to eyeball it otherwise. I.e., he'll either forfeit too much, or leave in some black.
(I'ld love (to) see an encoding tool permit me to bypass the tedious step of playing, screen-snapping, zooming it up in a picture viewer, and counting rows and columns. -- It's up there on my wish-list.)

I feel your pain... in PAL country we have 576 rows compared to your 480 !
Each row for you is gold-dust... you hardly want to crop more than is absolutely necessary.


:):devil::D
Pascal

zacoz
14th January 2008, 14:03
I'm guessing Honeyko means move the final video, audio & subtitle component files out of the temp directory into a directory with the name of the intended output filename.

e.g. intended output file name was TopGear.mkv (in d:\output directory) so instead of having each of the component files remain in d:\output\temp\*.* (along with other processing remnants) they are instead moved into d:\output\topgear 2008-01-14\*.* with note in log saying "Out of Disk Space. Files moved ready for manual muxing to alternate drive.".

Just guessing though :)

buzzqw
14th January 2008, 14:09
automkv don't delete temp folder.. so files are already here.. for muxing (there is even a muxing.bat!)

BHH

valnar
14th January 2008, 15:06
automkv don't delete temp folder.. so files are already here.. for muxing (there is even a muxing.bat!)

BHH

I would be nice to have the temp folder include *another* folder with the temp files for that particular encode. I sometimes have 3 or 4 videos in the same folder, and if I choose to keep the temp files, they all get thrown in the same temp directory. Or maybe not even create a "temp" folder for the encode, but create a folder entitled "temp-<name-of-video>" instead.

ie.
Let's say I have two AVI files I want to reencode to .MKV

C:\VIDEO\video1.avi
C:\VIDEO\video2.avi

Instead of C:\video\TEMP

do

C:\Video\TEMP-video1
C:\Video\TEMP-video2

or something like that....

Robert

Honeyko
14th January 2008, 19:45
lem is a great adaptive filter!Yeah; it's about the only one I can use on "Dragonslayer" that doesn't suck. Man, is that print *dirty*....just for your information
CRF Value for Quality Encoding = 40-(%quality_percent%/4)
so 100% = 40 -(100/4) = CRF 15 an overkill!
i suggest 88% = 40-22=18Thanks. I'll try that. (Although that's a lot of calculation for idiots like me who are used to just bapping 100% in AutoGK and getting XviDs that are about 60% size of original VOB. (I've had to explore new utilities because of the increasingly prevalence of really dirty prints--have people no shame?)
Suggestion: If space is lacking for the final mux, just move the files to be muxed into a new folder of the intended name+date, with a note added to the project's log.sorry pal.. where move ?Let's say my project space is volume Z: on my network. AutoMKV's temp directory is therefore Z/temp, and the destination Z itself. If I'm crunching a DVD9 from 8gb to 4.3gb, that means I'll need close to 9gb free space for the final mux. Often I don't have that at the moment the encode is complete, and the list process stops, leaving the completed raw x264 video file and audio files inside the Temp folder. ***PROBLEM***: If I had a queue list, and the next project starts, it'd wipe out the files in the Temp directory and destroy hours of work. Therefore, if final muxing is not possible due to space, then just move the files to the destination if the Temp directory and the destination are on the same volume (ideally they would go inside of a new AutoMKV-generated directory, and I would mux them manually later). I.e., if the eventual filename was going to be XYZ, then the generated directory name would be XYZ(date-time).

Honeyko
14th January 2008, 19:56
I feel your pain... in PAL country we have 576 rows compared to your 480! Each row for you is gold-dust... you hardly want to crop more than is absolutely necessary.Most of the time, it's not that bad because even though many film DVDs are advertised as anamorphic, they aren't FULLY anamorphic in the sense that the full vertical height of the format is used to encode picture. In such cases, a PAL DVD simply contains thicker black bars than an NTSC, and is encoded at 8000kbps rather than 9000. (Region2 PAL video quality may be further reduced if there are several language audio tracks taking space as opposed to only English tracks on the NTSC Region1. Ripping video from region1s and combining it with audio from other regions is something I like to do.)

Honeyko
14th January 2008, 20:02
IMO, (hints) should stay "perma-popped" as long as you're mouse-hovering over the right pixels.

Buzz? You *ROCK*!

Thanks, mucho....

--//--

Follow-up bug: If you check a box for something after looking at its pop-up hint, you cannot get the hint to appear again.

Honeyko
14th January 2008, 20:15
Minor BUG: There's no pop-up hint for "[ ] Specify Quality"
(This might be a good place for that 88% suggestion.)

Suggestions for Manual Crop:

1. There are two boxes at the top of the relevant area, one called "Use Manual Crop/Resize", and another to its right called "Manual Crop". Neither have pop-up hints, and it'll be confusing to the n00b which one to select.

2. The auto-entered numbers in "Specify Width/Height" do not change as manual crop values are entered. If the user does not change them, then his encode will be bloated. For instance, if I'm working with an NTSC DVD, it'll start at 720x480; and if I crop 60 top and 60 bottom (to shave black bars), the output would stretched vertically. Solution: Width and height numbers are automatically adjusted as crop values are changed. (They can then be manually adjusted further by the user after that.)

buzzqw
14th January 2008, 20:16
@Aylwin

i will try to build a new beta tomorrow
stay tuned

@Honeyko

ok.. i understud space issue.. i will try something

BHH

Honeyko
14th January 2008, 20:28
@Honeyko;
ok.. i understud space issue.. i will try somethingEnabling multiple destination volumes is another possibility.

ryc0203
14th January 2008, 20:33
AutoMKV 0.95 beta 5 mux ac3 the original avi even when I select mp3 and as a second audio track none the Virtualdubmod mux ac3 the original and mp3 in avi

If delete audio ac3 with Virtualdubmod size is the expected

:confused:

buzzqw
14th January 2008, 20:44
@ryc0203

ops.. thanks!

will be fixed in next beta!

BHH

Honeyko
14th January 2008, 21:01
Is there a way to force-background all processes?

I am scared to death of having something pop to the foreground when I am typing or mouse-clicking. "Q" will abort encodes in various command-line windows, and mouse-clicks on buttons are obviously bad depending upon the button accidentally hit.

Honeyko
14th January 2008, 21:58
#7....

HUGE BUG: For files using the .avi container, AutoMKV is now (always?) overwriting same-name .avi files in the destination directory --without warning-- instead of giving new encodes of that name a (datestamp)+name like it does with .mkv files. ;-P (A pre-existing "(name).mpg" text-file will also be appended to, rather than a new, unique text-file written. This occurs regardless of container format chosen.)

--//--

Bug: The last item in the Queue list does not disappear when everything is finished, and the "Start Queue" button is the only button available on the lower-right of the Basic Settings window ("Start Encoding" is grayed-out). Yep: ALL settings get hosed!

This will result in other weird behavior, such as the "Specify Quality" box becoming unchecked, but the "Specify Bitrate" box remaining invisible. (The only way to get rid of the weirdness is to close and re-launch AutoMKV.)

....a "Reload Saved Settings" button would be a very handy addition to the Basic Settings window.

--//--

Minor bug/annoyance: Whenever a different container or codec is selected is selected, "Profile" always defaults back to 2-Pass.

Minor bug/annoyance: Whenever a different file is selected to encode, if "NONE" was previously selected for audio-track 1, it will change to select a track. (If not caught, this will add audio-encoding time to "test-run" projects.)

Solution: Profile, Audio-track, and various other bits should not change when a new file, container or codec is selected -- unless the combination would result in "illegal" output.

--//--

Bug: Items in the Queue Job list do not highlight in WinXP(32). Edit Queue is also busted (if selected, all Basic and Advanced settings are reset to default, and otherwise nothing happens).

--//--

Minor annoyance: The "Open AutoMKV" links on the bottom of the General settings window, and the Paypal button, are easy to accidentally click (exacerbated by any automatic foregrounding), bringing up the user's default browser -- which he might have turned off with good reason during encodes. (In my case, it'll launch my really piggy Firefox with forty extensions, which inconveniently bumps me into using virtual-ram)

Solution: Move these items into a new "About AutoMKV" tab.

Honeyko
14th January 2008, 22:27
Bug: If one's saved settings include a Manual Resize/Recrop (Advanced Settings), when AutoMKV is relaunched, the Set Width Resolution (Basic Settings) is no longer grayed-out. (Set Width otherwise grays-out when Manual Resize is selected.) If Autocrop is selected and saved as a setting, when AutoMKV is relaunched, it will remain selected but Resize Filter will be defaulted back to None. ....These may prevent encoding in some circumstances.

buzzqw
14th January 2008, 22:37
HUGE BUG: For files using the .avi container, AutoMKV is now (always?) overwriting same-name .avi files in the destination directory --without warning-- instead of giving new encodes of that name a (datestamp)+name like it does with .mkv files. ;

already fixed in next beta

.a "Reload Saved Settings" button would be a very handy addition to the Basic Settings window.

the better,close automkv.. or use load configuration in advanced settings

qeque=pita ... don't promise anything

Minor bug/annoyance: Whenever a different container or codec is selected is selected, "Profile" always defaults back to 2-Pass.
Minor bug/annoyance: Whenever a different file is selected to encode, if "NONE" was previously selected for audio-track 1, it will change to select a track. (If not caught, this will add audio-encoding time to "test-run" projects.)
it's wanted. i will not change it

Minor annoyance: The "Open AutoMKV" links on the bottom of the General settings window, and the Paypal button, are easy to accidentally click (exacerbated by any automatic foregrounding), bringing up the user's default browser -- which he might have turned off with good reason during encodes. (In my case, it'll launch my really piggy Firefox with forty extensions, which inconveniently bumps me into using virtual-ram)
... not so easy.. and the payapl button should be clicked more often ;)

Bug: If one's saved settings include a Manual Resize/Recrop (Advanced Settings), when AutoMKV is relaunched, the Set Width Resolution (Basic Settings) is no longer grayed-out. (Set Width otherwise grays-out when Manual Resize is selected.) If Autocrop is selected and saved as a setting, when AutoMKV is relaunched, it will remain selected but Resize Filter will be defaulted back to None. ....These may prevent encoding in some circumstances.

i will check

thanks again !

BHH

Honeyko
14th January 2008, 23:01
BUG: All anamorphic settings appear to be non-functional if Manual Crop/Resize is selected. (At least I couldn't generate any differences in files when any combination of "[ ]Anamorphic Encoding", "Force Muxing AR" or "Force Mux W*H" were checked or altered.) Tested with avi/xvid clip, 720x480 source manually cropped 58 top, 60 bottom, Specify Width / Height of 720x368.

Honeyko
14th January 2008, 23:09
@Honeyko;
ok.. i understud space issue.. i will try somethingEnabling multiple destination volumes is another possibility.
Desirable feature: "[ ] No final muxing" Advanced setting. (When chosen, it will simply move fully-rendered audio and video files into a new destination directory of whatever date+name would have been given to a muxed file.

Rationale: Many times (in fact, most of the time) I'll have separately-rendered audio and subtitle files I need to include. In such cases, removing final muxing eliminates a lot of wasted time, especially when there are many queued projects.

delacroixp
15th January 2008, 00:31
I'm guessing Honeyko means move the final video, audio & subtitle component files out of the temp directory into a directory with the name of the intended output filename.

Let's face it... if 1 job can't complete muxing due to a lack of space, you probably shouldn't be queing even more jobs.
That said, you probably could assign a different destination drive for each job (if you have many drives with little space on each).


I would be nice to have the temp folder include *another* folder with the temp files for that particular encode. I sometimes have 3 or 4 videos in the same folder, and if I choose to keep the temp files, they all get thrown in the same temp directory.
Or maybe not even create a "temp" folder for the encode, but create a folder entitled "temp-<name-of-video>" instead.

Dr DivX uses this kind of strategy... one Temp folder but 1 subfolder for each job.
AutoMKV originally had a system of 'OUTPUT follows INPUT'... in other words, a temp directory in each INPUT folder.


Therefore, if final muxing is not possible due to space, then just move the files to the destination if the Temp directory and the destination are on the same volume (ideally they would go inside of a new AutoMKV-generated directory, and I would mux them manually later).
I.e., if the eventual filename was going to be XYZ, then the generated directory name would be XYZ(date-time).
I guess you and Zacob have both raised a very valid encoding practice... to completely separate each job by default, regardless of disk space issues.
Single jobs can always use the same folder, job_00 while batch jobs could continue up the ladder job_01, job_02, etc.
This will certainly guarantee that the temp folders do, in fact, get deleted... after passing their sell-by dates.

*** EDIT ***
Dr DivX had all it's temp files hidden away under "Documents and Settings" and only the final muxed file would 'appear' in your Destination Folder. Originally, there was no tool like DivXMux GUI (http://www.kamiwa.de/node/4/) and you simply redid the whole job.
AutoMKV is far less automated and more hands-on... I'm sure that user's will notice that 100 GB's of disk space has dissapeared after some serious batching... and a bit of cleaning up is necessary.


Most of the time, it's not that bad because even though many film DVDs are advertised as anamorphic, they aren't FULLY anamorphic in the sense that the full vertical height of the format is used to encode picture. In such cases, a PAL DVD simply contains thicker black bars than an NTSC, and is encoded at 8000kbps rather than 9000. (Region2 PAL video quality may be further reduced if there are several language audio tracks taking space as opposed to only English tracks on the NTSC Region1. Ripping video from region1s and combining it with audio from other regions is something I like to do.)
Interesting... so it's only the true 16:9 movies that really suffer most in NTSC land.
Good point about the audio... 1 track is almost insignificent but movies like The Lion King (http://en.wikipedia.org/wiki/The_Lion_King#Home_video_and_DVD_release) have a whole string of different language tracks... DTS can also load the DVD.


:):devil::D
Pascal

Honeyko
15th January 2008, 00:46
Cropping/anamorphic tests with b7:

TEST baseline settings:
- Disk Settings (Don't Care About Size)
- Profile: 1pass High Performance
- Filter: LEM
- x264/mkv
- Input = 2.35:1 image letterboxed on 720x480 DAR 16x9 VOBs
- Manual crop: 58 top, 60 bottom*
- Specify Width / Heigth 720x368
- Specify Quality 88%
(*"Select Width Resolution" automatically grays out; "Resize Filters" stays at NONE.)

TEST1 ....no other settings selected (other than NONE audio)
....yields 720x362 file with DAR of 532x362 (i.e., conforming to 3:2 AR of NTSC source as extrapolated from cropped height).

TEST2 ...."[ ]Anamorphic Encoding" box checked.
....yields 720x362 file with DAR of 643x362 (i.e., 16x9)

TEST3 ....unchecked Manual Crop. "Select Width Resolution" to AutoCrop. Recheck Manual Crop (re-enter same numbers; "Select Width Resolution" re-grays-out; "Resize Filter" remains); Anamorphic box checked.
....yields 720x368 (desired) with DAR of 872x368 (wrong; manually measured DAR of original source was 853x363 prior to cropping, or 2.3498:1; cropping an extra row for 853x362 should yield 2.3536 AR, and then a DAR of 867x368 when resized. 872 is thus wrong with either 363 or 362 height arithmetic. ...is AutoMKV unnecessarily rounding up to a mod8 number for DAR?)

TEST4 ....as above, but unchecked Anamorphic Encoding and selected Force Muxing AR of 2.35
....yields 720x368 with DAR of 720x368

TEST5 ....as above, but Anamorphic Encoding and selected Force Muxing AR of 2.35 are both checked
....yields 720x368 with DAR of 866x368, which is within one pixel of what I expected.


Bug Fix: If Manual Resize/Crop is selected, force a default Resize filter selection if none has already been previously selected.

Honeyko
15th January 2008, 00:53
Interesting... so it's only the true 16:9 movies that really suffer most in NTSC land.Actually the PALs still usually suffer the worst, because a full-frame 576-height PAL image requires a lot more gigabytes than the 480-height NTSC image -- and the manufacturers don't usually give it to them. In fact, the VOBs are often exactly the same size, and bit-rate for the PAL reduced even further (I've seen them as low as 4000), and that's quite infuriating if they're not utilizing the full space of a DVD9 in either case.

It's not a problem with 16x9 cartoon-movies, but when you're talking about "El Cid" or "Doctor Zhivago", you can really smell the suck.

valnar
15th January 2008, 01:00
Cropping/anamorphic tests with b7:

TEST baseline settings:
- Disk Settings (Don't Care About Size)
- Profile: 1pass High Performance
- Filter: LEM
- x264/mkv
- Input = 2.35:1 image letterboxed on 720x480 DAR 16x9 VOBs
- Manual crop: 58 top, 60 bottom*
- Specify Width / Heigth 720x368
- Specify Quality 88%
(*"Select Width Resolution" automatically grays out; "Resize Filters" stays at NONE.)

TEST1 ....no other settings selected (other than NONE audio)
....yields 720x362 file with DAR of 532x362 (i.e., conforming to 3:2 AR of NTSC source as extrapolated from cropped height).

TEST2 ...."[ ]Anamorphic Encoding" box checked.
....yields 720x362 file with DAR of 643x362 (i.e., 16x9)

TEST3 ....unchecked Manual Crop. "Select Width Resolution" to AutoCrop. Recheck Manual Crop (re-enter same numbers; "Select Width Resolution" re-grays-out; "Resize Filter" remains); Anamorphic box checked.
....yields 720x368 (desired) with DAR of 872x368 (wrong; manually measured DAR of original source was 853x363 prior to cropping, or 2.3498:1; cropping an extra row for 853x362 should yield 2.3536 AR, and then a DAR of 867x368 when resized. 872 is thus wrong with either 363 or 362 height arithmetic. ...is AutoMKV unnecessarily rounding up to a mod8 number for DAR?)

TEST4 ....as above, but unchecked Anamorphic Encoding and selected Force Muxing AR of 2.35
....yields 720x368 with DAR of 720x368

TEST5 ....as above, but Anamorphic Encoding and selected Force Muxing AR of 2.35 are both checked
....yields 720x368 with DAR of 866x368, which is within one pixel of what I expected.


Bug Fix: If Manual Resize/Crop is selected, force a default Resize filter selection if none has already been previously selected.

Wow am I confused. I hope Buzz got all this. This is why I leave all the math to you guys.... Perhaps it's just best I stay away from anamorphic. 1:1 is simple to me. As long as AutoMKV does the AR correct for me. :)

Robert

BlackDog21
15th January 2008, 01:27
I get a Windows Script Host error against file mkvmaudio_pip.vbs line 2 char 1 when trying to encode an xvid copying original audio. It then prompts to say "Audio wasn't encoded properly. After 120 seconds AutoMKV will go ahead without audio. Should I quit?"

delacroixp
15th January 2008, 03:03
TEST3 ....853x362 should yield 2.3536 AR, and then a DAR of 867x368 when resized.

Well, actually 853x362 yields a DAR of 2.35635



TEST5 ....as above, but Anamorphic Encoding and selected Force Muxing AR of 2.35 are both checked
....yields 720x368 with DAR of 866x368, which is within one pixel of what I expected.

If you now enter the 4-decimal 2.3564 you would get a DAResolution of 867x368

2.4 - - - AR gives 883
2.36 - - AR gives 868
2.356 -- AR gives 867
2.3564 - AR gives 867.2



:):devil::D
Pascal

delacroixp
15th January 2008, 03:50
Actually the PALs still usually suffer the worst, because a full-frame 576-height PAL image requires a lot more gigabytes than the 480-height NTSC image -- and the manufacturers don't usually give it to them. In fact, the VOBs are often exactly the same size, and bit-rate for the PAL reduced even further (I've seen them as low as 4000), and that's quite infuriating if they're not utilizing the full space of a DVD9 in either case.

It's not a problem with 16x9 cartoon-movies, but when you're talking about "El Cid" or "Doctor Zhivago", you can really smell the suck.
I'm not sure if old movies are a good example since El Cid (http://en.wikipedia.org/wiki/El_Cid_(film)) and Dr Zhivago (http://en.wikipedia.org/wiki/Doctor_Zhivago_(1965_film)) are both wide-angle movies, produced a decade after the First anamorphic movie (http://en.wikipedia.org/wiki/The_Robe_%28film%29) in 1953. The overall resolution or detail is so low that high bitrates are probably unnecessary.
I noticed that The Great Escape (1963) (http://en.wikipedia.org/wiki/The_Great_Escape_%28film%29) was, in fact, released in "4:3 wideangle" which is probably as much an indictment of the poor quality as it is to the total running time of 172 minutes.

I've updated my original post on Settings (http://forum.doom9.org/showthread.php?p=1086655#post1086655) and Band of Brothers (2001) (http://en.wikipedia.org/wiki/Band_of_Brothers) is my alltime Extreme movie.
At 800x448, Q20 it produces my highest 'BPP = 0.2 kbps Per Pixel' and also the highest 'Bitrate = 1800 kbps'.
It's a true 16:9 movie series but perhaps the totally digital production method also goes a long way in explaining the high figures.
(Many of my movies at similar settings produce a BPP = 0.15 or less and a Bitrate = 1000 or less)
Strictly speaking, a wide-angle, low-res movie like The Lord of the Rings (http://en.wikipedia.org/wiki/The_Lord_of_the_Rings_film_trilogy) 720x432, 311 kp (BoB (http://en.wikipedia.org/wiki/Band_of_Brothers) 720x576, 415 kp)should also have a high BPP eventhough the avg bitrate is quite low.
I haven't encoded many new movies recently... so I'm still checking !

Of course, my list includes a lot of older movies... 80's, 70's and 60's (Zorba the Greek (http://en.wikipedia.org/wiki/Zorba_the_Greek) [B&W]) where X264 excels in crunching very small.
I havn't encoded any movies (anamorphic or otherwise) from the 50's and I'm still looking for one of my alltime favourite... Nicholas and Alexandra (http://en.wikipedia.org/wiki/Nicholas_and_Alexandra).


:):devil::D
Pascal

Honeyko
15th January 2008, 08:19
I'm not sure if old movies are a good example since El Cid (http://en.wikipedia.org/wiki/El_Cid_(film)) and Dr Zhivago (http://en.wikipedia.org/wiki/Doctor_Zhivago_(1965_film)) are both wide-angle movies, produced a decade after the First anamorphic movie (http://en.wikipedia.org/wiki/The_Robe_%28film%29) in 1953.Whether a movie was actually filmed in Cinemascope (anamorphic) is irrelevant to whether or not its DVD video could be anamorphically encoded. (Just about any widescreen feature benefits.)The overall resolution or detail is so low that high bitrates are probably unnecessary.Don't believe it; many of those older epics were shot on 70mm, and were stunning in the theater. A cleaned-up print, treated right, would blow the socks off many modern pretenders in terms of quality.

Most old movies look terrible on DVD because their DVDs were often the first DVDs made (because the films were famous). You generally have to wait around for a restoration print.

buzzqw
15th January 2008, 09:04
update beta 8 http://www.64k.it/andres/data/a/AutoMKV095beta8.exe

fixed problem of overwriting on avi output
fixed problem of muxing even original audio file
fixed problem of save settings AND manual crop and resize

EDIT: at all Vista Users : please report any problem with libsndfile-1.dll

about manual crop and resize AND anamorphic... i cannot guarantee the perfect fuctions, moreover resize must be not NONE

for any check between automkv par/dar and correct values i suggest to test againt megui or http://somestuff.org/resizeCalc.php

thanks

BHH

delacroixp
15th January 2008, 11:28
Whether a movie was actually filmed in Cinemascope (anamorphic) is irrelevant to whether or not its DVD video could be anamorphically encoded. (Just about any widescreen feature benefits.)
Sure... I just meant that any 2.35 (very) wideangle movie like Lord of the Rings uses only 311 kp (720x432) instead of the full 415 kp (720x576) for 16:9 PAL movies.
That's 25% fewer pixels per frame... a lower bitrate of 5 or even 4 Mbps may not actually be so low after all.
Many of the older movies when the anamorphic format got going, were shot at 2.35 AR (a super wideangle to beat 4:3 TV).
It's just a shame that PAL released 2.35 movies have all that black matte. It would have been nice if they had used all the area and then expanded to 1360x576 DAR (bitrate would probably be a very real problem).



Don't believe it; many of those older epics were shot on 70mm, and were stunning in the theater. A cleaned-up print, treated right, would blow the socks off many modern pretenders in terms of quality.

Most old movies look terrible on DVD because their DVDs were often the first DVDs made (because the films were famous). You generally have to wait around for a restoration print.
I think you're right... I gather that most film was destroyed or badly neglected... leaving poor transfer material for DVD.
Any modern film shot on 35mm film and digitally transferred to DVD would look great, let alone 70mm film which has 2.5 times more real-estate.
Imagine IMAX (http://en.wikipedia.org/wiki/IMAX) which uses a 70mm film that has almost 10 times more area than 35mm film.

It's the ravages of time which has done most harm to old film.


:):devil::D:
Pascal

zacoz
15th January 2008, 16:23
Just tried out Beta 8 and although correct 16:9 AR detected in source by dgindex the muxing.bat was generated to use 5:4.
I can't see where it indicates it in the log, but "Force Muxing AR" was left at default of "Automatic". "Force PAR in avs" was also left at default "AUTO" setting.

23:02:19 0.95 beta 8 - - - - - - - - - - - - - START JOBS - - - - - - - - - - - - - -
23:02:19 OS Version: Windows XP
23:02:19 Selected Input file: D:\Capture\CSI 723 The Good, the Bad, and the Dominatrix.m2v
23:02:19 Selected Output dir: D:\Capture\temp\
23:02:19 Selected Final Name: CSI 723 The Good, the Bad, and the Dominatrix
23:02:19 Selected Container type: MKV
23:02:19 Selected Encoder: X264
23:02:19 Selected Size: Unlimited File Size
23:02:19 Selected Profile: Constant_Quality.xml
23:02:19 Selected Resizer: NONE / Original
23:02:19 Selected Filters: LEM(ff="""HQDN3D(3)""",flem="""Removegrain(mode=2)""")
23:02:19 Selected Deinterlacer: AUTO
23:02:19 Selected Field Order: AUTO
23:02:19 Enabled Constant Quality With Unlimited Size (Q 22)
23:02:19 Track Language 1: D:\Capture\CSI 723 The Good, the Bad, and the Dominatrix.mp2
23:02:19 Audio Codec 1: Nero AAC
23:02:19 Audio Quality 1: 0.35
23:02:19 Audio Channel 1: Stereo
23:02:19 Track Language 2: NONE
23:02:19 Audio Codec 2: Nero AAC
23:02:19 Movie title Name: CSI 723 The Good, the Bad, and the Dominatrix
23:02:19 Advanced Audio Settings DUMP Track 1
23:02:19 Audio Track Language: eng
23:02:19 Nero Option Profiles: AUTO --- Encoding Mode: Quality
23:02:19 CCT Option Profiles: AUTO --- Channel Options: AUTO
23:02:19 Lame Settings: ABR
23:02:19 Audio Normalization: 1
23:02:19 Frequency: AUTO --- Tempo: NONE --- Pitch: NONE --- Other Add:
23:02:19 Selected Unlimited media size
23:02:19 Dgindex CMD: E:\AutoMKV95b\exe\dgindex\dgindex.exe -FO=0 -OM=1 -YR=2 -AIF=[D:\Capture\CSI 723 The Good, the Bad, and the Dominatrix.m2v] -OF=[D:\Capture\temp\movie] -exit -minimize
23:02:59 Encoding D:\Capture\temp\CSI 723 The Good, the Bad, and the Dominatrix.mp2 to NeroAAC with 0.35 quality
23:05:42 Encoded 1' Audio Track: 35819416 bytes
23:05:45 Number of Frames: 62020
23:05:45 Framerate: 25.000000
23:05:45 Movie length in Seconds: 2481
23:05:45 Movie Width/Height: 720/576
23:05:45 DgIndex AR: 16:9
23:07:17 Source is declared tff by a margin of 17/17.
23:07:17 Advanced Deinterlace Routines Log
23:07:17 Analyzed 333 sections of five frames
23:07:17 Found Interlace Sections: 0 0.00%
23:07:17 Found Progressive Sections:333 100.00%
23:07:17 Found Telecined Sections: 0 0.00%
23:07:17 Found Zero Mov: 100.00% 333
23:07:17 Found One Mov: 0.00% 0
23:07:17 Found Two Mov: 0.00% 0
23:07:17 Found Three Mov: 0.00% 0
23:07:17 Found Four Mov: 0.00% 0
23:07:17 Found Five Mov: 0.00% 0
23:07:17 The Movie is declared to progressive
23:07:17 Starting X264
23:07:17 CRF encoding X264: E:\AutoMKV95b\exe\encoder\x264.exe --pass 1 --crf 22 --stats "D:\Capture\temp\.stats" --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --mixed-refs --trellis 1 --ref 3 --filter -2,-1 --direct auto --vbv-maxrate 25000 --me umh --no-ssim --level 4.1 --weightb --b-pyramid --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8,p4x4 --8x8dct --threads auto --thread-input --sar 1:1 --output "D:\Capture\temp\movie.264" "D:\Capture\temp\movie.avs"
01:01:55 X264 Final CRF Encoding Stats:
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX MMXEXT SSE SSE2 SSE3 SSSE3 Cache64
x264 [info]: slice I:810 Avg QP:20.35 size: 26081
x264 [info]: slice P:22730 Avg QP:22.40 size: 9146
x264 [info]: slice B:38480 Avg QP:23.97 size: 2375
x264 [info]: mb I I16..4: 28.7% 44.7% 26.6%
x264 [info]: mb P I16..4: 8.4% 12.4% 2.2% P16..4: 28.8% 10.9% 4.2% 0.8% 0.5% skip:31.7%
x264 [info]: mb B I16..4: 0.3% 0.9% 0.2% B16..8: 16.8% 0.8% 1.5% direct: 5.4% skip:74.2%
x264 [info]: 8x8 transform intra:53.5% inter:46.6%
x264 [info]: direct mvs spatial:99.6% temporal:0.4%
x264 [info]: ref P 70.7% 19.6% 9.7%
x264 [info]: ref B 77.7% 16.1% 6.2%
x264 [info]: kb/s:1033.2
01:01:55 Accepted values are between 697303040 and 741343232 bytes (movie+audio)
01:01:55 Got a file of size: 320438336 bytes + audio size 35819416 bytes (356257760)
01:01:55 Only Movie Size: 320438336 bytes
01:01:55 "E:\AutoMKV95b\exe\matroska\mkvmerge.exe" -o "D:\Capture\temp\CSI 723 The Good, the Bad, and the Dominatrix.mkv" --default-duration 0:25000/1000fps --track-name -1:"CSI 723 The Good, the Bad, and the Dominatrix" --aspect-ratio 0:1.250000 "D:\Capture\temp\movie.264" --language -1:eng --default-track -1:yes "D:\Capture\temp\CSI 723 The Good, the Bad, and the Dominatrix.mp4" --title "CSI 723 The Good, the Bad, and the Dominatrix"
01:02:41 Final Muxed size: 356937248 bytes
01:02:41 Encoding finished: 01:55:24 elapsed time
01:02:41 -----------------------------------------------------------------------
01:02:41 Script AutoCrop.log
01:02:41
01:02:41 Crop(2,0,716,576)
01:02:41 -----------------------------------------------------------------------
01:02:41 Script movie.avs
01:02:41
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\AddGrain.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\autocrop.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\aWarpSharp(Pruned).dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\blockbuster.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\cnr2.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\ColorMatrix.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\Convolution3D.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\corrector.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\DctFilter.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\Decomb.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\Deen.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\degrainmedian.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\DGDecode.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\EEDI2.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\FFMpegSource.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\FFT3DFilter.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\FluxSmooth.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\frfun7.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\hqdn3d.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\LeakKernelDeint.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\MaskTools.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\medianblur.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\MipSmooth.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\MSharpen.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\mt_masktools.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\mvtools.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\NicAudio.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\RemoveGrainS.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\RepairS.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\SangNom.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\SimpleResize.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\SoundOut.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\TBilateral.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\TDeint.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\TIVTC.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\TomsMoComp.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\TTempSmooth.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\UnDot.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\UnFilter.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\VSFilter.dll")
01:02:41 LoadPlugin("E:\AutoMKV95b\exe\filter\warpsharp.dll")
01:02:41 #loadpluginstart
01:02:41
01:02:41 #test1
01:02:41
01:02:41 Import("E:\AutoMKV95b\exe\filter\BlindDeHalo3_mt2.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\Deblock_QED_MT2.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\FastLineDarken 1.3 MT MOD.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\HybridFuPP.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\LanczosPlus.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\Lem.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\LimitedSharpenFaster.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\MCBob_v03c.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\mvbob.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\QMlib.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\seesaw.avsi")
01:02:41 Import("E:\AutoMKV95b\exe\filter\spresso.avsi")
01:02:41 #importstart
01:02:41
01:02:41 #test2
01:02:41
01:02:41 movie = mpeg2source("D:\Capture\temp\movie.d2v")
01:02:41 function getOrder(clip c) {
01:02:41 order = GetParity(c) ? 1 : 0
01:02:41 Return order }
01:02:41 #filter1start
01:02:41
01:02:41 #test3
01:02:41
01:02:41 last = movie
01:02:41 fixed_aspect = 1.767824
01:02:41 out_width = 720
01:02:41 out_height = 576
01:02:41 #resizestart
01:02:41
01:02:41 #test4
01:02:41
01:02:41 #filter2start
01:02:41
01:02:41 #test5
01:02:41
01:02:41 LEM(ff="""HQDN3D(3)""",flem="""Removegrain(mode=2)""")
01:02:41 -----------------------------------------------------------------------
01:02:41 Script mkvmaudio.avs
01:02:41
01:02:42 LoadPlugin("E:\AutoMKV95b\exe\filter\NicAudio.dll")
01:02:42 LoadPlugin("E:\AutoMKV95b\exe\filter\SoundOut.dll")
01:02:42 LoadPlugin("E:\AutoMKV95b\exe\filter\FFmpegSource.dll")
01:02:42 NicMPG123Source("D:\Capture\temp\CSI 723 The Good, the Bad, and the Dominatrix.mp2")
01:02:42 #Applying STEREO downmixing routines
01:02:42 function stereo(clip a)
01:02:42 {
01:02:42 flr = GetChannel(a, 1, 2)
01:02:42 fcc = GetChannel(a, 3)
01:02:42 lfe = GetChannel(a, 4)
01:02:42 lfc = MixAudio(fcc, lfe, 0.2071, 0.2071)
01:02:42 mix = MergeChannels(lfc, lfc)
01:02:42 lrc = MixAudio(flr, mix, 0.2929, 1.0)
01:02:42 blr = GetChannel(a, 5, 6)
01:02:42 Return MixAudio(lrc, blr, 1.0, 0.2929)
01:02:42 }
01:02:42 #
01:02:42 6==Audiochannels() ? stereo() : last
01:02:42 function addvideo(clip c) {
01:02:42 blankclip(length = Int(100 * AudioLengthF(c) / float(audiorate(c))), fps=100)
01:02:42 Return audiodub(last,c)
01:02:42 }
01:02:42 Normalize()
01:02:42
01:02:42 Soundout(output="cmd",type=1,format=3,autoclose=true,executable="E:\AutoMKV95b\exe\besweet\neroaacenc.exe",prefilename=" -ignorelength -q 0.35 -if - -of audio.mp4",postfilename="",nofilename=true,showoutput=false)
01:02:42
01:02:42 - - - - - - - - - - - - FINISHED JOBS - - - - - - - - - - - - - - - - -

buzzqw
15th January 2008, 16:50
i must admit that my knowledge abot dar/par are quite limited.. so i have replicated the same things (no crop, 16/9 input) on MeGui...

and the muxing string is this

[NoImage] Job commandline: "mkvmerge.exe" -o "muxed.mkv" --aspect-ratio 0:5/4 -A -S "_aaa.mkv" -a 1 -D -S "aaa T01 3_2ch 384Kbps DELAY 0ms.m4a" --no-clusters-in-meta-seek

so.. :confused: is MeGui wrong ?

.. remember that you haven't applied any crop..

BHH

zacoz
15th January 2008, 17:11
i must admit that my knowledge abot dar/par are quite limited..
My knowledge is about 1/10th of limited (or less). :confused: Easily fixed at any rate, I just amended muxing.bat and re-ran it :) Just thought I'd report it in case it was a bug.

I haven't the faintest where the 5/4 comes from or how you'd work out automatically that it should still be 16:9. I'm guessing though that if as is the case here, using original width with no manual cropping then auto PAR / AR should result in a 16/9 mux.

But then I don't even qualify for n00b status in this stuff. :stupid:

valnar
15th January 2008, 18:07
Buzz,

Just a heads up in case you weren't following the thread.....

Will you add or modify the profiles in AutoMKV to coincide with the final recommendations from this thread?

http://forum.doom9.org/showthread.php?p=1087511

Thanks, Robert

buzzqw
15th January 2008, 20:17
in the ps3 profile i have already removed b-pyramid

other profiles should be ok already.. maybe the insane have a number of ref very high

BHH

Aylwin
15th January 2008, 22:47
EDIT: at all Vista Users : please report any problem with libsndfile-1.dll
The error message is better as it tells the full path of where the file should be. However, it fails to place the file in c:\windows\syswow32. The folder doesn't exist. If I create the folder manually then the file is successfully copied there.

But why have the file in c:\windows\syswow32 in the first place? Why can't it be in c:\windows\system32? At least that's how it seems to be with 0.93a.

Would it be possible have the file placed in c:\windows\system32? That way, there's no change from previous versions and users don't have to manually create this new folder.

Honeyko
15th January 2008, 23:08
It's just a shame that PAL released 2.35 movies have all that black matte. It would have been nice if they had used all the area and then expanded to 1360x576 DAR (bitrate would probably be a very real problem).
It shouldn't be, as only 720x576 worth of real pixels are being pushed -- the rest is just player software anamorphic zooming.