Hi,
After installing from src, I noticed the messages
"using path '/usr/local/src/rezound-0.9.0beta/share'
for share data directory". I did 'chown' on that.
Afterwards, Rezound failed to start the gui but that
could be attributable to having existing
processes--'killall rezound'. With no existing
processes and the chown, it asked which
alsa_pcm:playback port I wanted twice and then the gui
started. According to the documenation, it should ask
twice. When the gui fails, it only asks once.
Maybe there's something to my madness. I don't know
but I'm happy to see it running.
ron
--- derek holzer <derek(a)x-i.net> wrote:
My current [Gentoo] Rezound doesn't do this on my
PC, but does on my
PPC. Also, I remember my CCRMA Rezound acting
similar. If that isn't bad
enough, you also won't get anything like normal
throughput using Rezound
+ Jack. My typical experience in this way had lots
of glitches and
awful, repetitive buffering noises.
In such a situation, Rezound is totally unreliable
for recording with
Jack, and its only thinkable use would be to edit
samples while in th
emiddle of a Jack session.
The problem is that Rezound is a very unruley Jack
client, and the
makers fully acknowledge this. One solution is to
put more pressure [in
the nicest possibly way] on the Rezound list to make
the app fully
compatible with Jack.
Another problem, which goes hand-in-hand with this,
is Audacity's
anachronistic dependency on OSS. The new versions of
Audacity can do
lots of stuff that I otherwise would use Ardour
for... namely the
ability to load lots of different clips and do my
arrangements there.
But without Jack, or even ALSA, I don't see myself
ever using it as a
real sound app in my setup. So Rezound, buggy as it
is, remains the main
choice.
good luck,
d.
R Parker wrote:
I've always had trouble getting the Rezound
CCRMA
package to work as a jack client. When starting,
it
asks what alsa_pcm:playback is wanted,
establishes
the
connection with jack but never starts the gui.
root 8244 1.8 2.1 19376 19376 pts/8 SL
12:00 0:03 rezound --audio-method=jack
It starts fine if the audio method isn't jack. It
also
will start with jack as the audio method if I
compile
from source. Is there some trick I need to
employ?
--
derek holzer :::
http://www.umatic.nl
---Oblique Strategy # 78:
"Go outside. Shut the door."
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs