Begin forwarded message:
Date: Fri, 30 Mar 2007 21:50:52 +0100
From: Folderol <folderol(a)ukfsn.org>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [linux-audio-user] Peak Level Monitor/Limiting
On Thu, 29 Mar 2007 16:01:12 -0400
"Lee Revell" <rlrevell(a)joe-job.com> wrote:
> On 3/29/07, Folderol <folderol(a)ukfsn.org> wrote:
> > Can anyone suggest a way I can effectively suppress these peaks while
> > actually recording (rather than going back later, checking, then
> > re-recording) or is there a VU type metering program that can be tacked
> > on to jack?
>
> meterbridge
Thanks. This looks pretty good.
--
Will J G
--
Will J G
Begin forwarded message:
Date: Fri, 30 Mar 2007 21:50:12 +0100
From: Folderol <folderol(a)ukfsn.org>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [linux-audio-user] Peak Level Monitor/Limiting
On Thu, 29 Mar 2007 23:16:31 +0200
"Arnold Krille" <arnold.krille(a)gmail.com> wrote:
> 2007/3/29, Folderol <folderol(a)ukfsn.org>:
> > As many of you will know I principally use ZynAddSubFX to generate most
> > of my sounds, so I can't really be sure if this is a Zyn problem or a
> > general one with software synths and mixing.
> > Very occasionally I get high amplitude spikes typically 6dB above the
> > 'normal' peaks. These give a false idea of the signal level so that if
> > I'm not watchful I end up recording at a much lower level that I need
> > to.
>
> Whats the problem with recording at lower volume? As long as there is
> no da/ad involved you won't have any quality-loss.
>
> But I prefer to work with hot-signals too. ;-)
>
> Arnold
Because I retain the 'source' files, it makes sense for me to produce a
final wav format recording that complements all the others in apparent
volume, so that I can cut a CD directly in any mix of my music without
having to worry about unmatched levels.
--
Will J G
--
Will J G
Hello,
the last hurdle of complete transition from a Mac based studio to a
Linux one is to get the multiple Midiinterfaces running. I have an old
Emagic AMT8 connected to the computer via USB which is cascaded to an
even older Unitor. The AMT8 channels are visible but no further ones.
Has anyone similar rig? If this not work, what are current options of
8x8 midi interfaces? The market seems empty. I guess getting another
AMT8 from evilbay is the option, or?
Someone on this list gave some hints with the virt-midi module but I
couldnt get this to work because the cascaded interface is not showing
up anywhere. Unitors cant be connected directly to the computer because
they have no USB.
Cheers,
Malte
--
Malte Steiner
media art + development
-www.block4.com-
> We are, as we have been always, quite on our own in this little pocket
> universe of ours.
I think this issue is amplified by the fact that the conference also targets
by and large the same crowd. I am also not convinced that we would not be
able to find some software allies provided we begin catering to more diverse
audience... Linuxaudio.org consortium already has several high-profile pro
audio members.
Stay tuned for more updates in the coming weeks. This summer may introduce
hopefully some cool additions to the Linuxaudio.org.
Ico
As many of you will know I principally use ZynAddSubFX to generate most
of my sounds, so I can't really be sure if this is a Zyn problem or a
general one with software synths and mixing.
Very occasionally I get high amplitude spikes typically 6dB above the
'normal' peaks. These give a false idea of the signal level so that if
I'm not watchful I end up recording at a much lower level that I need
to.
I have found that if I let these peaks go into limiting, there is no
detectable audio effect, and displaying the waveform very stretched in
Audacity shows just these occasional spikes neatly clipped.
Can anyone suggest a way I can effectively suppress these peaks while
actually recording (rather than going back later, checking, then
re-recording) or is there a VU type metering program that can be tacked
on to jack?
--
Will J G
Dear members,
I am proud to announce that we will proceed with the list migration
during the night between the 31st March and the 1st April (at 0h00
GMT).
>From this point on, emails should be sent to these addresses :
- linux-audio-dev(a)lists.linuxaudio.org for the developper mailing list
- linux-audio-user(a)lists.linuxaudio.org for the user mailing list
- linux-audio-announce(a)lists.linuxaudio.org for the announce mailing list
The following aliases have been defined, to make it look nicer.
Consider them as shorter equivalents :
- lad(a)lists.linuxaudio.org for the developer mailing list
- lau(a)lists.linuxaudio.org for the user mailing list
No alias for the announce list since it is an open list (non
subscribers are allowed to post) and we fear a increase in spam with a
too short name.
Also, to respond to a request to a few of you working with command
line mail clients, the list tag at the beginning of the subject line
will be shortened :
[LAD] for linux-audio-dev
[LAU] for linux-audio-user
[LAA] for linux-audio-announce
You may need to update your email filters accordingly.
Those of you posting on the old addresses will get a message providing
you with the new email to use.
__________________
Marc-Olivier Barre,
Markinoko.
Message: 5
Date: Thu, 29 Mar 2007 23:38:30 +0200
From: Dragan Noveski <perodog(a)gmx.net>
Subject: Re: [linux-audio-user] Peak Level Monitor/Limiting
i think, recording at low level, you are kind of "loosing disc space".
lets say, if you are recording at 24bit, on low level the signal
information will take only 12 bit (example) and the rest of 12 bit will
be only empty data information.
don't think that one can repair that with some gain plugin or
normalization...
If you think about this for a couple of seconds, you may
decide to reformulate your opinion. In a low-level signal,
you say the "top" (Most Significant) bits will be zero. In
a high-level signal, though, the bottom 12-bits are all ones.
What is the difference?
In the computer, a signal is a signal, regardless of the
value at which it is represented. It is only when you try and
look at the distance from that signal to either the noise floor
or the max, or deal with non-linear perceptual effects (equal
loudness curves, etc.) that level may come into play.
It's not the absolute level that matters, it's the dynamic
range.
Cheers,
Phil M
--
"To misattribute a quote is unforgivable." -- Anonymous
Hi,
I wrote a while back about problems getting synths up and running:
>I bought my first midi keyboard last week (a CME UF5), and it's great
>fun with the Reason demo in Windows. But I've spent hours and hours
>messing with about 4 different synths under Linux and each one failed
>(in a different way, of course!).
I've now managed to get them all working so I thought I'd report the
problems and fixes here, in case anyone is interested. (This is all on
Fedora Core 6, so other distros may have other issues.)
1) JACK - at first, qjackctl wouldn't start it (though ardour would).
I then tried running it as root, which worked OK but wasn't ideal.
Finally I found http://www.passback.co.uk/music/fedora-music-intro/
which explained about editing /etc/security/limits.conf and now it
works fairly smoothly. (And I got ZynAddSubFX working.)
Though I have to start JACK with qjackctl - the code to automatically
start it doesn't work. It outputs:
exec of JACK server failed: No such file or directory
This seems to be a known problem:
http://www.nabble.com/the-fix-for-jackd-libjack-tmpdir-mismatches-t3156301.…
2) amSynth - the main problem was figuring out how to connect up my
midi keyboard to it and get a sound out of it. I still don't know
how to do this with ALSA, but the fedora-music-intro document
above helped me get it set up with JACK.
3) ams - the problem here was that most of the demos/tutorials required
various LADSPA plugins that I didn't have. I had to do a lot of
googling to figure out what package each one was part of.
4) bristol - at first it crashed on startup. This turned out to be a
bug in Fedora Core 6 - gethostbyname("localhost") was returning NULL
as the /etc/hosts file didn't have an entry for localhost.
I then tried it with ALSA, but it wouldn't start up because of
problems either with real-time priority or with the period size.
I eventually got it working with JACK.
5) fluidsynth - it seems that some .sf2 files work but some don't.
It outputs things like:
fluidsynth: warning: Ignoring sample mgtr: can't use ROM samples
I finally found Unison.sf2 which seems to work OK.
So the main problem was lack of documentation for new users. With just a
few sentences of good documentation I could probably have got them all
running pretty easily.
Hardly anyone explains how to connect up the inputs and outputs to get
the synths working with JACK. (Are we supposed to be psychic??)
I noticed that some synths automatically connect up the outputs
(bristol, amSynth), but not all of them. None of them automatically
connect to my MIDI keyboard. Why not?
Anyway, hope this helps in some way.
Damon
Hello. I'm excited about my new audio setup. Got everything working nicely.
Have no experience or knowledge of audio engineering so please bear with me
if I ask dumb questions.
1) Why use MIDI? I have heard stuff that I recorded professionally
sequenced with MIDI and must say that I can hear a difference. Is this
because it's all perfectly synced up? What are other advantages, if any, of
MIDI over audio?
I'd like to play with Rosegarden but don't have any MIDI files except the
ones I made with Hydrogen. If I wanted to sync up a guitar track perfectly
with the MIDI beat, I guess the best way would be to have the guitar track
as MIDI too, but I don't have a MIDI hardware device. Next question...
2) Is there Linux software that can convert an audio signal/file to MIDI?
Thanks in advance for answering these basic questions.
--
View this message in context: http://www.nabble.com/Newb-MIDI-questions-here...-tf3468151.html#a9676817
Sent from the linux-audio-user mailing list archive at Nabble.com.
Basically, if I'm recording live on a midi track and I keep the note
sustained for more then a measure, instead of a single prolonged note I
get two or more notes, starting and ending exactly at the beginning each
new measure.
Is it a bug or a feauture? :-)
Am I doing something wrong? I don't remember this behavior on previous
versions.
Ciao,
c.
--
http://www.cesaremarilungo.com