On Sun, 2007-08-26 at 01:03 -0400, Paul DeShaw wrote:
> --- On Sat 08/25, Gordon JC Pearce < gordon(a)gjcp.net > wrote:
(this was originally meant to go to the list, not just the sender)
>> It needs a firmware loader to set up the software inside the interfaceitself, as far as I can tell.
> Yes, madfuload was installed about a month ago. Sorry I didn't mention that. All the gory details are in a thread in Ubuntu Forums:
> http://ubuntuforums.org/showthread.php?t=148467 Page 4 is the most relevent; I post as Aurora.
>> I know throwing money and kit isn't going to fix it, but I can't find a lot to complain about with my Novation Xiosynth 25. Class-compliantdevices ftw.Gordon
>
> That looks nice. The Ozone is just a controller, no sounds. You use softsynths and plugins.
>
> So can you record the sounds from the synth? Is the signal routing hard? I've used hardware synth modules with the college workstations, but never at home.
Yes. It just appears as an ALSA midi port and a couple of audio ports,
in and out. It does have a few limitations (separate capture and synth
outs in ALSA would be nice, and I'd *looove* a multitimbral version),
but for the money it does a lot and does it pretty well. Only downside
is that the overall feel is a bit plasticky and the
grey-on-greenish-metallic colour scheme can make the control labels hard
to read in a certain light.
Gordon
--- On Sat 08/25, Paul Davis < paul(a)linuxaudiosystems.com > wrote:
cat /proc/asound/cardscat /proc/asound/deviceslsmod | grep snd_seqlsmod | grep snd-seqaconnect -oaconnect -i
Thanks, here are my results:
pad@Studio909:~$ cat /proc/asound/cards
0 [IXP ]: ATIIXP - ATI IXP
ATI IXP rev 2 with ALC655 at 0xfe029000, irq 20
1 [Academic ]: USB-Audio - Ozone Academic
M-Audio Ozone Academic at usb-0000:00:13.0-1, full speed
pad@Studio909:~$ cat /proc/asound/devices
2: : timer
3: : sequencer
4: [ 1- 0]: digital audio playback
5: [ 1- 0]: digital audio capture
6: [ 1] : control
7: [ 0- 1]: digital audio playback
8: [ 0- 0]: digital audio playback
9: [ 0- 0]: digital audio capture
10: [ 0] : control
pad@Studio909:~$ lsmod | grep snd_seq
snd_seq_dummy 4740 0
snd_seq_oss 33408 0
snd_seq_midi 9600 0
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 53232 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24196 3 snd_rtctimer,snd_seq,snd_pcm
snd_rawmidi 25856 2 snd_seq_midi,snd_usb_lib
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
snd 54788 15 snd_atiixp,snd_ac97_codec,snd_seq_oss,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_pcm,snd_timer,snd_rawmidi,snd_seq_device,snd_hwdep
pad@Studio909:~$ aconnect -o
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 128: 'TiMidity' [type=user]
0 'TiMidity port 0 '
1 'TiMidity port 1 '
2 'TiMidity port 2 '
3 'TiMidity port 3 '
pad@Studio909:~$ aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
pad@Studio909:~$
I understand very little of that output.
>> Would I be better off with another interface? This one came with my >>Pro Tools setup blah blah Apple laptop yadda yadda Ubuntu >>Studio.
>the device should work OK AFAIK.
>> My needs are simple.
>Thats what everyone thinks :)Your biggest problem is a shared >filesystem. There really isn't a goodchoice for what to use as a >shared common filesystem between any two ofWindows/Linux/OS X. Making >it all three is even harder. If you don'thave a common filesystem, it >means you have to partition the disk tohold different filesystems for >different boots, and already the systemis starting to look less >ideal. --p
I was thinking a dual-boot with OSX and Ubuntu, and not share a filesystem for the laptop. My desktop is Linux-only. I might put a FAT 32 system on an external drive if I want to share files. I don't anticipate a lot of need for that since the sessions are not compatible between Pro Tools and, well, anything.
Thanks for your assistance. I'm under a deadline, so the current project will be done in Pro Tools to make sure it gets done on time. It's one song for a contest, the subission has to be in Sep. third. I have another song I want to try producing with just open-source software.
Thanks,
Paul
_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way your home on the Web - http://www.myway.com
Greetings,
I am at a loss how to make JACK recognize and connect my M-Audio Ozone MIDI keyboard controller/audio interface. I have searched the archives here, as well as Ubuntu forums. Is there anywhere else I could look? So far I have been able to use the Ozone as the soundcard for some applications, including (finally) Rosegarden. I can play a MIDI file with some synth plugins. I cannot control anything from the Ozone; it is not recognized by JACK as a MIDI client. I was also getting tons of xruns, but I fiddled with the frame rate and other parameters, and it seems to be much better now.
I am running Ubuntu Studio (32 bit) on an AMD 64 processor.
The graphics card is a low-end ATI, built in to the cheap ECS mobo. I am at a coffee shop now and can't get the exact models.
Please tell me what else you need to know.
Would I be better off with another interface? This one came with my Pro Tools setup, and I would like to save money by using it in everything. If I can successfully migrate to Linux for audio, I could get rid of the Ozone (and Pro Tools! Free at last!), but would like to stick with USB so I can use it with my Apple laptop (MacBook with Intel Core Duo at 2GHz). That's what I run Pro Tools on, and, hopefully, Ubuntu Studio at some point.
My needs are simple. A few vocal tracks, maybe up to 3 guitar tracks, some synth chords and bass. Pretty much just folksy, mostly acoustic stuff. It shouldn't be too hard, but I've been at it for about a year now, without success.
Thanks,
Paul in Seattle
_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way your home on the Web - http://www.myway.com
Hi folks
I've just released a new tarball of nekobee, my TB-303 plugin for DSSI.
Changes between 0.1.5 and 0.1.6 are:
* the configure script doesn't look for gtk1.x any more (thanks Juuso
Alasuutari)
* the release times of the envelopes are tweaked to eliminate an
unattractive bloppy noise on note off with certain keyboard controllers
* the volume has been reduced to around 1/5 of previous versions (in
line with other DSSIs), and an atan() waveshaper has been added to give
it a bit of crunch and rein in the excesses of the resonant filter
* the filter parameters have been tweaked to more closely reflect the
sound of the "18dB/oct" filter in the 303.
Try it out, have fun, and let me know if you run into any problems. Or
in fact, let me know if you *don't* run into any problems ;-)
Gordon
> ------------------------------
>
> Message: 3
> Date: Sat, 25 Aug 2007 08:27:30 -0400
> From: Dave Phillips <dlphillips(a)woh.rr.com>
> Subject: [LAU] water-damaged rhodes ?
> To: LAU Mail List <linux-audio-user(a)lists.linuxaudio.org>
> Message-ID: <46D02032.6030404(a)woh.rr.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Greetings,
>
> As some of you know, my hometown (Findlay OH) was hit by rather severe
> weather recently, including some impressive floods. I escaped any
> serious damage, but my garage and utility room were flooded. The water
> came up to my doorstep and stopped, thankfully, so the main dwelling
> space was untouched. All my gear is safe and intact.
>
> A large storage facility is near my house, and almost everything in
> the
> sheds has been thrown out and piled by the streets for trash pickup.
> When I walked by the piles this morning I noticed a case with a
> "Rhodes
> Instrument" label. I opened it, it's a mini-Rhodes, and other than the
> water damage it appears to in good condition. I packed it into my
> truck,
> and now I own a mini-Rhodes that needs cleaned and possibly repaired.
>
> So, how should I clean this thing ? My thought is to simply open it up
> and hose it down to get any crap out of its box, then I'll let it dry
> and try firing it up to see if it works. Any other advice or
> suggestions
> for this project ?
>
> Btw, if I get it working I'll sell it locally. It's too heavy to ship,
> it reminds of my bad old band days when we carted a B3 and a full-
> sized
> Rhodes. I admit to missing the great sounds from those instruments,
> but
> my back won't bear the strain these days. ;-)
>
> Best,
>
> dp
What is the most important part of Dave message? the fact he found a
water-damaged rhodes.... or the fact his hometown was hit by rather
severe weather recently, including some impressive floods ?
Speaking today probably the first part, but I would say the second
part will resound like another warning in a short time..
Stephane
jack_mixer version 6 "Dance of the headless corpse" released.
jack_mixer is GTK (2.x) JACK audio mixer with look similar to it`s
hardware counterparts. It has lot of useful features, apart from being
able to mix multiple JACK audio streams.
Changes since version 5:
* Fix building against jack 0.102.20
* Handle python prefix different from install prefix
* Fix LASH-less operation
* Update install instructions after lash-0.5.3 and phat-0.4.1 releases
* Apply Markus patch (thanks!) for sr #1698 (can't restore session using LASH)
Homepage with screenshots: http://home.gna.org/jackmixer/
Download: http://download.gna.org/jackmixer/
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Hi,
I just built and installed Jack_Mixer using Fedora 7. I can't get it to run
and I get this error message:
$ jack_mixer
Traceback (most recent call last):
File "/usr/local/bin/jack_mixer", line 22, in <module>
import jack_mixer_c
ImportError: No module named jack_mixer_c
Searching for the file I found this:
$ sudo find /usr/local -name "jack_mixer*"
/usr/local/share/jack_mixer
/usr/local/share/jack_mixer/jack_mixer.glade
/usr/local/lib/python2.5/site-packages/jack_mixer_c.py
/usr/local/etc/gconf/schemas/jack_mixer.schemas
/usr/local/bin/jack_mixer.py
/usr/local/bin/jack_mixer
Is it a problem with a Python environment variable?
Thanks!
Hector
--
===============================
http://www.hcenteno.net
