Quoting Daniel James <daniel(a)mondodesigno.com>:
> Hello Sampo,
>
> > sxpress is for controlling MMC compatible software & hardware with
> > USB DAW controllers. The DAW controller is interfaced through the
> > Linux input event API and MMC is sent via the ALSA sequencer.
>
> This sounds very interesting - which controllers have you tested it
> with?
>
I have a Contour Shuttle Xpress. It's the more-than-modest controller from
Contour, it has a jog/wheel, dial and 5 buttons. It's enough for me.
The configuration I use is as an example in the .tar.gz. It has
start/stop/rewind/punch recording, MMC locate (dial) and varispeed control
(jog/wheel). I use it with Ardour.
Sampo
Hello!
My DAW controller project is now stable enough for a small-scale
release. So, here it is:
sxpress is for controlling MMC compatible software & hardware with USB
DAW controllers. The DAW controller is interfaced through the Linux
input event API and MMC is sent via the ALSA sequencer.
Get it at:
http://www.helsinki.fi/~stsavola/software/sxpress-0.1.tar.gz
Please try it out. Feel free to comment!
Sampo
Hi all,
I've been messing the other day with figuring out new sounds that would "enhance the Linux desktop experience" (namely KDE, but obviously usable with any desktop that supports sound events) since the ones we currently have IMHO sound a bit too obtrusive.
Anyhow, I've come up with this new theme titled "Borealis." It is available for immediate download on the KDE-look website:
http://www.kde-look.org/content/show.php?content=12584
An .ogg preview of the start-up sound can be found here:
http://meowing.ccm.uc.edu/~ico/Linux/Borealis.ogg
Any comments and/or suggestions are most welcome and appreciated!
Best wishes,
Ico
CheeseTracker is a mature,versatile and extremely full-featured application
that works as an all-in-one sequencer/sampler/sample editor/fx processor. It
allows for the creation of professional sounding multitrack mixes.
It includes examples and docummentation, as well as on-line help.
It can be obtained at http://cheesetronic.sf.net
Sorry for the delay, even though this was ready some months ago, I didnt have
time to fix up a proper release..
Changes for this version follow:
-New (still scons-based) build system, should be easier to use..
-Fixed OSS detection for REAL
-Disabled RtAudio, must reenable it at least for OSX, but that will be
version 1.0.0
-All engine converted to floating point, may be a bit slower on pre p4/athlon
computers, though a bit more accurate
-Old FX core deprecated, sorry, this wont load effects on pre-9.9 songs,
though it will keep the routes.
-Added shift-f6, play pattern from cursor
-Added sample-being-played notification in sample screen.
-Fixed wave-loading bug, should work until i get libaudiofile working
-Fixed ugly bug in GXX introduced in 0.9.1
-More resamplers (FM/Cosine/Cubic Spline).
-Doubled filter range.
-Managed to reduce the source file size a bit
-NEW FILTERS!!! rewrote the filters, they are MUCH better now.. choose
between lowpass/bandpass/hipass/notch
-New Effect: Multiband (6/10/21/31) equalizer.
-New effect!: Distortion (with many distortion modes)
-New effect! Pitch Shifter (not amazing, but very tweakeable)
-New effect! Stereo FX (kickass post-production helper)
-New bugs! report them please!
Enjoy!
Juan Linietsky
Hi all,
this is my first post on the list, so I'll introduce myself shortly. I
play (bass guitar) in a punk rock band with a drum machine (an old Boss
DR-5). We are kind of limited by the drumbox, because of the small
memory size (200 patterns, 20 songs), the non-extensible and boring drum
kits and the lack of certain features. As a system administrator with a
bits of programming knowledge (I know Perl, a bit of C and some other
useful things) and a free software fan, I said to myself : let's get a
software drum machine on a laptop, it should have unlimited features.
So far I looked at a number of projects, but none is usable on stage.
Here's what I need :
1/ A simple programming interface (Hydrogen is perfect). It can also be
something like a simple programming language editable in a text editor.
2/ For length-fixed songs, it's just a playback of a .wav, no problems.
3/ On some songs, we stop the drumbox, play a bit, and start it again.
When I hit the stop pedal, it stops immediately (and therefore I need to
hit "reset" to be sure to be at the beginning of the pattern when it
starts again). It would like it to stop at the end of the pattern if I
hit the stop button.
4/ It should "know" the song structure:
"start" : plays part1 of song
"stop" : stops :)
"start" : again part1
"stop" : still stops
"start" : plays part2 of song
5/ We need programmable tempo changes.
6/ Big display, playlist control, easy to load songs ! We're on stage,
it's dark,, there is smoke, and it's not very practical to
"file/open/click/click/click..." with a guitar in the hand and people
jumping over you. Song name should be displayed BIG (full screen), the
name of the next song should be already programmed, so I just have to
press space (or a pedal wired to the parallel or whatever port) to jump
to the next song.
I just spoke about a pedal. I can build a "stop/start, next song" pedal
and code something that reads events and make it to the audio app.
For some songs, just chaining two or three .wav files works well enough.
But when it comes to things more elaborate, I have been unable to find
something appropriate.
== The point is to have something simple to use on stage. ==
I imagine a little program that feeds a software drumbox MIDI (or JACK?)
events for stop/start/jumpto/tempo changes. I just don't want to
reinvent the wheel.
If someone has something that does the job or some hints/useful
libraries/glue, I would be happy !
Thanks for your reading, enjoy music !
--
Charles
you can listen to some of my music on http://www.raia.info/
(french web site, sorry for non-french-speaking people)
> -----Original Message-----
> From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-
> user-bounces(a)music.columbia.edu] On Behalf Of Dan Harper
>
>
> I haven't used Audacity much, but as far as I know, some differences
> are:
> - Audacity is easier to use.
For me Audacity is only good for editing samples/sound files.
Using it as the many HDR for your DAW is not an option (yet). Lack of
realtime effect sends, bussing, automation, etc. would make it difficult
for me to suggest to anyone to use audacity as the center piece to their
DAW. That being said, it's a great program for what it does (I use at
home (linux CCRMA) and at work (winXP) for sample tweaking and editing.
_________________________________________________
Scanned on 11 May 2004 15:54:01
Scanning by http://erado.com
Anybody successfully compiled the latest Audacity v1.2.1? It breaks
spectacularly in the portaudio section for me with all kinds of wxGTK
errors. I have the whole wxGTK environment on my box including the devel
stuff and I haven't had these errors with previous versions.
--
Jack Bowling
mailto: jbinpg(a)shaw.ca
The main part of my post was....
>> FWIW, I have successfully built audacity-1.2.1 on SuSE 8.2...
I added the note...
>> message about it using portaudio 15 which restricts it to oss, and it said
>> would have to change to use the experimental (?) portaudio 16 to get alsa
Where I made my mistake...
>> ...On my audio machine, I've got an M-Audio
>> Audiophile-2496, and I think (?) I'm restricted to using oss (because of
>> envy24control?) anyway? I'm a bit unclear on that. I'll play more later (on
>> another machine). Just another "data point" for you guys.
>
>just curious ... how does envy24control restrict you to using oss?
>envy24control is an ALSA tool for controling an ice1712 chip's mixing,
>routing and other features. You pretty much have to be using alsa to use
>envy24control. Many people, myself included, are using envy24control and
>the alsa-drivers on cards (delta-66 for me) based on this chipset.
>
>-Eric Rz.
Thanks for the correction. As I indicated, I'm a bit fuzzy on the
interactions. What confuses me more is that these days I alternate between
two PC machines: one with Intel 82801AA-ICH and the other with ICE1712 - M
Audio Audiophile 24/96. I was shooting from the hip... and I missed... (I
should have checked everything before posting). I remember having to mess a
lot with the audio driver settings on the ice1712 machine in xmms to get
anything to play, but that may have been a problem with xmms(? see below).
On that envy24control thing viz. alsa... I do find it annoying that there is a
lack of "integration" between such apps as audacity and xmms and the audio
volume control. I'm not sure what the problem is. I would have expected that
the volume control on audacity or xmms should be "connectible" to the main
(which one? I would suggest analog volume, as "master"? or PCM1 & PCM2?)
volume control on the envy24control panel. With the 82801 it works that way:
I can control volume either with xmms slider, or from kmix (or any other?).
However, I think the xmms volume slider changes only the PCM volume (on my
i82801 machine), leaving the master where it was. With ice1712, I have to
bring up both audacity (dead slider) or xmms (dead slider) and envy24control
(to adjust volume, on analog output panel). I don't have "normalization" in
xmms working to my satisfaction yet, so it's even more annoying. I don't know
if it's a permanent problem, or whether it will (eventually) be fixed? How?
(getting a bit farther afield from audacity...)
I've had other problems with applications (such as xmms) storing machine
specific configuration stuff into my home directory (shared across machines).
Hopefully, all that stuff should also be fixed. In principle, I should be
able to move between machines (with different audio, etc.) and be able to run
my applications without having to tweak everything (yet again). An "initial
tweak" on a new platform is acceptable, but shouldn't mess up others. This
may have been the main confusing factor for me, making me distrust things.
(back to audacity!) Oh, and a couple of observations about audacity-1.2.1:
1) Mono recording on ice1712 is (again/still) transposed 1 octave down: the
default recording is mono, and it seems to mess up the data stream coming
from the M-Audio Audiophile-2496. I get my voice transposed 1 octave down,
must be some sample/buffer mapping thing. I've seen this before with previous
versions, and I've seen others mention it. Workaround is to record stereo.
2) (slight anomaly) recorded track identification panel missing until
recording stops. I don't know if this is "by design" or "by mistake". When I
start recording (in mono or stereo), the wavefore panels come up (empty,
natch), but the track identification panel on the LHS is missing. When I stop
recording, this panel appears (with the L/R panning slider, etc.). Maybe this
is "by design", to prevent people trying to tweak that stuff? Only for
playback? Not a problem (except you can't see mode info), but unexpected.
BTW, great mailing list! I'm picking up much useful stuff here. I still don't
have my audio stuff setup to my liking, but it's a background activity for
me. These days soliciting paying work is taking priority (unfortunately). I
do use audacity to record/playback to (re)learn some guitar and singing. It's
pretty bad (my performance that is), but it's getting better. The gear helps.
--
Juhan Leemet
Logicognosis, Inc.
>Jack Bowling <jbinpg(a)shaw.ca> escribió:
>
>> Anybody successfully compiled the latest Audacity v1.2.1? It breaks
>> spectacularly in the portaudio section for me with all kinds of wxGTK
>> errors. I have the whole wxGTK environment on my box including the devel
>> stuff and I haven't had these errors with previous versions.
>
>mmm... it's funny, it fails for me too. never had had problem with audacity
>before. i searched the audacity mailing list and nobody complained about
>this, though...
>
>anyone?
FWIW, I have successfully built audacity-1.2.1 on SuSE 8.2, but I haven't
tested it yet. All I had to do was adjust some package (dependency) naming,
since SuSE has different package names. While building, I did notice a
message about it using portaudio 15 which restricts it to oss, and it said I
would have to change to use the experimental (?) portaudio 16 to get alsa
support. I have not done that yet. On my audio machine, I've got an M-Audio
Audiophile-2496, and I think (?) I'm restricted to using oss (because of
envy24control?) anyway? I'm a bit unclear on that. I'll play more later (on
another machine). Just another "data point" for you guys.
--
Juhan Leemet
Logicognosis, Inc.
> -----Original Message-----
> From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-
> user-bounces(a)music.columbia.edu] On Behalf Of Russell Hanaghan
> Sent: Monday, May 10, 2004 6:54 PM
> To: A list for linux audio users
> Subject: (Erado Alert - Objectionable content) Re: [linux-audio-user]
> Newbie checks in
>
> I have not messed with USB audio cards specifically. I do use a
midiman
> 2x2 USB midi interface with no probs...Frank has much on USB sound
> devices...and none of it good! :)
Actually if you check the archives, Frank recommends a couple of cheap
USB sound devices. The ones he will tell you to stay away from are the
non complient ones like the Midiman USB stuff (their PCI however is
stellar).
m.
_________________________________________________
Scanned on 11 May 2004 15:58:26
Scanning by http://erado.com