Hi all,
at http://www.arnoldarts.de/drupal/?q=node/557 I have written down
(part of) my success-story with my new rack featuring a Presonus
Firepod. It works great using the freebob-drivers by P. Palmers & Co.
Thanks guys!
Feel free to ask and have a nice weekend,
Arnold
--
visit http://www.arnoldarts.de/
---
Wenn man mit Raubkopien Bands wie Brosis oder Britney Spears wirklich
verhindern könnte, würde ich mir noch heute einen Stapel Brenner und
einen Sack Rohlinge kaufen.
I tried MuSE today, on my Kubuntu system. I started Jack, and MuSE,
and opened up a Midi file. I saw MuSE Midi connection in the qjackctl
connection window, and I was able to play the midi file through an
external synth.
In the Audio tab of the qjackctl connection window however, I did not
see any inputs or outputs to MuSE. I imported a .wav file, but I did
not get any sound by playing it. Similarly, attempting to record from
my microphones, I saw that envy24ctl was getting audio from my mikes,
but no connections were shown in the qjackctl connection window, and
I recorded nothing but silence with MuSE.
With Ardour, all of the inputs and outputs show up in qjackctl
automatically. Is there something else that I must do to get
MuSE to connect to jack on the audio channels?
Oh, and also, how involved would it be to get my SBLive to respond
to Midi events with its internal synth?
Thanks,
Tobiah
Hello list,
I'm getting really, really frustrated and need some help. I've been
trying for the past week to install software that depends on pkgconfig
to find libraries. My most recent outing was to install dssi so I
could try out hexter. I install dssi by doing apt-get install etc.
Now I'm trying to compile hexter (there's no package for that), and it
complains that pkgconfig doesn't know about dssi, so I need to adjust
my pkg_config_path variable.
Now my understanding is that, in order for pkgconfig to "know" about a
library, there has to be a .pc file that contains metadata for it.
Alas, there is no dssi.pc on my system. Am I stuck?
--
Josh Lawrence
http://www.hardbop200.com
Hello,
I just started to use audacity with some live recorded music. I have a
few starting questions:
Audacity:
1. If the input waveform seems to go beyond the +1 and -1 scale, what
does that signify? I assume that shows recording circuit is being
saturated and that the output from mixer should be reduced.
2. If the input waveform is being shown saturated, how would that
manifest itself in the playback?
3. On a machine, I exported a portion of the captured wav to a wav file
(basically, saved a portion of the input). I then transfered it to my
home computer running Debian. While that sound wave file was shown
between +1 and -1 in the original machine, on my home machine is was
being shown between +0.5 and -0.5 in audacity. What gives?
Exporting to mp3
1. I would like to export a number of wav files to mp3 files. Instead of
doing it one by one from audacity, how can I export them using a shell
script? I want to be able to set some basic tag info in a file and call
that file to fill in the mp3 tags automatically. In essence, I want to
call a script that converts all wav files in a directory to mp3 files.
And of course, I would like to be able to set the bitrate in the script.
Suggestions on which tool to use for this?
2. I can export to ogg format from audacity. Can I do the same thing as
(1) for this as well? Does ogg format support tags.
Thanks,
->HS
Date: Mon, 19 Feb 2007 12:34:46 +0100
From: Lasse Lindner <dabalance(a)gmx.net>
To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
Subject: Re: [linux-audio-user] (no subject)
Message-ID: <20070219113446.GA3109(a)Xen.olympus.lan>
References: <20070217111112.41BA9F418B(a)station.olympus.lan> <200702190850.54680.rj(a)spamatica.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200702190850.54680.rj(a)spamatica.se>
User-Agent: Mutt/1.5.13 (2006-08-11)
Hi,
yes, I tried MuSE for some time and was very confused why it didn't work
until I read at the project page:
"Here are some stuff that hopefully will make it into 1.0:
[..]
- Sync IN/OUT should be working"
http://www.muse-sequencer.org/wiki/index.php/1.0goals
On 08:50 Mon 19 Feb , Robert Jonsson wrote:
> Hi,
>
> >
> > Hi,
> >
> > I spent several hours with looking for a sequencer for linux which is
> > able to handle incoming midiclock signal (external source), but
> > couldn't find one til yet. any ideas?
>
> Did you try MusE?
> http://muse-sequencer.org.
>
> The current stable version (0.8.1 or preferrably 0.9pre2) supports this,
> atleast to some extent. If it doesn't do let us know.
> Setting it up is a bit sketchy though.. If you don't succeed best bet is to
> try the MusE mailinglist.
>
> /Robert
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I decided I'd really like to try these convolution reverbs that people on other platforms have been using for nearly 10 years, apparently.
So I grabbed jack_convolve, libconvolve, and libDSP.
It seems the're not autotools-enabled, so they don't just magically figure out the right set of CFLAGS. Unfortunately, I have no idea which to use.
Building libDSP, I got stuff like:
gcc -march=pentium2 -mcpu=pentium4 -mmmx -O1 -ffast-math -fprefetch-loop-arrays -Wall -Werror -g -D_REENTRANT -D_THREAD_SAFE -D_ISOC9X_SOURCE -D_GNU_SOURCE -DDSP_X86 -I. -c X86.c
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
X86.c: In function ‘dsp_x86_sse_addf’:
X86.c:479: error: unknown register name ‘xmm1’ in ‘asm’
X86.c:486: error: unknown register name ‘xmm1’ in ‘asm’
X86.c:486: error: unknown register name ‘xmm0’ in ‘asm’
X86.c: In function ‘dsp_x86_sse_add’:
X86.c:501: error: unknown register name ‘xmm1’ in ‘asm’
X86.c:508: error: unknown register name ‘xmm1’ in ‘asm’
X86.c:508: error: unknown register name ‘xmm0’ in ‘asm’
X86.c: In function ‘dsp_x86_sse_mulf’:
Ah, great.
The CPU I'm using to build the software and (hopefully) to run it, is this one:
http://www.restivo.org/projects/macmini/system-details/cpu.txt
Anyone want to venture a guess as to what GCC flags to use, or, better yet, how to cheat and make autotools tell me, even though this package doesn't use it?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFF2Tgre8HF+6xeOIcRAkjtAJwKZcDG/2O87unVVMxnmy1HiEFtsgCgmiTR
S9c02T9GBq0EgoXglAlWqKc=
=hf/q
-----END PGP SIGNATURE-----
Date: Sat, 17 Feb 2007 12:11:12 +0100
From: Lasse Lindner <dabalance(a)gmx.net>
To: linux-audio-user(a)music.columbia.edu
Subject: incoming MIDI Clock signal?
Message-ID: <20070217111112.GA27271(a)Xen.olympus.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
Hi,
I spent several hours with looking for a sequencer for linux which is
able to handle incoming midiclock signal (external source), but
couldn't find one til yet. any ideas?
I'm trying to get Ghostess' jackmidi to work in Mandriva 2007(jack 102.5).
Alsa(1.0.12) is OK, but when I play through Dino jackmidi to Ghostess jackmidi
I get an error and Ghostess crashes:
[root@localhost src]# ghostess fluidsynth-dssi.so
ghostess: ghostess starting...
ghostess: instance 0 on channel 0, plugin 0
is 'fluidsynth-dssi/FluidSynth-DSSI/inst00'
ghostess ready
fsd-gui starting (pid 13792)...
ghostess: OSC: got update request from
<osc.udp://localhost:13560/dssi/fluidsynth-dssi/FluidSynth-DSSI/inst00>
ghostess: symbol lookup error: ghostess: undefined symbol:
jack_midi_get_event_n
[root@localhost src]#
I admit I'm having to try ghostess-20061127.tar.gz or Thac's
ghostess-0-0.20050916.1.mdk2006.0.mde.i586.rpm to even get a Ghostess
jackmidi port in Mandriva 2007. Dino and Om-synth jackmidi work OK, no
problem.
Ghostess is very useful and it would be great if it worked on Mandiva 2007.
Dragan Noveski:
>>>
>>
>> You need a compiled JUCE, and libjuce.so maybe in a directory that is
>> known in /etc/ld.so.conf, so -ljuce finds it.
>>
>>
> ok, but how to tell to juce that it builds libjuce.so at all
>
> i am running 'make' in the juce/build/linux successfully, but after
> that running updatedb first, and than:
>
Yes, that part is not documented very well. You need to build juce like
this: "make CONFIG=Release".
> nowhiskey@murija2:~/software/nove/mammut/juce/build/linux$ locate
> libjuce.so
> nowhiskey@murija2:~/software/nove/mammut/juce/build/linux$
>
>
> so i think .so is not build?
>
Yes. It doesn't make dynamic libraries, just static ones. So the
file you have build is called libjuce_debug.a . If you set CONFIG=Release,
you will get a file called libjuce.a
>
> also, since there is no 'make install' in juce, i understood you that it
> is enough to cp libjuce.so /usr/local/lib ??
Don't bother with that. Just let JUCEPATH in mammut's makefile point to
the directory you unpacked juce into.
>
> hope that i get some help, really interested to get mammut working here!
>
If everything else fails, you can use Mammut 0.22 instead, which requires
gtk1. Its not that much different.