Flash Player to include AVC and AAC and MP4 and TTXT support

[Blue_MiSfit]

@Smok3

What x264 settings did you use?

Are there any indication as to which profile specific features are supported - ie 8x8 DCT, CABAC, B-Frames etc?

~MiSfit

[slavickas]

to those lazy to check themself in hex editor/viewer

x264 - core 54 - H.264/MPEG-4 AVC codec - Copyleft 2005 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=1:4:0 analyse=0x1:0x111 me=hex subme=5 brdo=0 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 chroma_qp_offset=0 slices=4 nr=0 decimate=1 mbaff=0 bframes=2 b_pyramid=0 b_adapt=0 b_bias=0 direct=1 wpredb=0 bime=0 keyint=150 keyint_min=25 scenecut=40 rc=2pass bitrate=1600 ratetol=1.0 rceq='blurCplx^(1-qComp)' qcomp=0.60 qpmin=10 qpmax=51 qpstep=4 cplxblur=20.0 qblur=0.5 ip_ratio=1.40 pb_ratio=1.30

[Placio74]

Originally Posted by slavickas

to those lazy to check themself in hex editor/viewer

Or Avinaptic.

[ About file ]

Name: opr0Q3FN.mp4
Date: 22/08/2007 08:33:04
Size: 50,965,091 bytes (48.604 MB)

[ Generic info ]

Play duration: 00:03:59 (239.28 s)
Container type: MP4/MOV
Major brand: ISO Base Media version 1
Creation time: 17/08/2007 00:44:39 UTC
Modification time: 17/08/2007 00:44:43 UTC
Number of streams: 2
Type of stream nr. 1: audio (mp4a) {pple Sound Media Handler}
Type of stream nr. 2: video (avc1) {pple Video Media Handler}
Audio streams: 1

[ About quality ]

Resolution: VERY HIGH (1280 x 720)
Width: multiple of 16 (GOOD)
Height: multiple of 16 (GOOD)
Average DRF quality: LOW (28.389053)
Standard deviation quality: HIGH (2.737534)
Std. dev. weighted mean: HIGH (2.558997)

[ Video track ]

Codec: avc1
Resolution: 1280 x 720 (*)
Frame aspect ratio: 16:9 = 1.777777
Pixel aspect ratio: 1:1 = 1
Display aspect ratio: 16:9 = 1.777777
Framerate: 23.976 fps
Number of frames: 5737
Bitrate: 1603.275462 kbps

[ Audio track ]

Codec: mp4a
Bitrate: 96.149661 kbps
Channels: 2
Sample rate: 44100 Hz

[ About H.264 encoding ]

User data: x264
User data: core 54
User data: H.264/MPEG-4 AVC codec
User data: Copyleft 2005
User data: http://www.videolan.org/x264.html
User data: cabac=0
User data: ref=1
User data: deblock=1:4:0
User data: analyse=0x1:0x111
User data: me=hex
User data: subme=5
User data: brdo=0
User data: mixed_ref=0
User data: me_range=16
User data: chroma_me=1
User data: trellis=0
User data: 8x8dct=0
User data: cqm=0
User data: deadzone=21,11
User data: chroma_qp_offset=0
User data: slices=4
User data: nr=0
User data: decimate=1
User data: mbaff=0
User data: bframes=2
User data: b_pyramid=0
User data: b_adapt=0
User data: b_bias=0
User data: direct=1
User data: wpredb=0
User data: bime=0
User data: keyint=150
User data: keyint_min=25
User data: scenecut=40
User data: rc=2pass
User data: bitrate=1600
User data: ratetol=1.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: cplxblur=20.0
User data: qblur=0.5
User data: ip_ratio=1.40
User data: pb_ratio=1.30
SPS id: 0
  Num ref frames: 2
PPS id: 0
  Entropy coding type: CAVLC
  Weighted prediction: No
Number of frames: 5737
Drop/delay frames: 0
Corrupted frames: 0

P-slices: 2053 ( 35.785 %) #########                
B-slices: 3622 ( 63.134 %) ################         
I-slices:   62 (  1.081 %)                          
SP-slices:    0 (  0.000 %)                          
SI-slices:    0 (  0.000 %)                          

[ DRF analysis ]

Average DRF: 28.389053
Standard deviation: 2.737534
Max DRF: 35

DRF<20:   0 (  0.000 %)                          
DRF=20:   7 (  0.122 %)                          
DRF=21:  16 (  0.279 %)                          
DRF=22:  19 (  0.331 %)                          
DRF=23: 133 (  2.318 %) #                        
DRF=24: 221 (  3.852 %) #                        
DRF=25: 453 (  7.896 %) ##                       
DRF=26: 738 ( 12.864 %) ###                      
DRF=27: 637 ( 11.103 %) ###                      
DRF=28: 885 ( 15.426 %) ####                     
DRF=29: 608 ( 10.598 %) ###                      
DRF=30: 555 (  9.674 %) ##                       
DRF=31: 569 (  9.918 %) ##                       
DRF=32: 546 (  9.517 %) ##                       
DRF=33: 198 (  3.451 %) #                        
DRF=34: 128 (  2.231 %) #                        
DRF=35:  24 (  0.418 %)                          
DRF>35:   0 (  0.000 %)                          

P-slices average DRF: 27.172430
P-slices std. deviation: 2.635232
P-slices max DRF: 34

B-slices average DRF: 29.121479
B-slices std. deviation: 2.503479
B-slices max DRF: 35

I-slices average DRF: 25.887096
I-slices std. deviation: 3.278005
I-slices max DRF: 33

This report was created by AVInaptic (10-04-2007) on 22 ago 2007, h 08:57:01

[smok3]

Blue_MiSfit: lowb and highb are quicktime compatible, the ipodlike is the easiest one:

namely, qt:
x264.exe --pass 1 --bitrate %bit% --stats "%inpfullnoext%.stats" --bframes 1 --subme 1 --analyse none --me dia --progress --no-psnr --filter %fil% --output NUL

and ipod:
x264.exe --pass 1 --bitrate %bit% --stats "%inpfullnoext%.stats" --level 1.3 --no-cabac --subme 6 --analyse p8x8,b8x8 --qpmin 16 --vbv-maxrate 768 --vbv-bufsize 244 --me umh --merange 12 --threads auto --thread-input --progress --no-psnr --no-ssim --output NUL

[bond]

Originally Posted by Sergey A. Sablin

Is it you bond? Something strange happens to you...
Have a try to open stream in hex editor. You should know key word.

man

shouldnt be that fast with my conclusions
guess they remuxed the stream with quicktime?

[Corben9]

For the laziest of us a profile for MeGui vould be nice

[Corben9]

I made a demo in a skate edit i recently made under

http://www.studioc9.com/CevapiSession

under the HD version. Now it all works nicelly locally but form the server for some odd reason it does not ... Now as i understood it the file should start playing progressivey .. since i encoded the entier thing in 720p 4Mbit it is a rather high bitrate but nothing fast net shouldnt be able to handle... now the file is 20 min long so i was counting on the progressive downlaod and playback.... but it aint working.... I tried a few other test files and it waried form working to not working

id like some oppinions ... id really like to keep the h264 version in prestine quality ,

[Hellworm]

If you use progressive download instead of FMS make sure that the moov atom (which is the index information in MPEG-4 files) is at the beginning of the file. Otherwise you have to wait until the file is completely downloaded before it is played back.

http://www.kaourantin.net/2007/08/wh...on-web_20.html

[Corben9]

Jup I think thats the problem right now since i muxed the file in MeGUI .. i made another mux with MP4Box coz its supposed to put the moov at the start even by default ... Am I correct?

[Schrade]

Yeah, in YAMB 2.0.0.7 it's checked by default I believe.

[bond]

Originally Posted by Corben9

Jup I think thats the problem right now since i muxed the file in MeGUI .. i made another mux with MP4Box coz its supposed to put the moov at the start even by default ... Am I correct?

megui is "just" the gui. important is what the tools used in the background do:
1) x264 is a video encoder writing the video stream info directly into the mp4. doing so the header will be written at the end of the mp4, as the header is only known at the end of encoding
2) for muxing the video with audio mp4box is used in megui. mp4box writes the header at the beginning of the file with the default settings

therefore your mp4 should already have the header at the start. you can check this by running the mp4dump tool from mpeg4ip over the file. if the moov atom (the headers) is placed before the mdat atom (the plain video data) your header is at the start

edit: are you trying to stream this file:
http://www.studioc9.com/CevapiSession/CevapiSession.mp4

if yes, this seems to be borked. how exactly did you produce this?

[Corben9]

hej ! At the time u wrote the post i was just upoading the version I muxed via comandline on mp4box.

I produced it as follows>

Adobe Premiere for editing cuting ect exported as m2t hdv compliant transport stream so i can back up my master on tape.

then I unmuxed the m2ts with DGindex

Then using a avisnyth script and the Tdent and Spline36resize comand I had it frameserved to megui where i encoded at 25 fps High level x264 in mp4 at 4 Mbit bitrate .. no extra settings applied just standard high profile with 4 Mbit 3 pass encoding...

I also transcoded the audio in megeui with Winamp AAC ... then i muxed everything with the megeui mux tool and now again manually with MP4Box...

I also thought that it might be player related so i set manual buffer parameters but that didnt help eitehr...

I also tried to play it directly form the web with vlc it also transfers data but the screen stays black

can u please check the file and see if its ok im doing another upload coz the file might have gotten corrupted while upoading via FTP *gonna be up in like an hour*... it still doesnt work from the server but locally it plays fine over flash and VLC but it doesnt seem to work in Quicktime .. i still think that its a moov atom related issue but honestly I just dont know anymore...

If its borked and i have to encode again what settings should i use to make sure its compliant ... ?

[bond]

Originally Posted by bond

edit: are you trying to stream this file:
http://www.studioc9.com/CevapiSession/CevapiSession.mp4

if yes, this seems to be borked. how exactly did you produce this?

are we talking about this file? this one is borked

try encoding the aac with faac or nero or quicktime and mux the resulting audio and your video to a new mp4 (so do not mux one of the streams to an already existing mp4)

[Schrade]

Is there some way to detect if a file has its media information indexed at the beginning or not?

[bond]

Originally Posted by bond

therefore your mp4 should already have the header at the start. you can check this by running the mp4dump tool from mpeg4ip over the file. if the moov atom (the headers) is placed before the mdat atom (the plain video data) your header is at the start

here it goes

[Schrade]

Woops! Missed that. Thanks, bond. I was up really late last night when I first read your post where you said that. Thanks for pointing it out to me.

Is there some benefit for putting the moov atom after the mdat one? Why not just have all files with the moov first?

I tried it with QuickTime Atom Viewer and it works! Thanks for the tip on what to look for.

Here's standard Avidemux output, won't stream:


And here's an MP4 that will stream:

[Corben9]

Originally Posted by bond

are we talking about this file? this one is borked

try encoding the aac with faac or nero or quicktime and mux the resulting audio and your video to a new mp4 (so do not mux one of the streams to an already existing mp4)

Sorry to bug again and for been such a noob ... i have a version up now that should have the moov atom at the start and it works localy and over my home network if is stream it to anther comp... but it wont work form the server .. can u please check it .. its at the same place as before

http://www.studioc9.com/CevapiSession/CevapiSession.mp4

And another question regarding reencoding... when I encode the video to x264 what to you mean exactly with dont mux the aac to an already existing mp4?

Here is a screenshot from the begining of the file:


It looks rather different form the one Shrade posted that does stream... question remains how to edit the header to make it work ?

[Schrade]

You need to remux it into an MP4 again using YAMB 2.0.0.7. Make sure the option I showed in my post with the YAMB picture is checked.

I just checked and your moov atom is below the mdat one, it needs to be before it.

[Corben9]

I remuxed it again with all the options and checked, and the moov atom is still at the complete end of the file ... i really don't know why ... anyone know a way to manually move it or select the order they should be applied with .???

I find it odd since the options are turned on and it doesn't move it to the begining .. id really like a way to control these tags

[Hellworm]

On this page that was posted several times in this thread is a link to a program that does only move the atom to the beginning.