Hello,
just tried to update my installation of fst-1.6 to the newest (now beta!)
wine. But there are several problems:
the options to winebuild have changed and so in fst/Makefile the build-command
must be changed:
- the target must be renamed to "$(fst_exe_MODULE).spec.o:" cause winebuild
creates an assembler file that can't be processed by the implicit rule
".c.o:" -- but the new winebuild can create the ".o" file directly.
- "the executable must be named via the -F option" -- to get rid of this
winebuild error message the option '-F' must be inserted just before
$(fst_exe_MODULE)
With this modifications the build creates the libfst.so successfully but when
linking fstconfig with libfst there are two missing symbols:
./libfst.so: undefined reference to `__wine_spec_exe_entry'
./libfst.so: undefined reference to `__wine_spec_init_ctor'
Unfortunately the wine documentation is not updated to this new behaviour and
I was not able to figure out what to do. When building the intermediate
assembler source (just undo the extension change for the .spec.o) and looking
at it, the two symbols are destination marker: The first is just an address
in an internal table and the second is the target of a jump command.
I can't find any suggestions what to additionally link to libfst to satisfy
this unresolved references ...
Is there an updated version of libfst? Or someone with more wine knowledge,
who can solve this problems?
By further investigation I found a workaround that builds libfst but at least
ardour gives a "memory access fault" (Speicherzugriffsfehler):
Unpack the distribution
cp fst/libfst.spec.c fst/libfst.spec.c_backup
./configure
make
cp fst/libfst.spec.c_backup fst/libfst.spec.c
This uses the prebuilt libfst.spec.c but maybe this doesn't match the current
wine version ...
I have build ardour with "VST=1" and it only starts without "memory access
fault" when giving the option "-V"
Thank you
Uwe Koloska
gentoo
vanilla kernel 2.6.10
coldplug-20040920
hotplug-20040923
fxload-20020411
midisport_fw-0.5.0
to make this short....
I installed by following the instructions here...
http://alsa.opensrc.org/index.php?page=USBMidiDevices
I installed the midisport about a month ago and got it
working. I was using kde at the time. I uninstalled
kde and switched to windowmaker. Now the midisport
doesn't work I reinstalled the above packages. still
no luck. I even reinstalled kde. nothing.
any ideas on this one?
-Mike Fisher
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
Apparently my soundcard selecting skills are poor.
I thought that a USB card would be nice so that I could use it on
different machines. The M-Audio Audiophile USB had good specs and usb
audio was supposed to work ok.
After much googleing I seem to have the device recording 24/96k audio
but its only with arecord.
Trying to start jack (V 0.99) it whines that my format is not
supported. And if I choose plughw I get XRUNS.
How much work will it be to get jack to work with S24_3BE?
--
Richard A. Smith
I've written a simple patch to add info on the real-time capabilities
of LADSPA plugins in CheeseTracker.
I know I seem to be the only CheeseTracker user on the lists, but just
in case...
http://blog.dis-dot-dat.net/2005/10/cheesetracker-patch.html
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you."
(By Vance Petree, Virginia Power)
Hello,
Could someone please remove 'joesgarage79(a)cs.com' from the subscription list ?
The last weeks I get a bounce from AOL for every message posted...
--
FA
I'm going to convert my fathers record collection over to CD. Doing
some google research.
According to http://www.tracertek.com/newway.htm they claim the "new"
and best way to do LP to CD is to use a flat preamp, record at 24bit,
96kHz and then apply the RIAA curve in software after the fact.
Either before or after the DeNoise, De-Click, etc depending. I've
also seen a few other sites that say the same type things.
tracertek sells doze software to do the whole ball of wax but I'd like
to use Linux.
I haven't found any RIAA filters yet so I guess I'm looking at
writeing one. So does anyone have any information on where to find
the official RIAA curve to make a plugin from?
They also recommend using a pink-noise record to calibrate your setup
and then adjust the curve so it matches your system.
--
Richard A. Smith
Hi all,
I would like to route a microphone through a sound card and back to
powerful amplified speakers.
As we know in analog PA gear you have the microphone feedback problem
(usually it comes in form
of high pitched whistle sounds).
But if I route a mic from into the soundcard and out to the speakers,
there will be a small delay
due to the audio card buffers. Even if it's only a few msecs it makes
the problem much worse
than in the case of analogue gear because the feedback sound will come
in chunks that's one audio card buffer at time.
For example if I use 64 samples per buffer which gives me acceptable
latency for a live singer, the feedback noise
could possibly generate a much lower pitched signal/interference (I
assume something like 44100/64 Hz) which is I think
not easy to filter out compared to the high pitched feedback (is in the
latter case sufficient to cut some high frequencies using an EQ ?).
How can one solve the feedback problem in case of mic to speaker delays
of let's say 5-10msecs ?
Is an echo canceller algorithm needed ? If yes does this compromise the
quality of the input signal (the singer).
I think this is a very interesting topic and it would be cool if
knowledgable people could come up with topics and ideas.
(for example people that are good at DSP, room correction etc, like Fons
A. etc).
PS: I know that cards like DELTA 1010 and others (RME) can do zero
latency monitoring (hardware pass-thru) but
I'd prefer a software based routing since you can apply effects and
stuff before forwarding the output.
thanks for infos and toughts
Benno
http://www.linuxsampler.org
Introducing WhySynth, a DSSI softsynth plugin.
WhySynth, as in 'Y'-synth, the super-sized, frankensteinized,
evolved and mutated, still rather dorky younger sibling of
Xsynth-DSSI.
WhySynth, as in (I sometimes ask), "_why_ am I working on another
softsynth instead of on paying gigs?" (Following my bliss?
Addiction? One last shot at misspent youth?)
WhySynth, as in a mostly-new design featuring:
- 4 oscillators per voice, in your choice of 6 modes (minBLEP,
wavecycle, asynchronous granular, FM, waveshaper, and noise),
- 2 filters, also in multiple flavors,
- flexible routing and mixdown to stereo output,
- 3 (or is it 6?) LFOs (instrument-wide, per-voice, and multiphase),
- 5 multi-mode envelope generators,
- abundant modulation options,
- and effects (well, Tim Goetze's Versatile plate reverb is all at
the moment, unless you count the DC-blocker anti-effect).
WhySynth is a work in progress. Actually, since the kid was born,
progress has slowed to a near-utter standstill, but if I can't
release often, I might as well release early.
Get your tarball, boring screenshot, and html-ized README today at:
http://home.jps.net/~musound/whysynth.html
then get your butts back to making cool music -- however you define
that. Cheers,
-Sean
Hi,
I want to plug a ham radio receiver into the sound card of my PC, and
use the CPU of the PC to tidy up the signal, to hopefully make it more
readable.
One form of communications is called Morse Code, where a single tone is
switched on and then off to pass a signal over the radio.
I know it is easy to do band pass filters in Linux so that only the tone
gets through, but the other really useful thing would be a noise filter.
I was hoping that someone had already written a open source noise filter
that I could use. If so, can someone point me to it, because I can't
seem to find it on google.
The noise filter needs to happen in real time, so ideally a plugin for
ardour of something like that.
James
On 10.4, Apple removed the deprecated dlopen() mechanism of using
_init() and _fini(). Instead, function attributes should be used.
These have been supported in gcc since at least 2.9x.
So instead of:
void _init() {}
void _fini() {}
you should use:
__attribute__((constructor)) void init() {}
__attribute__((destructor)) void fini() {}
Thanks,
Taybin