Paul Winkler wrote:
"I could swear I remember seeing an old tube compressor that
had a gain reduction meter with "more" to the right, so it
moved in opposition to the corresponding VU meter.
No idea what model it was, and this was about 6 years ago
so I could be mistaken.
I wonder how consistent this is in the world of hardware?
maybe I'll pop a question on rec.audio.pro."
I built a tube compressor like that, an Altec436c.
The 'gain reduction' meter measures the bias current of the vari-mu
valve, which is reduced when gain reduction is required.
The meter goes from right to left. (Any other way would require more
circuitry, so I think it may just be a lucky accident.)
Talking of meters, don't some phase meters often go left *and* right
from a centre point to show averaged phase difference between the channels?
Hi,
has someone made experiences with the Terratec 5.1 PCI soundcard?
according to the alsa soundcard matrix, Terratec 5.1 Fun and 5.1 Sky are
supported, but i found no information about 5.1 PCI.
If not, maybe you can give me recommendations for another brand? the
terratec 5.1 pci costs about 20 euros; i don't need MIDI, and i don't
need sophisticated recording abilities. here's more about the card:
http://productsen.terratec.net/modules.php?op=modload&name=News&file=articl…
thanks,
Chris
I just realized I posted this to LAD but not LAU. Since the whole point
of HIGs is to be reflect user rather than developer needs, I am
reposting it here.
OK, so if I were to start writing the Linux Audio Human Interface
Guidelines based on all of the feedback from this post, I would say
something like the following. I have used the type of language you
would find in an Internet RFC.
"Sliders MUST be operable with the mouse wheel. This MUST only be
enabled when mousing over a slider, otherwise, the mouse wheel MUST
retain its normal behavior of scrolling the window.
For a vertical slider, rolling the mouse button away from you
(hereafter: wheel-up event) MUST increase the value of the parameter,
and wheel-down MUST decrease the value.
For a horizontal slider, wheel-up SHOULD increase the value, and
wheel-down SHOULD decrease the value by default. However, this behavior
MUST be configurable. If a system-wide facility to control
this is unavailable then the app MUST provide a configuration
mechanism."
Additional submissions are welcome and in fact essential, since the
above only covers one aspect of one widget's behavior.
Lee
->"Sliders MUST be operable with the mouse wheel. This MUST only be
enabled when mousing over a slider, otherwise, the mouse wheel MUST
retain its normal behavior of scrolling the window.
For a vertical slider, rolling the mouse button away from you
(hereafter: wheel-up event) MUST increase the value of the parameter,
and wheel-down MUST decrease the value.
For a horizontal slider, wheel-up SHOULD increase the value, and
wheel-down SHOULD decrease the value by default. However, this behavior
MUST be configurable. If a system-wide facility to control
this is unavailable then the app MUST provide a configuration
mechanism."<-
Possible to make it like one of those nintendo emulators, where you have
a default setting, several presets, plus "line item" configuration if
you want? From what I've read about this in the past, it seems like
there's enough difference in opinion that the only solution would be one
that allows people to keep their difference of opinion, and to me it
seems extra configuration is worth the extra work in coding... but I'm
not a programmer so I don't really know how much extra the work is.
Matt
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
Rick B
On Wednesday 25 August 2004, Michal Seta wrote:
> > I have tried just about any concievable configuration but to no
> > avail. Is there anything special I have to do, other than in 0.9.8
> > (recording worked fine there) to record?
>
> ok, so I recompiled 0.9.8 and eveerything seems to be working for now. I'm
> still willing to give 0.9.9 a go but...
There is a little change between Rosegarden 0.9.8 and 0.9.9 regarding record
devices. In 0.9.8 you could record only from one source, and the subscription
was automatic (although you could change it later) to the first readable ALSA
sequencer port in the system. In 0.9.9 you can record from any number of
devices at a time, but you need to subscribe to them by hand. To do this, go
to the main window menu, select "Composition/Studio/Manage MIDI devices" item
to open the MIDI Manager window, and use the bottom half controls (click over
some checkboxes under the "current" header column) to select the active(s)
MIDI recording devices.
This is a very new feature, and there can be bugs. Rosegarden is now in beta
testing, prior to the 1.0 release and we are very much interested on bug
reports. Please report if this doesn't work to the rosegarden-devel mailing
list. Thanks.
Regards,
Pedro
Hi,
I'm trying to compile hydrogen on my CCRMA/RedHat PC (Pentium 4)
And I get this error:
--------------------------------------------------------------------
g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I/usr/lib/qt-3.1/include
-I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -O3 -c -o
PatternEditor.o `test -f 'PatternEditor.cpp' || echo './'`PatternEditor.cpp
PatternEditor.cpp: In constructor `PatternEditor::PatternEditor(QWidget*,
PatternEditorPanel*)':
PatternEditor.cpp:41: `WNoAutoErase' undeclared (first use this function)
PatternEditor.cpp:41: (Each undeclared identifier is reported only once for
each function it appears in.)
make[3]: *** [PatternEditor.o] Error 1
make[3]: Leaving directory
`/I/Useful_Stuff/Linux/Audio/hydrogen-0.9.0beta1/hydrogen_gui'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/I/Useful_Stuff/Linux/Audio/hydrogen-0.9.0beta1/hydrogen_gui'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/I/Useful_Stuff/Linux/Audio/hydrogen-0.9.0beta1'
make: *** [all] Error 2
--------------------------------------------------------------------
Any suggestions?
Thanks in advance for any reply.
Peace,
~Jos~
Hi,
I would just like quickly whip some MIDI sequences. I had RG 0.9.8
but couldn't get metronome working (everything was fine in the setup
dialog, I could hear a sound and all but no luck when rolling). SO
anyways, short story, I noticed that 0.9.9 was out. Downloaded,
compiled and he metronome is working but I cannot record any midi. I
can see the levels associated with tracks going on MIDI events, on the
track canvas I can see white lines blinking when I play but nothing
actually stays recorded.
I have tried just about any concievable configuration but to no
avail. Is there anything special I have to do, other than in 0.9.8
(recording worked fine there) to record?
thanks in advance for any pointers.
./MiS
->Using fc2, I've tried to compile audacity so I can use it with jackd.
Primarily so I can use my ice1712 (delta 44) recording card.
I'm completely frustrated, anyone successfully done this? I'd love some
help.
Daryl<-
Will it not compile? I assume you've read all the directions about
enabling portaudio v19.... my biggest problem compiling audacity has
been in the linking. There is a known bug in the configure process for
portaudio v19, where you have to descend into the src directory of the
build tree, open the Makefile, and in the "LIBS" section, add -lasound
and -ljack at the end of the line - this may have been fixed since the
last time I tried compiling it... so I'm not sure if this is still a
problem. This is just my guess as to what your problem is; some
specifics would be helpful. (I've never tried it under the 2.6
kernel...)
Matt
