RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[Atak_Snajpera]

Just about to buy a quad core processor and was wandering if x264\wmv encoder supports 4 threads to make full use of it?

x264 codec will use all your cores

I got this error: "Windows - No Disk" "Exception Processing Message c0000013 Parameters 75b6bf9c 4 75b6bf9c" Upon starting the app... I think its looking for a disk that isnt there...

good advice. If you want to upload screenshots use imageshack. fix is on the way.

[Ajax_Undone]

Ok thanks bro.. By the way you can update the installer link on the first post...

Is there anyway the *.mov support can be implemented...

[Atak_Snajpera]

Ok thanks bro.. By the way you can update the installer link on the first post...

But fix is not ready yet :)

Is there anyway the *.mov support can be implemented...

Rename mov to mp4.

[Ajax_Undone]

[QUOTE=Atak_Snajpera;1096780]But fix is not ready yet :)

I know but at the verry leased its something LOL...
Once you pass the error by pressing ok it still work...

[Miryan]

Atak_Snajpera, can you check your first post? The download links are not in it. Thank you!

[DJ_Price]

Atak_Snajpera, can you check your first post? The download links are not in it. Thank you!

My guess is because a new update is on it's way soon.

[Tirade]

My guess is because a new update is on it's way soon.

I hope so, I deleted the old version before I checked to see if the new one was linked for download.

[Ajax_Undone]

Ok the updated link to the Installer can be found Here (http://www.megaupload.com/?d=WTTEVQ73) and in my signature.... Enjoy

PS:
It comes with a new version of FFDshow it is recomended that you install it...

[Bigmango]

@Bigmango
I hope this time file size will be closer to specified after TSRemux. I'm waiting for your results.

BTW with X-men3 (1:42)
I got m2ts 4453MB but after TSRemux with BluRay structure I got 4472MB.

So, I did a new movie with version 1.8.8. It is 1h49 long, and has ac3 640k audio like the other ones. I set the output size at 4480.

The m2ts file came out at 4500 (20 Mb more) and the tsremux blu-ray structure was 4520 (40 Mb more). So, we're still not there yet :/

The size seems to depend on the movie lenght. This raises another question to me: what will happen with longer movies, i.ex 3h ? Do you take this into account in your calculations ?

[Bigmango]

I have tried to load a 3h07 mkv movie with 640k ac3 (same as my other files that worked).

When selecting the input file it starts to demux the audio (as usual) but after a while it pops up media player classic playing "getinfo.avs" and showing the message "m2audiosource: "D:\temp\Ripbot264temp\job1\audio.3.ac3" is not a valid ac3 file (D:\temp\Ripbot264temp\job1\getinfo.avs, line 3)"

This is strange as there is no difference between this file and the other files I have tried... It plays fine and the audio is 640k ac3 like the other ones...

[Ajax_Undone]

It sounds like the ac3 header is corrupt... Try doing a direct stream copy in VdubMod and see if the new out put will work..

It wont re-encode anything but it will re-write the header's into a new video file...

[Atak_Snajpera]

The size seems to depend on the movie lenght. This raises another question to me: what will happen with longer movies, i.ex 3h ? Do you take this into account in your calculations ?

I really don't understand why m2ts is so unpredictable :( I will make a test tomorrow with Transformers (138min). Friend of mine has 4Ghz x 4 cores so it shouldn't take too much time :)

When selecting the input file it starts to demux the audio (as usual) but after a while it pops up media player classic playing "getinfo.avs" and showing the message "m2audiosource: "D:\temp\Ripbot264temp\job1\audio.3.ac3" is not a valid ac3 file (D:\temp\Ripbot264temp\job1\getinfo.avs, line 3)"

I think I've just found a bug.

[Tirade]

I think I see a small bug in the new version.


When selecting output location, if you just select C: as the folder (for example C:\test_movie.mp4) RipBot sets the output with an extra \ so you get C:\\test_movie.mp4

[Atak_Snajpera]

When selecting output location, if you just select C: as the folder (for example C:\test_movie.mp4) RipBot sets the output with an extra \ so you get C:\\test_movie.mp4

I've noticed that some time ago. Don't worry everything will be muxed correctly even with two \\ :) Tested.

[chuuey]

thanks for the update, keep it up :)

[arrarro]

thank you so much for your amazing program Atak_Snajpera! my iPod Touch bless you everytime I play a video on it! ;):thanks:

[jkleslie]

Awesome piece of software...I have to say.

I do have a slight problem that I found, however. In one of your latest versions you have the Temp directory being placed on the drive with the most space available. The problem here is that if you do drive mapping and have a large mapped drive, your temp files go there. I have my video share folder on my media center mapped, which is a 2TB array. My temp folder is being created there.

Would it be possible in the near future to add the option to specify the Temp location?

Thanks,

Jon

[Bigmango]

Would it be possible in the near future to add the option to specify the Temp location?
Jon

+1

I would also prefer to specify the temp location myself, i.ex in an "options/preferences" window.

[Atak_Snajpera]

I would also prefer to specify the temp location myself

What is your reason?

[Bigmango]

What is your reason?

While ripbot is doing its job (6-8 hours with 720p movies and more with 1080p) I often mux/demux some other files (often dvd5 or dvd9 size, but can be as big as 35Gb blu-ray m2ts).

Take this example that happens often:
I have 8 Gb free on 1 partion and 21Gb free on another.

I start ripbot with a 7Gb job, so I want to assign the temp folder to the 8 Gb partition.
So if I have 21 Gb free on the other partition I can demux a 20Gb file there, but I can't do it if ripbot decides on its own to store its temp folder there.

And there are a dozen more reason, like I can't download linux dvd disc images because ripbot has decided on its own to put its temp on the partition that just had enough space for the disc image (but if I could set the temp dir myself I could assign it elsewhere on a smaller partition that would be enough for the ripbot job), etc...

[Ajax_Undone]

Hey Installer link update.... Done!

The first selected area is for removal of old install files... (if any)

Thanks for DDLing...

[Bigmango]

I have now done a 2h40 movie with ripbot 1.8.9. I set the output size at 4435 (the previous encode with a 1h50 movie was about 40Mb too big if set at 4480, with 4435 it worked fine).

So now with this 2h40 movie the m2ts with a size set at 4435 comes out at 4510 (75MB bigger than 4480) and the blu-ray structure is 4538 (103Mb more than 4480).

So it definitely seems that the m2ts size is dependent on the movie lenght. How are you calculating the bitrate?


Btw, thx for the 1.8.10 update, and thx Ajax for the installer :)


PS: I hope we can find a way to fix this soon, it sucks to be forced to encode the movies twice to get the right size.

[survivant001]

@Atak

just to keep you inform. I still have problem with my movie. I created a new thread about the VBV Buffer underflow error.

here the link : http://forum.doom9.org/showthread.php?p=1098148#post1098148

look so hard to find a working command line.. I which I know which parameters to change when I get this error.

Oh ya.. can you add a new feature

check if you get this in the stdout of the process : "VBV buffer underflow" if it's the case.. can you popup a warning ? Like the file won't be valid for bluray authorising. need to tweak the parameters manually

[weaver4]

Are you planning on RB automatically detecting DeInterlace and IVTC in the future?

You may not agree, but I feel this capability would make your program the AutoGK of the H264 world.

[buzzqw]

@Atak_Snajpera

if you are interested on

Are you planning on RB automatically detecting DeInterlace and IVTC in the future?

in automkv i based analysis on this doc

http://avisynth.org/mediawiki/Interlace_detection

BHH

[weaver4]

AutoMKV does a great job of detecting Interlace!

[survivant001]

@Atak_Snajpera

first test with ripbot1.8.10

mkv -> m2ts 4.1 (crf 20)+ ac3.

I obtain "data corrupted"

ripbot264 removed the video.264 file, so I cann't mux it manually with tsmuxer.

I try mkv2vob and it works.

by the way, why do you remove the .264 file but not the audio.ac3 too ? I'll prefer to keep the both of the files.. for a particuliar case like this one

[Atak_Snajpera]

So it definitely seems that the m2ts size is dependent on the movie lenght. How are you calculating the bitrate?

Here is sample code:
if form2.m2ts.Checked=true then duration:=duration*1.065 else duration:=duration*1.0005; // manual adjustments to avoid oversize. However It doesn't work for M2TS :(
if (copyaudiostream=0) and (duration<>0) then tempcalc:=(size*1048576/duration*8-audiobitrate)/1000;
if (copyaudiostream=1) and (duration<>0) then tempcalc:=(size*1048576-AudioFileSize)/duration*8/1000;

Duration represents movie length in seconds
AudioFileSize is in bytes

PS: I hope we can find a way to fix this soon, it sucks to be forced to encode the movies twice to get the right size.

You don't have to tell me. I'm also pissed off :(

mkv -> m2ts 4.1 (crf 20)+ ac3.

I obtain "data corrupted"

I've just encoded small clip @ CRF20 + ac3 (FullHD bitrate around 20Mbps) and guess what...no problem...plays fine

Oh ya.. can you add a new feature

check if you get this in the stdout of the process : "VBV buffer underflow" if it's the case.. can you popup a warning ? Like the file won't be valid for bluray authorising. need to tweak the parameters manually

No I can not because I have never had that error with my settings. Your settings are extremely weired! --Keint 13 (!!!) and so on. So no wonder if you get unexpected results.

[gav1577]

First off thank you for the excellent program you have created
its just what i need to convert my bluray vc1 discs to h264 m2ts 25fps for my ps3 and keep the quality almost identical to the original and get smooth playback. 24fps pisses me off as i notice the playback seems slow and judders on my tv as it does not support
24p. so for me this is perfect great job thanks :-)

[weaver4]

On your latest version (1.8.10) the filesize for a single pass quantizer of 21 have gone up significantly. With the same setup that I was using before one video that was 1.4G went to 2.5G. I was using the 4.1 profile for both, Q=21, 128kbs audio, auto crop, DeInterlace = Off (Megui said it was progressive), TDecimate = 23.976, size 640x272.

When I tried to open up the movie in avinaptic here is what I got; with and error. I also included the avinaptic report for the movie that encoded correctly on a previous version.


Something appears to be really broken.

=======================================

[ About file ]

Name: Video--zrbq21-pch-b.mp4
Date: 9/02/2008 20:31:16
Size: 2,528,421,863 bytes (2411.291 MB)

[ Generic info ]

File type: ISO Media, MPEG v4 system, version 1

[ Hex dump ]

00000000: 00 00 00 18 66 74 79 70 69 73 6f 6d 00 00 00 01 |....ftypisom....|
00000010: 69 73 6f 6d 61 76 63 31 00 3e 15 e9 6d 6f 6f 76 |isomavc1.>.émoov|
00000020: 00 00 00 6c 6d 76 68 64 00 00 00 00 c3 d2 b0 ad |...lmvhd....ÃÒ°*|
00000030: c3 d2 b0 ad 00 00 02 58 00 4e cc d9 00 01 00 00 |ÃÒ°*...X.NÌÙ....|
00000040: 01 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 |................|
00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 |................|
00000060: 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 |............@...|
00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000080: 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 15 |................|
00000090: 69 6f 64 73 00 00 00 00 10 07 00 4f ff ff 29 15 |iods.......Oÿÿ).|

[ About H.264 encoding ]

Error: Errore di sintassi in NALU di tipo SEI

This report was created by AVInaptic (16-09-2007) on 9 feb 2008, h 22:59:43

=============================================


[ About file ]

Name: Video--zrbq21-pch.mp4
Date: 31/01/2008 20:48:10
Size: 1,462,988,006 bytes (1395.214 MB)

[ Generic info ]

Play duration: 02:23:27 (8607.081666 s)
Container type: MP4/MOV
Major brand: ISO Base Media version 1
Compatible brands: JVT AVC
Creation time: 31/01/2008 01:41:27 UTC
Modification time: 31/01/2008 01:41:27 UTC
Number of streams: 2
Type of stream nr. 1: video (avc1) {GPAC ISO Video Handler}
Type of stream nr. 2: audio (AAC Low complexity) {GPAC ISO Audio Handler}
Audio streams: 1

[ Relevant data ]

Resolution: 640 x 272
Width: multiple of 32
Height: multiple of 16

[ Video track ]

Codec: avc1
Resolution: 640 x 272
Frame aspect ratio: 40:17 = 2.352941 (~2.35:1)
Pixel aspect ratio: 1:1 = 1
Display aspect ratio: 40:17 = 2.352941 (~2.35:1)
Framerate: 23.976023 fps
Number of frames: 206362
Bitrate: 1227.571336 kbps

[ Audio track ]

Codec: AAC Low complexity
Bitrate: 128.447000 kbps
Channels: 2
Sample rate: 48000 Hz

[ About H.264 encoding ]

User data: x264
User data: core 57
User data: H.264/MPEG-4 AVC codec
User data: Copyleft 2005
User data: http://www.videolan.org/x264.html
User data: cabac=1
User data: ref=3
User data: deblock=1:0:0
User data: analyse=0x3:0x113
User data: me=umh
User data: subme=6
User data: brdo=1
User data: mixed_ref=1
User data: me_range=16
User data: chroma_me=1
User data: trellis=1
User data: 8x8dct=1
User data: cqm=0
User data: deadzone=21,11
User data: chroma_qp_offset=0
User data: threads=3
User data: nr=0
User data: decimate=1
User data: mbaff=0
User data: bframes=3
User data: b_pyramid=0
User data: b_adapt=1
User data: b_bias=0
User data: direct=3
User data: wpredb=1
User data: bime=1
User data: keyint=250
User data: keyint_min=25
User data: scenecut=40(pre)
User data: rc=crf
User data: crf=21.0
User data: rceq='blurCplx^(1-qComp)'
User data: qcomp=0.60
User data: qpmin=10
User data: qpmax=51
User data: qpstep=4
User data: ip_ratio=1.40
User data: pb_ratio=1.30
User data: aq=1:1.0:0.0
SPS id: 0
Profile: High@L4.1
Num ref frames: 3
PPS id: 0
Entropy coding type: CABAC
Weighted prediction: No

This report was created by AVInaptic (16-09-2007) on 9 feb 2008, h 23:03:32

[buzzqw]

latest build of x264 have added AQ automatically if not set "--aq-strenght 0" (the same on automkv, but fixed in next version)

the avinaptic problem is due to "--nal-hrd -aud" parameter used for compatibility with ps3/bluray

BHH

[survivant001]

No I can not because I have never had that error with my settings. Your settings are extremely weired! --Keint 13 (!!!) and so on. So no wonder if you get unexpected results.

ah ah ah

I'm not using keyint 13 for fun.. it's a test.

With the default command line from ripbot264 and automkv I still got the buffer underflowns.. and it's not for all the movies.. just one.

Still trying to figure what cause the problem. I think it's a bug in x264.

for now, I'm trying settings like Sagitaire suggested. (--qcomp 0.50) I did a test with keyint 24 and --qcomp 0.50, vbv-max 26000.. still got the error..

now keyint 24, vbv 30000 --qcomp 0.45 will know in 3.5 hours

[weaver4]

latest build of x264 have added AQ automatically if not set "--aq-strenght 0" (the same on automkv, but fixed in next version)

the avinaptic problem is due to "--nalhrd --aud" parameter used for compatibility with ps3/bluray

BHH

So I guess there is no way to do reasonable file size with single pass in this version. What version do I need to go back to.

Can we have a second "more conventional" Level 4.1 profile for computers, xbox, popcornhour and such. I don't like the fact I can not open it in avinaptic. PS3 is such a strange animal.

[buzzqw]

stay with cef's 709

BHH

[Atak_Snajpera]

So I guess there is no way to do reasonable file size with single pass in this version. What version do I need to go back to.

uncheck AQ quant. in profile

Can we have a second "more conventional" Level 4.1 profile for computers, xbox, popcornhour and such. I don't like the fact I can not open it in avinaptic. PS3 is such a strange animal.

uncheck AVCHD compatibility in profile

[Bigmango]

Here is sample code:
if form2.m2ts.Checked=true then duration:=duration*1.065 else duration:=duration*1.0005; // manual adjustments to avoid oversize. However It doesn't work for M2TS :(
if (copyaudiostream=0) and (duration<>0) then tempcalc:=(size*1048576/duration*8-audiobitrate)/1000;
if (copyaudiostream=1) and (duration<>0) then tempcalc:=(size*1048576-AudioFileSize)/duration*8/1000;

Duration represents movie length in seconds
AudioFileSize is in bytes


I have done some tests with a couple files.

Using your variation of the standard bitrate formula doesn't work with the files I have tested (you are not applying the overhead to the audio). To me it seems that adding a 5,2% compensation to the duration for the overhead (m2ts + avchd structure) does the trick using the standard bitrate formula.

BUT the audio bitrate must be used within the calculation, substracting the audio file size will not work (I don't know why, maybe because the audio is not the same duration as the movie, I'm not sure) (yes, I am using audio stream copy).

Btw: you forgot to apply the overhead to the audiofilesize (audiofilesize*1.065), but as I said above, even with applying the overhead (I use 1.052) to the audio filesize the video bitrate comes out to high. So, the only way I was able to make it work was by using the audio bitrate.

The standard bitrate formula is:
((Size - (Audio * Length )) / Length) *8° = Video bitrate

Example with a 2h40 movie:
L = 160 x 60 = 9600s
Duration = 9600 * 1.052 = 10099.2 (5.2% overhead)
S= 4480 x 1024= 4'587'520
A= 640k / 8° = 80KB/s (640k ac3)

V= (((4'587'520 - (10099.2 * 80))/10099.2)*8°) = 2994

I am testing this with some more movies with different durations, but until now it seems to be fine.

[Bigmango]

After some more testing it seems that the best way is to just substract 5.5% overhead from the media size. This will work if you use an audio bitrate and also if you substract the audio file size doing an audio stream copy.

Example (same 2h40 movie as above, 748405 is 730Mb audio size):

V= ((4'587'520*0.945 - (9600 * 80))/9600)*8° = 2973
and
V= ((4'587'520*0.945 - 748405)/9600)*8° = 2989

I think 5.5% is good as it keeps a small margin, 5% is not enough if using audio stream copy.


Edit: fyi, with this 2h40 movie a video bitrate of 2996 will match 4480Mb exactly (using audio stream copy).

[Atak_Snajpera]

V= (((4'587'520 - (10099.2 * 80))/10099.2)*8°) = 2994

I think 2994 is not correct value because x264 encoder uses this format 1Kbps = 1000 bps (not 1024!)

What do you think about this?
tempcalc:=(size*1048576/duration*8/1.052-audiobitrate*1.052)/1000;

So I get 3032 Kbps instead of 2994

[Bigmango]

I think 2994 is not correct value because x264 encoder uses this format 1Kbps = 1000 bps (not 1024!)

What do you think about this?
tempcalc:=(size*1048576/duration*8/1.052-audiobitrate*1.052)/1000;

So I get 3032 Kbps instead of 2994

Won't do, 3032 is too much. A video bitrate of 2996 matches 4480Mb exactly (check my above edit).

What do you think about just substracting 5.5% from the media size (as per my 2nd post) ?

Edit: in my example 4480Mb = m2ts + avchd structure (final tsremux blu-ray output, ready to burn to DVD)

[Atak_Snajpera]

Won't do, 3032 is too much.

So we should use 5.5% instead. From experience I'm sure that final result must be divided by 1000. If you divide by 1024 you will never get correct file size in MKV/MP4 (those have very small overheads)

What do you think about just substracting 5.5 from the media size (as per my 2nd post) ?

Encode smaller movie ~90 min and 2h:40 and let's see if this work. Use 640 for audio in all tests.

[Bigmango]

Encode smaller movie ~90 min and 2h:40 and let's see if this work. Use 640 for audio in all tests.

I have already done 2h40 (above example), and 1h40.

Now I have 3h07 in the pipe (about 40 minutes more encoding), and after this I am doing a 1h55 movie encode.

I have no 90 minutes movie at hand currently, but will test it as soon as I get the opportunity.

[Atak_Snajpera]

Now I have 3h07 in the pipe (about 40 minutes more encoding), and after this I am doing a 1h55 movie encode.

I have no 90 minutes movie at hand currently, but will test it as soon as I get the opportunity.

I will also make some tests with this formula filesize/1.055

Now I have 3h07 in the pipe (about 40 minutes more encoding), and after this I am doing a 1h55 movie encode.

What do you have QuadCore@4GHZ :)

[Bigmango]

Ok, so the 3h07 movie is done. 5.5% overhead is not enough, it needs a 6% overhead which will give it a 2435 bitrate.

I still don't have the right formula, but this is some info for you (audio is always 640k) based on real ripbot encodes (not calculations):

With a 3h07 movie to match 4480Mb exactly (full avchd structure( m2ts + tsremux blu-ray)) you need a 2440 bitrate.
With a 2h40 movie you need a 2996 bitrate to match 4480Mb.

These are the maximum bitrates the calculation must give for these movie lenghts.

I will test some more with shorter movies.

[Atak_Snajpera]

Ok, so the 3h07 movie is done. 5.5% overhead is not enough, it needs a 6% overhead which will give it a 2434 bitrate.

overhead is changing if movie is longer (has more frames) . I'm not surprised :) I'm encoding now 85min movie.It should be ready by tomorrow morning.

I still don't have the right formula
Once my encoding is ready I will be able to create formula which will calculate overhead according to number of frames

[Bigmango]

Once my encoding is ready I will be able to create formula which will calculate overhead according to number of frames

Nice !

If it can help you, these are the frame numbers of the above movies:

3h08: 269650 frames (max bitrate to reach 2440)
2h40: 229707 frames (max bitrate to reach 2996)

[Atak_Snajpera]

3h08: 269650 frames (max bitrate to reach 2440)
2h40: 229707 frames (max bitrate to reach 2996)

Give me also exact percentage values. I will need them to make a graph in excel.

[Bigmango]

Give me also exact percentage values. I will need them to make a graph in excel.

I didn't reach these exact bitrate numbers using a calculation (my calculations were always a few k/s off, as you can see above).

I found these bitrates by encoding the movies 2 times (and a 3rd encode confirms the bitrate is right). So this is the exact max bitrate.


BTW, I have 1 question: the 3h08 movie quality is very good @ 2440k, but I get some small blockyness sometimes on faces (but everything else is perfect). I am now encoding the movie again to improve this, with ESA, RDO lvl2, and p4x4. I think the PS3 will support this, but is p4x4 AVCHD compliant ? Also, would 4 b, 4 ref frames work ?

[Atak_Snajpera]

I am now encoding the movie again to improve this, with ESA, RDO lvl2, and p4x4. I think the PS3 will support this, but is p4x4 AVCHD compliant ? Also, would 4 b, 4 ref frames work ?

p4x4 is not allowed in Level 4.1. 4 ref and 4 b won't solve problem with blocking because 2440k is very low for 1280x544.

85 min = 4482 MB (m2ts + bluray) We are almost at home :)

[Bigmango]

p4x4 is not allowed in Level 4.1. 4 ref and 4 b won't solve problem with blocking because 2440k is very low for 1280x544.

Ok, :thanks:


85 min = 4482 MB (m2ts + bluray) We are almost at home :)

Nice !

[hfmls]

how do i define the temp folder?