Issue 29 in flvmeta: Create a library version

3 views
Skip to first unread message

flv...@googlecode.com

unread,
Mar 12, 2010, 12:02:51 PM3/12/10
to flvme...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 29 by michael.pliskin: Create a library version
http://code.google.com/p/flvmeta/issues/detail?id=29

It would be cool if flvmeta had a library version to link with - would be
much easier to re-use the code in other projects (have one in mind atm).
Probably splitting into the library and a command-line driver could make
some sense.. At least the code to read/write AMF is extremely valuable.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

flv...@googlecode.com

unread,
Mar 12, 2010, 12:06:57 PM3/12/10
to flvme...@googlegroups.com

Comment #1 on issue 29 by michael.pliskin: Create a library version
http://code.google.com/p/flvmeta/issues/detail?id=29

Not a defect but feature request for sure, and probably enhancement - just
cannot
change here..

flv...@googlecode.com

unread,
Mar 12, 2010, 12:22:30 PM3/12/10
to flvme...@googlegroups.com
Updates:
Status: Accepted
Owner: marc.noirot
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

Comment #2 on issue 29 by marc.noirot: Create a library version
http://code.google.com/p/flvmeta/issues/detail?id=29

I've been thinking about that, too, since I'm planning to do a GUI version
of flvmeta, which would benefit a lot
from using the functions from flvmeta, instead of simply being a wrapper.
Anyways, it makes sense from a developer stand point.

For the moment, if you're interested in the AMF code exclusively, there's
the libamf project that I created on
sourceforge, which is a spinoff from flvmeta where I'm intending to fully
support AMF0 as well as AMF3, eventually
in order to remove the legacy code from flvmeta and use that one instead.
It's far from being ready for production use yet, but it compiles and calls
for unit tests creation.

For the rest of the flvmeta code, I might separate the main frontend code
from what I will call libflv, code to read
and write flv files, and to deal with common issues related to that file
format.
Flvmeta now uses that code in the form of a nice callback-based parser,
showcased in the dumping functions.

flv...@googlecode.com

unread,
Mar 16, 2010, 5:16:50 AM3/16/10
to flvme...@googlegroups.com

Comment #3 on issue 29 by michael.pliskin: Create a library version
http://code.google.com/p/flvmeta/issues/detail?id=29

Thanks a lot Marc for the detailed reply, I need AMF only so far, so will
take a look
to libamf - that sounds like a good idea, thanks again!

flv...@googlecode.com

unread,
Jul 21, 2012, 9:44:52 AM7/21/12
to flvme...@googlegroups.com
Updates:
Status: WontFix

Comment #4 on issue 29 by marc.noi...@gmail.com: Create a library version
http://code.google.com/p/flvmeta/issues/detail?id=29

A `libflv` will certainly be useful, but it does not make sense in the
context of this project yet.

Reply all
Reply to author
Forward
0 new messages