[FFmpeg-devel] [PATCH] libmodplug wrapper

Michael Niedermayer michaelni
Mon Jul 13 10:31:19 CEST 2009


On Sun, Jul 12, 2009 at 11:57:07PM +1000, Peter Ross wrote:
> On Sat, Jul 11, 2009 at 04:27:23AM -0700, Baptiste Coudurier wrote:
> > Hi Peter,
> >
> > On 07/11/2009 02:38 AM, Peter Ross wrote:
> >> On Sat, Jul 11, 2009 at 06:11:29AM +0300, Kostya wrote:
> >>> On Sat, Jul 11, 2009 at 02:04:08AM +0200, Michael Niedermayer
> >>> wrote:
> >>>> On Fri, Jul 10, 2009 at 01:24:27PM +0000, Jai Menon wrote:
> >>> [...]
> >>>> The primary reason for the seperation in this case is so we can
> >>>> watch avi/mkv/nut files that have h264 video and mod/s3m/...
> >>>> audio
> >>> Err, you can legally kill anybody trying to make such perverted
> >>> format (i.e. Matroska devs).
> >>
> >> My reaction is completely the opposite.
> >>
> >>>> From my experience (several MOD-like and Adlib tracker formats in
> >>>> DOS
> >>> times), you can represent tracker as two parts: samples and notes.
> >>> For a bit modern people - like MIDI file with its own soundfont. So
> >>> usually you have hundreds of kilobytes or more of samples (which
> >>> may be treated as extradata) and less than 1KB of notes which
> >>> define what to play. Also notes are grouped into patterns and
> >>> subpatterns which may be repeated certain number of times, with
> >>> speed changes that results in each part playing time very greatly
> >>> varying. This makes it an awful sound format for generic
> >>> container.
> >>
> >> This suggests to me that FFmpeg's generic container format isn't
> >> generic enough.
> >
> > I don't recall FFmpeg having a generic container format. What do you
> > have in mind ?
> 
> What I intended to say that the current libavformat/libavcodec API
> targets the use of "generic container formats" comprising streams
> and time-stamped packets.
> 
> MOD-files do not adhere to this generic format. They contain
> instrument samples, patterns, and a pattern ordering table.

There are 2 ways to map mod to ffmpegs system,
1. instrument samples & patterns are extradata, pattern ordering are packets

2. instrument sampes are extradata, patterns are packets and the mod muxer
   would compress patterns using pattern ordering tables

to me these look like quite reasonable, ffmpeg or not. If one would want to
stream such a file, that is global headers and multicasted packets (that is
no feedback) one would even without ffmpegs API end at this very same thing,


[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No great genius has ever existed without some touch of madness. -- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20090713/7cb2a1b7/attachment.pgp>



More information about the ffmpeg-devel mailing list