AVCHDCoder - Blu-ray, MKV, M2TS, etc to AVCHD encoder. From input to ISO. Easy to use

[wakebrder]

True-HD will follow. Maybe next release or maybe not :)

Looks like there are no big bugs introduced in the new version so I am ready to add new features and improve features.

I think the next thing on the list will be:
-BDSup2Sup implementation.
-MP4 input
-Second audio track. (Not all formats just a couple of them: DTS/DTS, DTS/DTS-ES, DTS/AC3 640, DTS/AC3 448, DTS-ES/DTS-ES, DTS-ES/AC3 640, DTS-ES/AC3 448, AC3 640/AC3 640, AC3 640/AC3 448, AC3 448/AC3 448)

Just finished up an encode using DTS-MA with DVD-9 set as the target size. Came out at 7.56 GB. I can live with this!!

Great job!!:thanks:

[twazerty]

Just finished up an encode using DTS-MA with DVD-9 set as the target size. Came out at 7.56 GB. I can live with this!!

Great job!!:thanks:

I tested it as well and was little undersized as well. I added an extra safety barrier but I think it is not necessary. If I remove it the output size will be about 30MB-120MB larger.

[wakebrder]

I tested it as well and was little undersized as well. I added an extra safety barrier but I think it is not necessary. If I remove it the output size will be about 30MB-120MB larger.

Better a little under than over.:)

Can't wait for True-HD.:D

:thanks:

[twazerty]

Finally managed to add 64 bit encoding via bipebuf and avs2yuv. For now you have to activate it manually in the settings.

Edit: Spoke too soon. It's about twice as slow and first pass crashes at 80% on several video's.

[twazerty]

I need help with the selection of new x264 profiles.

Since x264 is changed it is time to use new profiles. This time I am adding a third speed. Slow/Fast/Very Fast

But the selection of profiles is hard to choose. I noticed that x264 has build in presets. Maybe we can use those and change them a little bit to get them right for blu-ray?

My suggestion for the Slow preset:
x264.exe --pass 1 --preset medium --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --output NUL "movie.avs"
x264.exe --pass 2 --preset slow --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --output "output.mkv" "movie.avs"

[turbojet]

My suggestions

slow (slow but helps in high compression situations):
--pass 1 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1 --b-adapt 2
--pass 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --subme 9 --me umh --ref 4 --direct auto --b-adapt 2 --trellis 2 --psy-rd 1.0:0.25 --partitions all --ipratio 1.1 --pbratio 1.1

normal (good for typical DVD5/9):
--pass 1 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1
--pass 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --me umh --direct auto --psy-rd 1.0:0.25 --ipratio 1.1 --pbratio 1.1

fast (good for BD25 output, fast but efficiency is still considered):
--pass 1 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1
--pass 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --preset fast --direct auto --ipratio 1.1 --pbratio 1.1

x264 slow/slower/placebo presets won't work with 1920x1080 because --ref 5+

[twazerty]

Thanx turbojet. I implemented them into AVCHDCoder.

There are some problems. --direct-auto doesn't work for Slow and Medium. Add had to remove it or else encoding doesn't work.

I did some testing and this are the results on a Core i7 920:
59 second sample
-----------Slow--Medium--Fast
Pass 1:----44----44-------44 seconds
Pass 2:----493---176------90 seconds
Total:-----537---220------134 seconds

The slow settings are very slow. No big deal. That is for hardcore users :P. The fast and Medium are to slow. It would be nice if Medium and Fast could be about 20% faster. Else people complain it is slower then usual. when I remove --psy-rd 1.0:0.25 at Medium it doesn't speed up.

Also some other questions. Since the very first release of AVCHDCoder there is a bitrate problem. To be more specific: The max bitrate can get to high. AVCHD can stutter on players because the bitrate is too High.

This is pass 1 of the new Medium profile:
x264.exe --pass 1 --vbv-bufsize <maxBitrate> --vbv-maxrate <maxBitrate> --bitrate <bitrate> --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1 --sar 1:1 --output NUL "input.avs"

Where:
<bitrate> is the calculated bitrate
<maxBitrate> can be: 18000 for AVCHD on DVD, 40000 for Blu-ray and 24000 for AVCHD at Stick or Custom output size.

Is this correct: --vbv-bufsize <maxBitrate> --vbv-maxrate <maxBitrate> ???

And what does the max bitrate exactly mean (Accordingly to the AVCHD specs). This:
videobitrate+audiobitrate+subtitlesbitrate
or:
videobitrate+audiobitrate+subtitlesbitrate+overhead

Support for second audio stream is almost ready. Only the graphical stuff needs to be fixed.

BTW: I have plans to make AVCHDCalculator cross platform. It is not too hard because it is a small program and that way I can learn something of Mac OS. I think I am going to make another application to generate hundreds of formulas so eventually AVCHDCalculator and AVCHDCoder support more then 2 audiotypes with lots of combinations.

Edit: I am doing a more realistic test right now at it seems the Medium speed is quite fast.

[turbojet]

x264 normal I posted is identical to the current AVCHDcoder output except for for enabling psy-trellis with --psy-rd 1.0:0.25 which is a minimal slowdown (>1% in my tests) while keeping details that are otherwise lost. Also --sar 1:1 is default so it's not really needed in x264 command line.

If --preset fast isn't as fast as you'd like maybe test out --preset veryfast it's about 50% faster but lesser quality. Also --psy-rd 1.0:0.25 can be used with --preset fast since --trellis 1, it won't have any effect with --trellis 0 which is what veryfast uses. Another option to speed up 'fast' is using --preset fast --trellis 0 the speedup won't be as much as veryfast would be but also the quality weren't be affected as much.

Your guess is as good as mine on --vbv-maxrate --vbv-bufsize and AVCHD standards. I've never seen much documentation on either. I haven't noticed and issues on a panasonic BD30 or PS3 with 24000/24000 and RipBot264 has been using it for awhile with no reports that I could see. But that also doesn't include video muxed with HD audio. My suggestion is if you can reproduce the stutter it try 18000/18000. If it still skips try lowering the bufsize to something like 9000 or so. If it still happens try using (18000 - <audio bitrate>) for maxrate/bufsize.

Oh and with slow and normal commands I posted it should be --direct auto instead of --direct-auto. I edited it.

[twazerty]

I added --sar because it is necessary for SD video's.

Now I tested with a 88 minute movie. This are the results:
------------Slow--Medium--Fast
Pass 1:-----53----53-------53 minutes
Pass 2:-----293---126------62 minutes
Total:------346---179------115 minutes
Total:------6-----3---------2 hours

The medium speed is about 30% faster as my previous Slow settings. Now it takes 3 hours instead of 4,5. The gap between Medium and Slow is Huge. It would be nice if we have a setting between Slow and Medium so people can choose better.

Now I am testing 64 bit encoding again. When second pass starts I get a strange error:
2nd pass has more frames than 1st pass (125593 vs 125592)

This is pass 1:
"pipebuf.exe" "avs2yuv.exe" "Fast DVD5 64bit.avs" -raw - : "x264.exe" --pass 1 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate 5123 --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1 --sar 1:1 --output NUL --frames 125593 - 1920x1080 : 4

and this is pass 2:
"pipebuf.exe" "avs2yuv.exe" "Fast DVD5 64bit.avs" -raw - : "x264.exe" --pass 2 --vbv-bufsize 24000 --vbv-maxrate 24000 --bitrate 5123 --level 4.1 --stats "movie.stats" --keyint 24 --min-keyint 2 --preset fast --direct auto --ipratio 1.1 --pbratio 1.1 --sar 1:1 --output "Fast DVD5 64bit.264" --frames 125593 - 1920x1080 : 4

The number of frames is requested from mediainfo:
Frame count : 125593

Is there a solution to bypass this problem?

In the next release --psy-rd 1.0:0.25 will be tweakable.

[wakebrder]

Tried another encode using DTS-MA with DVD-9 set as the target size. Came out around 11 GB. (not so good)

Maybe some more tweaking on the leaving DTS-MA untouched?

Thanks for your hard work!

[twazerty]

Tried another encode using DTS-MA with DVD-9 set as the target size. Came out around 11 GB. (not so good)

Maybe some more tweaking on the leaving DTS-MA untouched?

Thanks for your hard work!

What bitrate does mediaInfo give for the audio?
What is the filesize of the dts-hd ma file?
What is the duration of the audio? (HH:MM:SS)
And what bitrate is calculated?

Maybe I can find out what is going wrong.

Edit:

Just created a small app that generates formulas for me. Tomorrow morning I have 55 formulas. (110 times muxing)

To create formulas for 3 audiostreams in all combinations is impossible. It will take 10-thousands of muxings. For triple audio I limit it to a couple of formats. When I limit it to 5 formats I still need 1050 formulas. That are 2100 muxes. Approximately 1050*25GB = 25TB of muxing data. Even if I use smaller files it is still 13TB of muxing :)
But I think I only support 4 formats for triple audio. Still 350 formulas.
Forget the above :D

[turbojet]

With the slow settings I missed --b-adapt 2 in the first pass, I corrected it in the original post, the first pass will be very slow now but the second pass shouldn't be much slower than normal.

The time difference should be just about nothing between normal that I posted and old AVCHDcoder, are you sure you aren't using --preset medium? It uses --me hex which a considerable effieciency drop over --me umh but it does speed things up a bit. None of the presets are suitable for high quality AVCHD\BD output. The defaults (medium) is sub-par quality and slow is beyond the specs.

There isn't much you can do between normal and slow to improve quality with just a little speed decrease. --b-adapt 2 is what's slowing things way down and bringing a quality boost. --subme 9 --partitions all --me esa is about all you can do.

instead of --frames for avs2yuv try --fps 24000/1001

What I meant by --sar 1:1 being default is if you leave it out it gives a bit-for-bit identical file to if you have it in the command line, just streamlines things a bit.

[wakebrder]

What bitrate does mediaInfo give for the audio?
What is the filesize of the dts-hd ma file?
What is the duration of the audio? (HH:MM:SS)
And what bitrate is calculated?

Maybe I can find out what is going wrong.

Edit:

Just created a small app that generates formulas for me. Tomorrow morning I have 55 formulas. (110 times muxing)

To create formulas for 3 audiostreams in all combinations is impossible. It will take 10-thousands of muxings. For triple audio I limit it to a couple of formats. When I limit it to 5 formats I still need 1050 formulas. That are 2100 muxes. Approximately 1050*25GB = 25TB of muxing data. Even if I use smaller files it is still 13TB of muxing :)
But I think I only support 4 formats for triple audio. Still 350 formulas.

Just deleted to free up HDD space. :scared: I'll save logs & info next time.

[wakebrder]

Just finished a different clip. Also came out to exactly 11 GB. I had delete temp file after encode checked.:scared:

Is there any way to copy/paste log text from your program?

Or would the log file be in another location besides the temp folder?

[twazerty]

Just finished a different clip. Also came out to exactly 11 GB. I had delete temp file after encode checked.:scared:

Is there any way to copy/paste log text from your program?

Or would the log file be in another location besides the temp folder?

Ctrl+C to Copy and Ctrl+V to past it here. (Next version get Right Mouse Menu and savings to harddrive)
But without the rest of the information it is useless for this type of problem :)

Never thought file size could be useful so I add it in the next version too :D

BTW if you start conversion a second time with the same settings you can get the file sizes. When encoding starts just pause. Get the information I requested and then you can abort the process.

[wakebrder]

Ctrl+C to Copy and Ctrl+V to past it here. (Next version get Right Mouse Menu and savings to harddrive)
But without the rest of the information it is useless for this type of problem :)

Never thought file size could be useful so I add it in the next version too :D

BTW if you start conversion a second time with the same settings you can get the file sizes. When encoding starts just pause. Get the information I requested and then you can abort the process.

Here you go:

Edit:
DELETE

[twazerty]

In this case the Log isn't very useful :o
Bitrate is calculated just before encoding starts. It will also appear in AVCHDCoder and in Log. You stopped too soon;)

Wait when pass 1 is started, then hit pauze (Not abort!) and then fill in these values:
What bitrate does mediaInfo or tsMuxer give for the audio?
What is the filesize of the dts-hd ma file?
What is the duration of the audio? (HH:MM:SS): 02:14:40
And what bitrate is calculated?

For now it is the only way I can track down the problem. In my next release the above values will also be added to the Log.

[wakebrder]

In this case the Log isn't very useful :o
Bitrate is calculated just before encoding starts. It will also appear in AVCHDCoder and in Log. You stopped too soon;)

Wait when pass 1 is started, then hit pauze (Not abort!) and then fill in these values:
What bitrate does mediaInfo or tsMuxer give for the audio?
What is the filesize of the dts-hd ma file?
What is the duration of the audio? (HH:MM:SS): 02:14:40
And what bitrate is calculated?

For now it is the only way I can track down the problem. In my next release the above values will also be added to the Log.

Sorry. One more time:

13:47:06 --------Adding item---------
13:47:06 Source information: D:\Blu-ray\SB\BDMV
13:47:06 Source information: Video: 4113,H264,02:14:40,23.976,1920,1080,p
13:47:06 Source information: Audio: 4352,VBR
13:47:06 Source information: Audio: 4353,320
13:47:06 Source information: Audio: 4354,1536
13:47:06 Source information: Audio: 4355,192
13:47:06 Source information: Subs : 4608,PGS
13:47:06 Source information: Subs : 4609,PGS
13:47:06 Source information: Subs : 4610,PGS
13:47:06 Source information: Subs : 4611,PGS
13:47:06 Source information: Subs : 4612,PGS
13:47:06 Source information: Subs : 4613,PGS
13:47:06 Source information: Subs : 4614,PGS
13:47:06 Source information: Subs : 4615,PGS
13:47:06 Source information: Subs : 4616,PGS
13:47:06 Source information: Subs : 4617,PGS
13:47:06 Source information: Subs : 4618,PGS
13:47:06 Source information: Subs : 4619,PGS
13:47:06 Source information: Subs : 4620,PGS
13:47:06 Source information: Subs : 4621,PGS
13:47:06 Source information: Subs : 4622,PGS
13:47:06 Source information: Subs : 4623,PGS
13:47:06 Source information: Subs : 4624,PGS
13:47:06 Source information: Subs : 4625,PGS
13:47:06 Source information: Subs : 4626,PGS
13:47:06 Source information: Subs : 4627,PGS
13:47:06 Source information: Subs : 4628,PGS
13:47:06 Source information: Subs : 4629,PGS
13:47:06 Source information: Subs : 4630,PGS
13:47:06 Selected: Video: 4113,H264,23.976,1920,1080,p
13:47:06 Selected: Audio: 4352,VBR
13:47:06 Selected: Subs: 4612,PGS
13:47:06 Selected: Subs: 4614,PGS
13:47:06 Selected: Subs: 4615,PGS
13:47:06 Selected: Subs: 4616,PGS
13:47:06 Selected: Subs: 4619,PGS
13:47:06 Selected: Subs: 4625,PGS
13:47:06 Selected: Subs: 4627,PGS
13:47:06 Selected: Subs: 4630,PGS
13:47:06 --------Item added---------
13:47:28 --------Conversion started---------
13:47:29 Creating META file: MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
13:47:29 Creating META file: A_DTS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", track=4352, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4612, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4614, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4615, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4616, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4619, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4625, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4627, mplsFile=00001
13:47:29 Creating META file: S_HDMV/PGS, "D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts", fps=23.976, track=4630, mplsFile=00001
13:47:29 Demuxing playlist with TsMuxer: "C:\Program Files\AVCHDCoder\Tools\tsMuxeR_1.10.6\tsMuxeR.exe" "C:\Documents and Settings\Administrator\My Documents\AVCHDCoder\Temp\SB - item 1\SB2.META" "C:\Documents and Settings\Administrator\My Documents\AVCHDCoder\Temp\SB - item 1\"
14:08:22 Calculated bitrate: 7171
14:08:22 Total Subtitles size: 2.63190825E8
14:08:22 Creating AVS file: DirectShowsource("D:\Blu-ray\SB\BDMV\STREAM\00613.m2ts",fps=23.976,audio=false).ConvertToYV12().addborders(0,0,0,0)
14:08:22 Encoding Pass 1: "C:\Program Files\AVCHDCoder\Tools\X264\32bit\x264.exe" --pass 1 --bitrate 7171 --stats "C:\Documents and Settings\Administrator\My Documents\AVCHDCoder\Temp\SB - item 1\SB.stats" --level 4.1 --keyint 24 --min-keyint 2 --bframes 3 --weightb --direct auto --subme 2 --partitions none --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 9000 --vbv-maxrate 24000 --me dia --threads auto --thread-input --sar 1:1 --output NUL "C:\Documents and Settings\Administrator\My Documents\AVCHDCoder\Temp\SB - item 1\SB.avs"

[twazerty]

I See what is going wrong. The first time you tried when conversion succeeded you used a DTS-HD HR audiofile. While I was testing I also used DTS-HD HR 5.1 file. But now you tried a DTS-HD MA 7.1. When a audiofile is DTS-HD MA tsMuxer and MediaInfo doesn't give bitrate. I have to calculate it myself. This will be fixed in next version.

Why does it go wrong:
Now the bitrate will not be subtracted from the total bitrate and you will get a oversized disc.

Edit: Currently I am creating 286 formulas for triple audio.
For double audio I have 66 formulas
For triple audio I have 286 formulas
For single audio I have 15 formulas

Still to come:
39 for double audio
274 for triple audio

Then I have formulas for the following audio formats in every combination with a max of 3 files:
AC3: 192, 224, 256, 320, 384, 448, 512, 576, 640
DTS-ES, DTS, DTS HR 3018
Wav 5.1 and 7.1

If I want to have formulas for every audiotype with 4 files I need your help because that are 2380 formulas. :D Takes two weeks of non stop muxing:) and roughly 64TB of muxing data :D

[wakebrder]

I See what is going wrong. The first time you tried when conversion succeeded you used a DTS-HD HR audiofile. While I was testing I also used DTS-HD HR 5.1 file. But now you tried a DTS-HD MA 7.1. When a audiofile is DTS-HD MA tsMuxer and MediaInfo doesn't give bitrate. I have to calculate it myself. This will be fixed in next version.

Why does it go wrong:
Now the bitrate will not be subtracted from the total bitrate and you will get a oversized disc.

Edit: Currently I am creating 286 formulas for triple audio.
For double audio I have 66 formulas
For triple audio I have 286 formulas
For single audio I have 15 formulas

Still to come:
39 for double audio
274 for triple audio

Then I have formulas for the following audio formats in every combination with a max of 3 files:
AC3: 192, 224, 256, 320, 384, 448, 512, 576, 640
DTS-ES, DTS, DTS HR 3018
Wav 5.1 and 7.1

If I want to have formulas for every audiotype with 4 files I need your help because that are 2380 formulas. :D Takes two weeks of non stop muxing:) and roughly 64TB of muxing data :D

So, you need more log files from DTS-MA & True-HD?

I could help you with that.

FWIW, I'm only interested in keeping 1 audio track. Others might want multiple audio tracks. Is this your goal?

[twazerty]

So, you need more log files from DTS-MA & True-HD?

I could help you with that.

FWIW, I'm only interested in keeping 1 audio track. Others might want multiple audio tracks. Is this your goal?

Multiple audio is my goal :) I hate fixed overhead percentage. :D

You can help me with DTS-HD MA and True-HD after I released my next version. I already have my hands full with other stuff like x264 encode profiles and multiple audio. Also some fixes needs to be done.

[twazerty]

I am making a CLI app for calculating bitrate. It will be Cross platform (Linux, Mac OS and Windows). I have zero experience with CLI designing but I think a made a good User interface. Here are some examples:

All parameters with 1 audio stream:
ACLICalculator.exe --duration 6000 --output DVD+R-DL --subtitles-size 22575371 --audio-size 336000000 --audio-types 448

All parameters with 3 audio streams and custom output size:
ACLICalculator.exe --duration 6000 --output 14000000000 --subtitles-size 22575371 --audio-size 1803750000 --audio-types 1536+448+448

No subtitles size parameter if you have no subtitles:
ACLICalculator.exe --duration 6000 --output DVD-R --audio-size 2263500000 --audio-types 1536+1536

No audio size parameter. The audiosize is calculated. So it is not bit perfect but you'll never notice.
ACLICalculator.exe --duration 6000 --output BD25 --subtitles-size 22575371 --audio-types 1536+1536

Supported --audio-types values: 192, 224, 256, 320, 384, 448, 512, 576, 640, 768, 1536, 3018, 4806, 6144
With a maximum of 3 audiotypes. 3018, 4806 and 6144 can only be used without other audiotypes

Suported --output values: DVD+R, DVD-R, DVD+R-DL, DVD-R-DL, BD25, BD50, USB1.0, USB2.0, USB4.0, USB8.0, USB16.0, <custom>
<custom> may contain a value between 1000000 and 50000000000 bytes (1MB and 50GB, 0.95MiB and 46.57 GiB)

BTW the result is something like this:
5122
and maybe a Warning for audiosize.

Feedback please.

ACLICalculator stands for: AVCHD Command Line Interface Calculator

Edit:
For Windows I will release a exe file and for Mac OS and Linux a jar file that can be used like this:
java -jar /Users/tw/Desktop/ACLICalculator.jar --duration 6000 --output DVD+R-DL --subtitles-size 22575371 --audio-size 336000000 --audio-types 448

[turbojet]

While command line is nice for linux without a desktop environment I hope you can implement these things into the gui which does work for me in windows and linux but it isn't very accurate. Can't you add command line syntax to the current gui like BDSup2Sub has done?

[twazerty]

While command line is nice for linux without a desktop environment I hope you can implement these things into the gui which does work for me in windows and linux but it isn't very accurate. Can't you add command line syntax to the current gui like BDSup2Sub has done?

This module will be integrated in AVCHDCalculator and AVCHDCoder. AVCHDCalculator is currently windows only but that one will go cross platform too.

The main goal is that other encoders can also use this module. Maybe RipBot264 or Gotsend can integrate it.

What exactly do you mean with this:
Can't you add command line syntax to the current gui like BDSup2Sub has done?s

[nosnoop]

Thank you very much for an excellent program. Much easier to use than doing it manually using MeGUI. And I am very impressed with the accuracy of the bitrate.

Something to consider for your next version:
- default input folder settings
- current USB output settings is not too useful. It would be better if it can split into multiple 4GB m2ts files after selecting your desired file size; with optional 8.3 filename format for PS3.
- FPS display in progress bar as previously requested

[twazerty]

Thank you very much for an excellent program. Much easier to use than doing it manually using MeGUI. And I am very impressed with the accuracy of the bitrate.

Something to consider for your next version:
- default input folder settings
- current USB output settings is not too useful. It would be better if it can split into multiple 4GB m2ts files after selecting your desired file size; with optional 8.3 filename format for PS3.
- FPS display in progress bar as previously requested

Thank you for your interest :)
Default input folder will be changed to "Computer" aka "My Computer" and not far deep into Document. But a default openen folder that can be changed is a nice feature. It think I am going to add it.

FPS will be added. (Said it couple of times but now for real :P)

Splitting files is hard to do in my current design. For 4GB output there is no problem. I have premade menu files so I am not very flexible. But maybe I can do the following as a "Solution":
Splitting files is only possible with 1 item and without menu. That is the easiest way to achieve splitting. And some other time I go for more advanced splitting(multiple items and menu) bacause it takes some time. Currently fixing and adding more important things :)

[Betsy25]

When I open an .mkv file, the program doesn't find any audio.
General
Complete name : O:\Other DVD\Borat\borat.x264.mkv
Format : Matroska
File size : 733 MiB
Duration : 1h 20mn
Overall bit rate : 1 275 Kbps
Encoded date : UTC 2008-04-14 21:09:31
Writing application : mkvmerge v2.2.0 ('Turn It On Again') built on Mar 4 2008 12:58:26
Writing library : libebml v0.7.7 + libmatroska v0.8.1

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Muxing mode : Container profile=Unknown@5.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 1h 20mn
Nominal bit rate : 1 108 Kbps
Width : 720 pixels
Height : 458 pixels
Display aspect ratio : 16/9
Original display aspect ratio : 1.572
Frame rate : 25.000 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.134
Writing library : x264 core 59 r818M d4b7d2b
Encoding settings : cabac=1 / ref=5 / deblock=1:-2:-1 / analyse=0x3:0x113 / me=umh / subme=6 / me-prepass=0 / brdo=1 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=0 / threads=3 / nr=0 / decimate=1 / mbaff=0 / bframes=16 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / wpredb=1 / bime=1 / keyint=250 / keyint_min=25 / scenecut=40(pre) / rc=2pass / bitrate=1108 / ratetol=1.0 / rceq='blurCplx^(1-qComp)' / qcomp=1.00 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / pb_ratio=1.30 / aq=2:1.00
Language : English

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : Yes
Format settings, PS : No
Codec ID : A_AAC
Duration : 1h 20mn
Channel(s) : 6 channels
Channel positions : Front: L C R, Rear: L R, LFE
Sampling rate : 48.0 KHz
Resolution : 16 bits

Text
ID : 3
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha

[twazerty]

AAC isn't supported yet. It will be detected but not shown. Only formats that will be shown:
AC3
DTS
DTS-HD
True-HD

and LPCM and AAC will be added later.

[Krawhitham]

I am making a CLI app for calculating bitrate. It will be Cross platform (Linux, Mac OS and Windows). I have zero experience with CLI designing but I think a made a good User interface. Here are some examples:

All parameters with 1 audio stream:
ACLICalculator.exe --duration 6000 --output DVD+R-DL --subtitles-size 22575371 --audio-size 336000000 --audio-types 448

All parameters with 3 audio streams and custom output size:
ACLICalculator.exe --duration 6000 --output 14000000000 --subtitles-size 22575371 --audio-size 1803750000 --audio-types 1536+448+448

No subtitles size parameter if you have no subtitles:
ACLICalculator.exe --duration 6000 --output DVD-R --audio-size 2263500000 --audio-types 1536+1536

No audio size parameter. The audiosize is calculated. So it is not bit perfect but you'll never notice.
ACLICalculator.exe --duration 6000 --output BD25 --subtitles-size 22575371 --audio-types 1536+1536

Supported --audio-types values: 192, 224, 256, 320, 384, 448, 512, 576, 640, 768, 1536, 3018, 4806, 6144
With a maximum of 3 audiotypes. 3018, 4806 and 6144 can only be used without other audiotypes

Suported --output values: DVD+R, DVD-R, DVD+R-DL, DVD-R-DL, BD25, BD50, USB1.0, USB2.0, USB4.0, USB8.0, USB16.0, <custom>
<custom> may contain a value between 1000000 and 50000000000 bytes (1MB and 50GB, 0.95MiB and 46.57 GiB)

BTW the result is something like this:
5122
and maybe a Warning for audiosize.

Feedback please.

ACLICalculator stands for: AVCHD Command Line Interface Calculator

Edit:
For Windows I will release a exe file and for Mac OS and Linux a jar file that can be used like this:
java -jar /Users/tw/Desktop/ACLICalculator.jar --duration 6000 --output DVD+R-DL --subtitles-size 22575371 --audio-size 336000000 --audio-types 448


Please release this

[twazerty]

Please release this

Just some tweaks and it will be ready. What are the features of the upgraded AVCHDCalculator:
-CLI
-triple audio with AC3 192,224,256,320,384,448,512,576,640, DTS 768,1536,3045, LPCM 4608. LCPM 6144 not yet. For now only as single audio type. And a custom for dts-hd ma. Throw any bitrate you want with a max of triple audio.
-Also max bitrate will be used. So audio+subs+video is max 18Mbit, 24 Mbit or 40Mbit. You can set this at the commandline. Don't need to set it in the GUI.
-Hundreds of formulas. Currently 578 formulas.
-Couple of tests gave me a disc fill of 99.8% and up. (DTS-HD MA is not this accurate)
-Improved calculation when added subtitles. If you throw 1 or 32 subtitles. It doesn't matter. It gave you almost full discs.
-Support for Mac OS X and linux. (GUI and CLI)

No subtitles:
Useage : calc.exe <duration> <output target> <max bitrate> <audio types>
Example: calc.exe --duration 5625 --output DVD+R-DL --max-bitrate 18000 --audio-types 448

With subtitles:
Useage : calc.exe <duration> <output target> <max bitrate> <total subtitles size> <audio types>
Example: calc.exe --duration 5625 --output DVD+R-DL --max-bitrate 18000 --subtitles-size 12000000 --audio-types 448+1536+768

No subtitles with more accurate audioSize:
Useage : calc.exe <duration> <output target> <max bitrate> <total audio size> <audio types>
Example: calc.exe --duration 5625 --output DVD+R-DL --max-bitrate 18000 --audio-size 571189248 --audio-types 448+448

With subtitles with more accurate audioSize:
Useage : calc.exe <duration> <output target> <max bitrate> <total subtitles size> <total audio size> <audio types>
Example: calc.exe --duration 5099 --output DVD+R-DL --max-bitrate 18000 --subtitles-size 12000000 --audio-size 285594624 --audio-types 448


--output values: DVD+R, DVD-R, DVD+R-DL, DVD-R-DL, BD25, BD50, USB1.0, USB2.0, USB4.0, USB8.0, USB16.0, <custom>
<custom> may contain a value between 1000000 and 50000000000 bytes

--max-bitrate explanation: Max bitrate = videobitrate+audiobitrate+subtitlesbitrate.
For DVD and DVD DL you should use 18000, For Blu-ray discs you should 40000, For other media: 24000

--audio-types values: 192, 224, 256, 320, 384, 448, 512, 576, 640, 768, 1536, 3072, 4608, 6144, <custom>
<custom> is reserved for dts-hd ma. You may enter any value.
Maximum 3 audiotypes are supported. 6144 can only be used without other audiotypes!
Some examples:
--audio-types 6144
--audio-types 3072+4608
--audio-types 640+7045
--audio-types 6000+4521+448


Just need to do some final tweaks. When I am ready I release it. I think that will be today. And ofcourse this powerful calculator is added to AVCHDCoder. That needs some final tweaks to and it will be ready to release.

[shon3i]

@twazerty, thanks, finaly we have real Blu-Ray calculator :) btw did you plan to implement *.avs support? for calculating video duration. Aslo what about True-HD support?

[twazerty]

Didn't do any research yet. My next step is to find out what comes close to true-hd overhead. And implement those value's inside the GUI.

But my first feeling says you can enter the bitrate for True-hd at the custom value. Custom now is only for dts-hd but I think True-hd also works fine. Remember that is CLI only now.

AVCHDCalculator 1.1 for Mac OS X and Linux.zip (http://www.mediafire.com/file/ojaimii5kim/AVCHDCalculator 1.1 for Mac OS X and Linux.zip)

AVCHDCalculator 1.1 for Windows.zip (http://www.mediafire.com/file/m0wjgxozeew/AVCHDCalculator 1.1 for Windows.zip)

[Warbucks81]

A small suggestion for the Windows GUI version. You should include other output sizes such as DVD5+DVD9 or DVD9+DVD9. Many people will use multiple discs depending on the target bitrate they are looking for.

[Warbucks81]

I'm getting the following error when using the CLI version. The output size is a DVD+R DL and DVD+R combined. Looks as though you may be missing some zeros on the limit.

AVCHDCalculatorCLI.exe --duration 7020 --output 13248364544 --max-bitrate 18000 --audio-types 1536
Error: Output size not valid. Should be between 1000000 and 50000000 bytes
12747

[twazerty]

I'm getting the following error when using the CLI version. The output size is a DVD+R DL and DVD+R combined. Looks as though you may be missing some zeros on the limit.

Yes i am missing some zero's. My mistake :). I'll fix this today. And the 2 disc option for the GUI is a great idea. But there is a small problem. The bitrate will be calculated very accurately. And as far as I tried, tsMuxer doesn't split very accurate??? In that case your the second part of the split doesn't fit on the disc. What do you think I should do? Maybe a option to choose how much undersizing you want? (In percentages or maybe MB's)

[Warbucks81]

Yes i am missing some zero's. My mistake :). I'll fix this today. And the 2 disc option for the GUI is a great idea. But there is a small problem. The bitrate will be calculated very accurately. And as far as I tried, tsMuxer doesn't split very accurate??? In that case your the second part of the split doesn't fit on the disc. What do you think I should do? Maybe a option to choose how much undersizing you want? (In percentages or maybe MB's)

An option to choose under sizing would probably work. Have you had a chance to fix the issue I mentioned and add the other output target sizes?

[twazerty]

An option to choose under sizing would probably work. Have you had a chance to fix the issue I mentioned and add the other output target sizes?

2 Disc support is added to the GUI. Undersizing option still needs to be added. (Easy) Was very busy with AVCHDCoder. 2 days ago the latest version was released:

v09.09.09:
http://www.mediafire.com/?gm0jdoumqlz
more info on my website

Now I am very busy on installing Windows 7.

[Warbucks81]

2 Disc support is added to the GUI. Undersizing option still needs to be added. (Easy) Was very busy with AVCHDCoder. 2 days ago the latest version was released:

v09.09.09:
http://www.mediafire.com/?gm0jdoumqlz
more info on my website

Now I am very busy on installing Windows 7.

What about the standalone tool AVCHDCalculator? Was this updated to reflect those changes?

[twazerty]

What about the standalone tool AVCHDCalculator? Was this updated to reflect those changes?

AVCHDCalculator isn't released yet. V1.1 is the latest version available. If you do want AVCHDCalculator with the 2 disc option use the jar that is delivered with AVCHDCoder 09.09.09. If I added the undersizing option to AVCHDCalculator then I release it officially.

The CLI custom output size bug didn't/doesn't affect AVCHDCoder but only the CLI version.

Edit: AVCHDCoder uses AVCHDCalculator directly. 100% integration. When I remove AVCHDCalculator I cannot build/create an exe file AVCHDCoder ;)

[nosnoop]

v09.09.09:

Got an error with this version.
The previous version ran fine with my system (Windows 7 x64).

v09.09.09 with errors during video conversion (fast):
01:49:53 Encoding Pass 1: "C:\Program Files (x86)\AVCHDCoder\Tools\X264\32bit\x264.exe" --pass 1 --vbv-bufsize 18000 --vbv-maxrate 18000 --bitrate 6844 --level 4.1 --stats "H:\Workspace\Temp\Video - item 1\Video.stats" --keyint 24 --min-keyint 2 --ipratio 1.1 --pbratio 1.1 --sar 1:1 --output NUL "H:\Workspace\Temp\Video - item 1\Video.avs"
01:50:14 Converting video pass 1: Errorcode: 0x0401,Error occured when converting video

v09.07.26, no errors.
02:08:35 Encoding Pass 1: "C:\Program Files (x86)\AVCHDCoder\Tools\X264\32bit\x264.exe" --pass 1 --bitrate 6809 --stats "H:\Workspace\Temp/Video - item 1\Video.stats" --level 4.1 --keyint 24 --min-keyint 2 --bframes 3 --weightb --direct auto --subme 2 --partitions none --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 24000 --vbv-maxrate 24000 --qcomp 0.5 --me dia --threads auto --thread-input --sar 1:1 --output NUL "H:\Workspace\Temp/Video - item 1\Video.avs"

[twazerty]

Got an error with this version.
The previous version ran fine with my system (Windows 7 x64).

v09.09.09 with errors during video conversion (fast):


v09.07.26, no errors.

I will do some testing. I have windows 7 64 bit too and didn't notice any problems yet. Did you use windows 7 directshow tweaker to set ffdshow as default decoder?

Strange thing is that the one that doesn't fail actually is bugged (\Temp/Video - item 1\Video.stats) notice the / that should be \ :)
You could also try to update ffdshow and x264. ffdshow that comes with AVCHDCoder is tested on my system. You'll hear more tonight. What type was your input? (MKV M2TS etc.)

[MaXiMuS]

Originally Posted by twazerty View Post
2 Disc support is added to the GUI. Undersizing option still needs to be added. (Easy) Was very busy with AVCHDCoder. 2 days ago the latest version was released:

v09.09.09:
http://www.mediafire.com/?gm0jdoumqlz
more info on my website

2 Disc support is added to the GUI. but i can not find it .

http://img17.imageshack.us/img17/224/ripsplit.jpg

??

[twazerty]

2 disc support is for AVCHDCalculator :) So you can calculate bitrate if you want to use 2 discs. AVCHDCoder doesn't support multiple discs. Maybe in the future.

[MaXiMuS]

2 disc support is for AVCHDCalculator :) So you can calculate bitrate if you want to use 2 discs. AVCHDCoder doesn't support multiple discs. Maybe in the future.

:thanks:

thank you for your quick reply.

and i hope that future is very close :) (i really dislike using DVD9 for my backups, 2xDVD5or 3xDVD5 is great) but no rush i love using your AVCHDCoder as is.

[twazerty]

:thanks:

thank you for your quick reply.

and i hope that future is very close :) (i really dislike using DVD9 for my backups, 2xDVD5or 3xDVD5 is great) but no rush i love using your AVCHDCoder as is.

I am thinking on how to add the disc disc option. The technical solution isn't he problem. Example:
You add 1 item to a disc. Now it is logical to choose multiple discs.
But we go 1 step further.
You add 2 episodes of a TV series. Now it is not logical to choose multiple discs because you can make 2 discs. Each containing 1 episode.
For multiple episodes it is not logical to chose for 2 discs because the last thing you want is to switch discs within an episode or worser. The middle disc contains 2 splitted episode. (4 episodes on 3 discs for example)

My solution to the problem:
Multiple disc only for single item.

And what if you choose to add a menu. Should the second disc contain a menu or not if you choose to add a menu. AVCHDCoder needs to be easy in use so difficult this will not be added.

If you can help me to choose what to do...

[MaXiMuS]

My solution to the problem:
Multiple disc only for single item.


agree 100%

until someone have a better idea :)

[turbojet]

Thanks for the psy-rd settings and the fix fps fix with BD input, now just waiting on BDSup2Sub for full functionality.

When splitting beware of the TSMuxer splitting, it produces buggy, unplayable streams. The only way I've found is to split mkv with mkvmerge then input each mkv into tsmuxer.

[twazerty]

Thanks for the psy-rd settings and the fix fps fix with BD input, now just waiting on BDSup2Sub for full functionality.

When splitting beware of the TSMuxer splitting, it produces buggy, unplayable streams. The only way I've found is to split mkv with mkvmerge then input each mkv into tsmuxer.

Ok thanx for the information.
When I use mkvmerge for merging to mkv I do have to add a something to AVCHDCalculator that was already planned. 2 disc output will be added. What output sizes do you want to see?
DVD5+DVD5
DVD5+DVD9
and
DVD9+DVD9
??
Because I have to find a way to add them to AVCHDCoder without making a difficult selecting system.

Edit: BDSup2Sub is annoying. I still need to find a way to check when BDSup2Sub is completed with conversion. Because it isn't cli it is harder to use (You can startup via commandline but no feedback via command line)

[setarip_old]

@turbojetWhen splitting beware of the TSMuxer splitting, it produces buggy, unplayable streams.I have never had any such problem using "tsMuxeR" with either .MKV or .M2TS files (I don't know if it makes any difference, but I always increase the buffer from 500 to 14,425)

[twazerty]

@turbojetI have never had any such problem using "tsMuxeR" with either .MKV or .M2TS files (I don't know if it makes any difference, but I always increase the buffer from to 14,425)

In the past I noticed tsMuxer splitting is not accurate. Need some testing to see what solution I need to build.

I have added a trayIcon in the Systemtray. You can exit AVCHDCoder, hide and show AVCHDCoder.

What information do you want to see in the systemtray? And what options?