Re: [Lmuse-developer] parts has to go

[Florian J. <flo...@we...>]

Am 15.06.2012 11:31, schrieb Geoff Beasley:
> On 06/15/2012 09:01 AM, Florian Jung wrote:
>> my take is that essentially they are all the same things anyway.
>>
>> Point 1 :  a track is a given - that is ; EVERYTHING in muse is a track.
>> well, it shouldn't be. internally, this might be true.
>>
>> but a synth is simply not a track. at least not in most users' perception.
> 
> 
> add a softsynth in muse and you get a track. period. that's how muse is.

eek! imho, not the user shall adopt to muse. muse shall adopt to the user.

it's not "this is how it is, user, deal with it!", but it's "this is how
the user wants it, developer, deal with it!". at least if we're making
software for users, not four ourselves alone (yes, there is a discrepancy)

i just think: 99% of the people think in categories "there are various
things which share some commonities", but only 10% additionally think in
OOP "there are some commonities and then there are different things with
them".

> and now with automation available and Rob's show/hide switch that's a 
> good thing. it's just unique to muse2 that everything has a track 
> associated with it - even if no data is shown on the timeline. normally 
> this would be handled within a mixer, same as plugins, inputs,aux busses 
> etc. to this degree the mixer is inadequate.
> 
>> no! a track contains music, which is organized in (currently) parts. for
>> a user, these are not objects. these are music.
> 
> No they do not. In muse a track can be an audio Input, and Aux bus, a 
> softsynth..etc.. none of which by themselves contain music at all !

i mimiced the average user. and from a non-muse's point of view, a synth
IS NOT a track. even if it's implemented like that...

i mean, you are connecting memory sticks and USB mice to your computer.

when you have to group "USB mice, serial mice, USB storages, SATA
harddisks", most users would put "USB mice, serial mice" together, and
"USB storages, SATA disks" together. because what matters is _what they
do_ (control mouse movement vs store data), not _how they work_
(connection via USB vs connection via RS232 vs connection via SATA).



> 
> this is what i'm talking about...  tracks contain DATA in CONTAINERS and 
> what they contain is not always musical anyway! -  controllers for example.
good point. but they never contain "abstract stuff". _even_ if muse
would support that. for an (average) user, they always contain something
concrete. like "music plus controllers".


> 
> in daws we stream data. not all data contains music. in muse we are 
> forced to have tracks for every form of I/O. to say that tracks contain 
> music, just isn't correct.

i think, we mostly have an argument about top-down or bottom-up; that
is, "base class and specialisation" or "lots of (an OOP-progammer would
call them 'derived') things and generalisation/categorisation)".

> 
> but you know, i'm not going to spend any more time on this thread. i 
> said my piece and hope it has been useful.
true thing, this is going to be a flame thread ;)

greetings
flo

> 
> good luck with the manual boys.
> 
> best
> 
> g
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Lmuse-developer mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-developer
>