Hi, sorry for the double post, but maybe a user
knows the answer to this...
What is the right way to call fst_init() ?
I have installed fst-1.9 (tried 1.7 - 1.9), and
it runs standalone and loads vst's OK.
However, from within a simple 'hello world' app,
when I call fst_init(), it causes a seg fault.
The seg fault happens early within fst, in the 'wine_premain'
code, at getModuleHandleA().
I have tried that trick of reserving and initializing 1,000,000
stack bytes (taken from from jfst_reserve_memory()). No luck.
I really would like to get this working. Can you help?
Thanks. Tim.
terminator356 <at> users <dot> sourceforge <dot> net.
(Using a different computer)
Hmmm, the Jack I have here doesn't show any MIDI clients when I check
the MIDI tab. At least, it doesn't show my keyboard. That should be
listed as a client, yes?
--------------------------------
Something I've noticed in the most recent qjacjctl is that there are now tabs for midi and for alsa connections. The devices that formerly showed up as midi now show as alsa. Is that possibly the issue?
Also, I tried a new sequencer called non-sequencer which showed up in the midi tab and I couldn't figure out how to connect any inputs or soft synths as output. This might be a better question for the non-sequencer group. OTOH, what is the alsa/midi tab difference?
It looks like ecasound will continue processing until *all* the chains are done receiving input.
Is there some way to get it to quit when only *one* chain is done?
i.e., my little one-liner to use ecasound to feed JAMIN has a bug: it starts up perfectly at the start of the input file, but it sits there processing zeroes for as long as JAMIN is connected to the output chain. Not useful.
-ken
I didn't know that audacity worked with jack.
Have you tried to use the oss drivers instead of the alsa ones.
Should be an option for this if you're using qjackctl.
Do you get constant xruns when running jack?
Perhaps you can post the ouput of jack when you run it and run a sound
application that causes clicking.
Also, make sure you hit reply-to-all when replying to the list. ^_^
On Thu, 2008-09-18 at 16:15 -0700, un records wrote:
> Thanks for the response. how do you kill an artsd process? the
> clicking when happens when i open jack, sound recorder, ardour, or
> audacity. it's an irregular fast tick/clicking noise that changes
> speed slightly when i change the latency rate. it doesn't happen when
> i open a regular player like rythmbox or media player. It does happen
> when i open Hydrogen (drum sequencer). So it only happens with music
> creation/editing programs and Jack.
>
> --- On Thu, 9/18/08, Miguel Morales <therevoltingx(a)gmail.com> wrote:
> From: Miguel Morales <therevoltingx(a)gmail.com>
> Subject: Re: [LAU] clicking noise in all audio programswith
> new linux user
> To: unrecordsbooking(a)yahoo.com
> Cc: linux-audio-user(a)lists.linuxaudio.org
> Date: Thursday, September 18, 2008, 6:26 PM
>
> Does the clicking happen with an audio program that doesn't take input?
> i.e. zynaddsubfx.
> Also, make sure you kill any artsd process. Does the clicking happen
> when using alsa by itself. i.e. using xmms to play audio, without jack
> running?
>
>
> On Thu, 2008-09-18 at 13:38 -0700, un records wrote:
> >
> >
> > I am a new ubuntu user who is trying to optimize my system to run
> > ardour and audacity. It's a dell d630 laptop. I have installed both
> > programs and Jack, but there is a constant clicking noise whenever i
> > open any audio program including jack. I think it has something to do
> > with the latency, but i've tried all settings and the clicking
> > persists. I do not have programming experience. Is there any advice
> > you can give on how to set up my system.
> >
> >
> Thanks.
> >
> >
> > _______________________________________________
> > Linux-audio-user mailing list
> > Linux-audio-user(a)lists.linuxaudio.org
> > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
>
Hi Folks
Before I go through the painful process of collecting debug data and
filing bugs against Rosegarden, I thought I'd see if anyone was familiar
with the issues I am experiencing.
Having finally got various external issues resolved, earlier today I
attempted to record and play back a track on Rosegarden. I was using
the current Gentoo ebuild, being the rather old version 1.5.1. I
experienced a crash when trying to replay a track so upgraded to the
latest masked ebuild, 1.7.2 - same issues.
I have managed to get crashes when:
1) I attempt to play back a track.
2) I attempt to create a new track when there is a change to what is
already there. So, I do 'new', I get 'the current file has been
modified, do you want to save it?'. I say 'no', it crashes.
When the crashes occur, I get a KDE crash handler pop up (I never even
knew this was a KDE application) telling me that rosegardensequencer
crashed and caused the signal 11 (SIGSEGV). After a short time, I also
get a message from Rosegarden saying 'The Rosegarden sequencer process
has exited unexpectedly.'
Whilst these messages are popping up, Rosegarden disappears from the
Connections window of qjackctl.
The Rosegarden window itself, however, remains present.
Is this a behaviour with which anyone else is familiar? Thought I'd ask
around before running off and filing bug reports.
Just in case it's relevant, I'm actually running the Fluxbox window
manager, but KDE is installed and I run other KDE applications without
issues - I use Konsole all the time as I have never found another
terminal application that I like 1/1000th as much.
Now up to about 20 hours total getting all this set up - almost makes me
wish I'd stuck to analogue! (Or my Atari.)
Cheers
M
--
Matthew Smith
Smiffytech - Technology Consulting & Web Application Development
Business: http://www.smiffytech.com/
Personal: http://www.smiffysplace.com/
LinkedIn: http://www.linkedin.com/in/smiffy
Hello LAU community,
There is no shortage of recording and mixing software for
Linux. Probably five or six that are based on Ecasound,
with implementation languages including Lisp, Python,
Tcl/Tk, Perl/Tk and probably others.
Here is another one written in Perl.
Nama is available from CPAN, included in the module
Audio::Ecasound::Multitrack. The following command will
install the software on most systems:
cpan -i Audio::Ecasound::Multitrack
Nama has tracks, buses, marks, a mixer and other
conveniences allowing a person to record and mix using
Ecasound without needing detailed knowledge of Ecasound
chain setups.
The program is a refactoring of Ecmd, with significant
additions. Since I imported the original procedural code
into git a year ago, I have introduced:
- object-oriented code for buses, tracks, marks, etc.
- YAML for .namarc and state save/recall
- a command line grammar
- help for text commands
- default Tk GUI with a CLI in the terminal window
- text-only mode for use without X
- looping playback mode
- support for Ecasound playat/select/audio_loop/reverse
I have also found and closed many, many bugs.
I have intended for Nama to be simple, predictable, hackable.
and think I have achieved this, to some extent.
Will appreciate any comments, suggestions, bug reports,
patches or other feedback.
I'd like to include special thanks to Kai, for Ecasound, to
Brad Bowen for Audio::Ecasound, the Perl interface used by
Nama.
Joel
--
Joel Roth
I just downloaded and did a test run of NtEd 1.2.1 from
http://vsr.informatik.tu-chemnitz.de/staff/jan/nted/nted.xhtml .
I'm not involved in anyway with this project. But, I do encourage
everyone to give this a try. And say nice things to the author!
There are a few missing items which make a show stopper for me (mainly
chord symbols), but progress is fast and the author tells me that my
items are high on his list!
I did a few midi file imports and was impressed with the speed and
accuracy achieved.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
Aeolus is amazing! A totally synthetic pipe organ that sounds extremely
"real" and beautiful, amazingly spacious, complex and full-bodied.
I imported a MIDI file of Bach's Sinfonia to Cantata 29 into Qtractor,
then connected the MIDI output of Qtractor to Aeolus, then played back
the MIDI data while simultaneously recording the audio output of Aeolus
responding to that MIDI data, back into Qtractor. Then I pressed some of
Aeolus's stops while the file was playing and recording. I exported the
audio as an OGG-Vorbis file directly from Qtractor. Here it is (no
post-processing, no normalization, no editing nor effects at all) for
anyone interested:
http://flytrapranch.com/lau/aeolus_bach_sinfonia_cantata29.ogg
What an amazing sound Aeolus has. Thank you so much, Fons (Adriaensen).
It makes me want to buy this (if I had the money)--
3-manual MIDI organ keyboard
http://www.midiworks.ca/products/product_details.asp?productid=1&categoryid…
(I wonder if the stops just beneath the keys can be easily programmed in
Linux to correspond with stops in Aeolus)
--and this--
MIDI organ pedalboard to standard specifications
http://www.midiworks.ca/products/product_details.asp?productid=25&categoryi…
Steve
"Life does not give us a reason to live; we do." :-)
Am Montag, 22. September 2008 schrieben Sie:
> On Mon, Sep 22, 2008 at 4:05 PM, Arnold Krille <arnold(a)arnoldarts.de> wrote:
> > Am Montag, 22. September 2008 schrieb simone-www.io-lab.org:
> >> i am having hard time to get FreeBob working on my system ofr it seems
> >> like Jack can t even load the freebob driver, any idea?
> >> [root@localhost io]# /usr/bin/jackd -dfreebob -dplughw:0 -r48000 -p256
> >> -n3 -D jackd 0.109.2
> >> FreeBoB ERR: device (-d) argument not valid
> > Simply follow the rules: plughw is alsa-specific. freebob uses hw:X.Y for
> > numbering the devices and the reason there is a hw: in that term is only
> > for convenience. The X represents the fw-bus and Y is the device on the
> > bus. But you shouldn't need to specify any of those...
> ok here it is:
> [io@localhost ~]$ /usr/bin/jackd -dfreebob -dhw:0 -r44100 -p256 -n3 -D
> jackd 0.109.2
> Copyright 2001-2005 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK compiled with System V SHM support.
> loading driver ..
> SSE2 detected
> Freebob using Firewire port 0, node -1
> Ieee1394Service::initialize: Could not get 1394 handle: Invalid argument
> Is ieee1394 and raw1394 driver loaded?
> Fatal (devicemanager.cpp)[68] initialize: Could not initialize
> Ieee1349Service object
> Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device
> manager LibFreeBoB ERR: cannot create libfreebob handle
> FreeBoB ERR: FREEBOB: Error creating virtual device
> cannot load driver module freebob
> Segmentation fault
Probably the most common problem: /dev/raw1394 is not accessible by the
user...
Arnold
PS: surely you want this to stay on the list?
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a "rm -rf /". Or ask your
administrator to do so...
hi
i am having hard time to get FreeBob working on my system ofr it seems
like Jack can t even load the freebob driver, any idea?
Fedora 8 CCRMA - FA-66
[root@localhost io]# /usr/bin/jackd -dfreebob -dplughw:0 -r48000 -p256 -n3 -D
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
SSE2 detected
FreeBoB ERR: device (-d) argument not valid
cannot load driver module freebob
no message buffer overruns
--
.wmv , .wma , .pps along with all proprietary Windows formats won t be
accepted and/or viewed....