20 Feb
2012
20 Feb
'12
5:58 a.m.
Sometimes, I wonder why I even bother... First, recordmydesktop didn't
work, so I had to film the screen with a video camera, then ffmpeg2theora
took ages to transcode the video from MJPEG and added some annoying clicks
to the audio track, then the new archive.org uploader didn't work, so I was
stuck with using youtube.com, which refuses to display the video in HD.
Alas, I am to learn again and again that the only way to have things done
right is to do them yourself. On that note, I'd like to introduce to the
wider audience a project that I started shortly after writing this:
http://lists.linuxaudio.org/pipermail/linux-audio-dev/2008-May/021084.html
... post to the LAD list back in 2008. Well, I haven't been very active
since then--well, such is life--but in the past couple of weeks I've spent
some time developing the idea and I'd like to demonstrate it in the
following video:
http://www.youtube.com/watch?v=ui-gC_ZMeGM
I'll be pushing my changes in the next week or two along with some other
fixes and enhancements to the Non-* family. Those who have been following
on #lad may have already seen draft versions of the NSM API. The final
draft (version 1.0) will be posted to the LAD list soon also.
Robust audio session management on Linux is now a solved problem. You're
welcome ;-)
Enjoy!
21 Feb
21 Feb
6:12 p.m.
From: "J. Liles" <malnourite(a)gmail.com>
Date: Sun, 19 Feb 2012 20:58:27 -0800
<snip>
I'll be pushing my changes in the next week or two
along with some other
fixes and enhancements to the Non-* family. Those who have been following
on #lad may have already seen draft versions of the NSM API. The final
draft (version 1.0) will be posted to the LAD list soon also.
so glad to see some maintenance on Non-* -- i always felt these were really
ground-breaking tools, but when i tested them they didn't seem quite ready for
production use.
Robust audio session management on Linux is now a
solved problem. You're
welcome ;-)
and, thanks so much for this; i will be eager to check out what you've done!
congrats and cheers!
.pltk.
6:56 p.m.
On 02/21/2012 06:12 PM, plutek wrote:
From: "J.
Liles"<malnourite(a)gmail.com>
Date: Sun, 19 Feb 2012 20:58:27 -0800
<snip>
Cool! Yoshimi would be a more logical choice these days maybe, but alas...
If you didn't notice ;) , there is also JackSession now (and Ladish).
Maybe some documentation how to add support for your session stuff to
other session managers would be good.
\r
I'll be pushing my changes in the next week
or two along with some other
fixes and enhancements to the Non-* family. Those who have been following
on #lad may have already seen draft versions of the NSM API. The final
draft (version 1.0) will be posted to the LAD list soon also.
so glad to see some maintenance on Non-* -- i always felt these were really
ground-breaking tools, but when i tested them they didn't seem quite ready for
production use.
Robust audio session management on Linux is now a
solved problem. You're
welcome ;-)
and, thanks so much for this; i will be eager to check out what you've done!
congrats and cheers!
22 Feb
22 Feb
5:55 p.m.
Cool! Yoshimi would be a more logical choice these days maybe, but alas...
If you didn't notice ;) , there is also JackSession now (and Ladish).
Maybe some documentation how to add support for your session stuff to
other session managers would be good.
\r
Someone mentioned that after I had already patched ZynAddSubFX. The patch
doesn't readily apply to the Yoshimi code, but I'll look into adapting it.
JACK-Session is, from my perspective, far too basic to be useful. And,
AFAIK, Ladish is still lacking a robust protocol, currently relying on Unix
signals, JACK Session, and LASH to communicate with clients. And, of
course, LASH was always inadequate. I first started having issues with SM
back in 2008. Not much has actually been accomplished since then to meet
the requirements mentioned in my 2008 post (although Ladish does behave
better in many important aspects than lashd ever did).
The NSM API is well documented and I think that having support for it in
Ladish would be a Good Thing and not incompatible with the project goals,
although the user experience may suffer if LASH, JACK Session, etc clients
are allowed to mix in an NSM session becuase certain points of consistency
could no longer be guaranteed (due to the limitations of those APIs).
That being said, as you can see in the demo, Non-* will come with a fairly
fully featured session manager right out of the box if you can live without
the Ladish 'rooms' concept.
24 Mar
24 Mar
11:51 a.m.
New subject: Non Session Manager
On 02/22/2012 05:55 PM, J. Liles wrote:
Cool! Yoshimi would be a more logical choice these days maybe, but
alas...
If you didn't notice ;) , there is also JackSession now (and Ladish).
Maybe some documentation how to add support for your session stuff
to other session managers would be good.
\r
Someone mentioned that after I had already patched ZynAddSubFX. The
patch doesn't readily apply to the Yoshimi code, but I'll look into
adapting it.
JACK-Session is, from my perspective, far too basic to be useful. And,
AFAIK, Ladish is still lacking a robust protocol, currently relying on
Unix signals, JACK Session, and LASH to communicate with clients. And,
of course, LASH was always inadequate. I first started having issues
with SM back in 2008. Not much has actually been accomplished since then
to meet the requirements mentioned in my 2008 post (although Ladish does
behave better in many important aspects than lashd ever did).
The NSM API is well documented and I think that having support for it in
Ladish would be a Good Thing and not incompatible with the project
goals, although the user experience may suffer if LASH, JACK Session,
etc clients are allowed to mix in an NSM session becuase certain points
of consistency could no longer be guaranteed (due to the limitations of
those APIs).
That being said, as you can see in the demo, Non-* will come with a
fairly fully featured session manager right out of the box if you can
live without the Ladish 'rooms' concept.
Works nice here (!), all though I'm missing a option to add parameters
to a client (like mididings etc.). Where are the sessions stored by
default? How do I remove a session completely?
\r
4621
days inactive
4654
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
J. Liles -
plutek -
rosea.grammostola