Re: [LAD] LV2: Communicate from the DSP to the UI
On Wed, 2013-11-06 at 15:21 +, Aurélien Leblond wrote: [...] > > Using instance-access for visualization is 100% OK (assuming graceful > > degradation if the plugin does other things). Using it for control is > > grounds for being taken out back and shot. [...] > Well, there is one simple reason why I cannot use instance-access - > Ingen doesn't and won't support it :) > My requirements for this scope are: > - must be compatible with Ingen. I want this scope to be used with > other plugins from the avw.lv2 suite [...] > - I don't want to rely on outside jack apps I could plug Ingen into. [...] > As far as synchronization goes, I'm not that demanding... My scope > needs to be able to compare two inputs, so as long as they are > received in the same "event" I should be ok. The other case would be > to compare the output from a LFO with what I actually hear, but LFO > are so slow that even a 40ms delay shouldn't be much of an issue. Such a scope is certainly useful. Hardcore graphics stuff like Robin is into is nice for some things, but not really necessary for most. -- dr ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] JAudioLibs' AudioServer API and JNAJack
Hi All, I've written up a blog post on some recent changes to the JAudioLibs' AudioServer API [1]. This is a Java callback audio API loosely inspired by PortAudio, and the recommended approach for adding JACK support to a Java application with JNAJack. The AudioServer API makes it easy to switch between JACK support and JavaSound support without requiring code changes. The recent code additions provide for better runtime service discovery and optional extension features. For example, it is now possible to more easily control JACK connections, server autostart and client ID, as well as for the first time directly access the JackClient if necessary. More info in the blog post. The source code on GitHub [2] is now up-to-date for testing, though a new binary download is not yet available. Other changes include fixes to JNAJack to build against JNA 3.5+ (binary downloads already work), and minor improvements to the JavaSound server performance, particularly on Linux (ALSA / PulseAudio). Comments and feedback welcomed. Thanks and best wishes, Neil [1] http://praxisintermedia.wordpress.com/2013/11/06/jaudiolibs-audioservers-a-portaudio-esque-java-api/ [2] https://github.com/jaudiolibs/ -- Neil C Smith Artist : Technologist : Adviser http://neilcsmith.net Praxis LIVE - open-source intermedia development - www.praxislive.org Digital Prisoners - interactive spaces and projections - www.digitalprisoners.co.uk OpenEye - the web, managed - www.openeye.info ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] LV2: Communicate from the DSP to the UI
On Thu, 2013-11-07 at 00:49 +0100, Robin Gareus wrote: > On 11/06/2013 04:21 PM, Aurélien Leblond wrote: > > > @Robin: I'll defo have a look at the example you sent though, that > > looks like exactly the type of example I was looking for. > > I've just brushed it up a bit, removed all raw-atom write calls, added > RDF attributes for channel-id, etc and also sanitized the drawing > routine somewhat. pushed to > > https://github.com/x42/sisco.lv2 > > Now it is a proper example and should be about halfway towards your needs. Perhaps a good candidate for "official" (i.e. included) example? -- dr ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [LV2] LV2: Communicate from the DSP to the UI
On 11/09/2013 08:10 PM, David Robillard wrote: >> > I've just brushed it up a bit, removed all raw-atom write calls, added >> > RDF attributes for channel-id, etc and also sanitized the drawing >> > routine somewhat. pushed to >> > >> > https://github.com/x42/sisco.lv2 >> > >> > Now it is a proper example and should be about halfway towards your needs. > > Perhaps a good candidate for "official" (i.e. included) example? eg-scope, sure, fine with me; but please give me a few days to add some more comments to the source: elaborate on Atom-msgs and clearly note that the scope display itself is horribly wrong design. It's actually a perfect textbook example of what *not* to do: * no thread sync. it redraws somewhat randomly * it's neither accurate nor stable * it displays raw samples (a proper scope should^Wmust not do that) * the display itself just connects min/max line segments * no labels, no scale, no calibration * ... maybe Aurélien is going to address some of these issues, and his project will eventually be suited better for inclusion as official example. Alternatively removing the drawing routine would IMHO be appropriate for an example atom-vector communication plugin. @Aurélien: are you planning to implement a trigger mechanism and/or history? any plans to add up-sampling and interpolation? what about markers and numerical readout? best, robin ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
