This is Steinway_IMIS soundfont, version 2.2.
ftp://musix.ourproject.org/pub/musix/sf2/Steinway_IMIS2.2
This version fixes the issue with loops. I hope this is the good one
and there are no more remaining major bugs.
Marcos is a little busy right now, so he asked me to make this fix. He
is thinking to make other improvements, so expect more updates soon.
Hello,
Does anyone know of a good plugin that will generate subharmonics?
I would like to put a little more low frequency "oomph" into my bass
track. Preferrable LADSPA, but VST would work, too.
Thanks for any help!
-TimH
Hi guys (and gals),
a good friend of mine is in the market for a mixer that is at least
capable of recording a whole band simultaneously.
He thinks that 16 channels might be a minimum for that, but he isn't
exactly experienced, and me neither.
It would be nice if it would work as firewire audio interface as well,
like the mackie onyx mixers, mainly because it might mean less trouble
overall.
Those onyx mixers look nice, and are supported by ffado, but we'd
like to have some more options.
Linux support isn't a strict requirement but it would be really nice to
have as option. So far it didn't work for him, but when the hardware
works with linux I can show him what's there and what's new from time
to time.
In this case he has a budget of up to 3000 Euros or possibly more, but
the stuff really needs to work for a studio.
Thanks in advance for any advice,
best regards
Philipp
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 !
I'm using an Adaptec AHA-7850 SCSI interface card. I used this in the
past with Sound Forge (back when it was made by Sonic Foundry) and it
worked fine.
I think SMDITools' problem with the ESI4000 is sample numbering. I
believe SMDITools starts at 0 where the ESI4000 starts at 1 (0 is the
clipboard). I'll come back with more info when I get another chance to
dig around in the SMDITools code (my C is far from great though (far
from good, even)).
Thanks,
Dan
Gordon J. C. Pearce (MM3YEQ) wrote:
> On Fri, 2008-09-19 at 15:23 -0400, Dan Richert wrote:
>
>> I posted about this a couple years ago on LAD or LAU, but I thought a
>> fresh thread might attract some new insight.
>>
>> I'd like to get SMDI transfers to/from an E-Mu ESI4000 working under
>> Linux. I've tried SMDITools ( http://nolv.free.fr/SMDITools/ ), but
>> that doesn't seem to work quite right with the ESI4000. It's been a
>> little while since my most recent go at it so I don't remember the exact
>> problems I was running into.
>>
>> Has anyone had any luck getting SMDI transfers to work with the ESI4000
>> under Linux?
>>
>
> No, but it's something I'm interested in. I started to develop Ensoniq
> Mirage and EPS MIDI transfer tools, and downloaded the SDS and SMDI
> spec, but haven't started on those yet. There seems to be a serious
> lack of SDS tools in Linux (please don't mention sox - I *know* it will
> create something approximately like SDS, but it's not SDS and will
> actually crash most samplers).
>
> Which SCSI card are you using? Has anyone successfully used SMDI with a
> USB-to-SCSI adaptor, or used one of these adaptors at all in Linux?
>
> Gordon
>
>
schoappied schrieb:
Sorry, no, I didn't realize I was sending to you only. This one gets me just so
often...
> Thanks, for your comment... (did you realize it was just to me and not
> to the LAU mailinglist?)
>
I have some limited experience playing other keyboards/E-Pianos than my own old
Roland JX-305, which is a 61-semi weighted keys synth which specialised in
'Dance, R&B, Techno' etc kind of sounds. It was the keyboard version of the
MC-505 Groovebox in fact. Initially, I started off as a guitarist and just
wanted to have a keyboard/synth to play some accompaniments to my guitar
noodling. Today I play more keyboard then guitar, also for other reasons.
I have tried/played some diff. keyboards/controllers, like i.e. the M-Audio
Keystation Pro 88 (favoring a controller/softsynth approach), some of the better
Roland/Yamaha Stagepianos, the Yamaha CP-series and then some...
I personally most often preferred the Roland keys in the lower pricerange, the
Yamaha keys win in the upper pricerange IMHO. The CP series i.e. are all high
quality, keys and soundwise. But then these are all outta your pricerange I
guess, unless you'll find some 2nd hand top offer.
> I think you speak some right words.. Have you experience with playing
> elektr. piano/ keyboards?
>
Polyphony is the max playable number of notes that can be played at any one
time. So, if you're playing a simple C chord, you'll use up 3 voices of
polyphony (C - E - G). But if now you keep them ringing with the sustain pedal
to play some single notes over your chord, you stack up the voices.
Since Piano/E-Piano playing very much involves your sustain pedal, it quickly
builds up to way more then 32 voices.
> Where do you use polyphony for? Does 64-voices of polyphony also mean
> that the keyboard has 64 keys?
>
Good luck in your search. It may be worth checking local garage sales, flea
markets and the 'for sale' columns of your local newspaper/hebdomadal magazines.
> Yes, I try to find somewhat second hand.
>
> And I will take some hours to test a bit in a local store. Good advice,
> thanks!
>
> Dirk
>
Cheers
Raphael ;)
--
________________________________
"A mind is like a parachute -
It doesnt work if it's not open."
|- - - - - - - Frank Zappa - - - - - - -|
Hi,
I've got a strange behaviour with my midi controller and/or freebob/ffado.
I made a pure data patch, with a midi learn function. So I can control
everything with my midi controller.
When I use jack with Freebob or ffado (I tested both) and a Presonus
Firebox, I got cracking sounds every time I move faders, pots from my Midi
Controler.
When I use jack with alsa and a poor usb berhinger UCA202 it works perfectly
: no cracking sounds
I am running Gentoo, with a rt kernel. I configured the rtirq script.
I tested it on a opensuse with rt kernel too, and it does the same.
Could someone test my patch and tell me if he got cracks ? with firewire ?
with alsa ?
You will need at least pd-0.40 or more.
Some externals, they are not necessary to hear sounds (bbogart (for popup),
sigpack~, zexy, iemlib).
The patch contain
* 3 live loopers with effects
* Master to set tempo, general volume, general pitch, and rooting + a
preset/bank system.
* a sub-patch with a DrumStation
* a sub-patch with a small synth (TriOsc)
To test rapidly you just have to click on the load bank button (on the
bottom-left corner), and you should hear sounds from the TriOsc synth
Then you can assign control clicking the green led under each control. The
red one is to forget the assignement.
here is the patch : http://mysthr.free.fr/Documents/LiverLooper-0.6.tar
Thank you very much !
kind regards,
Mysth-R
--
*
***************************************************************************************
* {^_^} Mysth-R {^_^}
* <= Aide Auditive =>
*
* http://myspace.com/mysthr
* http://myspace.com/aideauditive
* http://mysthr.free.fr/Joomla => Site dédié à l'audio sous
Fedora/PlanetCCRMA.
*
***************************************************************************************
Hi,
I have turned an old analogue electric organ into a MIDI controller. All the
old push buttons, switches, pots, drawbars can now trigger MIDI events.
Because I would like to make the MIDI messages static (i.e. they are linked
with particular buttons and faders and will not be changed) I have thought of
using an external application (keykit in this case) to work on incoming MIDI
events of the MIDI controller, filter them and trigger newly defined MIDI
events with it.
I would like to make the MIDI messages transmitted by the controller as short
as possible. I have thought of assigning the Bx (Control Change) command to
the buttons and faders, but this would mix with/overwrite other control
change commands sent by other MIDI devices.
It has to be possible to distinguish between the buttons/faders by the MIDI
message that each one triggers.
How about the System Common Message F4 and F5 which are not yet defined in the
MIDI standard? Could I add some extra data bytes to identify the type (button
or fader), the number and value?
Like this:
F4 125 70 (Fader 125 sends value 70)
keykit would recognize this fader and set volume level for channel 2 for
fluidsynth.
Or, in another situation, increase sustain value for channel 3 for fluidsynth.
or:
F5 10 1 (Button 10 sends value ON)
keykit would recognize the button and turn on sustain for channel 1.
Thanks for any hint and kind regards,
Crypto.
I'm looking for a free way to convert my PDF scores to MIDI files, to save
the work of manual entry.
I think it can be done in Finale (convert pdf to tiff first), but that
doesn't help me any.
Is it possible?
--
Christopher Stamper
Email: christopherstamper(a)gmail.com
Web: http://tinyurl.com/2ooncg
gTalk: http://tinyurl.com/6e359r
Skype: cdstamper
On Mon, 29 Sep 2008 17:52:27 +0100, garryo <garry.ogle(a)tiscali.co.uk>
wrote:
> strangely the guy in the vid set rt priorities for qjackctl, ardour and
> other audio softs he was using as well as the expected jackd.
> surely only jackd and the sound card IRQ need real time priorities?
> or am i missing something here?
I finally found the time to look at it... It is probably one of the best
rt-audio tutorials I have seen...
Picture that: a guy actually takes the time to make *video* for the *linux
journal* to tell you to change the RT prio of.... QJACKCTL ! I hope I
misunderstood... Really...
And what's all this about set_rlimits ? There's PAM for that (well, except
maybe on slackware where they... don't like PAM)
Oh, a good one too : "As is usually the case with Linux, the first thing we
need to do is recompile the kernel". Dude... this is 2008... We have audio
distros out there...
Seriously, who's that guy ?
-- Marc-Olivier Barre --
--- MarcO'Chapeau ----
- www.marcochapeau.org -