[Demo] Trailers 1080p H264 ultra low bitrate

[Sagittaire]

Here little demo trailers:

Superman (http://jfl1974.free.fr/upload/superman.mp4)
Video MPEG4 AVC High Profil 1920*1088*23.976 1600 Kbps
Audio MPEG4 AAC High Efficiency 5.1 48 Khz 160 Kbps

XMenIII (http://jfl1974.free.fr/upload/XMenIII.mp4)
Video MPEG4 AVC High Profil 1920*1088*23.976 1600 Kbps
Audio MPEG4 AAC High Efficiency 2.0 48 Khz 72 Kbps


1) With same source Superman 720*304 q2 XviD done 1200 Kbps. With same source XMenIII 720*304 q2 XviD done 1500 Kbps.Compressibility q2 XviD for usual movies is in [1000 Kbps - 1500 kbps] interval for something like 90% of the sources. These trailers are representative sources for compressibility.

2) As you can see quality for these trailers are very high and especially quality for Superman trailer with very low bitrate, certainely very better than DVD quality. What is the utility for the 30 Go from HD-DVD and the 50 Go from BR ?

3) My little sempron 2.1 Ghz can play very well these 1080p trailers with CoreAVC and CoreAAC filter ... ;-)

[fight2win]

can u pls tell me where to download coreavc?

[ChronoCross]

can u pls tell me where to download coreavc?

currently not available to the public as they have taken down the beta to prepare for the official launch. it will cost money when it comes out.

[bob0r]

Yet, files saves the day:

http://files.x264.nl/CoreAVC20060113.7z = latest test version, which was available for download.

[Oline 61]

How do you install the .ax file?

Also, how did they make the quality so high, when I struggle to get that kind of quality at 640x480 2200 kbit/s with max settings in x264?

[ToS_Maverick]

because normally you watch your videos at ~200% of it's original size. at 1080p you watch the trailers at about 50%, which makes it a lot harder to spot artifacts.

[Oline 61]

Doh. I never thought about it that way.

Also, figured out how to install the filter. FFDShow managed to play about 1 frame for every 100 frams, whereas it's smooth as glass with CoreAVC. Definitly something worth buying when it comes out.

[Sagittaire]

Also, how did they make the quality so high, when I struggle to get that kind of quality at 640x480 2200 kbit/s with max settings in x264?

Well I think that H264 powerfull can simply use higher resolution than ASP codec like XviD or DivX. IMO if 640*480 q2 MPEG4 ASP is good for your eyes then you must try 1024*576 for H264 with DVD source.

because normally you watch your videos at ~200% of it's original size. at 1080p you watch the trailers at about 50%, which makes it a lot harder to spot artifacts.

Well not exactly. Relative size for codec artefact (blocking or ringing) are simply smaller. It's simple to see 8*8 block for H264 q30 with 640*360 resolution. It's very hard to see 8*8 block for H264 q30 with 1920*1088 resolution.

In fact the problem here is quantizer vs resolution for each codec generation. With same bitrate and same source the best choice was certainely something like 150 000 pixel and q3 for DivX 3.11, and after certainely something like 200 000 pixel and q4 for ASP. Perhaps that best choice for H264 will be 300 000 pixel and q24 or perhaps 600 000 pixel and q28 ... who say ... ???

[metalmania]

Excuse me but can I ask a question? I played the two mp4 files using MPC6487, CoreAVC and CoreAAC and Haali Splitter. However my CPU usage was always almost 100%. :( My sig: Athlon XP2500+ OC 3200+, 1GB SDRAM, ATI 9800pro. I tried Kmplayer with CoreAVC and CoreAAC, it played even worse.

[Oline 61]

If the files played allright, then what do you have to worry about? With that processor I would expect 100% usage on HD AVC stuff anyway.

[Revgen]

I encoded a 1080i .ts video into a 1080p (60p) AVC with x264 and it didn't play back well at all with any of the decoders (CoreAVC, FFDshow, VLC player) so far. CoreAVC played back at about 28fps while the others were way lower.

I decided to encode it to Xvid and only VLC player could play it back at a reasonable speed.

Hopefully devs out there can add Dual-Core functionality to their decoders so that these vids can be processed faster.

[LoRd_MuldeR]

Doesn't play smooth, even with latest MPC and CoreAVC :(
CPU is AthlonXP 2800

[Sagittaire]

My config:
CPU Sempron 2500+ 1.8Ghz@2.1Ghz bus 333Ghz@400Ghz
GPU ATI 9550 250Mhz@400Mhz 128 Mo
RAM PC3200 2*512Mo 8, 3, 3, 3.0
DD 2*80 Go

Trailer with Haali Media Splitter, CoreAVC and CoreAAC

Superman : average speed = 31.21 fps for video only
http://jfl1974.free.fr/upload/ChargeSuperman.PNG

XMenIII : average speed = 31.92 fps for video only
http://jfl1974.free.fr/upload/ChargeXMenIII.PNG

Superman :
CoreAVC average speed = 31.21 fps
libavcodec average speed = 18.47 fps


My little Sempron (70$) seem to be very good ... lol

[bill_baroud]

i don't think your FSB is at 400Ghz though ;)

[breez]

For those having problems with CPU usage, switch to overlay if you are using VMR.

[blash_]

How do you install the .ax file?

Here's the cccp's guide:

cccp-project.net/wiki/index.php?title=CoreAVC (http://cccp-project.net/wiki/index.php?title=CoreAVC)

[metalmania]

"Superman : average speed = 31.21 fps for video only",.....does that mean the audio filter was not used?

[Sagittaire]

"Superman : average speed = 31.21 fps for video only",.....does that mean the audio filter was not used?

that's mean perhaps something like 30.50 fps with video+audio. My sempron 2.1 Gkz play perfectly XMenIII and Superman (audio + video) without dropping frame as you can see on my CPU graph (there are not 100% CPU saturation).

[murattttt]

I downloaded the Superman trailer happily but could not playback it to the end in any of the players I got (Windows mplayer2, MPC, Videolan, Nero Showtime). I can say I have the latest ffdshow and version of the players are up to date. After 10~20 seconds any of theses players crash miserably. Though the place doesn't seem to be the place for playback problem solving I've had my luck with short h264 videos downloaded from internet so far (quicktime, x264, HD xvid, etc) I wonder what could be the problem. The file size downloaded is 21.231.547 bytes.


Anyway the quality is so over the top I found myself resizing my CRT to 1940x sth. after all those happy 1280x1024 desktop years. Even so I have to admit it is almost impossible to compare it to a decent xvid encode. Congrats to whoever made it possible guys!..

[Oline 61]

I have no idea why it would crash with the latest versions of everything.

I got the superman trailer to play in the latest Mplayer CVS copmiled specifically for my Athlon 64 3200+ Venice. If I enable caching it looks ok, but is a little jerky. Without caching it is completely unwatchable. So a highly optimized libavcodec decoder can play it on a fast machine. It would probably playback perfectly on an A64 over 2.4ghz or a P4 Prescott over 3.2ghz. The FFDshow libavcodec h264 implementation is just not as fast as MPlayer.

[Yong]

I have the same probs with murattttt too,
i played it with mplayer(cvs built), couldnt render at realtime with p4 2.4ghz... :(
Im not sure these 2 source file files was corrupted
(im lazy to re download again because the download speed is too slow :p ), but the file size show in propeties is about ~8mb(my hd have ntfs compression), although flashget shows its 100% completed...

[Oline 61]

After some tweaking I can play superman at about 32 fps in mplayer on default settings.

[blubberbirne]

Mediaplayer Classic crashed after a few seconds.
Using latest coreavc with haalis media splitter

Cpu is AMD X2 3800+ (think its fast enough *g*)

[Oline 61]

Were there any error messages? Define crashed in this situation.

[murattttt]

Here is a huge error file - Yet I tried to delete the repetitions:
MPlayer dev-CVS-051119-17:07-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices Athlon 64 Newcastle; Athlon 64 X2 Manchester (Family: 15, Stepping: 1)
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
Compiled with runtime CPU detection - WARNING - this is not optimal!
To get best performance, recompile MPlayer with --disable-runtime-cpudetection.

getch2: 6 can't get number of input events [disabling console input]
Playing D:\Documents and Settings\Zoban\Desktop\Superman Returns HDTV.mp4.
Quicktime/MOV file format detected.
--------------
Warning! pts=235339647 length=235443918
MOV track #0: 206 chunks, 2257 samples
MOV: AVC decoder configuration record atom (47)!
MOV: Found unknown movie atom btrt (20)!
Image size: 1920 x 1088 (24 bpp)
Display size: 1920 x 1088
Fourcc: avc1 Codec: ''
--------------
MOV track #1: 207 chunks, 2209 samples
Audio bits: 16 chans: 2 rate: 24000
MOV: Found MPEG4 audio Elementary Stream Descriptor atom (42)!
Fourcc: mp4a
--------------
MOV: longest streams: A: #1 (2209 samples) V: #0 (2257 samples)
VIDEO: [avc1] 1920x1088 24bpp 23.976 fps 0.0 kbps ( 0.0 kbyte/s)
==========================================================================
Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding)
AUDIO: 48000 Hz, 2 ch, s16le, 161.2 kbit/10.49% (ratio: 20149->192000)
Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder)
==========================================================================
Opening video filter: [expand aspect=4/3 round=2]
Expand: -1 x -1, -1 ; -1, osd: 0, aspect: 1.333333, round: 2
Opening video filter: [screenshot=2]
ScreenShot: compression level: 2
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Building audio filter chain for 48000Hz/2ch/s16le -> 0Hz/0ch/??...
AO: [dsound] 48000Hz 2ch s16le (2 bytes per sample)
Building audio filter chain for 48000Hz/2ch/s16le -> 48000Hz/2ch/s16le...
Starting playback...
[Mixer] No hardware mixing, inserting volume filter.
VDec: vo config request - 1920 x 1088 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.76:1 - prescaling to correct movie aspect.
SwScaler: using unscaled Planar YV12 -> BGR 24-bit special converter
Expand filter uninited.
VO: [directx] 1920x1088 => 1920x1088 Planar YV12
aspect: Warning: no suitable new res found!
New_Face failed. Maybe the font path is wrong.
Please supply the text font file (~/.mplayer/subfont.ttf).
subtitle font: load_sub_face failed.
aspect: Warning: no suitable new res found!
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Unexpected fill element with SBR data
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Scalefactor out of range
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change


************************************************
**** Your system is too SLOW to play this! ****
************************************************

Possible reasons, problems, workarounds:
- Most common: broken/buggy _audio_ driver
- Try -ao sdl or use the OSS emulation of ALSA.
- Experiment with different values for -autosync, 30 is a good start.
- Slow video output
- Try a different -vo driver (-vo help for a list) or try -framedrop!
- Slow CPU
- Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
- Broken file
- Try various combinations of -nobps -ni -forceidx -mc 0.
- Slow media (NFS/SMB mounts, DVD, VCD etc)
- Try -cache 8192.
- Are you using -cache to play a non-interleaved AVI file?
- Try -nocache.
Read DOCS/HTML/en/video.html for tuning/speedup tips.
If none of this helps you, read DOCS/HTML/en/bugreports.html.

FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Scalefactor out of range
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Scalefactor out of range
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Channel coupling not yet implemented
FAAD: Failed to decode frame: Quantised value out of range
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Unexpected fill element with SBR data
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Invalid number of channels
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Maximum number of scalefactor bands exceeded
FAAD: Failed to decode frame: Unexpected channel configuration change
FAAD: Failed to decode frame: Gain control not yet implemented
FAAD: Failed to decode frame: Unexpected channel configuration change


MPlayer interrupted by signal 11 in module: decode_video
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.

Maybe it has sth to do with a corrupted download. As I get from the line:
Warning! pts=235339647 length=235443918
I'll download again without flashget.

[Shapierian]

> Maybe it has sth to do with a corrupted download.

can someone post md5sums

[IgorC]

i don't think your FSB is at 400Ghz though ;)

For normal people (even for programmers ) it's only typo's error. But not for electronic technic (for electronic engineer it's even worse :angry: ) ;) . Nothing new

[Yong]

After some tweaking I can play superman at about 32 fps in mplayer on default settings.
tweaking? please tell us the secret. ;)
I want to play hd avc trailer at 32fps with p4 2.4ghz too :p :D

[Oline 61]

I used -march=k8 in gcc when I compiled it. That optimizes for Athlon 64's. I also use -vo null -nousound for benchmarking, so actual playback will be slower. For realtime playback -vo xv and -ao alsa is sufficient on my system. With that setup caching has no effect. Not sure why it did before.

[Yong]

I using -vo null -nosound -benchmark for apple's avc trailer too(720p)
http://www.apple.com/quicktime/guide/hd/bbc-andes.html

Default config:
BENCHMARKs: VC: 137.385s VO: 0.016s A: 0.000s Sys: 2.552s = 139.953s
BENCHMARK%: VC: 98.1651% VO: 0.0114% A: 0.0000% Sys: 1.8235% = 100.0000%

After added some extra cflags:
BENCHMARKs: VC: 133.819s VO: 0.047s A: 0.000s Sys: 2.416s = 136.282s
BENCHMARK%: VC: 98.1927% VO: 0.0345% A: 0.0000% Sys: 1.7728% = 100.0000%

Which one is fps... :p

[Oline 61]

You have to divide the number of frames played by the the seconds at the end of the first line.

[Yong]

Ok thx :)
the bbc-andes trailer have 6444 frames.
The default config for mplayer are :
-fno-PIC -O4 -march=pentium4 -mtune=pentium4 -pipe -ffast-math -fomit-frame-pointer -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

"extra" cflags...:
-mmmx -msse -msse2 -mfpmath=sse
i think the default config already optimal so these extra cflags doesnt help in performance...

i re-benchmark it many time but still got near 139 sec(~44 fps) result :p

[bratao]

I play the file realy nice, with the lastest ffdshow..(btw using Jetaudio, the best player ever to me..)
But not 100%, it resided in player to ~75%

[russo121]

MPlayer interrupted by signal 11 in module: decode_video
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.
[/SIZE]
Maybe it has sth to do with a corrupted download. As I get from the line:
Warning! pts=235339647 length=235443918
I'll download again without flashget.


I've solved the problem by reinstalling directx - directx_feb2006_redist.exe - that you can download from microsoft.:confused:

I still can't play with vlc, but now, I can play with wmp or nero showtime without any problem.

Edit : i can play with mpc also

[Soulhunter]

Smooth playback via MPC (Overlay mode) + CoreAVC on my XP2600+ ^^


Bye

[LoRd_MuldeR]

CoreAVC + MPC + directx_feb2006_redist.exe:
Playback seems to be okay, but CPU usage is still at 95% all the time and everything else is freezing during video playback.

CPU is AthlonXP 2800+

[BlackSharkfr]

i was wondering how you could have reached such a high quality @ only 1600kbps... :confused:

and then i watched the vids again and i saw lots of fades to black, and lots of almost still images and finally a framerate of 23.976 whereas i usually work at 30... ok then i understand why you obtain such i high quality for those trailers....

I usually encode vids from the game Trackmania so it's constant action... having less quality in under those conditions is normal...

By the way, i get some stuttering with my xp2000+, well it's an old cpu, i'm stuck at 100% cpu use.
1080p is too big for me then...

edit :
How do you make your benchmarks ?

[Sagittaire]

1) Movie use always 23.976 or 25 fps for all source. 29.970 fps is only NTSC with telecine process and real framerate for the source is in fact always 23.976 fps.

2) Compressibility for these trailer are the same that 90% usual movie. Video from the game Trackmania are not usual movie source. Generaly compressibility for video game are extremely low ...

[BlackSharkfr]

real framerate for the source is in fact always 23.976 fps.
I didn't know that, i thought it was 24.0 and 23.976 was because of NTSC

Video from the game Trackmania are not usual movie source.
Let's have a try !
I can put exactly the cameras i want, the game features a special shooting feature, i can add motion blur, a special ultra high antialiasing (25x) and use the resolution and framerate i want.

What else whould i need to simulate an HD film source ?
-check that i use realistic camera movements
-motion blur on
-antialiasing 25x
-resolution 1920x1080
-framerate 23.976

[Sagittaire]

What else whould i need to simulate an HD film source ?


Use an HD film source ... :o

Approximatively with same source x264 -crf 28 1920*1088 done same bitrate than XviD -q2 720*400. Generaly for 90% of the real movie XviD -q2 720*400 done [1000-1500] kbps for the bitrate ...

[foxyshadis]

Shifting textures, jerky motion, and nonstop explosions with flying gibs are very common in games but hardly common at all in movies (except vin diesel movies). The constant twitches usually hurt badly even when motion blur, AA, and anistropic are on (if they're off, kiss goodbye to compressing with anything). Even if you're using a 3rd party camera, levels and characters still have lots of sharp edges and misaligned textures (ok, I might be dating myself with this one).

[BlackSharkfr]

Use an HD film source ... :o
I'll get one from te game no problem about that lol

But i was wondering if there were any technical stuff that i need to respect to match the quality of an HD camera.

[BlackSharkfr]

Well i can't use a framerate with decimal numbers so i'll use 25fps.

Don't worry about explosions or flying gibs... it's Trackmania, and the cameras are smooth, the tool is provided by the game developper.
Well you'll see when i'll post the 1080p video (that i won't even be able to watch myself) :)

[Sagittaire]

If you want same quality for your video I use crf 28 for XMenIII encoding and crf 25 for Superman encoding.
x264.exe --bframe 3 --b-pyramid --b-rdo --bime --ref 5 --mixed-refs --filter -1:-1 --crf 26 --pass 1 --stats "x264_stat.log" --qcomp 0.75 --ipratio 1.25 --pbratio 1.33 --analyse "all" --8x8dct --weightb --me "hex" --subme 6 --trellis 1 --progress -o MI3_x264_1080p_3.mp4 Encodage.avs

If you obtain something like 3000 or 4000 Kbps it's simply because compressibility for your source is very low ...

[BlackSharkfr]

i'll compress it with a 2 pass average bitrate of 2000kbps i think we'll see the quality it gives.

mmmm i've got some trouble shooting in 1088p... there's a probleme somewhere but if i don't find how to solve it i may need to use a smaller resolution (720p?)

[BlackSharkfr]

i couldn't use 1088p :( there was some kind of rendering issue, a friend on trackmania forums said he could do it so i guess it's a driver bug (i downloaded the one from nvidia that supports h264 hardware acceleration, but it's beta)
So here's the 720p file. http://blacksharkfr.free.fr/tm/HQ%20test%20TM-ESWC%20720p.mp4
I doesn't compress as well as a movie, but it's probably because of the constant actions... there are no dialogues with few movements...

[Sagittaire]

free http is very low actually ... :mad:
free is very low actually ... lol

[vio_man]

I got a MPC crash when using CoreAVC Dshow filter to watch the Superman trailer (at the final part of the trailer).

[asegura]

What is wrong with these files?
Just a tiny black image and MPC hangs.

I have the latest MPC and ffdshow, but the latter is not even loaded, instead a Nero Video Decoder filter is loaded by MPC (all other H264 in AVI or MP4 is correctly handled by ffdshow).

MPC identifies the A/V streams as "GPAC" (???):

Video: MPEG4 Video (AVC) 1920x1088 [GPAC ISO Video Handler]
Audio: AAC 24000Hz stereo 161Kbps [GPAC ISO Audio Handler]

and so are sent to Nero Decoder instead of ffdshow.

How were these files encoded? (I never had problems with AVC content, even Nero film trailer samples play correctly with MPC and ffdshow).

[xmltok]

plays very well with vlc nightly intel build and 2.16ghz macbook pro