On Tue, Aug 05, 2008 at 05:16:18PM +0700, Patrick Shirkey wrote:
> I disagree. After all petrol is considered a fuel but unless you burn it
> you don't get much energy from it.
Petrol is considered a fuel because you can burn it,
and then it delivers thermal energy. In the same way
you can burn hydrogen, so it's a fuel. What remains
in that case is water. That doesn't make water any
more a fuel than the waste products of burning petrol.
> Also it is way more catchy...
Being catchy is no virtue. On the contrary, the
'catchy' way science is presented in the popular
media is doing more harm than anything else.
It creates the false illusion that the current
state of science can be understood in intuitive
ways, which is simply not the case.
That goes not only for e.g. physics which we
are discussing in this thread, but also for
'human' sciences such as psychology. Just ask
around: most people are convinced they has some
insight in the psychology of e.g. persons of some
public interest, e.g. noted criminals, by using
terms as 'the human mind', 'passions', 'the
unconscious', etc. etc. while scientific psychology
has discredited and dropped these useless inexact
terms for at leas the last forty years.
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
O tu, che porte, correndo si ?
E guerra e morte !
Quoting Patrick Shirkey <pshirkey(a)boosthardware.com>:
> While we are discussing alternative fuels for cars, some of you may be
> interested in my new blog and the latest advancements in open source
> research on using water as a fuel ...
>
> http://yeswaterisfuel.com
You can use energy (electricity) to divide water molecules into oxygen and
hydrogen and thus using water as a no-loss battery.
But a fuel? No, water is not a fuel. Hydrogen, now there's a fuel.
This technology is very interesting and has potentially huge uses as a
no-loss battery making solar power very usable for homes. But this website
uses "water as a fuel" to do what looks like nothing but childish experiments.
Sampo
hi there everyone.
i hope this is the right list for this, but i just had a question
about embedded hardware.
if i was wanting to develop a small (up to around 20cm square) device
using an embedded linux setup, is there any high end (pro quality jack
compatible) audio devices that are easily attainable? basically
something like a high end adc/dac for minipci or something similar i
suppose.
anyone on here know?
thanks
porl
ps. should this be posted to the users list instead, since i suppose
it doesn't have a direct connection to linux development?
it would be nice to see something like this integrated into ardour, at
least in the output channels as an option. i'd like the ability to get
a standard reference level to compare against apart from the 'ok, it
has clipped now, turn it down a tad' level it currently shows :)
porl
2008/8/4 Raphaël Doursenaud <rdoursenaud(a)free.fr>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Fons Adriaensen a écrit :
>> Hello all,
>>
>> The first release of jkmeter is now available in the
>> usual place:
>>
>> <www.kokkizinita.net/linuxaudio/downloads>
>>
>> Also updates of japa and jnoise (mostly maintenance,
>> but see also below).
>>
>>
>> From the README:
>>
>>
>> jkmeter-0.1.0 (03/08/2008)
>> --------------------------
>>
>> Jkmeter is a horizontal or vertical bargraph level
>> meter based on the ideas of mastering guru Bob Katz.
>> See <http://www.digido.com/bob-katz/index.php> and
>> follow the links on 'level practices'.
>>
>> This is the type of meter you want for live recording,
>> mixing and mastering. It probably makes no sense to
>> use it on all tracks of a DAW, where keeping digital
>> level within limits is the main purpose of metering.
>>
>> This release implements the K-20 meter. Future
>> releases will include the K-14 meter as well.
>>
>> A K-meter displays both the true RMS level and the
>> digital peak level. The ballistics as defined by Bob
>> Katz are somewhat ambiguous. In this implementation
>> the RMS meter is about 15% faster than an VU, but
>> without the overshoot. This provides a good indication
>> of subjective loudness.
>>
>> Instead of providing extra gain for the RMS level,
>> the K-meter displays it on the same scale as the
>> digital peak level, but puts the '0dB' mark and the
>> color change well below the OdB full scale level.
>> For the K-20 meter it is 20dB down, for the K-14
>> this is (surprise !) 14 dB.
>>
>> To use the meter as envisaged by Bob Katz, you
>> should have a fixed monitoring level, adjusted
>> so that pink noise indicating 0dB on the meter
>> corresponds to 83 dB(C) (from each speaker) as
>> indicated by an sound level meter. Note the (C)
>> - not (A) - weighting.
>>
>> As of release 0.4.0, both japa and jnoise provide
>> a pink noise source at exactly this level.
>>
>> The current release does not include the 22kHz
>> lowpass filter required for frequencies such as
>> 96kHz and higher.
>>
>>
>> Enjoy !
>>
>>
> Thanks a lot! It's been some time I was waiting for such a meter!
>
> Of course the adress is : http://www.kokkinizita.net/linuxaudio/downloads/
>
> - --
> Raphaël Doursenaud
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFIlcHdaZKmNAdXaVURAqRjAJ0RKzH1aBd2X2b4uLd7DlmzPn7RTgCggOde
> fHD2FVK7O1gbUSawrnjNuQs=
> =yLA9
> -----END PGP SIGNATURE-----
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 3:
* Fix typos in docs
* Disable use of C++ demangling in sigsegv. Fix for sr #2074
* Fix a2j_control help text (thanks kfoltman!)
* Request fixed JACK client name. Fix for bug #12139
* Handle missing svnversion executable nicely. Fixes bug #12138
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Hello all,
The first release of jkmeter is now available in the
usual place:
<www.kokkizinita.net/linuxaudio/downloads>
Also updates of japa and jnoise (mostly maintenance,
but see also below).
>From the README:
jkmeter-0.1.0 (03/08/2008)
--------------------------
Jkmeter is a horizontal or vertical bargraph level
meter based on the ideas of mastering guru Bob Katz.
See <http://www.digido.com/bob-katz/index.php> and
follow the links on 'level practices'.
This is the type of meter you want for live recording,
mixing and mastering. It probably makes no sense to
use it on all tracks of a DAW, where keeping digital
level within limits is the main purpose of metering.
This release implements the K-20 meter. Future
releases will include the K-14 meter as well.
A K-meter displays both the true RMS level and the
digital peak level. The ballistics as defined by Bob
Katz are somewhat ambiguous. In this implementation
the RMS meter is about 15% faster than an VU, but
without the overshoot. This provides a good indication
of subjective loudness.
Instead of providing extra gain for the RMS level,
the K-meter displays it on the same scale as the
digital peak level, but puts the '0dB' mark and the
color change well below the OdB full scale level.
For the K-20 meter it is 20dB down, for the K-14
this is (surprise !) 14 dB.
To use the meter as envisaged by Bob Katz, you
should have a fixed monitoring level, adjusted
so that pink noise indicating 0dB on the meter
corresponds to 83 dB(C) (from each speaker) as
indicated by an sound level meter. Note the (C)
- not (A) - weighting.
As of release 0.4.0, both japa and jnoise provide
a pink noise source at exactly this level.
The current release does not include the 22kHz
lowpass filter required for frequencies such as
96kHz and higher.
Enjoy !
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
O tu, che porte, correndo si ?
E guerra e morte !
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Fons Adriaensen:
>
> The data used by car manufacturers to describe engine noise
> is a spectral description, where some small divider of the
> RPM (depending on engine configuration) is regarded as the
> funcdamental frequency. For each harmonic you have a smooth
> amplitude map in function of RPM and throttle position.
>
> Staring from these it's not so difficult to synthesise
> something quite realistic.
>
The company "Staccato" tried to provide synthesized car sounds
for race car games in 1999, according to this page:
http://www.scandalis.com/Jarrah/PhysicalModels/index.html
Florian Faber wrote:
> Peter,
>
>> I doubt that it is easy over a transport protocol that doesn't have a
>> global absolute time reference (like ethernet).
>
> What time reference do you have in mind on ethernet that can be used as
> word clock source?
My formulation is a bit unfortunate. I mean that ethernet does NOT have
a global absolute time reference. And word clock is not a time
reference. It's a 'rate' reference, which does not contain absolute time
information. What you need to output signals on different devices with
sample accurate phase is an absolute time reference. Which ethernet does
not have.
Greets,
Pieter
I have some doubts, as both host and plugin programmer, regarding the text
encoding that should be used for Ladspa v1 metadata fields. Is there any
convention? Utf8? Is it limited to plain ASCII? Which fields are restricted
and which are not?
I supose that unicode is supported in some way as many 'makers' have weird
signs on their name but the header-documentation does not provide any answer
to that.
David García Garzón.