Greets to all,
As in subject, I'm gonna buy a Delta44, and I would like to have some
impressions about its reliability with JACK, as I am still bugged with
the occasional crackling problem (with no xruns) with my SB Live and
other consumer cards I own, but I think it's a poor hardware design
issue or an ALSA driver bug, as suggested by Paul Davis et a. on this
list (but, hey Lee revell, have you got that problem with SBLive?)
So, any Delta44, or M-Audio and JACK enthusiast here?
Thanks in advance!
ciao
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
Hi!
I'm going to learn one of this apps. The aim is to use one of them to create
a functional generator (with sliders, switches, attenuations. mixings and so on)
for audio-DIY-ing purposes. JACK server will be in use for routing.
Which app to select? I think, learn period is not too short to try both :-)
Thanks in advance!
Andrew
Hi,
I just tested the Trigger Finger (link below) by m-audio at the local
dealer's shop, and it worked immediately when I plugged it in thanks to
the snd_usb_audio module. Thanks to all devels!
The only thing I miss is the possibility to make backups. m-audio has a
tool called Enigma (available for Mac OS and Windows) to make backups
of the settings (and even programming the device). The device itself
has no option to make it send a sysex dump of its memory contents to
the computer.
I asked m-audio for the request string to do a backup, but I was told
that this is only possible using the Enigma software and the special
usb-audio-driver by m-audio.
I doubt that. Can anyone provide request strings for any
evolution/midiman/m-audio products (UC33, m-audio keyboards)? If so, I
could likely derive the requests for the Trigger Finger from it. Even
Enigma (nomen est omen?) can handle a large scale of m-audio devices,
and I guess that all devices work in a similar manner internally.
Any hint, even to a PDF doc or similar which contains sysex
documentation for any similar device would be helpful.
Thanks in advance,
ce
Product Link:
http://www.thomann.de/thoiw2_maudio_trigger_finger_midi_drumcontroller_prod…
Hi,
I'm being really lazy here and looking for some ideas on how to do
a couple of things easily. I really don't want to spend much time on
there. Thanks in advance.
1) Assume I have an existing wave file (mono or stereo) and want to
convert it to text. I'd like each sample written in 8/16/24-bit hex to
its own line in the file. Any easy way to do it?
2) Assume I've chosen a sample rate and bit-depth. Now want to
generate a hex file with sine wave data, again with each sample
written to its own line. Any easy way to do it?
Thanks,
Mark
I make interviews on minidisc and air them on FM. I'm looking to
replace the minidisc either with an Edirol R-1 or a usb soundcard that
I can jack into my ultraportable.
If I go for the soundcard option I'd like to find something with more
then one mic input. I use ordinary el chepo electret mics, no fancy
XLR phantom powered stuff.
What are my options for usb soundcards, if I wan't something that
works under linux (without patching and hacking)?
alex
--
Alex Polite
http://flosspick.org - finding the right open source
On 10/22/05, Martin Wohlleben <Martin.Wohlleben(a)gmx.de> wrote:
> Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark Knecht:
> > On 10/21/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
> > > On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector Centeno-Garcia wrote:
> > > > Thanks! We help ourselves... that's the nice thing about open source.
> > > > With the -r option Crystal works for me now. What is this option for?
> > > > One plugin that I can't get working is the SRI_1010. It would be very
> > > > nice to have this one unless you know of any other free convolution
> > > > plugin. I tried with and without the -r option and I get:
> > > >
> > > > err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of this
> > > > midi device. Assuming FM Synth
> > > > gui_thread_id = 10
> > > > could not post message to gui thread
> > > > cannot create editor
> > >
> > > hmmm... this looks like the plugin is trying to open a midi port by
> > > itself. try to configure wine so that it does not see any alsa midiport.
> > >
> > > > Have any of you tried to use this one?
> > > >
> > > > cheers!
> > > >
> > > >
> > > > Hector.
> > >
> > > --
> > > torben Hohn
> > > http://galan.sourceforge.net -- The graphical Audio language
> >
> > Hi all,
> > I just got a few minutes to try xfst on my AMD64 machine. Did
> > anyone else run into this:
> >
> > mark@lightning ~/CODE/xfst-0.3 $ make
> > winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
> > fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
> > winebuild: unrecognized option `--debug'
> > Usage: winebuild [OPTIONS] [FILES]
> >
> > <SNIP>
> >
> > make: *** [xfst.exe.dbg.c] Error 1
> > mark@lightning ~/CODE/xfst-0.3 $
> >
> > I hope I'm doing this correctly. I put the Steinberg headers in the
> > vst directory and then ran make. That seems to be what the README file
> > suggests. There is also a file called readme.jack-fst which seems ot
> > be leftover from the older Jack_fst. Is that correct?
> >
> > Make does seem to want to run winebuild, and winebuild on my system
> > doesn't support an option called debug.
> >
> > mark@lightning ~/CODE/xfst-0.3 $ wine --version
> > Wine 20050930
> > mark@lightning ~/CODE/xfst-0.3 $
> >
> > Did I miss some conversation about this?
> >
> > Thanks,
> > Mark
>
> Hi Marc,
>
> I got the same failure with wine20050930. I downgraded wine to wine20050830
> and xfst-0.3 compiled cleanly.
> You also have to change the vst header as for jack_fst. Otherwise you get some
> error messages and make will "fail". I don't know exactly what I changed
> exactly, but you can find the headers which I used attached to this e-mail.
> I still got a failure message, during compilation but xfst works.
>
> good luck,
> Martin
>
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
My apologies for the accidental cross post to dev, I hit
the wrong address.
ce wrote:
>there was a talk at LAC 2005; AFAIR the latency was 50msecs this time.
>I don't know if it is less these days.
I believe I am at 10 msec. now - have not pushed it
further yet.
>are they already working on a true ALSA driver?
I believe they are. There is a dev. road map on the sourceforge
page.
Regards,
Brad Hare
I plan on doing some torture tests over the next
few days. So far I have not spent any time on
latency etc, I'm just happy to have things going
in and out. From what I've seen so far I believe
the current drivers may be quite usable for simple tasks
(stereo recording). That would be enough to keep me
busy while the freebob devel guys are finishing off
the real thing.
Regards,
Brad Hare