Log in

View Full Version : Badaboom yes or no?


Scoty
24th November 2009, 18:11
Have Badaboom a good or bad quality. Badaboom is fast but good and what is better?

Atak_Snajpera
24th November 2009, 18:33
Quality is terrible compared with x264 so don't pay for this crap.

poisondeathray
24th November 2009, 18:53
Agree with atak, and this test was done with abr, not crf... (you'd get better quality with crf)

http://i47.tinypic.com/1zv6745.png

Cyber-Mav
24th November 2009, 19:07
i fina badaboom good enough to do quick conversions for playing video on me iphone.

LoRd_MuldeR
24th November 2009, 19:09
i fina badaboom good enough to do quick conversions for playing video on me iphone.

Did you compare Badaboom against x264 with settings the encode at the same speed ???

Scoty
24th November 2009, 19:34
Ok i make a test with RipBot264 but this extrem slow and the qulity is not good. For a Video 03:50 minutes i need with the x264 profile 40 minutes. Whene i convert a Movie with 2 houres with RipBot264 i need days.

LoRd_MuldeR
24th November 2009, 19:37
Of course x264 will be slow, if you use slow settings :rolleyes:

What about trying something like "--preset fast" ???

Scoty
24th November 2009, 19:41
I have use the standard settings and output mkv.

LoRd_MuldeR
24th November 2009, 19:52
I have use the standard settings and output mkv.

So you want "fast" settings, but you used "medium" (standard) settings. And now you complain about speed? http://forum.gleitz.info/images/smilies/gruebel.gif

Scoty
24th November 2009, 20:00
Yes but with medium settings the quality is not good. With fast settings....??

LoRd_MuldeR
24th November 2009, 20:03
Yes but with medium settings the quality is not good. With fast settings....??

Of course "medium" settings will deliver worse quality than "slow" settings. And "fast" settings will be even worse. If you want speed, you must sacrifice some quality.

However claiming that x264's quality with "medium" settings was "no good" is blasphemy. Especially if we keep in mind how horrible Badaboom looks!

Dark Shikari
24th November 2009, 20:05
Of course "medium" settings will deliver worse quality than "slow" settings. And "fast" settings will be even worse. If you want speed, you must sacrifice some quality.

However claiming that x264's quality with "medium" settings is "no good" is blasphemy. Especially if we keep in mind how horrible Badaboom looks!He's probably encoding at very low bitrates with x264 and comparing to high bitrates with Badaboom...

poisondeathray
24th November 2009, 20:07
There is a tradeoff between quality and speed. Choose one or the other or something in the middle.

There is no question that x264 max quality is better than badaboom's max quality

If your current results aren't good enough another option is to use a lower crf value or higher bitrate too

Scoty
24th November 2009, 20:08
I make a new test with 2-pass with 8000 bitrate. I hope with this settings looks better.

Atak_Snajpera
24th November 2009, 20:08
He's probably encoding at very low bitrates with x264 and comparing to high bitrates with Badaboom...
By default CRF22 is used in Ripbot264. However if you change to 2-pass then default kbps is 1024. Scoty just USE default CRF22. DON'T USE 2-pass!

Scoty
24th November 2009, 20:10
I have make default with the first test but the Video looks nod good.

Atak_Snajpera
24th November 2009, 20:14
I have make default with the first test but the Video looks nod good.
You definitely do something wrong! CRF@22 with default 4.0 HIGH profile should give excellent quality. BTW what does 'nod good' mean in terms of quality? Show us Log from Logs folder.

LoRd_MuldeR
24th November 2009, 20:14
I have make default with the first test but the Video looks nod good.

Repeating it over and over again doesn't make it any better :p

Most important make sure that you only compare files of identical size when judging quality!

prOnorama
24th November 2009, 20:14
Ok i make a test with RipBot264 but this extrem slow and the qulity is not good. For a Video 03:50 minutes i need with the x264 profile 40 minutes. Whene i convert a Movie with 2 houres with RipBot264 i need days.


I get around 20 FPS on a quad core Phenom 955 with x264 medium settings, CRF 23, progressive source to 720p output. For 1080p output I still get 11-12 FPS.

Maybe it's time to get a faster CPU if a 2 hour movie takes days to encode at those settings.

Atak_Snajpera
24th November 2009, 20:17
Maybe it's time to get a faster CPU if a 2 hour movie takes days to encode at those settings.
Exactly. You should finally dump your 'Pentium 4'. You can buy Athlon X4 for less than 100 euro these days.

Scoty
24th November 2009, 20:18
I have use 4.1 Profil. Ok here the Info from the original Video:

Allgemein
ID : 3200
Vollständiger Name : ******.ts
Format : MPEG-TS
Dateigröße : 290 MiB
Dauer : 3min 35s
Gesamte Bitrate : 11,3 Mbps

Video
ID : 1011 (0x3F3)
Menü-ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format-Profil : Main@L4.0
Format-Einstellungen für CABAC : Ja
Format-Einstellungen für ReFrame : 4 frames
Dauer : 3min 35s
Bitrate : 9 904 Kbps
Breite : 1 920 Pixel
Höhe : 1 080 Pixel
Bildseitenverhältnis : 16:9
Bildwiederholungsrate : 25,000 FPS
Auflösung : 24 bits
Colorimetrie : 4:2:0
Scantyp : Interlaced
Scanreihenfolge : oberes Feld zuerst
Bits/(Pixel*Frame) : 0.191
Stream-Größe : 254 MiB (87%)
colour_primaries : BT.709-5, BT.1361, IEC 61966-2-4, SMPTE RP177
transfer_characteristics : BT.709-5, BT.1361
matrix_coefficients : BT.709-5, BT.1361, IEC 61966-2-4 709, SMPTE RP177

Audio #1
ID : 1012 (0x3F4)
Menü-ID : 1 (0x1)
Format : MPEG Audio
Format-Version : Version 1
Format-Profil : Layer 2
Dauer : 3min 34s
Bitraten-Modus : konstant
Bitrate : 256 Kbps
Kanäle : 2 Kanäle
Samplingrate : 48,0 KHz
Auflösung : 16 bits
Video Verzögerung : 125ms
Stream-Größe : 6,56 MiB (2%)
Sprache : Englisch

Audio #2
ID : 1013 (0x3F5)
Menü-ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Dauer : 3min 34s
Bitraten-Modus : konstant
Bitrate : 384 Kbps
Kanäle : 6 Kanäle
Kanal-Positionen : Front: L C R, Surround: L R, LFE
Samplingrate : 48,0 KHz
Video Verzögerung : 75ms
Stream-Größe : 9,84 MiB (3%)
Sprache : Englisch

Menü
ID : 1010 (0x3F2)
Menü-ID : 1 (0x1)
Liste : 1011 (0x3F3) (AVC) / 1012 (0x3F4) (MPEG Audio, Englisch) / 1013 (0x3F5) (AC-3, Englisch)




and here from RipBot264:

Allgemein
Vollständiger Name : *******.mkv
Format : Matroska
Dateigröße : 216 MiB
Dauer : 3min 35s
Gesamte Bitrate : 8 432 Kbps
Filmname : *********
Kodierungs-Datum : UTC 2009-11-24 19:13:32
Kodierendes Programm : mkvmerge v2.9.8 ('C'est le bon') built on Aug 13 2009 12:49:06
verwendete Encoder-Bibliothek : libebml v0.7.7 + libmatroska v0.8.1

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format-Profil : High@L4.1
Format-Einstellungen für CABAC : Ja
Format-Einstellungen für ReFrame : 3 frames
Muxing-Modus : Container profile=Unknown@4.1
Codec-ID : V_MPEG4/ISO/AVC
Dauer : 3min 35s
Bitrate : 8 008 Kbps
nominale Bitrate : 8 181 Kbps
Breite : 1 920 Pixel
Höhe : 1 080 Pixel
Bildseitenverhältnis : 16:9
Bildwiederholungsrate : 25,000 FPS
Auflösung : 24 bits
Colorimetrie : 4:2:0
Scantyp : progressiv
Bits/(Pixel*Frame) : 0.154
Stream-Größe : 205 MiB (95%)
verwendete Encoder-Bibliothek : x264 core 77 r1292kGIT e381f6d
Kodierungseinstellungen : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=3 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=3 / wpredb=1 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=8181 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=25000 / vbv_bufsize=25000 / ip_ratio=1.40 / aq=1:1.00

Audio
ID : 2
Format : MPEG Audio
Format-Version : Version 1
Format-Profil : Layer 2
Codec-ID : A_MPEG/L2
Codec-ID/Hinweis : MP2
Dauer : 3min 35s
Bitraten-Modus : konstant
Bitrate : 256 Kbps
Kanäle : 2 Kanäle
Samplingrate : 48,0 KHz
Auflösung : 16 bits
Stream-Größe : 6,57 MiB (3%)

Atak_Snajpera
24th November 2009, 20:19
Hey hombre did you deniterlace your source before encoding??

Scoty
24th November 2009, 20:22
Here is the log file:



I:\>"F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\avs2yuv\pipebuf.exe" "F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\avs2yuv\avs2yuv.exe" "I:\temp\RipBot264temp\job1\job1.avs" -raw - : "F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\x264\x264_x64.exe" --pass 1 --bitrate 8181 --stats "I:\temp\RipBot264temp\job1\job1.stats" --fps 25 --min-keyint 25 --keyint 250 --frames 5377 --sar 1:1 --level 4.1 --aud --nal-hrd --vbv-bufsize 25000 --vbv-maxrate 25000 --filter 0,0 --ref 3 --bframes 3 --b-adapt 1 --direct auto --subme 7 --aq-mode 1 --trellis 1 --partitions all --me umh --output "I:\temp\RipBot264temp\video.264" - 1920x1080 : 2

x264 [info]: 1920x1080 @ 25.00 fps

x264 [info]: using SAR=1/1

x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64

x264 [info]: profile Main, level 4.1
I:\temp\RipBot264temp\job1\job1.avs: 1920x1080, 25 fps, 5377 frames

x264 [info]: frame I:57 Avg QP:13.45 size:129712

x264 [info]: frame P:3721 Avg QP:14.81 size: 48092

x264 [info]: frame B:1599 Avg QP:14.27 size: 23170

x264 [info]: consecutive B-frames: 45.3% 42.7% 3.4% 8.6%

x264 [info]: mb I I16..4: 50.9% 0.0% 49.1%

x264 [info]: mb P I16..4: 46.5% 0.0% 0.0% P16..4: 43.1% 0.0% 0.0% 0.0% 0.0% skip:10.4%

x264 [info]: mb B I16..4: 4.2% 0.0% 0.0% B16..8: 31.7% 0.0% 0.0% direct:25.2% skip:38.8% L0:36.7% L1:49.5% BI:13.8%

x264 [info]: final ratefactor: 16.31

x264 [info]: direct mvs spatial:96.2% temporal:3.8%

x264 [info]: coded y,uvDC,uvAC intra: 19.5% 79.5% 55.4% inter: 19.3% 41.1% 3.8%

x264 [info]: i16 v,h,dc,p: 55% 18% 12% 15%

x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 27% 19% 5% 4% 4% 4% 5% 4%

x264 [info]: kb/s:8309.25



encoded 5377 frames, 11.81 fps, 8309.25 kb/s


I:\>"F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\avs2yuv\pipebuf.exe" "F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\avs2yuv\avs2yuv.exe" "I:\temp\RipBot264temp\job1\job1.avs" -raw - : "F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\x264\x264_x64.exe" --pass 2 --bitrate 8181 --stats "I:\temp\RipBot264temp\job1\job1.stats" --fps 25 --min-keyint 25 --keyint 250 --frames 5377 --sar 1:1 --level 4.1 --aud --nal-hrd --vbv-bufsize 25000 --vbv-maxrate 25000 --filter 0,0 --ref 3 --bframes 3 --b-adapt 1 --direct auto --subme 7 --aq-mode 1 --trellis 1 --partitions all --me umh --output "I:\temp\RipBot264temp\video.264" - 1920x1080 : 2

x264 [info]: 1920x1080 @ 25.00 fps

x264 [info]: using SAR=1/1

x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64

x264 [info]: profile High, level 4.1
I:\temp\RipBot264temp\job1\job1.avs: 1920x1080, 25 fps, 5377 frames

x264 [info]: frame I:57 Avg QP:13.79 size:120472

x264 [info]: frame P:3721 Avg QP:15.22 size: 49842

x264 [info]: frame B:1599 Avg QP:15.72 size: 17205

x264 [info]: consecutive B-frames: 45.3% 42.7% 3.4% 8.6%

x264 [info]: mb I I16..4: 28.5% 59.9% 11.7%

x264 [info]: mb P I16..4: 10.2% 15.4% 1.8% P16..4: 38.6% 13.1% 7.1% 0.1% 0.1% skip:13.6%

x264 [info]: mb B I16..4: 0.5% 0.8% 0.2% B16..8: 34.2% 1.1% 1.5% direct:10.1% skip:51.5% L0:38.0% L1:54.3% BI: 7.6%

x264 [info]: 8x8 transform intra:56.4% inter:79.8%

x264 [info]: direct mvs spatial:90.5% temporal:9.5%

x264 [info]: coded y,uvDC,uvAC intra: 44.2% 82.3% 54.7% inter: 22.1% 43.3% 4.2%

x264 [info]: i16 v,h,dc,p: 55% 18% 7% 20%

x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 24% 16% 39% 3% 3% 4% 3% 4% 3%

x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 26% 25% 21% 4% 5% 5% 5% 4% 4%

x264 [info]: ref P L0: 75.4% 15.8% 8.8%

x264 [info]: ref B L0: 89.0% 11.0%

x264 [info]: kb/s:8177.09



encoded 5377 frames, 3.23 fps, 8177.09 kb/s


I:\>"F:\Software\Software_Tools\Multimedia\HDTV\RipBot264v1.14.5\tools\mkvtoolnix\mkvmerge.exe" -o "C:\Users\Schrotty\Desktop\beyonce_mtv europe music awards 2009_sf.mkv" --title "beyonce_mtv europe music awards 2009_sf" --default-duration 0:25fps -d 0 -A -S "I:\temp\RipBot264temp\video.264" --language 0:und --sync 0:0 -a 0 -D -S "I:\temp\RipBot264temp\job1\audio.1.mp2"

mkvmerge v2.9.8 ('C'est le bon') built on Aug 13 2009 12:49:06


'I:\temp\RipBot264temp\video.264': Using the AVC/h.264 ES demultiplexer.


'I:\temp\RipBot264temp\job1\audio.1.mp2': Using the MP2/MP3 demultiplexer.


'I:\temp\RipBot264temp\video.264' track 0: Extracted the aspect ratio information from the MPEG-4 layer 10 (AVC) video data and set the display dimensions to 1920/1080.


'I:\temp\RipBot264temp\video.264' track 0: Using the MPEG-4 part 10 ES video output module.


'I:\temp\RipBot264temp\job1\audio.1.mp2' track 0: Using the MPEG audio output module.


The file '*******.mkv' has been opened for writing.




The cue entries (the index) are being written...


Muxing took 3 seconds.

-------------------------

Elapsed Time: 00h:35m:26s

Atak_Snajpera
24th November 2009, 20:24
did you deniterlace your source before encoding??

Scoty
24th November 2009, 20:26
did you deniterlace your source before encoding??

No, is not my source.

Atak_Snajpera
24th November 2009, 20:28
No, is not my source. I have downloaded.
So say good bye to this thread :)

Scoty
24th November 2009, 20:32
With CRF22 the bitrate is under 3000.

Cyber-Mav
24th November 2009, 21:44
Did you compare Badaboom against x264 with settings the encode at the same speed ???

yes i did, badaboom is far faster on my opteron 144 1.8ghz, 2ram machine that has a 8800gt in it.

sure x264 has better quality but it takes a order of magnitude to get the job done too.

slavickas
24th November 2009, 21:54
yes i did, badaboom is far faster on my opteron 144 1.8ghz, 2ram machine that has a 8800gt in it.

sure x264 has better quality but it takes a order of magnitude to get the job done too.
oh and i7 with intel integrated graphics sucks at crysis....
You DO understand that your CPU is relative weak compared to GPU for video encoding?

Dark Shikari
24th November 2009, 22:03
People are never bloody satisfied.

If we made x264 use --preset veryfast by default, people would complain about how the quality isn't nearly as good as it could be.

And when we make x264 use --preset medium by default, people complain about how it's slower than an encoder that uses fast settings by default.

:rolleyes:

G_M_C
24th November 2009, 22:16
Q: Badaboom, yes or no ?
A: No.

LoRd_MuldeR
24th November 2009, 22:18
Q: Badaboom, yes or no ?
A: No.

I'd say: If you have a very weak CPU with a high-end GPU and if you don't care about quality, then yes.

Otherwise no.

G_M_C
24th November 2009, 22:19
I'd say: If you have a very weak CPU with a high-end GPU and if you don't care about quality, then yes.

Otherwise no.

Shure, but OP only gave 2 possible options :p

And anyway, a very weak CPU with a very powerfull GPU will be bottlenecked by the CPU; So even then badaboom wont be fast. Also i dont think i'll be a likely combination.

Cyber-Mav
24th November 2009, 22:48
oh and i7 with intel integrated graphics sucks at crysis....
You DO understand that your CPU is relative weak compared to GPU for video encoding?

which is why i use badaboom for encoding and not x264 on that that machine, whats your point?

you expect me to use x264 on fastest settings and still wait for a much longer time period for the encode to finish over badaboom, on this machine badaboom is the better option.

if someone had an i7/i9 and a super fast graphics card the better option for them would be to use x264 to do the encoding.

all im saying is badaboom does have its advantages. if you have a poor performer of a cpu and and good video card then put the video card to use.

Atak_Snajpera
24th November 2009, 23:02
which is why i use badaboom for encoding and not x264 on that that machine, whats your point?
You should buy Athlon x4 . It costs less than 100euro. BTW. You encode movie once but after you will be watching it many times. So it is better to wait longer for better result.

Cyber-Mav
24th November 2009, 23:10
You should buy Athlon x4 . It costs less than 100euro. BTW. You encode movie once but after you will be watching it many times. So it is better to wait longer for better result.

that makes no sense? why should i go out and buy a whole new machine when badaboom does the job perfectly fine on my current machine?
your saying i only going to encode once? you didnt read my above posts im not encoding for archival quality its video for an iphone, stuff like tv series, and cartoons etc, i need speed of encoding so i can watch the stuff on the phone on the train.

for archival quality id carry on using x264 like i do now to encode home videos made on the digicam.

Chengbin
24th November 2009, 23:21
that makes no sense? why should i go out and buy a whole new machine when badaboom does the job perfectly fine on my current machine?
your saying i only going to encode once? you didnt read my above posts im not encoding for archival quality its video for an iphone, stuff like tv series, and cartoons etc, i need speed of encoding so i can watch the stuff on the phone on the train.

for archival quality id carry on using x264 like i do now to encode home videos made on the digicam.

He's asking you to buy another CPU only. For 100 euros you can buy a Athlon X4, which is literally 10 times faster than what you have right now.

You really need to upgrade your CPU anyway. A single core 1.8Ghz CPU + 8800GT?? That's wrong.

Cyber-Mav
24th November 2009, 23:24
so your saying an x4 will fit directly into my socket 939 motherboard, and i wont even need to change the memory? your wrong on this, socket AM2/AM3 cpu's wont work in socket 939 motherboards.

Disabled
24th November 2009, 23:45
@poisondeathray You forgot to share the second interesting graph from that page:
http://i49.tinypic.com/27yb9mh.pnghttp://i47.tinypic.com/1zv6745.png
(Second pic added for quick comparison).
System used was Windows Vista x64 SP1
Core i7 920 2.66GHz 4.8GT/s
3GB 1DDR3-1333
GeForce GTX 260+ 896MB Forceware 185.65

*edit* sorry for being a bit late to the show, I just thought that was a very nice comparison even if I don't understand a word chinese. If anyone has similar comparisons please share.

poisondeathray
24th November 2009, 23:58
@poisondeathray You forgot to share the second interesting graph from that page:

Yep, sorry I didn't post the full links. They had been posted in other threads before (the spurs engine and cuda encoding thread here at doom9, and I didn't want to spam too much - in fact this whole thread has been discussed before). You can use google translate, but the graphs are easy to read.

http://www.pcinlife.com/article/graphics/2009-07-15/1247632564d831.html
http://www.pcinlife.com/article/graphics/2009-04-06/1239027193d770.html

The comparison screenshots on page 7 of spurs engine to x264 quality @ 500kb/s are laughable; but badaboom is supposed to be a bit better in quality than spurs engine
http://www.pcinlife.com/article/graphics/2009-04-06/1239027193d770_6.html

And to be fair, I think badaboom added High profile to the latest version. So it should be retested.

chipzoller
25th November 2009, 00:59
Badaboom yes or no?
Answer: No.

Go x264 or go home.

ajp_anton
25th November 2009, 01:21
Those graphs don't really say anything. x264 is slower but higher quality. What about dropping x264's quality to the same levels so their speeds can actually be compared?

dstln
25th November 2009, 01:33
If gpu encoding is faster over x264 at the same quality and speed is a high priority, no one would blame you for using it. But in general, that wouldn't be the case and misinformation/misunderstandings lead to stuff like this :-\

Disabled
25th November 2009, 02:50
Those graphs don't really say anything. x264 is slower but higher quality.
Compared to Baddaboom its faster and better. Mediacoder is twice as fast though.

Dark Shikari
25th November 2009, 03:09
Compared to Baddaboom its faster and better. Mediacoder is twice as fast though.You mean nvcuenc. Mediacoder is just a crappy GUI.

G_M_C
25th November 2009, 05:49
[...]
A single core 1.8Ghz CPU + 8800GT??
[...]

Single core 1.8 GHz & 8800GT is more or less silly anyway. That CPU will bottleneck the GPU, and so reducing the benefit of badaboom in the first place. All-in-all the advise to get a better CPU isn't a bad one; Even if you insist on using badaboom and its mediocre quality.

roozhou
25th November 2009, 07:46
so your saying an x4 will fit directly into my socket 939 motherboard, and i wont even need to change the memory? your wrong on this, socket AM2/AM3 cpu's wont work in socket 939 motherboards.

Try OC your 144 to 3GHz:)

DiKey
29th November 2009, 00:21
The ONLY use of Badaboom is to free your cpu for more important things.