[FFmpeg-soc] [soc] libavsequencer [PATCH 01/08] Music module public API header file.

[Sebastian Vater]

Ronald S. Bultje a écrit :
> Hi,
>
> On Tue, Jul 13, 2010 at 5:55 PM, Sebastian Vater
> <cdgs.basty at googlemail.com> wrote:
>   
>> That's clear! Just want to mention the point, that the user today
>> expects the feature of having multiple (in this case modules) files
>> opened at once and thus editing them. We're not anymore in the eighties
>> were it was common just to have one file opened at the same time.
>>
>> So I thought of a way of allowing the user exactly that, that's why I
>> plan to add multiple modules to AVSequencerContext. The programmer
>> developing the GUI has to take care of this list though mostly by itself.
>>
>> To draw all this as a tree, I would do it the following way (AVSequencer
>> is abbreviated simply lavs):
>> lavsContext:
>>    1.  list of lavsModule ->
>>         1.1. list of lavsSongs (sub-songs)
>>    2. list of lavsInstruments (all instruments shared between sub-songs).
>>    3. Same for envelopes, etc.
>>
>> lavsSongs of course descendends to order list and track data.
>> lavsInstruments descend to samples, which descend to synths each.
>>     
>
> Why not open a new lavsContext per file? That's what libswscale does,
> for example. And which structure is BSS in this schematic?
>   

Would be possible, too. But I did a small mistake in my tree, see my
latest mail on this. Ok, after sending this one, the mail I meant is the
2nd latest. ;)

Just thought that it would be more conclusive to have all the opened
modules in one lavsContext.

Sorry I'm probably still thinking a bit too much on TuComposer's terms.
There lavsContext was the equivalent of TuComposer's base library which
managed everything.

-- 

Best regards,
                   :-) Basty/CDGS (-: