7 Jan
2010
7 Jan
'10
12:41 p.m.
Hi!
I'm just waring with a gs3 setup. I got samples and .gig files seperately,
now I'm supposed to import them. Here's the relevant excerpt from the guide:
Right-click in the sample window and choose "Replace all samples in all
folders".
In the "Replace all samples" window, set the Root Directory to the folder
containing the .wav-samples.
Check the "Match samples by name to .wav/.dlx files anywhere under the root
directory
Click on the "Replace" button.
After all samples are replaced, choose "Save" under the "File" menu.
If GigEdit can do this, there's another question: Can I start a LinuxSampler
engine on my system and allow someone to use it from the outside? IOr do I
better compile/install everything necessary here and grant ssh access?
Thanks and kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
7 Jan
7 Jan
3:38 p.m.
On Thu, Jan 7, 2010 at 8:40 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Hi!
I'm just waring with a gs3 setup. I got samples and .gig files seperately,
now I'm supposed to import them. Here's the relevant excerpt from the guide:
Right-click in the sample window and choose "Replace all samples in all
folders".
In the "Replace all samples" window, set the Root Directory to the folder
containing the .wav-samples.
Check the "Match samples by name to .wav/.dlx files anywhere under the root
directory
Click on the "Replace" button.
After all samples are replaced, choose "Save" under the "File" menu.
It works, at least in my experience, but it's never been an easy
process so I've only tried it once or twice and that was a LONG time
ago... IIRC there are also a LOT of extra steps you'll have to go
through if you want to map multiple samples to the same key vs
velocity or anything complicated like that. For instance, even a
simple setup where you just have a wave file because you take you gig
file and extracted certain samples, or just have samples you want to
use, and then want to map that wave into a gig at specific keys, etc.,
then it gets very work flow oriented, but it's only mildly
complicated.
If GigEdit can do this, there's another question: Can I start a LinuxSampler
engine on my system and allow someone to use it from the outside? IOr do I
better compile/install everything necessary here and grant ssh access?
Don't know as I no longer use LS.
Good luck,
Mark
3:43 p.m.
Hello Mark!
Well this .gig-file was already prepared to take on the sample set, that's
coming in. It was just constructed thusly:
Get the complete folder of samples (.wav) and include files for other
samplers, which do it directly.
Offer another package with a mini .gig-file, with placeholder samples, as
far as I could make out and tell the user to build in the real samples, which
are organised and named as they are in the .gig-file.
But it's good to know, that it should work. I'm just setting up everything
for ssh-ing and GUI-ing in. :-)
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
3:51 p.m.
On Thu, Jan 7, 2010 at 11:43 AM, Julien Claassen <julien(a)c-lab.de> wrote:
Hello Mark!
Well this .gig-file was already prepared to take on the sample set, that's
coming in. It was just constructed thusly:
Get the complete folder of samples (.wav) and include files for other
samplers, which do it directly.
Offer another package with a mini .gig-file, with placeholder samples, as
far as I could make out and tell the user to build in the real samples,
which are organised and named as they are in the .gig-file.
But it's good to know, that it should work. I'm just setting up everything
for ssh-ing and GUI-ing in. :-)
Kindest regards
Julien
It sounds like you should be in pretty good shape.
On the other hand if you run into any problems you are going to
understand very quickly why you'd rather buy gig files than build them
yourself... ;-) (i.e. - dealing with problems in these files isn't
fun.)
Don't forget to do serious testing once you put it all together, most
especially testing against velocity if you're doing that. When I did
this I set up predefined MIDI files I was playing in Rosegarden to
check that each and every note sounded good. If you use any form of
mixing between samples - where two samples get played and relatively
mixed based on how much they are supposed to contribute to the final
sound - then get ready for serious time sink...
If your task is simple then I expect that you'll be OK. You're a smart
guy with a lot of these tools. It's just that dealing with 1000 wave
files in a single gig file can get very tedious.
Cheers,
Mark
4:19 p.m.
Hi Julien,
On Thursday 07 of January 2010 17:40:59 Julien Claassen wrote:
I'm just waring with a gs3 setup. I got samples
and .gig files
seperately, now I'm supposed to import them. Here's the relevant
excerpt from the guide: Right-click in the sample window and choose
"Replace all samples in all folders".
In the "Replace all samples" window, set the Root Directory to the
folder containing the .wav-samples.
Check the "Match samples by name to .wav/.dlx files anywhere under
the root directory
Click on the "Replace" button.
After all samples are replaced, choose "Save" under the "File" menu.
Gigedit has a "replace all samples" function that works ok. There is one
issue though: Giga samples which are larger than 2 GB need to be split
into multiple files (.gig, .gx01, etc.). LinuxSampler can read those,
but Gigedit can't save them. So, if your samples happen to be larger
than 2 GB, you're out of luck.
I had this problem with the Sampletekk pianos I bought last month (White
Grand and Black Grand), and the only solution I could find was to get
hold of a copy of GigaStudio and run it on Windows :(
On the LinuxSampler forum I found a small program called updatebg5
that's supposed to work at least for the Black Grand, but for me it
crashed after processing the first 2 GB file...
Dominic
5463
days inactive
5463
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Dominic Sacré -
Julien Claassen -
Mark Knecht