Hello again,
Just wanted to let everyone know, that I found a way to solve the problem - I
uninstalled rezound!. Seems such a shame as it was a nice lookin app, but I already have one app that doen't play nice with jackd, don't need two do I =).
Oh, and I was having a problem with fftw. seems a person needs the old version (2.1.?) AND the new version (3.0.1), found this out by trial and error as googleand the archives weren't of any help.
So the batting average is thus:
9 audio applications installed or attempted. None work fully, 3 work soso.
Funny thing is, in windows, I can take the apps that have been ported over to windows by those very same *nix developers and they work. So I'm wondering why they "finish" the job whenever they port to windows? Could it be that they know the windows people expect a certain standard? Maybe developers get lazy when designing for Linux? I don't know.
The sadest thing is that I hate M$ and don't really care to use its OS, yet it looks like I'm still going to have to for some apps :(
Lest you think it is my "unfamiliarity" with Linux. This is a lfs-4.0 system that I have made myself, it is connected to the net and 99% of it works just fine.
well, gtg, seems I've got to reinstall win2k on that box I took it off of :X
later,
james
hehe, these apps still don't make any noise :D
--
airbrush(a)sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
I built jack and ssm (and rebuilt my 2.4.22 kernel with caps, lowlat,
preempt) and I'm having problems getting the plugin to work.
First, there was a function pointer type mismatch in the sample
rate change callback function, which I fixed. Now, recent cvs
ssm builds with jack-0.80.0 (well, for me... I could send my
patch...)
I get the jack plugin gui rect on the canvas of ssm without
problem, it does switch back and forth between detailed and
simple GUI.
When I have the jack plugin without connecting it to anything
and not attached to the jack server, output to the oss output
works fine, but when I tell the jack plugin to attach, I get
a buzz sound whose pitch is the same as the rate the Process
callback is being called; if I have a mixer before the output
plugin, the volume of the pitch is scaled by the volume sliders.
When I have any jack plugin input connected from any ssm plugin
output, -and- the plugin is attached to jackd -and- the jack
plugin's input is routed to an alsa output, I get a different-
sounding buzz that is also the same rate as the Process callback
invocations. This buzzing sound is -not- scaled by any volume
sliders in ssm.
At the moment, I'm not sure what to do... but I'm looking into
the possibility that the samples as represented by jack are
not of the same data type (-and- don't get converted) as the
samples as represented by ssm.
Comments? Help? :)
-Jim
--
Jam sessions community web site: http://jam.sessionsnet.org
hi all - I'm trying to understand the concept of Jack Transport, so I can
understand what's not working, and what I'm just missing...
here's an example I crossing my fingers on, but figured wouldn't work: run
jack, run ardour, run rosegarden. set ardour to "jack transport master" and
rosegarden to "jack transport slave" - play ardour, hope that rosegarden
starts up - of course this didn't happen, but I can hope! :)
I knew it wouldn't happen, because the sync capabilities in both programs
aren't done, I know that part - but I was curious if it would try at least,
or what
but then it occurred to me that even with everything working, there may be
something more to do, perhaps with Jack (what? I dunno maybe
jackd --enablethedamntransport or something :) ) - so I thought I'd try and
find this out - and as always, I look around a bit, and if I don't start
finding mention of it pretty quick, I ask this list...
---------------------------------------------------------------
Houston Poetry Slam Team
www.houstonpoetryslam.com
NQuit Records
www.nquit.com
---------------------------------------------------------------
yeah yeah I'm workin' hard, sendin lotso questions - sorry if I yack too
much :)
Cheesetracker - maybe cool - can't tell - very unintuitive for me - are
there any tutorials, step by steps, how-to's, or demo/example files (the
last because if I can hear it do it's job with something already made I'll
start to understand really fast)
---------------------------------------------------------------
Houston Poetry Slam Team
www.houstonpoetryslam.com
NQuit Records
www.nquit.com
---------------------------------------------------------------
Hi All,
I'm considering buying a secondhand M-Audio Quattro. There are plenty of
them popping up on ebay all the time. The problem is I live in Australia
and the quattro uses an external power supply - does anyone know if a
Quattro bought in the US can be made to work on Australia's 240V mains
power - either through an adaptor or a different power supply?
Cheers,
- Adam
Hi!
I have a problem starting my alsa drivers... doing:
# /etc/init.d/alsa start
Starting ALSA (version 0.9.6): ens1370-failed failed
I have a soundblaster with ensoniq 1370 chip. What I'm doing wrong?
Audio works fine without alsa... loading es1370 module, but I need
alsa to run ardour.
Thanks a lot,
PD: My computer is running debian/unstable
--
Félix Cuello
--
Al que a buen árbol se arrima, buena sombra le cobija.
Greetings:
Yes, it's true, I've finally updated the sites with a new edition for
your weekend browsing pleasure. If you don't already know the drill, you
can follow these links to the goods:
http://linux-sound.org (USA)
http://www.linuxsound.at (Europe)
http://linuxsound.jp (Japan)
Have fun !
Best regards,
Dave Phillips
Hi once again all,
I have installed rezound (succesfully I hope! ). But it seems to hang if I try to use jaskd.
Here's what happens:
I fire up an xterm and type:
jackd -d alsa -d hw:0
Then I see this:
jackd 0.80.0
---notices---
jack compiled with System V SHM support
loading driver ..
hw:0|hw:0|1024|2|4800|nomon|swmeter|rt
open
starting engine
Then I fire up another xterm and type: rezound
the second I do that in the first xterm (jackd's) I see this:
alsa_pcm:xrun of at least 8.834msecs
Then (or at the same time) a dialog box pops up on the screen:
Choose port for output Chose 1
I choose: alsa_pcm:playback.1
and I click on ok (green check mark)
Then everything stops
when I get tired of waiting and ^c the rezound window, this pops up in the jackd term:
subgraph starting at rezound timed out (subgraph_with_fd=11, status = 1086326156, state = Triggered)
subgraph starting at rezound timed out (subgraph_with_fd = 11, status = 1088326156, state = Triggered)
I am using the latest rezound :0.8.3beta
and jack is 0.80.0
alsa is version 9.rc2
sblive 5.1
850mHz stick of Celery
256mBram
lfs-4.0 distro
Hope this is enough info =)
thanks again for al the help guys
james
--
airbrush(a)sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Hi all,
I have been able to record guitar parts in audacity. It weems to work real fine so far. However I still can't get anything to come through stompboxes2 other than a hissing sound. I guess it just wasn't meant to be.
What I intended to do with stompboxes2 was to just play through them at first, with the option of recording through them later. The way I usually record guitars is to tun them through an amp, and mike the amp, the mike going to a mixer, or more preferable the br-008.
I'm not too heartbroken over the stompboxes2 being broken because I still have the br-008, and I can always record through audacity ( pretty good ladspa effects there too!).
Thanks all who tried to help.
This is one "Kick Butt" forum!
later,
james
--
airbrush(a)sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Hi guys, I don't konw if you can help me out here, but I could not
find anywhere to ask this, so here I go.
I recently downloaded an compiled OpenAL on my system via CVS. Every
thing was OK, except when I tried to compile with support for my
SB-Live! card (emu10k1 chipset, running through ALSA). I went trhough
the instructions and the package did configure correctly, here's what I
asked of it:
./configure --help (just to see what options did I have)
./configure --enable-arch-asm=yes --enable-alsa=yes --enable-sdl=yes
--enable-emu10k1=yes --enable-vorbis=yes --enable-smpeg=yes\
--enable-capture=yes
make
Here's the error I get:
arch/emu10k1/emu10k1.c -o arch/emu10k1/emu10k1.o
arch/emu10k1/emu10k1.c:13:25: AL/alkludge.h: No such file or directory
arch/emu10k1/emu10k1.c: In function `emu10k1_blitbuffer':
arch/emu10k1/emu10k1.c:247: `fd' was not declared here (first use in
this fuction)arch/emu10k1/emu10k1.c:247: (Every identifier is only
reported once
arch/emu10k1/emu10k1.c:247: for the function in which it appears)
arch/emu10k1/emu10k1.c:267: warning: implicit declaration of function
`ASSERT'
arch/emu10k1/emu10k1.c:240: warning: variable `fds' not used
arch/emu10k1/emu10k1.c:241: warning: variable `i' not used
arch/emu10k1/emu10k1.c: In function `release_emu10k1':
arch/emu10k1/emu10k1.c:299: the value indicated by the subindex is
neither matrix nor pointer
arch/emu10k1/emu10k1.c:305: the value indicated by the subindex is
neither matrix nor pointer
arch/emu10k1/emu10k1.c:306: the value indicated by the subindex is
neither matrix nor pointer
arch/emu10k1/emu10k1.c:310: the value indicated by the subindex is
neither matrix nor pointer
arch/emu10k1/emu10k1.c: In main level:
arch/emu10k1/emu10k1.c:322: conflicting types for `get_emu10k1channel'
arch/emu10k1/emu10k1.h:28: previous declaration of `get_emu10k1channel'
arch/emu10k1/emu10k1.c:345: conflicting types for `set_emu10k1channel'
arch/emu10k1/emu10k1.h:29: previous declaration of `set_emu10k1channel'
arch/emu10k1/emu10k1.c: In function `pause_emu10k1':
arch/emu10k1/emu10k1.c:381: incompatible asignment types
arch/emu10k1/emu10k1.c: In function `resume_emu10k1':
arch/emu10k1/emu10k1.c:406: incompatible asignment types
arch/emu10k1/emu10k1.c: In function `capture_emu10k1':
arch/emu10k1/emu10k1.c:548: warning: `return' without values, in a
function tha does not return void
arch/emu10k1/emu10k1.c:553: warning: this function may return with or
without a value
gmake[1]: *** [arch/emu10k1/emu10k1.o] Error 1
gmake[1]: Exiting directory `/home/gianni/openal/linux/src'
make: *** [all] Error 2
Sorry if some of the messages are misspelled, since the output was
originally in Spanish I had to translate the best I could. Any ideas?
Thanks!
Gian Paolo