Hi
I'm trying to get started using lv2 synths inside ardour. I have calf
monosynth and reasonable sort of working. I use a2jmidid to get input
from my usbkeyboard showing up in as jack midi. I then connected the usb
keyboard to midi through in alsa tab in qjackctrl and midi through is
bridged to jack midi. So I selected a2j as midi in put for the two
synts. However they are both playing (makes sense, since they're both
connected to the keyboard), but how can I handle them, for instance so
that one only plays when I sit on the corresponding track?
Regards
--
Atte
http://atte.dkhttp://modlys.dk
I have an unusually pleasant surprise here: a MIDI wind controller
can drive a software synth without even having both of their apps
running. I would like to be able to get the resulting audio-signal
that is an output from this (normally sent to the PC's speakers)
redirected to Audacity's input-selector so that I can record it.
Any ideas?
Brian
In case anyone is interested. There are some bug fixes, and plans for more
feature additions.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hi,
say two guys would like to collaborate on the same Ardour project.
Remotely. Not realtime.
What would be the easiest way to share the project?
I am thinking about taking the files under git (session's
'interchange' dir *only*).
Is it completely insane?
Any ideas ?
Thank you
--
Carlo Ascani | carlorat.me
skype: carloratm
Hi guys!
The amzing mr Ricard has created a sweet patch editor for Waldorf
Blofeld. If you also happen to love that box but not so much its
interface, this is special for you!
https://github.com/polluxsynth/midiedit
Have a delicious awoken time,
--
Set Hallstrom
AKA Sakrecoer
http://sakrecoer.com
I've been slowing working my way though Yoshimi, looking for bugs and trying
to understand the code, with some success. However, I've come across something
that has me completely stumped.
On a modern machine if you look in the AdSynth edit window 'Detune' shows a
variable number of trailing digits, where it should only show 2 after the
decimal point. This is also true of all cases where a recalculated slider value
is indirectly shown in an associated uneditable box. It happens nowhere else.
I've seen this on 64bit dual core AMDs and on 32bit Atoms. However, on an
AthlonXP the problem doesn't occur.
At first I thought it might be due to different version of FLTK but having tried
various releases of debian, from 'lenny' up to the current 'testing', the
*only* differentiating feature I can discover is that the AthlonXP doesn't
recognise the sse flag.
Finally, to add to the confusion, compiling on any of the other machines,
without the sse flag set, still produces the fault - I'm wondering if even
without this, some math feature is still being used that causes the fault.
Any help or suggestions would be gratefully welcomed!
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
I've been using triangle dithering when I export at 16-bit in Ardour.
Not to start a religious war or anything, but I'd actually be interested
in hearing opinions about why that or some other alternative might be
better (shaped noise, etc.). How do you usually dither? Does it make a
difference?
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
Just a little, mellow improvisation with yoshimi DX rhodes while testing
my E-MU midi-usb dongle with my ancient yamaha keyboard. No editing,
just recorded directly through jack...
Dedicated with admiration and appreciation to all you sleepless open
source developers out there :-)
http://lorenzosu.net/temp/yoshimi_dx_impro.ogg
Good night,
Lorenzo.
On 03/02/2014 04:38 AM, Harry van Haaren wrote:
>/ On Sun, Mar 2, 2014 at 2:43 AM, david <gnome at hawaii.rr.com <http://lists.linuxaudio.org/listinfo/linux-audio-user>
/>/ <mailto:gnome at hawaii.rr.com <http://lists.linuxaudio.org/listinfo/linux-audio-user>>> wrote:
/>/ > On 03/01/2014 08:51 AM, Harry van Haaren wrote:
/>/ >> I generally export to 32bit float .flac... so no dithering (or burning
/>/ >> to CD's :)
/>/ > Hmm, I thought FLAC only did 24-bit???
/>/ I think the FLAC spec says it will handle anything from 4-32 bit-depth:
/>/ https://xiph.org/flac/faq.html#general__samples
/>/ That said, Audacity only has FLAC export options of 16 & 24 bit depths.
/>/ Ardour supports 8, 16 and 24. Still no 32 bit float support (at
/>/ application level).
/
24bit integer is equivalent to 32bit float in terms of resolution, and
pretty much identical as long as the float samples are clamped between
-1.0f and 1.0f.
>/ I should correct my previous statement though: I *thought* I exported
/>/ 32bit float: but it turns out they're 24bits (from Ardour3), dithering
/>/ set to None. And cropping the resulting output in Audacity and exporting
/>/ was to 16-bit PCM, so I was actually doing this all wrong (no dithering,
/>/ 32 -> 24 -> 16).
/>/
/>/ A better workflow would be to:
/>/ A) Ardour export 32 bit float -> 16bit (with dither) -> Audacity 16bit
/>/ in, crop, 16bit out
/>/ B) Ardour export 32 bit -> 24 bit (no dither) -> Audacity 24bit in,
/>/ crop, export 16bit (with dither).
/>/
/>/ The important part being to not dither twice, since then you'll be
/>/ adding noise to the signal twice!
/
actually, you *must* dither at every truncation step - if you don't, you
will lose information _and_ introduce signal-dependent requantisation
noise, which can never be removed again.
so the best approach is to only reduce the wordlength once, at the very
end of the chain, before going to CD.
some mastering people (bob katz among them) even go as far as demanding
dither at every level control in the chain.
however, if you are exporting from JACK's native 32bit float to 24bit
int _and_ you make sure that there is no sample larger than full-scale
(floats are funny :), then there is no actual loss of information, and
no dithering is required. all you do is map the 23 mantissa bits and the
sign bit of the float to the 24 bits of the integer.
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487
Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister VDT
http://stackingdwarves.net
I just wanted add a couple thoughts. First, the level of the dither
signal that you add depends on the target bit depth. So the dither for
24 bits is generally 8 bits (48 dB) softer than a dither for 16 bits.
Therefore, there is is nothing wrong with dithering one or more times to
24 bits. Keep in mind that quantization distortion or dither noise will
both be some 24 dB's below the threshold of hearing in a 24 bit file. I
wouldn't be particularly worried about either, but dither is much better
to have. I think you may run into issues if you use noise-shaped dither
repeatedly. Or, using noise shaped dither followed by equalization would
not be good in the sense that you could make the dither more audible.
There also may be issues with dithering floating point material since the
actual level of the musical signal is a bit of a moving target.
So, I would really only make sure about dithering one time as the absolute
last step in mastering to 16 bits. And if you have any thoughts about futher
processing of a 16 bit track, do not used noise-shaped dither.
Grekim
www.acousticrefuge.com/mixer4.htm
