1 Apr
2010
1 Apr
'10
6:28 a.m.
Excerpts from alexander's message of 2010-04-01 00:43:20 +0200:
On 04/01/2010 12:50 AM, Arnold Krille wrote:
Did you have contact with the gigedit authors? Maybe the fix is minor.
It would be a pity if the quality would suffer from something that could
be fixed easily.
Hi,
On Wednesday 31 March 2010 12:42:58 alexander wrote:
Hmm, how's that for a version 2.0? :) I haven't noticed any
up-sampling
problems yet. But I do agree, 24bit48khz would be much more fun. I would
have to cut 3 layers at least, we're talking about shaving 0.6gb's here :)
I think I'll just shove it down a bz2 archive.. I'm currently making a rather big grand piano
sample library. It is a
Yamaha C5 recorded with 2 AKG C414 in an AB position about 10cm above
the strings at 24bit48khz. It is downsampled to 16bit44.1khz because
gigedit couldn't save files larger than 2gb. It's sampled in minor
thirds with 17 velocity layers (some only 16 due to a nasty head ache
when I recorded)
I haven't actually listened to the demo yet, but:
- Can we convince you of going 48kHz/24bits? That is far more common in audio
production. Using 44.1kHz in a setup running at 48kHz includes possibly nasty
artefacts from up-sampling and a loss of precision and frequencies. Down-
sampling is far easier on the quality...
Maybe its better to make do with one or two layers less. And maybe help to
fix gigedit. linuxsampler is said to be able to do more then 2GB files.
- When looking for compression for easier distribution: What about
distributing a "source" archive that contains the wavpack/flac compressed raw
samples, the gigedit file and a makefile for creation of the .gig-file?
Have fun,
Arnold