[Ffmpeg-devel] Call for volunteers to write NUT de/muxer for libavformat

Oded Shimon ods15
Thu Nov 2 22:25:30 CET 2006


On Thu, Nov 02, 2006 at 10:16:43PM +0100, Michael Niedermayer wrote:
> Hi
> 
> On Thu, Nov 02, 2006 at 02:57:22PM -0500, Rich Felker wrote:
> > On Tue, Oct 31, 2006 at 11:52:50PM +0100, Michael Niedermayer wrote:
> > > Hi
> > > 
> > > On Tue, Oct 31, 2006 at 02:33:34PM -0800, Mike Melanson wrote:
> > > > Oded Shimon wrote:
> > > > >What does Hachoir mean? And what do you mean by standalone parser? libnut 
> > > > >is already a standalone demuxer. A de/muxer for libavformat is necessary.
> > > > 
> > > > Check hachoir.org -- a neat framework for parsing file formats for 
> > > > studying and other purposes.
> > > > 
> > > > >Make them yourself from either ogg vorbis files or mpeg-4+mp3+avi files 
> > > > >using nutmerge - svn co svn://svn.mplayerhq.hu/nut/
> > > > 
> > > > Is it too much to ask for you to mux some simple sample files and make 
> > > > them available on samples.mplayerhq.hu? They must have several megabytes 
> > > > free for this type of thing. I get a lot more interested in new formats 
> > > > when I can study actual samples. And I'm extremely lazy and hate making 
> > > > my own samples.
> > > 
> > > i fully agree, we should have some nut samples
> > > someone (not me iam lazy) should mux some free video and audio into nut
> > > (or just grab a camera and film something funny like what happens with
> > > an egg in the microwave or something else where AV synch can be seen)
> > 
> > Yes, a couple small issues tho:
> > - Oded needs to fix nutmerge to use correct fourcc for mp3, not twocc
> > crap. :)
> > - It's possible that we could find implementation bugs causing samples
> > not to be strictly valid. I wonder if it would be too hard to make
> > 'nutlint' to test samples before we bless them as official..?
> 
> hmm, IMHO even if samples are not totally correct its still better to
> have some then have none ... we could call them draft samples or so
> also we should definitly say very clearly that we should be contacted
> if anyone notices during (de)muxer development that there are some
> bugs in our reference samples (or reference implementation or spec)

Actually, it wouldn't matter anyway because they still hold NUT version 2, 
so they are not legal for anything except testing, as specified by the 
spec... So, if anyone is up for it, feel free to use nutmerge or this 
lavf-libnut patch to create NUT samples and put them up somewhere...

- ods15
-------------- next part --------------
Index: Makefile
===================================================================
--- Makefile	(revision 6840)
+++ Makefile	(working copy)
@@ -62,6 +62,8 @@
 EXTRALIBS+=-lswscale$(BUILDSUF)
 endif
 
+EXTRALIBS += ../nut/libnut/libnut.a
+
 all: lib $(PROGS_G) $(PROGS) $(PROGTEST) $(VHOOK) $(QTFASTSTART) $(DOC)
 
 lib:
Index: libavformat/Makefile
===================================================================
--- libavformat/Makefile	(revision 6840)
+++ libavformat/Makefile	(working copy)
@@ -4,7 +4,7 @@
 #
 include ../config.mak
 
-CFLAGS+=-I$(SRC_PATH)/libavcodec
+CFLAGS+=-I$(SRC_PATH)/libavcodec -I../../nut/libnut
 
 OBJS= utils.o cutils.o os_support.o allformats.o
 
@@ -77,8 +77,8 @@
 OBJS-$(CONFIG_MPJPEG_MUXER)              += mpjpeg.o
 OBJS-$(CONFIG_MXF_DEMUXER)               += mxf.o
 OBJS-$(CONFIG_NSV_DEMUXER)               += nsvdec.o riff.o
-OBJS-$(CONFIG_NUT_DEMUXER)               += nut.o riff.o
-OBJS-$(CONFIG_NUT_MUXER)                 += nut.o riff.o
+OBJS-$(CONFIG_NUT_DEMUXER)               += libnut.o riff.o
+OBJS-$(CONFIG_NUT_MUXER)                 += libnut.o riff.o
 OBJS-$(CONFIG_NUV_DEMUXER)               += nuv.o riff.o
 OBJS-$(CONFIG_OGG_DEMUXER)               += ogg2.o           \
                                             oggparsevorbis.o \
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libnut.c
Type: text/x-csrc
Size: 9107 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20061102/dee99fe5/attachment.c>



More information about the ffmpeg-devel mailing list