Are w3m and Iceweasel broken here?
Does the calculator work for anybody?
http://www.sengpielaudio.com/Rechner-RCglied.htm
I know there are more extensive calculators available, but I would have
a simple calculator like this, to demonstrate something.
Does anybody know such a simple calculator that works?
Thanks in advance,
Ralf
PS: Sorry, it's OT, but I suspect that some of you know such a thingy.
Hi to all,
I'm an audio engineer in my day (and night) work, but definitely not a
programmer.
Yet there is one endless discussion between friends and colleges of mine
that I usually do not participate in due to the lack of knowledge.
The topic is algorithms of software (DAW) mixers. Some people say that they
can hear a sound difference between several kinds of software mixers (e.g.
Cubase, Protools etc.).
I must say that I never made any serious A\B testing but I didn't notice
that there is any difference. Although I do work with Pro-tools and Cubase
(in other studios), most of the time I'm actually using Ardour (and I'm
loving it).
My questions would be:
1. Is it only me that can't here a difference between different DAWs mixing
algorithms?
2. To the developers out there, what is your opinion? Is there a
better/worse algorithm, or is the whole thing another "pay 600$ for this
software - it has great algorithms!!!" hype?
3. If there is a difference what's the explanation?
4. Analog emulation plugins. How does one "emulate" analog waveforms in a
digital world? That sounds like a paradox to me.
Hope that's not to many questions in one mail.
Thanks for your time
Moshe
Hi, I'm trying to compile Calf plugins from GIT
(http://repo.or.cz/w/calf.git) on a Debian Wheezy.
I did those steps:
- retrieve the code with git clone
- run autogen.sh
- run make... the following error occurs:
/usr/bin/ld: ./.libs/libcalfgui.a(gui.o): undefined reference to symbol
'XML_SetUserData'
/usr/bin/ld: note: 'XML_SetUserData' is defined in DSO
/usr/lib64/libexpat.so.1 so try adding it to the linker command line
/usr/lib64/libexpat.so.1: could not read symbols: Invalid operation
Does anyone know how to fix this?
--
Nicola Pandini
On 07/19/2011 07:00 AM, Rustom Mody wrote:
> On Mon, Jul 18, 2011 at 4:37 PM, Robin Gareus <robin(a)gareus.org> wrote:
>
>>
>> Actually http://www.sonicvisualiser.org/ may be the tool of choice.
>> Here's a video where it is used to slow down some Bach so that you can
>> hear the "beating/pulsing" introduce by equal-temperament tuning:
>> http://www.youtube.com/user/mcldx#p/a/u/0/uOOhvw89jc4
>>
>>
> Hey Thanks! sonic visualizer seems to be what I want.
> Showing temperament variations visually is high on my list of what I want to
> do though that video is not doing such a good job of it.
indeed, even though one gets the gist.
Well, here's your chance to make a better one :)
The videos at http://www.sonicvisualiser.org/videos.html are better
quality, but there's nothing there about temperament-analysis or
demonstrating analogies of patterns at different orders of magnitude of
frequency.
> Any other suggestions for that will be most welcome!
maybe http://clam-project.org/http://isophonics.net/sawa/ is a web-interface that can do so (alas, the
website's upload function seems to broken at the moment) but under the
hood it uses the http://www.vamp-plugins.org/ as does sonic-visualizer.
Maybe s.o. else on the list knows one.
> On the other hand I can put take Indian classical music, slow it down with
> sonicV and get more microtonal distinctions than one can easily hear at
> normal tempo.
sure, it's definitly a good tool to hands-on explore the "wider
ramifications of music".
have fun,
robin
Hello hello,
The second official source code release Petri-Foo is now available.
IMPORTANT: I have designated this release as a 'preview' release to
indicate this is still a work in progress so that users may be aware
things may change and their files may not be usable without alteration
in future versions.
HOWEVER: I feel Petri-Foo has moved along quite nicely since 0.0.1 in
April and would like to share that work with a few more of you than
are subscribed to the Petri-Foo developers list.
WHAT'S NEW.... and good (since 0.0.1):
* Default Patch
A default patch using a looped generated triangle wave sample, with an
ADSR, LFO, and MIDI CC setup with sensible/default values so a new
user can immediately hear audio.
* Selectable MIDI controllers
MIDI controllers are now selectable amongst all the other modulation
sources. This has two benefits, the first is being given the choice
(of course), and the second is that you can now control how much
effect the controller has.
* Patchlist context menu
You can now right-click on the patch list to get a context menu to
allow you to perform add, remove, rename, and duplicate operations on
patches.
* Keyboard tracking
Keyboard tracking has been added to all the parameters, and
additionally, to the envelopes where it modifies envelope duration.
* LFO Amplitude modulation
The LFOs now have amplitude modulation so that. For example, the
default patch uses this in combination with the MIDI Mod Wheel
controller to control pitch modulation.
* RAW sample format loading
Allows one to load files never intended to be heard :-)
* Removal of LASH support
* Removal of ALSA *audio* output (note: ALSA MIDI still supported)
* Miscellaneous bug fixes and GUI clean ups.
Home pages...
http://petri-foo.sourceforge.nethttp://github.com/jwm-art-net/Petri-Foo
Download...
http://sourceforge.net/projects/petri-foo/files/Source/petri-foo-0.0.2.tar.…
git clone git://github.com/jwm-art-net/Petri-Foo.git
Bug reports...
https://sourceforge.net/tracker/?group_id=404816
jwm.art.net(a)gmail.com
Mailing list...
https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
please note, if you're not a member your messages ****are
automatically rejected**** :-p
cheers,
regards,
James.
Hi all,
I'm trying to build an audio logger- a machine to record audio that can stay
running all the time. I've been attempting to use Rotter and Jack for this,
but I'm getting the same problems across a variety of distros (Arch, Ubuntu,
Ubuntu Studio, CentOs &c.). I'm using an Edirol FA-101, attached to a P4
3ghz machine with a second SATA drive as an audio recording volume. I
launch jack, with a big period so as to avoid xruns:
jackd -v -d firewire -r 44100 -n 3 -p 4096 2> jack_stderr.log >
jack_stdout.log &
Then I launch multiple instances of Rotter, one per channel, six total:
rotter -f flac -c 1 -n channelone -d 500 -L flat -v
/secondsatadrive/channelone
.
.
.
rotter -f flac -c 1 -n channelsix -d 500 -L flat -v
/secondsatadrive/channelsix
Then I launch esjit and patch physical input one to rotter instance
channelone, etc.
This works, for a while. Jackd still gets xruns, but the recording happens
and files are written properly. However, after several hours and a whole
lot of xruns, it stops working. Files are still written and named properly,
but they are only a few hundred k in size and contain no audio. The error
logs show the xruns, but nothing else (no error messages, except for xruns).
The output of Rotter also does not show anything wrong. Clearly, jackd is
breaking somehow; anyone have clues? Any way to get more info from jackd?
What am I doing wrong? This problem is the same across several distros
(see above), and occurs whether or not I use the -R realtime flag.
I am preparing to give a talk on the wider ramifications of music.
One of the things I wish to demonstrate is that things that look different
are merely analogs but at different scales.
eg if something vibrates at 400Hz we hear a sound of A-flat. If it
'vibrates' at 4 Hz we hear a beat.
In the same analogy a 2 vs 3 poly-rhythm (should?) change to a do-so chord.
And so on.
Is there some kind of software where I can make a 4 Hz beat and pull a
slider or a freq text box entry until it sound like a A-flat note?
