linuxaudio.org

--20cf307f3be26f9f8104bc5f34e8

Content-Type: text/plain; charset=ISO-8859-1
2012/3/29 Louigi Verona 
> my 2 cents from user perspective: I know where I save my files, I know

quoted text
> where my sample collections are. i know that if i delete my sample

> collection, sessions won't load. i don't need any program to tell me

> that.

>

> in fact, in using FL Studio or Cubase or LMMS you have the same

> situation. a project can use same files as another project and if you

> damage those files - well, sorry.

>

> I do not see any reason for complications in session manager design. i

> agree with david, all of this is unnecessary and only will make NSM a

> session manager developers would be reluctant to adopt.

>

> louigi verona.

>

> On 3/29/12, rosea.grammostola  wrote:

> > On 03/24/2012 11:09 PM, Fons Adriaensen wrote:

> >

> >>

> >> 3. Clearly defining the way an app should behave w.r.t. its

> >>     File menu entries (when managed). This is quite intrusive

> >>     to existing clients, but it is IMHO absolutley essential.

> >>     Kudos to the designer(s) for the having the courage to do

> >>     this instead of allowing application developers to take

> >>     the 'least effort' way (which would of course be better

> >>     marketing, but invite later misery).

> >

> > How easy or how difficult is it compared to JackSession for example, to

> > add NSM support to an application?

> >

> > Is it possible to have NSM and JackSession support in one application?

> >

> > Regards,

> >

> > \r

>

wasnt there a link somewhere in this mail thread about a comparison of all

the pros and cons of 'all' SM's ?

i went trough the thread but could not find it  :-(

ah well, maybe i'm just dreaming

would be nice though, such a comparison matrix
follow me on my Audio & Linux blog  !
--20cf307f3be26f9f8104bc5f34e8

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
2012/3/29 Louigi Verona <louigi.verona@gmail.com>
my 2 cents from user perspective: I know where I save my files, I know

where my sample collections are. i know that if i delete my sample

collection, sessions won't load. i don't need any program to tell m=

e

that.
in fact, in using FL Studio or Cubase or LMMS you have the same

situation. a project can use same files as another project and if you

damage those files - well, sorry.
I do not see any reason for complications in session manager design. i

agree with david, all of this is unnecessary and only will make NSM a

session manager developers would be reluctant to adopt.
louigi verona.
On 3/29/12, rosea.grammostola <rosea.grammostola@gmail.com> wrote:

quoted text
> On 03/24/2012 11:09 PM, Fons Adriaensen wrote:

>

>>

>> 3. Clearly defining the way an app should behave w.r.t. its

>> =A0 =A0 File menu entries (when managed). This is quite intrusive<=

br>

quoted text
>> =A0 =A0 to existing clients, but it is IMHO absolutley essential.<=

br>

quoted text
>> =A0 =A0 Kudos to the designer(s) for the having the courage to do<=

br>

quoted text
>> =A0 =A0 this instead of allowing application developers to take

>> =A0 =A0 the 'least effort' way (which would of course be b=

etter

quoted text
>> =A0 =A0 marketing, but invite later misery).

>

> How easy or how difficult is it compared to JackSession for example, t=

o

quoted text
> add NSM support to an application?

>

> Is it possible to have NSM and JackSession support in one application?=

>

quoted text
> Regards,

>

> \rwasn=

t there a link somewhere in this mail thread about a comparison of all the =

pros and cons of 'all' SM's ?i went trough the threa=

d but could not find it =A0:-(

ah well, maybe i'm just dreamingwould be nice though, s=

uch a comparison matrix=A0follow me on =

my=A0Aud=

io & Linux blog !
--20cf307f3be26f9f8104bc5f34e8--