linuxaudio.org

Am Sat, 02 Jul 2011 23:02:27 +0200

schrieb rosea grammostola :
> On 07/02/2011 10:40 PM, m.wolkstein@gmx.de wrote:

quoted text
> > Am Thu, 30 Jun 2011 11:03:05 +0200

> > schrieb rosea grammostola:

> >

> > huhu,

> > i currently finished a simple hydrogen implementation.

> > callback with:

> > save session(save the current song file)

> > save and exit(save and quit hydrogen)

> >

> > so far so good.

> Thanks a lot! I am surprised how fast devs are picking this up. Phasex,

> Hydrogen, Rakarrack ... great work already :)

>

> Next thing what would be good to have imo is a good software mixer with

> JackSession support. Unfortunately non-mixer is not a good candidate

> afaik, cause it changes port names. I don't know if Fons is still busy

> with his mixer and if he has explored and made up his mind about the

> actual implementation of the JackSession API already. Otherwise Jack

> Audio Mixer might be a good candidate maybe: http://home.gna.org/jackmixer/

yes the mixer is the heart of all. and jackmixer is one of the best i ever use

beside the buildin ardour mixer. cant wait for jack session support on it.

a global jack session support sound's like a dream. jack session support is IMO the KEY

or the next step to make music under linux much more attractive, productive and at least

more creative. one of the main problems is the long time you need to start your lovely

linux audio-system, make connections and try to remember how you can restore the set from

your last cool session and so on. at least i often give up to create music, because the

idea is gone after all this more or less unlikely administrative work.

beside this, sometimes if everything worked as expected and you currently make really

cool music, you become mournful while you are playing. why? because you now it is mostly

not possible to reconstruct the current session to continue this creative process and his

product(nice music). the super-GAU is when you make dozens of connections and your mixer

stop working, and you directly return to your starting point.

ok, this is all off-topic and for sure discussed hundreds of times. but i am often

frustrated to use linux-audio applications because the eat my time without a creative

output. since ~10 years, i only don't give up try working creative with linux-audio

applications, because my big pighead and my unbreakable hope.
g wolke
> > but i didn't agree to save the application data into the jack-session folder!

quoted text
> > imo, this is dangerous because you can lost all data very quick. mainly if you

> > overwrite a session. also people like me, which plays often improvised

> > music-sessions, will create tons of sessions folders with duplicated data.

> >

> > that's why i prefer the h2 implementation with absolute filenames. so currently h2

> > don't use the ${SESSION_DIR} prefix to store the song files.

> Qjackctl 0.3.8 has the possibility to use 'versioning', it makes backups

> of the old folder when you overwrite it.

> I wonder how much space those folders take in general and if that space

> is really a problem normally.

>

> Would be good if Torben (and/ or Rui) could comment on this.

> > checkout hydrogen trunk to get it.

> > if jack/session.h is available on your system, hydrogen compile by default with jack

> > session support.

>

> Regards,

>

> \r

> > lg wolke

> >

> >

> >> Linux Audio Developer,

> >>

> >>

> >> May I make a feature request here for your Linuxaudio application(s)?

> >>

> >> Could you please add JackSession support? It makes working with JACK

> >> standalone applications a lot more user friendly. There are some apps

> >> who support it already and they work fine, like Yoshimi, Qtractor,

> >> Pianoteq, Ghostess, Guitarix, Jack-Rack, Ardour3, Bristol, Seq24, Jalv,

> >> Ingen, Connie, Specimen and probably more.

> >>

> >> It is possible to use applications without JackSession-support in a

> >> session (via so called infra clients), it starts the applications, make

> >> the connections, but doesn't save the state. So obviously it would be

> >> far more useful if those applications would get JackSession-support also.

> >>

> >> Qjackctl is able to work as Session Manager, so is Pyjacksm (and likely

> >> Patchage in the future).

> >>

> >> According to comments on IRC by Paul Davis, it's very easy to add

> >> JackSession support to your application.

> >>

> >> "Its really easy, just handle 1 more callback from the server. Torben's

> >> walkthrough shows what is necessary."

> >>

> >> Torben's walktrough:

> >> http://trac.jackaudio.org/wiki/WalkThrough/Dev/JackSession

> >>

> >>

> >> Thanks in advance,

> >>

> >> \r

> >> _______________________________________________

> >> Linux-audio-dev mailing list

> >> Linux-audio-dev@lists.linuxaudio.org

> >> http://lists.linuxaudio.org/listinfo/linux-audio-dev

> > _______________________________________________

> > Linux-audio-dev mailing list

> > Linux-audio-dev@lists.linuxaudio.org

> > http://lists.linuxaudio.org/listinfo/linux-audio-dev

>

> _______________________________________________

> Linux-audio-dev mailing list

> Linux-audio-dev@lists.linuxaudio.org

> http://lists.linuxaudio.org/listinfo/linux-audio-dev

_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev