Comments on: A Problem and Solution for FLV Metadata Injectors and the Maximum Duration of FLV Videos

By: Rodrigo Polo

Rodrigo Polo — Thu, 24 Sep 2009 04:39:25 +0000

Where I can find a win32 build or any build for the FaceBook flvtool++?

By: Daniel Latorre

Daniel Latorre — Mon, 14 Sep 2009 08:19:01 +0000

Hi, I’ve experimented exactly the same problem. Somehow, my it’s a little more hard to fix for me because I’m working with a sequence of movies. I has some little movies (each movie has 10 seconds aprox.). A XML file say to flash wich movie and how long must be played and flashplayer plays that sequence. It never stops and it must be hours playing that sequence. So, after 4h 30minutes flashplayer’s sound and video becomes crazy. There’s no error messages on my system so I can ensure that it’s flashplayer’s cause. And if you turn off and then turn on the fullscreen mode, it works fine again.

As you said, flashplayer has a counter from 0 to 16777990. Would’nt that counter be reset to 0 when I’m reading a new movie? How could I force reset the counter? It seems to be possible to reset it because I think that it’s what fullscreen does. I’m clearing all variables I know without any success.

As you would see, I cannot set TimeStampExtended… I’m working with XML files!

Any help will be great. Thank you in advance.

PD: I’m so sorry for my english, I’m spanish and my english suck’s!

By: Keith

Keith — Sun, 21 Jun 2009 00:32:37 +0000

Hey, I’m not exactly like you guys here – not programmer but I just like the flv. format. Just wanted to say I had same issue with large files till I stumbled unto “yamdi.” It stands for Yet Another MetaData Injector and it does what the author of this article asks – works for files greater than 800MB. It addes the correct time duration for files greater than 4 hrs. It is literally a simple command line. Also its pretty fast, I’m pretty sure its alot faster than “flvmdi.” Check him pretty cool – especially for newbies. http://yamdi.sourceforge.net/

By: Christian

Christian — Sun, 07 Jun 2009 09:48:58 +0000

@George
Sorry, I completely forgot that you have to put the h264 in a flv container first!
Here’s the complete stanza to cheat h264 content into a flv container with metadata:

ffmpeg -i in.mp4 -f flv -vcodec copy -acodec copy intermediate.flv
flvtool++ -nomerge -tag framerate “25.000000″ \
-tag videocodecid “avc1″ -tag audiocodecid “mp4a” \
-tag audiosamplerate “22050.000000″ -tag stereo “false” \
-tag width “320.000000″ -tag height “240.000000″ \
intermediate.flv out.f4v

By: Christian

Christian — Sun, 07 Jun 2009 09:13:09 +0000

@George:

I succeeded by means of forcing a few tags. Example:

flvtool++ -nomerge -tag framerate “25.000000″ \
-tag videocodecid “avc1″ -tag audiocodecid “mp4a” \
-tag audiosamplerate “22050.000000″ -tag stereo “false” \
-tag width “320.000000″ -tag height “240.000000″ \
in.mp4 out.f4v

By: Marc

Marc — Tue, 21 Apr 2009 22:30:36 +0000

I think I will implement cuePoint insertion in flvmeta1.1, that feature has been asked more than often.

By: George Gardiner

George Gardiner — Sat, 28 Mar 2009 21:38:00 +0000

Does anybody know what happens with really long videos encoded in the FLV container using h.264. After reading through the specs I see a problem with the fact that the AAC Composition Time is still only 24 bits, and features no extended time stamp.

I am in the process of writing a meta injector for live content streamed using h.264 to Flash… Guess I’ll find out in 3 hours or so when I get back from the pub

By: Haribo

Haribo — Fri, 13 Mar 2009 09:40:49 +0000

Hello,

Does anybody know a Linux CLI tool to inject onCuePoint events in existing FLV files ?
flvtool2 seems to be the only one but it’s really too sloooow.
yamdi or flvmeta are great but they don’t support this feature.

Thank you.

By: Robert M. Hall, II

Robert M. Hall, II — Tue, 10 Mar 2009 05:12:58 +0000

Ahh – the test files were pretty much designed so that they would be small in size for testing this specific bug/issue. The original 4 hour video with real content at 640×480 was indeed well over a gigabyte in size. The only thing I can suggest is to lower your bitrate, framerate, keyframes and width/height dimensions as low as you can tolerate for your needs, and used either On2-VP6 or H.264 – those are the parameters you’ll need to compromise on in one way or another to get a smaller file. Also, you mentioned you are getting them in MPEG-2 format. If you can get a copy straight from either the film source, or in a CODEC that is lossless or hasn’t already been through a lossy process (Apples 422, or uncompressed 10bit, similar CODECS), you’ll get a better cleaner encode that should encode a slight amount smaller since it would have less artifacts interfering with the encode process of the target CODEC.

By: Jyotsna

Jyotsna — Mon, 09 Mar 2009 20:06:14 +0000

Hey there,

Glad to have found you . I also plan to serve humongous files through BG. But the thing I am most impressed is how you got an 8hr file to 1.4 GB. Was that the On2 magic ? I have 90 min files that clock in at 1 GB when encoded in MP4. The source files I get are in MPEG-2 format and tend to be even larger, at about 4GB – 7 GB

Thanks for any leads you can give me.