om-synth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Om-synth] om-synth: improving usability


From: Antonio
Subject: Re: [Om-synth] om-synth: improving usability
Date: Sun, 30 Oct 2005 09:50:44 +0100

Hi Dave,

2005/10/30, Dave Robillard <address@hidden>:
> > On om_gkt:
> > * When saving a session I think would be useful to save the jack and
> > midi connections too. Not all the jack and midi connections, of
> > course, but only those connecting to, from or between om's patches. So
> > lashd it's not required if one uses om only to play some patch.
>
> No.  Om is not a patch bay, and this is a horrible idea for numerous
> reasons.

Can I ask you to argument a bit more on this please?

> I think the idea of "session" is going to go away completely in Om
> actually, in favour of just saving everything in a patch.  Session is an
> unecessary arbitrary layer I now realise.

I agree, but sometimes can be really useful IMHO, and if you don't use
it, it doesn't hurt.

> > On lash_panel:
> > * Should be possible to open a session, make some modifications
> > starting from there and then save a new session without deleting the
> > old session. The current way of deleting the old session on rename
> > makes very laborious to create a set of similar sessions, because one
> > has to create from scratch every session or manually copy the
> > directory of one session and them one and modify the copy.
>
> This entire area needs to be looked at.  Saving to directories is a much
> more annoying problem than just saving to files.

I'm not sure I'm explained myself rightly. My point is that lash_panel
should permit to save a new session starting from an old one, without
deleting the old one.

BTW, thinking about which is better between saving to files or to
directory it's a good think too ;-).

> > * Should be nice that lash_panel could start the lashd server, if
> > wanted. This should be selectable through  a command line switch
> > and/or through a button in the GUI. Ideally a windows that shows the
> > server messages would be the optimal solution, but also the basic
> > functionality to start the server would be a nice improvement. In this
> > way one have to run only one program (after jack, of course) and from
> > there can quickly load any desired session.
>
> Yeah, eventually.  And lashd will be able to start jack, so you don't
> need to manually start any daemons at all.

I'll wait the day when lash_panel and patchage can completely
substitute qjackctl ;-). Thanks.

Cheers,

  ~ Antonio




reply via email to

[Prev in Thread] Current Thread [Next in Thread]