Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
piano_sample_instrument [2019/05/10 16:14] – created reposted after it hadn’t been moved to its new location. Paulinko | piano_sample_instrument [2019/05/12 03:08] (current) – this page superceded by ios_piano_thoughts espiegel123 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | ||
- | ##Piano Sample Instruments | ||
- | by posted to the Knowledge base by @LinearLineman | ||
- | |||
- | ### | ||
- | |||
- | ####Layers and Velocity Mapping | ||
- | * Here's what I know about velocity. The midi spec ties a velocity value from 0-127 to every note. So a keyboard app would map some ranges it detects to values between 0-127. A velocity map in the App would align these input velocity numbers with 2 things: | ||
- | |||
- | * a sample from a specific layer (softest to hardest) | ||
- | |||
- | * layer 1 - velocities from 1-10 | ||
- | * layer 2 - velocites from 11-20 | ||
- | * etc. | ||
- | |||
- | * then output that sample with an adjustment in volume to smooth out the jumps from 10 to 21 for example. | ||
- | |||
- | * The layers allow the tone of the piano at various volumes to come through increasing the realism BUT they increase the overall sample size (13GB Clossus with 24 layers). | ||
- | |||
- | #### | ||
- | * Samples can be capture in 16, 24 or bits and at 41K, 44K or 96Khz. Colossus is 24-bit at 96Khz. It's a better recording essentially. | ||
- | |||
- | ####CPU, RAM Resources and Disk Streaming | ||
- | * Larger samples at 96Khz consume a lot more CPU to process. To be processed the sample must be in RAM. Disk streaming means the application loads up enough sound to start any note at any volume. After a note it invoked the additional portion of that sample is brought up from the disk. Somewhere in the IOS hardware there' | ||
- | |||
- | * Colossus Piano by Christian Schoenebeck d/b/a Crudebyte[🏪](https:// | ||
- | |||
- | * **AU support** | ||
- | * An AU may not work correctly with a DAW controlling the CPU and the AU App being coded to function as a standalone App. The devloper' | ||
- | * Auria Pro - Music Production by WaveMachine Labs, Inc.[🏪](https:// | ||
- | * **Korg** | ||
- | * People want Korg and others to just slap an AU interface on their products and support the users satisfaction. Big companies usually won't take the risk of explaining that all AU's won't work all the time in all cases. It's not their fault. Supplying an AU must factor in the consequence of handing control to another App that's scheduling resources and keeping that output buffer full with wonderful planned sounds. | ||
- | |||
- | ### | ||
- | * We only have 10 fingers so 10 notes at a time should do it right? Wrong. Enter the missing " | ||
- | * So, great piano apps can offer over 100 notes played in a stereo image (bass on the left and treble notes to the right) for additional realism. Most top end Piano Apps have MIDI Players in the product so a piano can play along with another piano with another piano... to the max polyphony. Some of the entrants in the Piano Poll were just throwing away NOTE events due to limited CPU resources or a lack of polyphony in the MIDI file player. The MIDI Clock never rests for the App to catch up. It just tells the app to make a specific note the next note using time stamps on every note. Miss a note's time stamp and just drop the event. No crackles... just missing chord tones or worse the melody. Still not sure what changed some G#'s to G natural on Contestant #19 (BeatHawk[🏪](https:// | ||
- | * Colossus specs show 140 notes in stereo and 280 in mono. | ||
- | * To feel real to the pianist the application has to be responsive. Less than 10 millisecond to be undetectable I think. That means the DAW has to output sound within 1/100th of second. Making that a priority over processing FX or mixing in other sounds to the output buffers. | ||
- | * I keep sharing the Colossus specs because Crudebyte reports them. Ravenscroft 275 Piano by UVItouch[🏪](https:// | ||
- | * The Salamander sample set in Auria Pro is closer to the Crudebyte approach but the resource management is in the DAW's sampler. So, it sounds wonderful using great multi-GB wave files and has great tools in the DAW for EQ, Reverb, Compression and velocity mapping. | ||
- | * "Piano in 162" Library I thought it was a finalist has these specs: | ||
- | * 5GB Sample Library in SFZ standard format (It's also available in Kontakt and Korg Kronos formats) | ||
- | * It's a Steinway B and not a Yamaha C (Players will tend to prefer one or the other for personal use vs playing live in a combo). Similar to IOS uses in a solo context vs adding it to a complex mix. | ||
- | * all notes have been sampled, for full duration | ||
- | * NOTE: Salamander' | ||
- | * 2 stereo mic positions (Close and Ambient " | ||
- | * five dynamic levels (layers?) | ||
- | * two round robins: a simple way to let sample developers play back a different sampled version of the same sound each time you hit the same key, so that just like most acoustic instruments each note sounds slightly different for more realism | ||
- | * a separate pedal on and off samples for a true to life sound with realistic sympathetic resonance | ||
- | * Add in Auria doing Disk Streaming you've got a world class sounding piano. It's just not normalized in the SFZ format so you have to add a lot of compression to use it. The default Compressor in Auria Pro colors the sound too much so you need to upgrade the Compressor. I have my eye on the FabFilter Pro C 2 which just went "off sale". The AUv3 model will probably come out at the same $30 price. | ||
- | |||
- | </ | ||
- | |||
- | {{tag> piano sampler_instrument sample_library Auria Beathawk Ravenscroft Colossus SFZ round_robin disk_stream}} |