AutoMKV 0.95c - (DVD/TS/AVI/AVS to X264/XviD/WVC1 into MKV/MP4/WMV) update 12/02/2008

[zacoz]

@Zow
Try removing the language setting (--language -1:esp) from the command line in muxing.bat and see if it works.

[buzzqw]

@Amed

that's strange automkv write automkv.ini only when save setting is pressed...

@Gruelius
I dunno if this is a bug or my stupidity but hwen i select "Autocrop only" in the width resolution listbox it still resizes the film.
for keeping best ar. you can manually crop (using the manual crop on advanced settings, then set NONE as resize in main panel)

@zacoz @Zow

good suggestion!

BHH

[zacoz]

@buzzqw

Gone back and looked at Zow's previous post (http://forum.doom9.org/showthread.php?p=1097010#post1097010) with the log and it also had the esp language setting in the mkvmerge command line.

Where does AutoMKV source the language from for this, as the audio advanced options is the only place I can see a language selection but esp isn't in the list?

If esp is supposed to be spanish then it should be "spa" or "es" I believe to be accepted by mkvmerge.

[buzzqw]

automkv don't internally "translate" esp to spa... it simply keep the first three letters (espana -> esp).

I will add an exception for this (as for finnish->suo, japan ->jpn ...)

BHH

[zacoz]

Some positive feedback :)

Just processed a capture of 4:3 movie broadcast in 16:9 (black bars on left and right). I applied a manual crop to remove bars and some noise at the top, and specified a desired width, leaving AutoMKV to decide on height, SAR & DAR.

Perfect results both with and without anamorphic encode selected. :cool:

Thanks for all the work with AR and such on 0.95 :thanks:

[buzzqw]

thanks zacoz, it's was an hard work. Mainly because i don't knew what doing ;)

i will soon publish the 0.95b with varius fixes.

the next beta (0.96) will be focused on wmv, BUT if someone don't fix the avs2asf on audio part... i am lost :(

i'am also waiting for some feedback from DivX, i will love to add support to DivX codec by using CLI.exe (as in Dr.DivX) interface

BHH

[Tirade]

At roughly what point does diminishing returns kick in with CRF? I started with a 4.7GB DVD Rip of Fantastic 4 16X9

1st transcode - 2 pass better CQ90 - size 1.23GB
2nd transcode - CRF 16 - size 1.65GB
3rd transcode - CRF 10 - size 3.07GB


Ive done about 10 encodes on 2 PC's over the last 3 days trying to iron out a solid setting before batch transcoding all my DVD's.

I removed b-pyramid and removed p4X4mv for DXVA compatibility (thx valnar)

This is my current command line:

--pass 1 --crf 14 --stats "C:\Movies\Fantastic 4\FANTASTIC FOUR 169\VIDEO_TS\.stats" --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --mixed-refs --trellis 1 --ref 3 --filter -2,-1 --subme 6 --direct auto --vbv-maxrate 14000 --me umh --level 3.1 --weightb --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --threads auto --thread-input --aq-strength 0.50 --aq-sensitivity 13 --no-dct-decimate --sar 1:1


I'm using auto-crop and anamorphic encoding on 16X9 sources.

Is there anything big I'm missing? Trying to iron out these last few details is tough because I'm starting to get lost. I'm not sure what resize filter I should be using on my auto crop stuff and I'm not sure if I should be using the RemoveGrain(mode=2) filter that is enabled by default. Is there a good source that explains these filters and also a good source for explaining the results of different CRF values?

[buzzqw]

crf 14 is a little overkill, even 16 should produce a near trasparent quality

i will you a sharp resizer, stick with lanczos or spline36, and ermovegrain(mode=2) cannot damage your source, so use it without doubt

i will remove i4x4, not a big deal leaving it. and maybe.. rainse bframes to 4 ... try with this settings, just for fun :)

BHH

[Zow]

automkv don't internally "translate" esp to spa... it simply keep the first three letters (espana -> esp).

I will add an exception for this (as for finnish->suo, japan ->jpn ...)

BHH

Thanks, zacoz and buzzqw. Sorry about the attachments, it looked like they approved them right away, but I guess not.

Is there something I can manually edit now, or should I just wait for the next version (which is O.K., I am not in a terrible hurry?)

[buzzqw]

edit the muxing.bat and substitute esp for spa

next time, when working on ifo , hit advanced audio buttons and select language here

anyway will be fixed in next update (wait some days)

BHH

[Tirade]

i will remove i4x4, not a big deal leaving it. and maybe.. rainse bframes to 6 ... try with this settings, just for fun :)

BHH

Is raising the bframes to 6 going to cause a compatibility issue with DXVA?

I saw this thread and I am curious.

http://forum.doom9.org/showthread.php?t=132924

[Taddeusz]

@buzzqw

I think I have an idea what's going on with some of the videos with subtitles. I've discovered that the VOB that came out correctly has exactly the same PTS for it's audio and video. The VOB where the subtitles display at the incorrect times the PTS values are slightly different between the audio and the video. Somehow I believe this causes AutoMKV to display subtitles at the wrong time.

[buzzqw]

@Tirade

you are right! thanks

i have edited my post


@Taddeusz

The VOB where the subtitles display at the incorrect times the PTS values are slightly different between the audio and the video. Somehow I believe this causes AutoMKV to display subtitles at the wrong time.

just to be precise: automkv use dgindex to create the d2v, and the audio delay is fixed at muxing/encoding time

BUT subtitles are ripped as is, and muxed as is.

The time of display subs(idx/sub) are inside the .idx, and automkv will not touch this file.

So i suppose something is wrong on subripping (pgc/vts/angle/chain...). I must say that often when i need subs (rarely needed) i subrip previusly, check the timing, then add as external subtitle

BHH

[Crono141]

thanks zacoz, it's was an hard work. Mainly because i don't knew what doing ;)

i will soon publish the 0.95b with varius fixes.

the next beta (0.96) will be focused on wmv, BUT if someone don't fix the avs2asf on audio part... i am lost :(

i'am also waiting for some feedback from DivX, i will love to add support to DivX codec by using CLI.exe (as in Dr.DivX) interface

BHH

Any idea when you'll have the .96 build ready? The software has great potential to be my one-stop video conversion utility. There's literally nothing out there that reliably and easily converts to WMV.

I'm not trying to be demanding, so sorry if I come across that way. I was just curious if your a few days away from release, or a few weeks or months.

Thanks again for the nice software.

[darbid]

It is not the first time I have written here. i am trying the same m2ts file from a backedup copy of Worlds End - AVC and AC3

1 I am demuxing with elecard
2. mux the .avc file into a ts stream (does not work otherwise)
Then loading both files into Automkv. For the sound I am just choosing keep original.

23:08:50 0.95 beta 21 - - - - - - - - - - - - - START JOBS - - - - - - - - - - - - - -
23:08:50 Selected Input file: E:\DVD\elcard\mux.ts
23:08:50 Selected Output dir: E:\DVD\elcard\temp\
23:08:50 Selected Final Name: mux
23:08:50 Selected Container type: MKV
23:08:50 Selected Encoder: X264
23:08:50 Selected Size: 1 CD / 1
23:08:50 Selected Profile: 1_Pass_Fastest.xml
23:08:50 Selected Resizer: SimpleResize (neutral soft) / Automatic
23:08:50 Selected Filters: RemoveGrain(mode=2)
23:08:50 Selected Deinterlacer: AUTO
23:08:50 Selected Field Order: AUTO
23:08:50 Manual Crop: Enabled
23:08:50 Left Crop: 0
23:08:50 Top Crop: 0
23:08:50 Right Crop: 0
23:08:50 Botton Crop: 0
23:08:50 Manual Width: 1280
23:08:50 Manual Height: 720
23:08:50 Enabled CRF/CQ AutoRes at 18 value
23:08:50 Track Language 1: E:\DVD\elcard\00001_audio1.ac3
23:08:50 Audio Codec 1: Copy Original
23:08:50 Track Language 2: NONE
23:08:50 Audio Codec 2: Nero AAC
23:08:50 Enabled Use DirectShowSource for AUDIO and VIDEO
23:08:50 Activate use ProjectX
23:08:50
23:08:55 Number of Frames: 2876
23:08:55 Framerate: 23.976044
23:08:55 Movie length in Seconds: 120
23:08:55 Movie Width/Height: 1920/1080
23:10:49 Source is declared tff by a margin of 1/0.
23:10:49 Advanced Deinterlace Routines Log
23:10:49 Analyzed 572 sections of five frames
23:10:49 Found Interlace Sections: 0 0.00%
23:10:49 Found Progressive Sections:572 100.00%
23:10:49 Found Telecined Sections: 0 0.00%
23:10:49 Found Zero Mov: 100.00% 572
23:10:49 Found One Mov: 0.00% 0
23:10:49 Found Two Mov: 0.00% 0
23:10:49 Found Three Mov: 0.00% 0
23:10:49 Found Four Mov: 0.00% 0
23:10:49 Found Five Mov: 0.00% 0
23:10:49 The Movie is declared to progressive
23:10:49 Encoded 1' Audio Track: -2 bytes
23:10:49 Unable to encode Audio, try piping with FFmpeg!
23:13:34 Unable to encode Audio even piping from FFmpeg!

[Honeyko]

SUGGESTION (because no other utility has it):

Ability to open an audio file (any of those currently supported) and re-time it by entering in a desired time-length in hhh:mm:ss:mmm format.

-- This will resolve the annoyance of some audio tracks still being out of the sync after using the PAL>NTSC (or vice-versa) presets found in other applications. (And by "out of sync", I don't mean "it just needs a delay factor"; I mean it's still too fast or too slow.)

(General audio messin' around without it being part of a video project would be a fantastic addition.)

[Atak_Snajpera]

General audio messin' around without it being part of a video project would be a fantastic addition

I think I will be able to write that app. It should be quite easy. Do you transcode only to AC3 or to other format?

[Don_Genaro]

I think I found two bugs in automkv0.95a:

When using Constant Quality profile to hit a target size... the audio gets encoded to audio.mp4 but the application then looks for a %movie_name.mp4 and it doesn´t find it, then it starts to encode the audio again with ffmpeg and once again the audio doesn´t get noticed.

Then the avs script for the movie instead of the original width it places "ORIGINAL" on the value, so avisynths complains about not knowing what to do with "ORIGINAL".

:thanks:

I really like automkv! hope it will continue to getting better and better.

Suggestion: A feauture that lets you choose the final output size based on a percentage of the original file size. Example: One wants to encode a xvid file to x264 but to a 70% of it´s original size.

[Honeyko]

General audio messin' around without it being part of a video project would be a fantastic additionI think I will be able to write that app. It should be quite easy. Do you transcode only to AC3 or to other format?It doesn't matter, actually, since once the stuff is properly retimed, I can use BeSweet, et al, to convert it to any other format. Of course the more input/output choices there are, the more convenient the utility becomes.

Note that (1) retiming to the millisecond and (2) cutting/splicing are about the only things BeSweetGUI doesn't do, so those are the things I'm most interested in.

[Honeyko]

Suggestion: A feauture that lets you choose the final output size based on a percentage of the original file size. Example: One wants to encode a xvid file to x264 but to a 70% of it´s original size.Already built in: Take original file size and multiply by 0.7; enter value in Disk Settings after selecting a 2-pass profile.

[Encoder888]

@buzzqw

I'm experiencing a huge final mux size difference in this version, compared to 0.93. I encoded a movie with original Constant Quality @ 18 default quantitizer and AQ settings 15 for sensitivity and 8 for strength and original resolution / no filters, which is very high quality. In 0.93 the final file size of that movie was around 3GB. Using the EXACT same settings, with 0.95 I get a final size of 3.4GB. I can't even detect a difference in quality, so where did the extra 400MB come from?

Actually, the only difference is that in 0.95 I check the "Anamorphic Encoding", because in 0.93 it does it automatically even if you don't check it and in 0.95 you have to check it, but I don't think that affects final size in any way.

Anyone else experience the same problem? I mean, I heard that the AQ in this version cannot be disabled, but I used it in both, so it's not that... So what is it? Any ideas?

I have the complete codes from both versions, let me know if you need to see them and I'll post them...

[thomaspf]

I recently installed autoMKV 0.95a but I can't seem to get beyond the startup.

It hangs there with a message

"Parsing profiles"

I saw that the same question was asked on the 0.93 thread but I could not find an answer there how to fix this condition.

Cheers

Thomas

[buzzqw]

@Crono141

first beta of 0.96 maybe appear at end month, then will be the beta testing... (if my soon don't decide to born early..., my wife it's already at 8 month)

@darbid

could you please PM me a link where to download a sample ?

@Honeyko

audio file could be already encoded without need of a video.. just feed the audio file as input

and in advanced audio settings there is already the possibility to stretch audio

@Don_Genaro

post your log

@Encoder888

substitute the x264 build ...

@thomaspf
need some info
1) in what folder have you un-rarred the automkv_full file ?
2) what os ?
3) have you installed all needed files ?

BHH

[Don_Genaro]

@Don_Genaro

post your log



05:31:17 0.95a - - - - - - - - - - - - - START JOBS - - - - - - - - - - - - - -
05:31:17 OS Version: Windows XP
05:31:17 Selected Input file: F:\Case\some_movie.avi
05:31:17 Selected Output dir: F:\Case\temp\
05:31:17 Selected Final Name: some_movie
05:31:17 Selected Container type: MKV
05:31:17 Selected Encoder: X264
05:31:17 Selected Size: 1150 / 1
05:31:17 Selected Profile: Constant_Quality.xml
05:31:17 Selected Resizer: NONE / Original
05:31:17 Selected Filters: RemoveGrain(mode=2)
05:31:17 Selected Deinterlacer: NONE
05:31:17 Selected Field Order: AUTO
05:31:17 Enabled Constant Quality With Fixed Size (Q 21)
05:31:17 Using Queue: queue0.ini of 1 works
05:31:17 Track Language 1: some_movie.avi
05:31:17 Audio Codec 1: Nero AAC
05:31:17 Audio Quality 1: 0.40
05:31:17 Audio Channel 1: Stereo
05:31:17 Track Language 2: NONE
05:31:17 Audio Codec 2: Nero AAC
05:31:17 Advanced Audio Settings DUMP Track 1
05:31:17 Nero Option Profiles: AUTO --- Encoding Mode: Quality
05:31:17 CCT Option Profiles: AUTO --- Channel Options: AUTO
05:31:17 Lame Settings: ABR
05:31:17 Audio Normalization: 1
05:31:17 Frequency: AUTO --- Tempo: NONE --- Pitch: NONE --- Other Add:
05:31:17 Selected Hit Media Size
05:31:42 Number of Frames: 152862
05:31:42 Framerate: 29.969999
05:31:42 Movie length in Seconds: 5101
05:31:42 Movie Width/Height: 720/480
05:31:42 Encoding F:\Case\temp\some_movie.avi to NeroAAC with 0.40 quality
05:42:39 Encoded 1' Audio Track: some_movie.mp4 -1 bytes
05:42:39 Unable to encode Audio, try piping with FFmpeg!
05:42:39 NeroAACEnc doesn't accept piping from ffmpeg, switching to LibFaac at 128 kbps
05:42:39 "C:\X264GUIS\AutoMKV095_NORIP\exe\BeSweet\ffmpeg.exe" -i "F:\Case\some_movie.avi" -vn -acodec libfaac -ab 128000 -vol 256 -f aac audio1.aac
05:42:39 "C:\X264GUIS\AutoMKV095_NORIP\exe\matroska\MP4Box.exe" -new "F:\Case\temp\audio1.mp4" -add "F:\Case\temp\audio1.aac"
05:51:59 Encoded 1' Audio Track: audio1.mp4 74526264 bytes
05:52:00 Starting X264 AutoResize with WIDTH of Original and wanted size of 1205862400 bytes
05:52:00 Testing ABR of: 1767
05:52:00 CRF encoding X264: C:\X264GUIS\AutoMKV095_NORIP\exe\encoder\x264.exe --bitrate 1767 --ratetol inf --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --mixed-refs --trellis 1 --ref 3 --filter -2,-1 --subme 7 --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 "F:\Case\temp\resmovie.mp4" "F:\Case\temp\resmovie.avs"
05:52:04 CRF Iterate LOG
05:52:04 End of first Sample LOG
05:52:04 No CRF FOUND - Skipping !!! Please download a newer build of x264


and the avs script:


#test3

last = movie
fixed_aspect = 0.985994
out_width = Original
out_height = 480
#resizestart


If you replace the "Original" with a number the script works, but as it is avisynth complains about no knowing what "Original" is.

:thanks:

[zacoz]

@buzzqw

I'm experiencing a huge final mux size difference in this version, compared to 0.93. I encoded a movie with original Constant Quality @ 18 default quantitizer and AQ settings 15 for sensitivity and 8 for strength and original resolution / no filters, which is very high quality. In 0.93 the final file size of that movie was around 3GB. Using the EXACT same settings, with 0.95 I get a final size of 3.4GB. I can't even detect a difference in quality, so where did the extra 400MB come from?...
I've played around with swapping the x264.exe (r709) from AutoMKV 0.93 package into use with the AutoMKV 0.95 package (normally r736) and testing with and without aq-strength & aq-sensitivity.

0.95a using x264 r709 aq-str 0 aq-sens 0 5,687 KB
0.95a using x264 r736 aq-str 0 aq-sens 0 5,761 KB 1.3% increase
0.95a using x264 r709 aq-str 8 aq-sens 15 9,824 KB
0.95a using x264 r736 aq-str 8 aq-sens 15 11,040 KB 12.3% increase
Seems to indicate that while x264 r736 does create slightly larger files than x264 r709, the application of aq increases this difference significantly.
Personally I was hard pressed to see the visual difference for the extra 11-12%, but maybe my eyesight is failing as I get older ;)
I heard that the AQ in this version cannot be disabled
It can be disabled, just isn't by default or via the aq-strength / aq-sensitivity boxes.
If you add the following into the "Add to line" box at the bottom of the "Advanced Profiles Editing" tab, it will deactivate aq.
--aq-strength 0 --aq-sensitivity 0
Not required after 0.95b is released however - just use 0 in the respective boxes then as I understand it.

As buzzqw said "substitute the 264 build" if you don't like the output of the 736 build that comes with 0.95. I'm considering this myself.

@buzzqw
Looking forward to good reports of a healthy bouncing baby boy/girl. Your first?
At 8 months I can see an extended beta test schedule being the likely outcome, unless you draw midnight feeding duty and can't get back to sleep of course :D

[zacoz]

@Don_Genaro

Reproduced here (whether run alone or from the queue) - but have no idea what the issue is.

[Honeyko]

@Honeyko: and in advanced audio settings there is already the possibility to stretch audioUhm...where? I see some presets under the "Tempo" section of "Normalize", but nothing which would give me to-the-millisecond finesse. (I'll test the "Edit Me" after my current project gets done...I have a sneaky hunch that the BeSweet module will choke just the same way it does when non-standard preset fps numbers are entered in BeSweetGUI. We'll see....)

[Encoder888]

@buzzqw

Well, I don't wanna substitute the x264.exe with an older build, I wanna stay updated with the current version. My only question is - why the extra size ? Does the newer build increase AQ additionally, or does it increase the quantitizer quality or what?

If I encode a movie with 0.93 which uses the older build and I use AQ sensitivity 15 and strength 8 or if I encode the same movie with 0.95 and I use sensitivity 15 and strength 5, I basically get the same size, and I frankly can't tell if there's a difference in quality... I'm sure there's some sort of a difference, but I don't know what it is, is it overall, is it AQ... so I can't make up my mind... it's all so darn confusing... If I wait for 0.96, is it going to fix the extra size problem, or are all the x264 builds from now on gonna produce the extra size?

Sorry, it's just, I've been waiting for so long to find a good quality/size combination and I thought had it with 0.93 and now it's all crazy again with this size increase... Looks like there's always gonna be something wrong.

[zacoz]

@Encoder888

Thing is that the larger size issue is totally unrelated to AutoMKV. I haven't read it but this thread (http://forum.doom9.org/showthread.php?p=1076312#post1076312) might contain some of the info you're looking for.


EDIT: Not sure now after perusing thread

[Encoder888]

@zacoz

Okay, so AutoMKV 0.95 uses x264 r736. Hmm... From what I got from that post, it seems that now the defaults for AQ in r736 are 13 and 0.5, as opposed to 15 and 0.5 in the older build and that's why files made with x736 are bigger, because the sensitivity is higher. So, when I'm using the same settings for both builds, I'm actually increasing the sensitivity in the r736... (so confusing isn't it)

It's just a theory, but a good way to find out would be to test x736 (through AutoMKV 0.95) at 15 and 0.5 (so I'm decreasing sensitivity from the default) and the older one (through AutoMKV 0.93) at 13 and 0.5 (so I'm increasing sensitivity from the default) and if I get almost identical results, then I've found what the difference is - sensitivity. I don't know actually if that makes any sense whatsoever but I'll give it a shot and I'll let you know. The thing is that I thought if you change it manually it doesn't matter, but I guess the manual settings are multiplications of the default, so... I'll test and and I'll let you know. Thanks.

[zacoz]

Hmmm, after looking through the thread I linked I'm not sure if it is the AQ implementation in the r736 included in AutoMKV 0.95 or a different patched AQ also build using r736. May just be that the changed defaults are reflected in both. But I guess the change of defaults would infer that there was a change in the algorithm somewhere.

[Encoder888]

@zacoz,

I tried downloading the latest r736 x264 build from its official site (and from a few others to make sure it's always the same thing) and I copied it over the one AutoMKV 0.95 uses (it was 15-20kb bigger, so it's not exactly the same one), but it won't work... AutoMKV stops after the audio encoding is complete...

I don't know, what did you do? Did you copy the old x264 build from 0.93 or are you using the new one? I think I'm just gonna use the new one with 15 sensitivity, but I'll use lower the strength, just so I get approximately the same bit rate I used to get with 0.93... I think that's a better idea than substituting the build, because you probably don't wanna keep an old build forever.

And I'm sure the change in the new build is for the better, otherwise they wouldn't have made it so... I just hope that the extra size goes to AQ and making block areas crisper and not just to overall quality.

[hfmls]

i want to convert mkv to wmv, can u guys tell me wich profiles is the most fast/good quality ? like a a balance between quality and speed? pls

and to mp4 too please (both to play with x360)

if i use coreavc to decode mkv will the total process time be less? (trwoing things at air now)


edited

[Atak_Snajpera]

Stardust.2007.1080p.HDDVD.x264.DTS-DEFiNiTE

Let me guess... Your grandma encoded this file... ;)

[hfmls]

hm? so.. :S

[Atak_Snajpera]

You haven't read rules...

[hfmls]

i have a doubt! right?what is the problem with my source file? do i have to erase that text? if so..i will do it.

[valnar]

i have a doubt! right?what is the problem with my source file? do i have to erase that text? if so..i will do it.

Yes.


Change Stardust.2007.1080p.HDDVD.x264.DTS-DEFiNiTE to My.Pirated.Movie.2007

It'll be less obvious that way. :rolleyes:

Robert

[buzzqw]

@Don_Genaro

thanks for your log, i will look at this issue

@zacoz and Encoder888

it's a patched 736, since it include the hrd-nal/aud,vbv buffer... NOT a official one

Looking forward to good reports of a healthy bouncing baby boy/girl. Your first?
At 8 months I can see an extended beta test schedule being the likely outcome, unless you draw midnight feeding duty and can't get back to sleep of course

the first, yea, a little boy (name in english should be Edward (Edoardo in italian))
... i must admit that extended beta testing could be not avaiable or applicable... don't know.. i hope for a calm/love to sleep baby ;)

BHH

[Encoder888]

@zacoz (and everybody else)

After some testing I discovered something pretty weird in regards to the oversize of files in 0.95. I had been testing with sensitivity 15 and strength 8 and getting very different results with 0.93 and 0.95. In order to get similar results, I had to use strength 5 instead of 8 in 0.95. So, this time, I thought, I'd play with the sensitivity - and normally, as it was in 0.93, when you decrease the number, you get better sensitivity and a larger size. Well, apparently, that is NOT the case in 0.95, because I decreased it to 13 (still keeping the strength at 8), just to see what happens and I actually got a significantly smaller size, very close to what I got with 15 and 5.

To sum up - in 0.95 I got very similar results with 15 and 5 and 13 and 8. So, if you wanna increase the sensitivity in 0.95 you actually have to increase the number, not lower it. I don't know if that's a bug or if it was a bug in 0.93, which got fixed. The 15 and 5 version though looks much better, even the very block areas which would be affected by even very small sensitivity, so that's another thing to think about... I wish things were simpler.

[Tirade]

@zacoz (and everybody else)

After some testing I discovered something pretty weird in regards to the oversize of files in 0.95. I had been testing with sensitivity 15 and strength 8 and getting very different results with 0.93 and 0.95. In order to get similar results, I had to use strength 5 instead of 8 in 0.95. So, this time, I thought, I'd play with the sensitivity - and normally, as it was in 0.93, when you decrease the number, you get better sensitivity and a larger size. Well, apparently, that is NOT the case in 0.95, because I decreased it to 13 (still keeping the strength at 8), just to see what happens and I actually got a significantly smaller size, very close to what I got with 15 and 5.

To sum up - in 0.95 I got very similar results with 15 and 5 and 13 and 8. So, if you wanna increase the sensitivity in 0.95 you actually have to increase the number, not lower it. I don't know if that's a bug or if it was a bug in 0.93, which got fixed. The 15 and 5 version though looks much better, even the very block areas which would be affected by even very small sensitivity, so that's another thing to think about... I wish things were simpler.

So this would seem to be an issue with x264 build and not with AutoMKV. I think .93 and .95 used different x264 builds.

Maybe you should check other encoder threads to see if others are having this same problem. That would confirm if its x264 or AutoMKV. Maybe someone can track down DS and ask him to explain :)

[Honeyko]

BUG:

1. If source is MKV(h264/AC3) and...
2. "Use FFmpegSource" is checked in Advanced Settings, and...
3. ...source and destination are different drives...

4. The BUG: (name)mkv.ffa1cache and (name)mkv.ffv1cache files will be written on the source drive rather than in the Temp folder created on the destination drive. Quite naturally this will cause problems if the source drive is unwritable or has limited space.

Follow-up BUG:

FFmpegSource will waste a lot of time demuxing audio tracks even if NONE is selected for audio.

[thomaspf]

I recently installed autoMKV 0.95a but I can't seem to get beyond the startup.

It hangs there with a message

"Parsing profiles"

I saw that the same question was asked on the 0.93 thread but I could not find an answer there how to fix this condition.

Cheers

Thomas

@thomaspf
need some info
1) in what folder have you un-rarred the automkv_full file ?
2) what os ?
3) have you installed all needed files ?



Hi,

I started with the setup version AutoMKV-v0.95a-Setup.exe which installed everything into

C:\Program Files\AutoMKV

Since that lead to the hang with Parsing Profiles I uninstalled and reinstalled using the 15.2MB download AutoMKV095.rar and also installed that into that directory. Here is what that looks like. I am running Vista SP1 and I assume with the setup version I should have all the files I need. Unfortunately I still get the hang at startup.

Thanks for your help

Thomas

Directory of c:\Program Files\AutoMKV

2/09/2008 08:09 PM <DIR> .
2/09/2008 08:09 PM <DIR> ..
1/28/2008 05:14 PM 3,946 automkv.ita
2/05/2008 09:29 AM 72 AutoMKV.url
2/05/2008 11:54 AM 843,776 AutoMKV095.exe
6/06/2007 06:24 PM 137 AutoMKV_Wiki.url
2/24/2006 01:05 AM 69,632 AVSredirect.dll
2/05/2008 11:57 AM 84,091 Changelog.txt
2/09/2008 08:07 PM <DIR> exe
2/05/2008 11:38 AM 35,638 License.txt
2/09/2008 06:34 PM <DIR> profiles
1/28/2008 01:00 PM 3,302 tips.txt
2/09/2008 06:36 PM 85,076 uninst.exe
9 File(s) 1,125,670 bytes
4 Dir(s) 119,255,793,664 bytes free

[superdragonpoop]

I have currently only run this through the .93 build but...
I have an AC3 with a length of 20:31. When converted to MP3 it is being shortened to 19:24. Additionally when muxed the audio is in sync in the beginning, but gradually falls out of sync. At the end of the video it's about 1500ms behind.

I ran the same video/audio through AGK 2.48b. Besweet produced an audio track that was 20:31. However it also loses audio sync at the end of the video by approximately 1500ms.

It's odd that the shortened audio track still muxes (nearly) properly even though it's a full minute shorter in length. I can't explain why it's losing sync either.

I'll run this vid through the .95 build tomorrow and see if it does any better.

I'm not sure which log files would help you, but I can supply them if you think they'll help. I've only been using automkv for a couple days so I'm still picking through the logfiles to see what I can learn.

[morgankane]

Hi,

How can I manually "force" 16:9 aspect ratio?

I have couple of DVD:s which are 16:9, but for some reason autoMKV (and AGK too) allways makes 4:3 MKV from them.

I assume there is wrong aspect ratio code somewhere in DVD ifo, but I have tried edit them with bad luck.

[nanorch]

too small to be called a bug: in v0.95a the link "Open AutoMKV Thread" (english, can't access the italian one at the moment) still points to the thread for v0.93

[buzzqw]

update 0.95b http://www.64k.it/andres/data/a/AutoMKV095b.exe

changelog

0.95b 12/02/2007
ADDED: Now AutoMKV create a muxing.bat even for M2TS muxing. For hand made facilities (suggestion by survivant001)
ADDED: In case of M2TS muxing AutoMKV will compute an overhead of 6% on bitrate (suggestion by survivant001)
ADDED: M2TS Container Logo (fell free to suggest better logo)
FIXED: "Do HQ First Pass" wasn't applyed when encoding to XivD (thansk to XhmikosR)
FIXED: On log file "Enabled CRF/CQ AutoRes" wasn't displyed on case of "Specify Quality" (thanks to Honeyko)
FIXED: Double use of --sar option. Pay attention to <Sar> value in profiles (thanks to survivant001)
FIXED: Link to new 0.95 thread (thanks to nanorch)
FIXED: Clicking on "Preview" will now force "Use Manual Crop/Resize"
FIXED: Usage of AQ (previusly was always on) (thanks to zacoz)
FIXED: SPA to ESP in language (thanks to zacoz)
FIXED: Use of Constant_Quality with constrained disk settings AND Original width/height (thanks to Don_Genaro)

BHH

EDIT: link fixed

[Encoder888]

The link doesn't seem to work for me... :(

[buzzqw]

link fixed

BHH

[AMED]

using the insane profile with x264 is the --me dia meant to be there instead of --me umh on the first pass?

x264cmdq_pass1.bat"E:\AutoMKV095_NORIP\exe\encoder\x264.exe" --pass 1 --bitrate 761 --stats "E:\Movies\temp\.stats" --ref 1 --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --no-fast-pskip --filter -2,-1 --subme 2 --direct auto --vbv-maxrate 25000 --me dia --no-ssim --level 4.1 --merange 32 --b-pyramid --analyse none --threads auto --thread-input --aq-strength 0 --aq-sensitivity 0 --sar 14412009:10000000 --output NUL "E:\Movies\temp\movie.avs"

x264cmdq_pass2.bat"E:\AutoMKV095_NORIP\exe\encoder\x264.exe" --pass 2 --bitrate 761 --stats "E:\Movies\temp\.stats" --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --no-fast-pskip --mixed-refs --trellis 2 --ref 16 --filter -2,-1 --subme 6 --direct auto --vbv-maxrate 25000 --me umh --no-ssim --level 4.1 --merange 32 --weightb --b-pyramid --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8,p4x4 --8x8dct --threads auto --thread-input --aq-strength 0 --aq-sensitivity 0 --sar 14412009:10000000 --output "E:\Movies\temp\movie.264" "E:\Movies\temp\movie.avs"

AutoMKV log22:16:24 0.95b - - - - - - - - - - - - - START JOBS - - - - - - - - - - - - - -
22:16:24 OS Version: Windows XP
22:16:24 Selected Input file: E:\FullDisc\DONNIE DARKO DIRECTORS CUT\VIDEO_TS\VTS_01_0.IFO
22:16:24 Selected Output dir: E:\Movies\temp\
22:16:24 Selected Final Name: DONNIE DARKO DIRECTORS CUT
22:16:24 Selected Container type: MKV
22:16:24 Selected Encoder: X264
22:16:24 Selected Size: 1/4 DVD-R / 1
22:16:24 Selected Profile: 2_Pass_Insane_Quality.xml
22:16:24 Selected Resizer: Lanczosmtplus / Automatic
22:16:24 Selected Filters: RemoveGrain(mode=2)
22:16:24 Selected Deinterlacer: AUTO
22:16:24 Selected Field Order: AUTO
22:16:24 Enabled CRF/CQ AutoRes at 20 value
22:16:24 Activate PGC Ripping: 1
22:16:24 Track Language 1: 80: English (AC3 6ch, 0xBD 0x80) [0]
22:16:24 Audio Codec 1: Copy Original
22:16:24 Track Language 2: NONE
22:16:24 Audio Codec 2: Nero AAC
22:16:24 Activate Anamorphic Encoding
22:16:24
22:16:24 Activate PGC processing: PGC 1 [2:08:21:15]
22:16:24 Dgindex CMD: E:\AutoMKV095_NORIP\exe\dgindex\dgindex.exe -FO=0 -OM=1 -TN=80 -YR=2 -AIF=[E:\FullDisc\DONNIE DARKO DIRECTORS CUT\VIDEO_TS\VTS_01_1.vob] -OF=[E:\Movies\temp\movie] -exit -minimize
22:19:36 D2V file size: 1002802
22:19:36 Audio 1: movie t80 3_2ch 448kbps delay 0ms.ac3
22:19:36 Pre Audio 1' Size: 431287808 bytes
22:19:36 Renamed file movie t80 3_2ch 448kbps delay 0ms.ac3 to movie t80 3_2ch 448kbps delay 0ms_.ac3
22:19:36 Encoded 1' Audio Track: movie t80 3_2ch 448kbps delay 0ms_.ac3 431287808 bytes
22:19:41 Number of Frames: 192540
22:19:41 Framerate: 25.000000
22:19:41 Movie length in Seconds: 7702
22:19:41 Movie Width/Height: 720/576
22:19:41 DgIndex AR: 16:9
22:25:41 Source is declared tff by a margin of 75/73.
22:25:41 Advanced Deinterlace Routines Log
22:25:41 Analyzed 477 sections of five frames
22:25:41 Found Interlace Sections: 0 0.00%
22:25:41 Found Progressive Sections:477 100.00%
22:25:41 Found Telecined Sections: 0 0.00%
22:25:41 Found Zero Mov: 100.00% 477
22:25:41 Found One Mov: 0.00% 0
22:25:41 Found Two Mov: 0.00% 0
22:25:41 Found Three Mov: 0.00% 0
22:25:41 Found Four Mov: 0.00% 0
22:25:41 Found Five Mov: 0.00% 0
22:25:41 The Movie is declared to progressive
22:25:41 Starting X264 AutoResize with WIDTH of Automatic and wanted size of 1169162240 bytes
22:25:41 CRF encoding X264: E:\AutoMKV095_NORIP\exe\encoder\x264.exe --pass 1 --crf 20 --stats "E:\Movies\temp\.stats" --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --no-fast-pskip --mixed-refs --trellis 2 --ref 16 --filter -2,-1 --subme 6 --direct auto --vbv-maxrate 25000 --me umh --no-ssim --level 4.1 --merange 32 --weightb --b-pyramid --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8,p4x4 --8x8dct --threads auto --thread-input --aq-strength 0 --aq-sensitivity 0 --sar 14412009:10000000 --output "E:\Movies\temp\resmovie.mp4" "E:\Movies\temp\resmovie.avs"
22:55:10 Finished Autosize procedure
22:55:10 Tested total movie: 5%
22:55:10 AutoResize movie size: 38611648 bytes
22:55:10 Movie Width suggested: 1072 value based on sample size (148.89% of original width)
22:55:10 Starting X264
22:55:11 Command Line 1' Pass X264: E:\AutoMKV095_NORIP\exe\encoder\x264.exe --pass 1 --bitrate 761 --stats "E:\Movies\temp\.stats" --ref 1 --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --no-fast-pskip --filter -2,-1 --subme 2 --direct auto --vbv-maxrate 25000 --me dia --no-ssim --level 4.1 --merange 32 --b-pyramid --analyse none --threads auto --thread-input --aq-strength 0 --aq-sensitivity 0 --sar 14412009:10000000 --output NUL "E:\Movies\temp\movie.avs"
22:55:11 Command Line 2' Pass X264: E:\AutoMKV095_NORIP\exe\encoder\x264.exe --pass 2 --bitrate 761 --stats "E:\Movies\temp\.stats" --progress --keyint 250 --bframes 3 --qpmin 10 --qpmax 51 --no-psnr --no-fast-pskip --mixed-refs --trellis 2 --ref 16 --filter -2,-1 --subme 6 --direct auto --vbv-maxrate 25000 --me umh --no-ssim --level 4.1 --merange 32 --weightb --b-pyramid --b-rdo --bime --analyse p8x8,b8x8,i4x4,i8x8,p4x4 --8x8dct --threads auto --thread-input --aq-strength 0 --aq-sensitivity 0 --sar 14412009:10000000 --output "E:\Movies\temp\movie.264" "E:\Movies\temp\movie.avs"