Hi,
Just for fun I created a google map for linux audio users to post their
location (and IRC handle), if they so desire. I've seen it done with
other groups, so I thought we needed one of our own. :-)
Here is the short link:
http://goo.gl/maps/Rk0rC
Rich...
Hallo,
I want do sync my old atari programs with mtn/mmc to jack.
I did some experiments with ardour rosegarden and muse. Start and stop
commandos work, but all programs don't synchronize the tempo.
Is there a program that can sync jack as slave to external mtc or midi
clock?
thanks
--
www.christian-bunge.de
--
www.christian-bunge.de
--
www.christian-bunge.de
--
www.christian-bunge.de
Hello everyone!
Trying to compile eq10q I have a problem: I can't compile plotmm and Debian
Squeeze has no package named plotmm.
Two alternatives: Can I exclude the GUI creation from the Makefile?
If not: in plotMM I get a problem, that sigC is not defined. Which package
to install for that? I have libsigc++-2.0 and libsigc++-02c (plus dev of
course). I also installed libsigx on a whim. No go. Version of one of them too
new perhaps?
Kind regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
Hi,
It has come to my attention that the SFLC has said they are not prepared
to take on Dolby in regards to licensing the ac-3 patent to the OBE
project for professional broadcasters. Apparently they feel that ac-3 is
not a big deal to the Linux Audio community and that professional
broadcasters should be left to take on Dolby at their own expense.
I am wondering what people on this list feel about their position and
Dolby's unwillingness to play fair under their FRAND obligations.
This is also linked to the attack on Kim Dotcom that has been undertaken
by certain Hollywood players and it has had a direct impact on the New
Zealand movie industry as well as delayed the release of the Hobbit movies
among other things.
My feeling is that this would be a very big case for the SFLC to fight and
they would be more interested if they knew how much it affects Linux Audio
and Multimedia software adoption for professional use.
--
Patrick Shirkey
Boost Hardware Ltd
I didn't realize I had jack set to a 48k sample rate and exported a wav.
Oops.
Any simple way to convert this?
I just used sox to do this:
sox export.wav -r 441000 resample.wav
Exported 500MB of silence.
Thanks for any advice.
Hello,
currently I have set up a ALSA <-> JACK connection with the loopback
device approach as described here:
http://www.penguinproducer.com/2011/11/jack-alsa-bridge-kit/
This works fine, except for one problem: Simultaneous playback of
multiple applications using the ALSA loopback device to channel the
audiostream to JACK fails with this error:
Device or resource busy
The setup in my asound.conf is quite simple:
# Audio _to_ JACK
pcm.jack_playback {
type plug
slave.pcm "hw:Loopback,0,0"
}
# Audio _from_ JACK
pcm.jack_capture {
type plug
slave.pcm "hw:Loopback,0,1"
}
pcm.playback_loop {
type plug
slave.pcm "hw:Loopback,1,0"
}
pcm.capture_loop {
type plug
slave.pcm "hw:Loopback,1,1"
}
pcm.jack_audio {
type asym
playback.pcm "jack_playback"
capture.pcm "jack_capture"
}
I thought that "type plug" should autoconfigure the device in use
accordingly. I tried to make a manual configuration with dmix but it
didn't work and I'm not sure if it is necessary. The alsa documentation
states that dmix is used when the device has no hardware mixer and I'm
quite sure that a virtual loopback device has none.
best,
semkath
Hello all,
I've been asked (in a private mail) if I would provide 'upstream'
support for the logarithmic F-scale patches for JAAA which have
been discussed recently on this list.
The answer is maybe, but certainly not in their current form.
1. As a first and sufficient reason, I don't want to develop
the current codebase any further. It's a glorious mess, and
in order to add some other features I want to add it needs
to be redesigned from scratch or at least completely refac-
tored.
2. The current log X-axis grid and annotations are a no-go.
I pride myself on getting such things (including slider and
meter scales etc.) right, even if that often takes more work
than the actual DSP code. Very few tools get this right, even
Gnuplot's log scale is useless in many cases (try zooming in).
A decent log F-axis needs a lot of ad hoc code (which I mostly
have, from other projects). It needs to support arbitrary
zooming, and both a technical (i.e. based on a 1, 2, 5, 10
sequence) and a musical (based on octaves, as in JAPA) format.
3. JAAA's original purpose was to measure organ pipe spectra
(it was presented at the same LAC as Aeolus IIRC). More
generally it is a technical tool, meant for for electronic
or acoustic engineers, not for sound engineers doing their
normal job of recording or mixing music. As a technical
tool it must provide results that are both as accurate as
possible and well-defined. Well-defined means results that
correspond to quantities, equations, etc. that are used in
electronics, acoustic and DSP theory, not necessariy the
most relevant ones in a musical context. For such technical
uses the most convenient presentation is on a linear F-scale,
for the simple reason that the analysis performed by JAAA
(essentially a DFT with some extensions) is defined in terms
of a linear frequency domain.
4. In those cases where a logaritmic frequency axis presentation
would make sense (the classical 'marketing style' frequency
response plots), JAAA is simply not the right tool. It does
not provide enough resolution at LF, or tons of irrelevant
and misleading detail at HF. And anyway, you can't measure
speakers, mics, etc, with continuous signals (as expected by
JAAA) unless you have a large anechoic room at your disposal.
And if you really want to do such measurements, the tool the
use ATM is JAPA with either a slow logarithmic sine sweep or
pink noise. There *is* a lack of good Linux based tools for
this sort of thing, but the cure is not a log F-scale for
JAAA but some extra features in e.g. Aliki.
But of course I'm looking at this from my perspective. If there
are any people out there using JAAA _and_ wanting a log F-scale
I'd like to know what exactly they are doing. It may not result
in a log F-scale for JAAA, but maybe in something better.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
On Saturday 22 September 2012 11:38:22 Ricardus Vincente did opine:
> On Fri, 2012-09-21 at 23:13 -0400, Gene Heskett wrote:
> > An even better idea would be to tell us how to place a pin. Its not
> > obvious.
>
> When the maps loads, you will see an EDIT button. The EDIT button will
> appear on the page where you see the SAVE/DONE buttons in the attached
> image. Hit the EDIT button, and after a few moments, a toolbar will
> appear at the top of the map (see attached image). Select the middle
> tool (I call it the pin tool). When you have selected it, some sort or
> marker, or X (the pin) will appear under your mouse cursor. Drag the pin
> to your location, and when it's where you want it, click the left mouse
> button. You might have to change the zoom level (zoom out) of the map to
> get where you want to go more quickly. As you get closer to your desired
> location, you can zoom in more to get a more precise placement. You
> should also see a dialog in which you can enter your IRC nickname, or
> name, and some other info about yourself.
>
> Please be careful when you are in edit mode, because you can move other
> peoples' pins.
>
> When you are finished hit SAVE and DONE and you should be fine.
>
> http://goo.gl/maps/Rk0rC
>
> Rich...
I got it, sorta. That page needs popup help in the worst way. I centered
my location on the map, then clicked on the pin, and the map took off north
about 10 miles before it autoplaced the pin by hitting the lower border of
the window. And it only gave me one chance to move it afterwards. The pin
and the map became locked and couldn't be unlocked. It is within about 100
feet, but the map of my subdivision is so wrong that its difficult to make
sure I put it correctly. Two adjacent streets show the same name, and
another street whose name should be on the eastern duplicate named street,
does not exist and had not existed in the about 50 year history of this
development. That of course is not your fault, thats 100% google's
problem. It also appears that the sat photos have been updated since 2008,
with new stuff that is much less sharp so it is no longer possible to
overlay the photos on the street map to correct it with absolute certainty.
I have done this once before, quite some time back, and compared to that
experience, this version has more bugs than 7 day old road kill. That too,
is quite likely NOT this groups problem. For this particular application,
I'd have to say that the programmer should have been (figuratively) shot 5
years ago when it was a usable application.
Oh well, perhaps another shot of coffee will help my attitude? When one is
north of 3/4ths of a century, it does tend to get a bit jaded.
Thanks all who responded.
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
A bug in the hand is better than one as yet undetected.