Here's my list of audio products that are based on Linux. Does anybody
have more to add? Is there somewhere online we can post and maintain a
list?
Harrison consoles
Yamaha Motif XS
Korg OASYS
Waves DPA
Roland Edirol RG-100
Lemur multi-touch controller
Muse Receptor
Plugzilla
HHB Portadrive
Midas XL8
Lawo consoles
Hartman Neuron
Lionstracs MediaStation keyboard
LCS Systems
-Ben Loftis
Hi there,
Thanks for the reply. Which UM-2 were you using? I see a few out
there. The UM-2 I know of is only midi. I need audio in/out.
Thanks,
DT
--
Technical Director - Virginia Center for Computer Music
http://www.virginia.edu/music/VCCM/
Has anyone seen source for it? I'm frankly tantalized. First of all, the
unit sounds very well. And, while the new display is apparently
colorful, it's still all text--I'm guessing ncurses or slang. Does
anyone know?
My interest and hope is to access display data over the builtin
ethernet tcp/ip connection in order to provide a speaking alternative
interface for blind musicians (like me). This seems emminently possible
except that Yamaha have locked all ports by default--I know, I nmap'd
it.
Still, they chose to build the XS using Linux. And they clearly have
chosen more f/oss tools, at least Samba is also clearly there judging by
the options available in the Network configuration menu.
So, how to gain access? How to get some small shell on board? I should
think the source is a place to start. It's clear they know they're under
the GPL here, because they publish it in Chapter 34 of the User Manual.
But the source ... ... ? ? ?
--
Janina Sajka, Phone: +1.202.595.7777; sip:janina@a11y.org
Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janina(a)a11y.org
Linux Foundation http://a11y.org
Hi everyone!
I still have the problem: If I try to create more than 2 jack-devices,
LinuxSampler just quits. did anyone else ever experience that problem? Is that
problem known to the LS-crowd? Is it possibly just a restriction, for I get no
error or is it a real bug?
I'd be happy about some answers, for it'd be really a great help in
recording and processing my tracks.
If there's anything I can do to assist in isolating the problem, just tell
me what to do!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Curious if anyone has had luck with some small usb audio devices and
ALSA? Kernel 2.4?
Thanks,
DT
--
Technical Director - Virginia Center for Computer Music
http://www.virginia.edu/music/VCCM/
William Weston <sysex.net(a)sysex.net> writes:
> Ahhh... I misunderstood and thought you were having troubles only
> when JACK was requesting a shutdown (which is only partly solved by
> the above patch). Thanks for being clear on this. The segfault on
> shutdown was caused by a race condition on thread cancellations and
> threads exiting normally. Version 0.10.3 contains the fix for this
> (which also improves shutdown time) as well as fixes for slowness
> when accessing the file menu for the first time and slow display of
> file dialogs.
I'm still getting crash on exit:
(gdb) r
Starting program: /usr/bin/phasex
[Thread debugging using libthread_db enabled]
[New Thread -1220261392 (LWP 9044)]
[New Thread -1220265040 (LWP 9047)]
JACK tmpdir identified as [/tmp]
[New Thread -1229153360 (LWP 9049)]
[New Thread -1237546064 (LWP 9050)]
[New Thread -1248474192 (LWP 9051)]
[New Thread -1256866896 (LWP 9052)]
Thank you for using PHASEX!
(C) 1999-2007 William Weston <weston(a)sysex.net>
Released under the GNU Public License, Ver. 2
[Thread -1237546064 (LWP 9050) exited]
Program received signal SIG32, Real-time event 32.
[Switching to Thread -1248474192 (LWP 9051)]
0xb7f3d410 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7f3d410 in __kernel_vsyscall ()
#1 0xb7e3dcf6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x0805050a in engine_thread (arg=0x0) at engine.c:1126
#3 0xb7e3b3dd in start_thread (arg=0xb595cbb0) at pthread_create.c:261
#4 0xb774ec8e in clone () from /lib/libc.so.6
(gdb) The program is running. Exit anyway? (y or n) y
Btw sysex.net(a)sysex.net address you are sending mails from seems to be
wrong.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
The [P]hase [H]armonic [A]dvanced [S]ynthesis [EX]periment, version
0.10.2 is ready for download (source tarball and FC6 RPMs) at:
http://sysex.net/phasex/
This release contains many fixes, most notably better support for
older GTK versions. PHASEX now works with GTK2 versions as low as
2.4.x, which should help most of the build issues on older distros.
Here's everything from the Changelog for this release:
* Fixed typos and omissions in parameter help file.
* Improved error handling and reporting in jack.c.
* Fixed JACK thread shutdown.
* Added Pete Shorthose's patch for saving memory with a single
knob anim.
* Added Lars Luthman's patch for improper style handling in
gtkknob.c.
* Fixed knob centering on middle click drag events.
* Cleaned up style and whitespace in gtkknob.c, added boilerplate.
* Added current midimap file to saved settings.
* Fixed build and runtime problems with GTK versions 2.4 to 2.8
* Fixed invalid setting of patch modified flag on startup.
* Updated error message for unhandled ALSA MIDI errors.
* Fixed passing of debug flags in configure.ac.
* Fixed detection of functions in libm.
* Added install of phasex.desktop to Makefile.am.
* Fixed uninitiailized varibable warnings in midi.c.
* Fixed missed internal update on boolean parameters first
switching to zero.
* Removed dead update_widget_val() in callback.c.
* Disabled engine side of audio ringbuffer locking (easier on JACK).
* Changed name of ALSA MIDI sequencer input port for readability.
* Added project roadmap.
Special thanks go to Pete Shorthose and Lars Luthman for your
patches to the gtkknob code, and to the rest of you for offering
incredible feedback, especially on the build issues and ALSA/JACK
startup issues.
Cheers!
--ww
--
/* William Weston <weston(a)sysex.net> */
Well, it's been over 2 (3?) years since last release, but rtmix refuses to
die ;-). Thanks solely to Robin Gareus and his heroic work in making rtmix
gcc4 compliant, I am releasing rtmix version 0.76. Apart from compile error
fixes (courtesy of Robin), there have been a few cosmetic tweaks, but most
notably, the source is now released under a 100% GPL-compliant license. That
being said, the code is still a dirty hack, the internal event cue
occasionally still misbehaves (albeit only in very complex situations), and
unfortunately native alsa seq is still MIA (uses old unix dev access). OTOH,
the thing does work as advertised, has been used, and continues to be used
in my works without a hitch. Apart from oss midi, rtmix supports networking,
OSC, and other goodness making it rather practical for on-screen
coordination as well as interaction between performer(s) and computer.
For more info on what really rtmix is please consult the HTML documentation
included with the tarball (or see online documentation info below). The
tarball (5MB) comes with source, documentation (some statements in it are
likely a bit outdated, so please take those parts with a grain of salt),
tutorials, and precompiled binary on Ubuntu 6.10 (i686, qt3, gcc), so if you
have these a simple "make install" should do it (installs in
/usr/local/rtmix and binary in /usr/local/bin). For a "simon" tutorial with
sounds you will also need sounds zipfile (11MB-ish) which are downloadable
from the same folder (just browse the folder).
To download latest RTMix click here:
http://ico.bukvic.net/Linux/RTMix/rtmix-latest.tar.gz
Online documentation:
http://ico.bukvic.net/Linux/RTMix/RTMix-docs/
Complaints to: /dev/null
Future roadmap:
Rtmix in its current state is a project in a need of a total rewrite. This
is primarily due to the fact that despite the fact rtmix appears to do the
job in 99.9% of instances, the code is an ugly hack which makes its
maintenance and perhaps more importantly expandability exponentially
difficult. That being said, I am looking forward to one of the upcoming
summers when I will dig into the code once again and rebuild the darn thing
from the ground up the way it was meant to be all along. Until then, this
version should prove an adequate substitute.
Enjoy!
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology, CCTAD, CHCI
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-1137
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/people/faculty/bukvic/http://ico.bukvic.net
William Weston <sysex.net(a)sysex.net> writes:
>> The patch does not help. I beleive the AFAIK the jack_shutdown_handler()
>> is called only when jackd is being shut down, not during jack client
>> shutdown. I added printf in the function and it does not show during
>> phasex shutdown. It appeared however when I tried to stop jackd while
>> phasex was running (and there were some other strange messagest too):
>>
>> # phasex
>> JACK tmpdir identified as [/tmp]
>> cannot read server event (Success)
>> cannot complete execution of the processing graph (Resource temporarily unavailable)
>> zombified - calling shutdown handler
>> jack_shutdown_handler() called.
>
> Finally figured what's going on here. It turns out that the engine
> thread will shut down cleanly, even if currently blocked on the
> pthread_cond_wait() after the jack thread goes away. The segfault
> is being caused by the jack_shutdown_handler() being called from a
> thread other than the jack thread, thus calling jack_deactivate()
> and jack_client_close() from the wrong thread. Try this one:
>
> --- phasex-0.10.2/src/jack.c 2007-05-22 15:38:29.000000000 -0700
> +++ phasex/src/jack.c 2007-05-22 15:38:50.000000000 -0700
> @@ -231,11 +231,6 @@
> *****************************************************************************/
> void
> jack_shutdown_handler(void *arg) {
> - if (client != NULL) {
> - jack_deactivate(client);
> - jack_client_close(client);
> - client = NULL;
> - }
> phasex_shutdown("JACK shut down client.\n");
> }
>
>
> The phasex_shutdown() function already handles a clean shutdown of
> phasex's jack thread (and the jack_deactivate() and
> jack_client_close() calls are already made in the normal thread
> cleanup handler), so this appears to be the best way to handle it.
>
> Let me know if it still gives you any troubles.
[start jackd]
[start phasex]
JACK tmpdir identified as [/tmp]
[stop phasex]
Thank you for using PHASEX!
(C) 1999-2007 William Weston <weston(a)sysex.net>
Released under the GNU Public License, Ver. 2
Segmentation fault
[start phasex]
JACK tmpdir identified as [/tmp]
[stop jackd]
cannot read server event (Success)
cannot complete execution of the processing graph (Resource temporarily unavailable)
zombified - calling shutdown handler
jack_shutdown_handler() called.
JACK shut down client.
Thank you for using PHASEX!
(C) 1999-2007 William Weston <weston(a)sysex.net>
Released under the GNU Public License, Ver. 2
Segmentation fault
As I already noted jack_shutdown_handler() is not called on phasex stop
at all.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
