AutoMKV 0.93a - (DVD/TS/AVI/AVS to X264/XviD/WVC1 into MKV/MP4/WMV) update 30/12/2007

[buzzqw]

Did you understand the problem that no matter what rate you load in a profile, if you check the "Use This Profile" (perhaps you changed the v_keydist) the rate gets multiplied by 1024. If you don't check this, it does not get multiplied by 1024 ??

to correct this i had divided in profiles by 1000 the v_bitrate
Es. from <v_bitrate>512000</v_bitrate> to <v_bitrate>512</v_bitrate>
i hadn't change the code, this value will be multiplied by 1024 in final script

Are you inviting me to do that instead of you, or in addition, or what?

i had already done, BUT i would like if can suggest/build more correct profiles

Everything I did with movie.avs and movie_wmv.bat was AFTER the encoding stalled and I terminated the WME script command window

please look at time.avs: is avisource or directshowsource in use ?
also: is frame.txt created ?

x264.exe just starts idling when about 10% is encoded

this issue is related to you pc AND x264.exe, try disabling Antivirus/firewall

tell me any progress!

BHH

[dlflannery]

@buzzqw:

What you have done with the Zune profiles sounds good to me. Only after I test them would I possibly have any changes to suggest. Thanks!

I can create the .xml files based on your posts, or should I wait for the next version, in case there are other things you changed, not mentioned in your posts?

Regarding the 1024 bitrate factor, are you saying no code change is needed beyond 74e -- just using 512 instead of 512000 in the xml profile?

[buzzqw]

I can create the .xml files based on your posts, or should I wait for the next version, in case there are other things you changed, not mentioned in your posts?

sounds good to me... tomorrow i will pm you with a direct link to new WMV ZUNE profile package.
Do your best on changing/fixing these profiles !

Regarding the 1024 bitrate factor, are you saying no code change is needed beyond 74e -- just using 512 instead of 512000 in the xml profile?

YES! since i multiply by 1000 there is no need to write 512000

BHH

[dlflannery]

Originally Posted by buzzqw

.....please look at time.avs: is avisource or directshowsource in use ?
also: is frame.txt created ?
BHH

time.avs uses avisource.

frame.txt has this:
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1
3143 30.000000 320 240 1

[dlflannery]

@buzzqw
I edited the Zune_1pass_quick profile to 512 for bitrate (instead of 512000). This prevents the huge numbers, as you said it would. However there are still some minor problems that you might want to fix in the next release:

I have saved this profile in my automkv.ini file. If I start the program and go to the Advanced profile Editing tab, the command line window will have some odd number (like 128000) for the v_bitrate. If I click Reload Profile the number changes to 512000. If I then check Use this Profile the number changes to 524288 (= 512000 * 1.024). If I encode before checking Use this Profile the bitrate passed to the encoder will by 512000. After checking it, the bitrate passed is 524288.

Shouldn't the command line window and the number passed to the encoder be identical for all these conditions?

If I set the bitrate up to 600 on the Advanced Settings tab, the value used for encoding is 624400 (i.e., 600000 * 1.024). Looks like 1000 is used in some cases and 1024 in others.

These are minor inconsistencies -- no significant difference in the encoding result -- just confusing to the operator.

I'll look forward to your PM regarding the new profiles.

Regards and thanks.

[dlflannery]

I modified the Zune_2_pass profile as follows:

1. v_bitrate at 512 instead of 512000
2. v_peakbitrate at 736000 instead of 1500000

I used 64kpbs audio so the total peak bit rate should have been 800 kbps or less.

The encoded .wmv had a peak bitrate (mediaInfo says) of 1.2 Mbps! Looking at the options file for the WME command line script indicates that the v_mode option should be 4 (instead of 3 now used) if the peak bitrate is going to be limited by the v_peakbitrate option.

So I further modified the profile by using 4 for v_mode. However the command line passed to the script now was missing several things:
1. v_codec
2. v_bitrate
3 v_mode
and the encoding was not good -- single pass very low bitrate.

So I modified movie_wmv.bat by adding these options:
-v_codec WMV8
-v_bitrate 512000
-v_mode 4
The encoding went OK and the result .wmv was good. MediaInfo said the peak bitrate was 736 kbps, as desired, and the file synched to the Zune device without forced re-encoding and played fine. It looks like some code changes will be needed to implement this 2-pass VBR WMV8 profile, since apparently the code removed three needed parameters from the encoder command line options when I set the v_mode to 4 in the profile XML file (???). Also, probably should use 64_44_2 for the audio option instead of 128_44_2.

I repeated but with v_bitrate set to 400. All OK and the clip played fine on the Zune device with no noticeable quality loss compared to 512 bitrate. The file size was reduced to 85% of what it was at 512. My interest in 2-pass started recently when an OP PM'ed me they were having blocks in fast motion portions using the 1-pass CBR profile. I would guess with peak bitrate allowed up to 736 kbps, the blocks would be removed even at only 400 kbps average rate. (I've never had blocks but none of my test videos have enough rapid motion, I guess.)

[buzzqw]

@dlflannery

check your pm

thanks!

BHH

[dlflannery]

Originally Posted by buzzqw

@dlflannery
check your pm
thanks!
BHH

Got the profiles and test program. The Zune 2 pass profile tests good! Got the same file length (within 6 bytes) that I got with my modified movie_wvm.bat before, and the specs per mediaInfo are identical. Plays good on Zune device and does not require re-encoding on synch. With this profile (and any WMV7 or WMV8 VBR mode 4) the audio bitrate should be limited to 64kbps. Is there a way to have the program enforce that?

I will test the other Zune profiles but I looked at them and they seem correct.

I still see the command line v_bitrate jumping up by factor of 1.024 when I check "Use this Profile" (??).

Looks good so far! Thanks!

[glynor]

Originally Posted by buzzqw

@dlflannery
@glynor
i prefer not to do hack... expecially due on quickcrapplayer bugs... , BUT go on advenced settings, click on last avs string and add: AssumeFPS(30000,1001) or AssumeFPS(24000,1001)
BHH

Thanks. I can certainly understand you not wanting to do a hack for Apple's incompetent software.

Unfortunately, I tried out using the AssumeFPS(30000,1001) and it still doesn't work. The results are somewhat better, but still no good (I now don't get an error message, and the audio plays, but the video is black in Quicktime Player). I've tried a wide variety of settings and profiles, including limiting the output bitrate to 600 and the width to 320). Interestingly, when I include the AssumeFPS(30000,1001) line with a 29.970 FPS source, the resulting MP4 I get is 29.971 FPS, but I no longer get the error message in QTPlayer, just the black video window.

The main reason I need to be able to support Quicktime Player is that I have a lot of people I produce content for that use Macs. VLC is available for OSX and works, but I can't force people to install and use additional software...

Also, a lot of people I know in other forums have expressed interest in using AutoMKV to produce iPod compatible MP4s, but I can't get this to work well either. If I select the PD-iPod 5.5G.xml profile with basically any encoding settings, I get this:



The vanilla PD-iPod.xml profile appears to work, but I still get no video playback in Quicktime (which makes me think it's not gonna work on an actual iPod either, though I don't have one available to test right this second).

Anyone have any further ideas? I've searched for the past two hours around the forums but haven't come up with much...

[buzzqw]

i have an idea of what search around... but i first MUST (and i dislike) install quicktime player

BHH

[glynor]

Originally Posted by buzzqw

i have an idea of what search around... but i first MUST (and i dislike) install quicktime player

Can't say I blame you there!

My office is about 70% mac users, so I don't have much choice to support them. I like Quicktime on the Mac honestly, but for Windows I certainly prefer the alternative...

[Shark_jlc]

I already had DVDFab Decrypter installed, so I grabbed the AutoMKV build that did not have it.

When I run AutoMKV, it appears to not detect my installation of DVDFab Decrypter and DGIndex just kinda... sits there.

Also, a clean way to cancel an encode would be nice.

Thanks for the tool!

[dlflannery]

I've tested all three 2-pass Zune profiles. No problems were seen. Peak bitrates reported by mediaInfo are 736kbps for WMV7 and WMV8 and 1.5 Mbps for WMV9. All files synched without re-encoding to my Zune device and played fine. It may have been my imagination but I actually thought I could detect the slight quality differences.

I happened to find a strange problem. Just before one encoding I was curious about what resizers were available so I pulled down the Resize Filter menu. I didn't change the filter from the Simple Resize that is normally there. However the encoding called the WMCmd script twice. The first time was very short, then the second time produced the output file which was OK. Here is part of the log file:

22:43:03 Autoresize CMD: cscript.exe "C:\AutoMKV074\exe\encoder\WMCmd.vbs" -input "C:\Video\ForZune\temp\resmovie.avs" -output "C:\Video\ForZune\temp\resmovie.wmv" -v_codec WMV7 -v_mode 2 -v_quality 85 -s_config "C:\Video\ForZune\temp\wmv_crb" -v_bframedist 1 -v_dquantoption 2 -v_lookahead 0 -v_mbmodecost 0 -v_mmatch 0 -v_mslevel 1 -v_msrange 0 -v_mvcoding 1 -v_mvcost 0 -v_peakbitrate 736000 -v_bdeltaqp 1 -a_codec WMASTD -a_mode 0 -title "Bf2passQktest" -year 2007 -copyright "Done with AutoMKV! 0.74e" -a_setting 64_44_2
22:43:24 Tested total movie: 5%
22:43:24 AutoResize movie size: 392706 bytes
22:43:24 Movie Width suggested: 51136 value based on sample size (14527.27% of original width)
22:43:24 WMV CMD: cscript.exe "C:\AutoMKV074\exe\encoder\WMCmd.vbs" -input "C:\Video\ForZune\temp\movie.avs" -output "C:\Video\ForZune\temp\movie.wmv" -v_codec WMV7 -v_mode 4 -v_bitrate 512000 -s_config "C:\Video\ForZune\temp\wmv_crb" -v_bframedist 1 -v_dquantoption 2 -v_lookahead 0 -v_mbmodecost 0 -v_mmatch 0 -v_mslevel 1 -v_msrange 0 -v_mvcoding 1 -v_mvcost 0 -v_peakbitrate 736000 -v_bdeltaqp 1 -a_codec WMASTD -a_mode 0 -title "Bf2passQktest" -year 2007 -copyright "Done with AutoMKV! 0.74e" -a_setting 64_44_2
22:45:13 Final Muxed size: 10646474 bytes

Only after pulling down the resizer choices (not changing) is the first call to WMCmd.vbs made. (???)

[cosmos]

Originally Posted by Shark_jlc

I already had DVDFab Decrypter installed, so I grabbed the AutoMKV build that did not have it.

When I run AutoMKV, it appears to not detect my installation of DVDFab Decrypter and DGIndex just kinda... sits there.

Doesn't work that way actually: the no-fab version of AutoMKV is not for those who have fab installed, but rather for those who due to legal constraints would be in violation of local law if fab was downloaded... Plus AutoMKV needs a specific version of fab decrypter, one which understands command line switches.

Bottomline: just download the "full" version (and do make sure that in your first rip with the automkv's embedded fab you answer "no" to the "fab updated version found; update?" prompt)

[buzzqw]

@cosmos

thanks, good answer!

thanks ! (wow... someone can answer at automkv questions... and it isn't me !!! )

@dlflannery

automkv will dinamically parse value in its box... so it will wait till a choice is made (even if encoding is started)

BHH

[buzzqw]

@glynor

.... something strange is around..

i have done some test (Quicktime profile and no "hack" at all):
with PAL material: ok audio and ok video
with FILM material: after TIVTC (so 23.9xx framerate) it is OK video and audio

with quicktime player 7.1.3.100 (for windows)

link to a playable (for me...) mp4 done with automkv



BHH

[cosmos]

Originally Posted by buzzqw

@cosmos

thanks, good answer!

thanks ! (wow... someone can answer at automkv questions... and it isn't me !!! )

You have thrown so much effort into maintaining AutoMKV and answering questions around, that I really feel I have to return something as well Just our appreciation for all the work you've done for a great piece of software

[SeeMoreDigital]

Hi glynor,

If you want MPEG-4 AVC encodes to be QuickTime player 7 compatible, you will have to edit the "CE-QuickTime.xml" file. You need to change the default number of B-frames from "1" to "0". And only encode using "2Ch" AAC audio.

QT7 will then be able to save the .MP4 file to .MOV

Please note: This is not an issue with AutoMKV... it's been around for a year or so.


Cheers

[dlflannery]

Originally Posted by buzzqw

@dlflannery
automkv will dinamically parse value in its box... so it will wait till a choice is made (even if encoding is started)
BHH

The encoding is set up identically in two cases but in one case the extra run of WMCmd.vbs occurs. The only difference was in one case I pulled down the Resize Filter menu to look at the choices but did not change the filter choice from what it already was. This was done before starting encoding. This does not seem logical to me. What is the first short run doing?

[buzzqw]

the extra run could be due to AUTORESIZE, if you leave width=AUTO , automkv will try to define the better width (and so more wvm to run)

BHH