Menu
▾
▴
linuxsampler-devel
|
From: Mark K. <mar...@gm...> - 2004-12-31 22:07:28
|
What LS should I be using for release velocity testing? While dragging notes around in Pro Tools I made this happen in an older version of qsampler/LS: 14:04:19.646 ADD CHANNEL 14:04:19.651 SET CHANNEL AUDIO_OUTPUT_TYPE 0 JACK 14:04:19.656 SET CHANNEL MIDI_INPUT_TYPE 0 ALSA 14:04:19.657 SET CHANNEL MIDI_INPUT_PORT 0 0 14:04:19.663 SET CHANNEL MIDI_INPUT_CHANNEL 0 0 14:04:19.670 LOAD ENGINE GigEngine 0 Starting disk thread...OK 14:04:19.871 LOAD INSTRUMENT NON_MODAL '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial Grand Version 2.2.gig' 0 0 14:04:19.905 SET CHANNEL VOLUME 0 1 QFont::fromString: invalid description '(null)' 14:04:19.943 Open session: "/home/mark/Bardstown.lscp". Loading gig file '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial Grand Version 2.2.gig'...OK Loading gig instrument...OK Caching initial samples...OK 14:05:25.095 lscp_reset_channel: Timeout during receive operation (errno=-4) No unused stream found (OrderID:69) - report if this happens, this is a bug! No unused stream found (OrderID:70) - report if this happens, this is a bug! No unused stream found (OrderID:71) - report if this happens, this is a bug! No unused stream found (OrderID:72) - report if this happens, this is a bug! No unused stream found (OrderID:73) - report if this h0x4561e7c0Disk stream not available in time! No debugger found FATAL: exception not rethrown 14:05:26.747 Client disconnecting... 14:05:26.749 Client disconnected. 14:05:26.751 Server was stopped with exit status 0. |
|
From: Vladimir S. <ha...@gm...> - 2004-12-31 22:14:37
|
Mark, Happy new year!!!! Older versions have known bugs. Streaming bug that you've seen just now was one of the known bugs. Please try the latest LS. The latest LS has only one known bug (as far as i know): the release velocity bug. (i'm not completely sure it's really gone but no one has reported it yet with the latest LS). all other bugs are unknown at this point and i'd like to know about them! :) Regards, Vladimir. On Fri, 31 Dec 2004 14:07:21 -0800, Mark Knecht <mar...@gm...> wrote: > What LS should I be using for release velocity testing? > > While dragging notes around in Pro Tools I made this happen in an > older version of qsampler/LS: > > 14:04:19.646 ADD CHANNEL > 14:04:19.651 SET CHANNEL AUDIO_OUTPUT_TYPE 0 JACK > 14:04:19.656 SET CHANNEL MIDI_INPUT_TYPE 0 ALSA > 14:04:19.657 SET CHANNEL MIDI_INPUT_PORT 0 0 > 14:04:19.663 SET CHANNEL MIDI_INPUT_CHANNEL 0 0 > 14:04:19.670 LOAD ENGINE GigEngine 0 > Starting disk thread...OK > 14:04:19.871 LOAD INSTRUMENT NON_MODAL > '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial > Grand Version 2.2.gig' 0 0 > 14:04:19.905 SET CHANNEL VOLUME 0 1 > QFont::fromString: invalid description '(null)' > 14:04:19.943 Open session: "/home/mark/Bardstown.lscp". > Loading gig file '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The > Bosendorfer Imperial Grand Version 2.2.gig'...OK > Loading gig instrument...OK > Caching initial samples...OK > 14:05:25.095 lscp_reset_channel: Timeout during receive operation (errno=-4) > No unused stream found (OrderID:69) - report if this happens, this is a bug! > No unused stream found (OrderID:70) - report if this happens, this is a bug! > No unused stream found (OrderID:71) - report if this happens, this is a bug! > No unused stream found (OrderID:72) - report if this happens, this is a bug! > No unused stream found (OrderID:73) - report if this h0x4561e7c0Disk > stream not available in time! > No debugger found > FATAL: exception not rethrown > 14:05:26.747 Client disconnecting... > 14:05:26.749 Client disconnected. > 14:05:26.751 Server was stopped with exit status 0. > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > -- Regards, Vladimir |
|
From: Mark K. <mar...@gm...> - 2005-01-01 00:27:15
|
On Fri, 31 Dec 2004 17:14:24 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, > > Happy new year!!!! And to you and all the LS Developers and users also! > > Older versions have known bugs. Streaming bug that you've seen just > now was one of the known bugs. > Please try the latest LS. The latest LS has only one known bug (as far > as i know): the release velocity bug. (i'm not completely sure it's > really gone but no one has reported it yet with the latest LS). > all other bugs are unknown at this point and i'd like to know about them! :) > > Regards, > Vladimir. > OK, I'm building from CVS right now. Rui's page doesn't seem ot have been updated for a while so this seems best. When this finishes in a minute I would begin testing using the following set of tools: linuxsampler-cvs-20041231 libgig-1.0.0 liblscp-0.2.4 qsampler-0.0.4 Look good to you? Have a great SAFE evening! - Mark |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 00:43:38
|
Looks good! but . . . i haven't actually tested with the GUI for a little while, so i can only speak for LS itself. but since we didn't change anything in lscp area for a while it should work. if it doesn't, please let me know and i'll try to fix it asap. i still have a few vacation days :) > OK, I'm building from CVS right now. Rui's page doesn't seem ot have > been updated for a while so this seems best. When this finishes in a > minute I would begin testing using the following set of tools: > > linuxsampler-cvs-20041231 > libgig-1.0.0 > liblscp-0.2.4 > qsampler-0.0.4 > > Look good to you? |
|
From: Mark K. <mar...@gm...> - 2005-01-01 01:30:14
|
On Fri, 31 Dec 2004 19:43:27 -0500, Vladimir Senkov <ha...@gm...> wrote: > Looks good! > but . . . i haven't actually tested with the GUI for a little while, > so i can only speak for LS itself. but since we didn't change anything > in lscp area for a while it should work. > if it doesn't, please let me know and i'll try to fix it asap. i still > have a few vacation days :) > > > OK, I'm building from CVS right now. Rui's page doesn't seem ot have > > been updated for a while so this seems best. When this finishes in a > > minute I would begin testing using the following set of tools: > > > > linuxsampler-cvs-20041231 > > libgig-1.0.0 > > liblscp-0.2.4 > > qsampler-0.0.4 > > > > Look good to you? > OK, I've done some very preliminary, initial tests with the toolset show above in comparison with GSt Ver. 2.50.48 running under Win XP. I'm using the Bardstown Bosendorfer piano gig. I have a short MIDI file in Pro Tools (on a separate, 3rd PC) driving both samplers and I've recorded the audio from each into Ardour on separate passes. So far I cannot hear any differences at all, but I'm using headphones and have a bit of a headache. (geez...New Years Eve and I ALREADY have a headache!) ;-) My MIDI file is very simple. The first number is the note-on velocity and the second is the note-off velocity. 16 notes - 1/1, 9/9, 17/17, ...118/118, 127/127 16 notes - 96/1, 96/9, 96/17, ...96/127 16 notes - 1/50, 9/50, 17/50, ...127/50 16 notes - 1/96. 9/96, 17/96, ...127/96 Is thi ssort of MIDI file appropriate for findign the release sample problem if it exists? I suppose my only comments at this point are: 1) While the Bardstown Piano advertises release samples it's not 100% clear that they are being used in this voice. I'd like to know how to be sure of this using gigdump or some other tool if possible. 2) LS is producing about 2db higher output than GSt when GSt has all settings at max level. (I need to check my hardware setting in hdspmixer to ensure I'm not doing something silly with levels.) On a good note I tested LS hard for the streaming problem I saw earlier today and that seems to have completely gone away, at least for single note testing. I can drag the note around in Pro Tools causing lots of real time events. All notes seem to be played and there were no lockups. I did notice some sonic problems with a few notes in the Bardstown piano that I have not heard before. I need to check and see if those are in the gig file itself and also present on the GSt side. Also, the Scarbee J-Fingered Bass gig still does not work correctly. All in all, very positive results! Congrats to the developers. I need to do some testing with more complicated MIDI files and multiple gig files loaded at the same time. I am a bit concerned about memory usage as reported by top while LS is running, ut possibly it's not really a problem. top is often confused about such things. Is there a way I can see the amount of memory LS is allocating to each gig file? It would be good to know this sort of thing I think. With best regards, Mark |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 01:55:10
|
Mark, This is great news! I'm almost ready to start celebrating :))) Memory stats could be looked at by tools like "top" but there is nothing currently in LS itself (as far as i know) that could output memory usage stats. I think it is a good idea and we should add a feature that would allow this. I'm not sure how it should look like exactly but i'll think about it. Can you do a "gigdump" on Scarbee J-Fingered Bass gig so we could have a bit more info to try to figure out why it doesn't work. Also, if you hear something strange that you haven't heard before and if GS doesn't sound the same, could you try against previous verion of LS (the one before optimization, the one from Rui's site should do). Another thing to try is to use the -no-tune flag to disable SSEMMX optimizations on the latest LS. HAPPY NEW YEAR!!! you have 6 minutes to go there on the west coast :) Regards, Vladimir. |
|
From: Mark K. <mar...@gm...> - 2005-01-01 02:12:26
|
On Fri, 31 Dec 2004 20:54:54 -0500, Vladimir Senkov <ha...@gm...> wrote:
> Mark,
>
> This is great news!
> I'm almost ready to start celebrating :)))
>
> Memory stats could be looked at by tools like "top"
Yes, but that doesn't show what each gig file or each sample, etc., is
using. I'm thinking that it's not a fair comparison if LS takes 600MB
to do a piano and GSt does it in 50MB. (Numbers just made up to make a
point.) I don't really know how to get the numbers for GSt either.
> but there is
> nothing currently in LS itself (as far as i know) that could output
> memory usage stats. I think it is a good idea and we should add a
> feature that would allow this. I'm not sure how it should look like
> exactly but i'll think about it.
> Can you do a "gigdump" on Scarbee J-Fingered Bass gig so we could have
> a bit more info to try to figure out why it doesn't work.
Did it. The file is 105K lines long and about 10MB of data. gig files
are large. Here's a taste of what I see:
ALL Available Samples (as there might be more than referenced by Instruments):
Sample 1) "CJ1F sus-soft-index A2", 44100Hz, 1 Channels, 0 Loops,
Length=114688 Compressed=true
Sample 2) "CJ1F sus-medium2-index A2", 44100Hz, 1 Channels, 0
Loops, Length=233472 Compressed=true
Sample 3) "CJ1F sus-hard-index A2", 44100Hz, 1 Channels, 0 Loops,
Length=112640 Compressed=true
Sample 4) "CJ1F sus-soft-index D3", 44100Hz, 1 Channels, 0 Loops,
Length=112640 Compressed=true
<BIG SNIP>
Sample 1069) "CJ1F Slide-down-slow-tail G3", 44100Hz, 1 Channels,
0 Loops, Length=28303 Compressed=false
Sample 1070) "CJ1F Slide-down-fast-tail G3", 44100Hz, 1 Channels,
0 Loops, Length=13147 Compressed=false
Sample 1071) "CJ1F Gra-n-wh-slow-dw-tail A4 x", 44100Hz, 1
Channels, 0 Loops, Length=55296 Compressed=true
Available Instruments:
Instrument 1) "J-Fingered 1 - Jam Bass", MIDIBank=0, MIDIProgram=1
Region 1) Sample: "No sound", 44100Hz,
KeyRange=21-21, VelocityRange=0-127, Layers=1
Loops=0
Dimensions=3
Dimension[0]: Type=MODWHEEL, Bits=2, Zones=4, SplitType=NORMAL
Dimension[1]: Type=RELEASETRIGGER, Bits=1, Zones=2, SplitType=BIT
Dimension[2]: Type=VELOCITY, Bits=2, Zones=4,
SplitType=CUSTOMVELOCITY
Dimension Region 1)
Sample: "CJ1F sus-soft-index A#2", 44100Hz,
LFO1Frequency=3Hz, LFO1InternalDepth=0,
LFO1ControlDepth=0 LFO1Controller=0
LFO2Frequency=3Hz, LFO2InternalDepth=0,
LFO2ControlDepth=0 LFO2Controller=0
LFO3Frequency=4Hz, LFO3InternalDepth=15,
LFO3ControlDepth=18 LFO3Controller=2
EG1PreAttack=0permille, EG1Attack=6.02386e-09s,
EG1Decay1=0.005s, EG1Sustain=1000permille, EG1Release=0.02s,
EG1Decay2=1.66007e+08s, EG1Hold=0
EG2PreAttack=0permille, EG2Attack=6.02386e-09s, EG2Decay1=0.005s,
EG2Sustain=1000permille, EG2Release=2s, EG2Decay2=1.66007e+08s
VCFEnabled=0, VCFType=0, VCFCutoff=127,
VCFResonance=0, VCFCutoffController=1
VelocityResponseCurve=NONLINEAR,
VelocityResponseDepth=3, VelocityResponseCurveScaling=0
Pan=0
Dimension Region 2)
Sample: "CJ1F mute2 D3", 44100Hz,
LFO1Frequency=3Hz, LFO1InternalDepth=0,
LFO1ControlDepth=0 LFO1Controller=0
LFO2Frequency=3Hz, LFO2InternalDepth=0,
LFO2ControlDepth=0 LFO2Controller=0
LFO3Frequency=5Hz, LFO3InternalDepth=0,
LFO3ControlDepth=0 LFO3Controller=0
EG1PreAttack=0permille, EG1Attack=6.02386e-09s,
EG1Decay1=0.005s, EG1Sustain=1000permille, EG1Release=0.02s,
EG1Decay2=1.66007e+08s, EG1Hold=0
EG2PreAttack=0permille, EG2Attack=6.02386e-09s,
EG2Decay1=0.005s, EG2Sustain=1000permille, EG2Release=2s,
EG2Decay2=1.66007e+08s
VCFEnabled=0, VCFType=0, VCFCutoff=127,
VCFResonance=0, VCFCutoffController=1
VelocityResponseCurve=NONLINEAR,
VelocityResponseDepth=3, VelocityResponseCurveScaling=0
Pan=0
Dimension Region 3)
Sample: "CJ1F sus-soft-index A#2", 44100Hz,
LFO1Frequency=3Hz, LFO1InternalDepth=0,
LFO1ControlDepth=0 LFO1Controller=0
LFO2Frequency=3Hz, LFO2InternalDepth=0,
LFO2ControlDepth=0 LFO2Controller=0
LFO3Frequency=4Hz, LFO3InternalDepth=15,
LFO3ControlDepth=18 LFO3Controller=2
EG1PreAttack=0permille, EG1Attack=6.02386e-09s,
EG1Decay1=0.005s, EG1Sustain=1000permille, EG1Release=0.02s,
EG1Decay2=1.66007e+08s, EG1Hold=0
EG2PreAttack=0permille, EG2Attack=6.02386e-09s,
EG2Decay1=0.005s, EG2Sustain=1000permille, EG2Release=2s,
EG2Decay2=1.66007e+08s
VCFEnabled=0, VCFType=0, VCFCutoff=127,
VCFResonance=0, VCFCutoffController=1
VelocityResponseCurve=NONLINEAR,
VelocityResponseDepth=3, VelocityResponseCurveScaling=0
Pan=0
etc.........
The file ends a bit abruptly, but possibly it's fine.
When Christian and I discussed this problem, probably about a year
ago, it was my understanding he thought that the compression
algorythmn might be different than other files and hence this causes
the problem. I don['t think we ever tested that idea fully.
>
> Also, if you hear something strange that you haven't heard before and
> if GS doesn't sound the same, could you try against previous verion of
> LS (the one before optimization, the one from Rui's site should do).
> Another thing to try is to use the -no-tune flag to disable SSEMMX
> optimizations on the latest LS.
I will certainly let you know if I hear problems. My big issue right
now is getting LS to handle maybe 3 gig files at the same time so I
can push it a little harder. (The other email I just sent...)
>
> HAPPY NEW YEAR!!! you have 6 minutes to go there on the west coast :)
Nahh...I'm 6 hours away...
|
|
From: Christian S. <sch...@so...> - 2005-01-01 16:27:39
|
Happy new year everybody! :) Wow, Vladimir was really assiduous and that even on new years eve! Es geschah am Samstag 01 Januar 2005 03:12 als Mark Knecht schrieb: > > Memory stats could be looked at by tools like "top" > > Yes, but that doesn't show what each gig file or each sample, etc., is We could easily collect the amount of cached sample data in the InstrumentResourceManager. But I think we'll better postpone that for the time after the first release. > When Christian and I discussed this problem, probably about a year > ago, it was my understanding he thought that the compression > algorythmn might be different than other files and hence this causes > the problem. I don['t think we ever tested that idea fully. I thought you only had problems with LS's interpretation of articulation informations. If there's a problem wirh the decompression algorithm you would hear noise or something. Or did I get you wrong? Mark, you mentioned there was still a problem with your Scarbee J-Fingered Bass gig. What exactly was the problem? Vladimir, you are right regarding the disk thread. Of course it makes sense to share one single disk thread between all instances of the same sampler engine type. I also planned to change that long ago, but did not do it yet due to priorities. The engine concept should also be changed a bit, but I propose to do these things after the upcoming release. CU Christian |
|
From: Mark K. <mar...@gm...> - 2005-01-01 18:14:53
|
On Sat, 1 Jan 2005 17:15:52 +0100, Christian Schoenebeck <sch...@so...> wrote: > Happy new year everybody! :) And to you! > > Wow, Vladimir was really assiduous and that even on new years eve! > > Es geschah am Samstag 01 Januar 2005 03:12 als Mark Knecht schrieb: > > > Memory stats could be looked at by tools like "top" > > > > Yes, but that doesn't show what each gig file or each sample, etc., is > > We could easily collect the amount of cached sample data in the > InstrumentResourceManager. But I think we'll better postpone that for the > time after the first release. If the info was going to be part of the app then I agree. I'm wondering if it is possible to write some small support app, just console based, that could query LS (or Linux itself) for LS memory usage? > > > When Christian and I discussed this problem, probably about a year > > ago, it was my understanding he thought that the compression > > algorythmn might be different than other files and hence this causes > > the problem. I don['t think we ever tested that idea fully. > > I thought you only had problems with LS's interpretation of articulation > informations. If there's a problem wirh the decompression algorithm you would > hear noise or something. Or did I get you wrong? Sorry. I do hear noise with these gig files. Underneath the noise I can hear the note, but badly distorted. It's a bass guitar, but I hear mostly high frequencies only and covered up with noise. > > Mark, you mentioned there was still a problem with your Scarbee J-Fingered > Bass gig. What exactly was the problem? As stated above. I can record the gig from both apps and send you mp3's if it will help. Can gigdump extract certain samples from the gig file? Maybe I could send a single sample and you could figure it out from there. Or tell me how I might investigate this more here and I'll give it a try. > > Vladimir, you are right regarding the disk thread. Of course it makes sense to > share one single disk thread between all instances of the same sampler engine > type. I also planned to change that long ago, but did not do it yet due to > priorities. The engine concept should also be changed a bit, but I propose to > do these things after the upcoming release. > WRT to the upcoming release I think you guys are really very close. In my mind there are just a couple of things that must happen either before or soon after release: 1) More a qsampler issue possibly but based on yesterday's work I'm having lots of problems saving and restoring setups. I store *.lscp file and then it won't restore. LS reports that it cannot set up channels or parameters. I would encourage the group to take a close look at this and make sure it won't look flaky to new users. (I expect almost all users to end up using qsampler.) 2) The Scarbee issue as above. It's a pretty popular set of libraries used by a lot of folks. If you do release without it fixed then we need to state it doesn't work up front and say when we'll fix it. (Basic errata issue) 3) More structural, but LS needs to support more than a stereo output. I record LS output into Ardour or Pro Tools and I need piano, drums, bass, all on separate stereo channels. Folks doing orchestral are used to recording maybe 8-10 separate groups of sounds for mixing later. LS doesn't seem to support anything like this today. We need some of the features in the DSP station portion of GSt, where we route LS channels to certain mixer elements and then attach certain mixer elements to certain hardware outputs. (Or alsa_pcm channels.) Those are my thoughts for now. I've just finished build Vladimir's latest updates so I'll do some more testing today and see how it goes. My main goal right now is to do some 30-100 voice recordings using Pro Tools and LS only to see how well it holds up. It broke yesterday so I hope Vladimir's work helps. Cheers, Mark |
|
From: Christian S. <sch...@so...> - 2005-01-01 20:15:16
|
Es geschah am Samstag 01 Januar 2005 19:14 als Mark Knecht schrieb: > If the info was going to be part of the app then I agree. I'm > wondering if it is possible to write some small support app, just > console based, that could query LS (or Linux itself) for LS memory > usage? Sure > Sorry. I do hear noise with these gig files. Underneath the noise I > can hear the note, but badly distorted. It's a bass guitar, but I hear > mostly high frequencies only and covered up with noise. > > > Mark, you mentioned there was still a problem with your Scarbee > > J-Fingered Bass gig. What exactly was the problem? > > As stated above. I can record the gig from both apps and send you > mp3's if it will help. That would be fine. > Can gigdump extract certain samples from the gig file? Maybe I could > send a single sample and you could figure it out from there. Or tell > me how I might investigate this more here and I'll give it a try. Not with gigdump, but with gigextract you can extract samples as .wav files (man gigextract). If you just want to extract certain sample(s), then look at the output of gigdump, and use the repective sample number(s) as shown there. > 3) More structural, but LS needs to support more than a stereo output. > I record LS output into Ardour or Pro Tools and I need piano, drums, > bass, all on separate stereo channels. Folks doing orchestral are used > to recording maybe 8-10 separate groups of sounds for mixing later. LS > doesn't seem to support anything like this today. We need some of the > features in the DSP station portion of GSt, where we route LS channels > to certain mixer elements and then attach certain mixer elements to > certain hardware outputs. (Or alsa_pcm channels.) LS aready has that. But audio and MIDI device management (including routing) is not yet completely implemented in qsampler. But something like the following LSCP script would do it: # load audio and MIDI driver CREATE AUDIO_OUTPUT_DEVICE JACK CREATE MIDI_INPUT_DEVICE ALSA # increase the amount of output channels of the LS's Jack client e.g. to 4 SET AUDIO_OUTPUT_DEVICE_PARAMETER 0 CHANNELS=4 # connect to MIDI keyboard SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='72:0' # set up 1st sampler channel (using default output channels, that is 0 and 1) ADD CHANNEL LOAD ENGINE gig 0 SET CHANNEL AUDIO_OUTPUT_DEVICE 0 0 SET CHANNEL MIDI_INPUT_DEVICE 0 0 LOAD INSTRUMENT '/home/me/ns_kit7free.gig' 0 0 # set up 2nd sampler channel (using output channels 2 and 3) ADD CHANNEL LOAD ENGINE gig 1 SET CHANNEL AUDIO_OUTPUT_DEVICE 1 0 SET CHANNEL MIDI_INPUT_DEVICE 1 0 LOAD INSTRUMENT '/home/me/freepiano.gig' 0 1 # this will alter the audio channel routing # connect the engines output channel 0 to JACK clients output 2 SET CHANNEL AUDIO_OUTPUT_CHANNEL 1 0 2 # connect the engines output channel 1 to JACK clients output 3 SET CHANNEL AUDIO_OUTPUT_CHANNEL 1 1 3 # not necessary, just to see our setup GET CHANNEL INFO 0 GET CHANNEL INFO 1 Sorry for the inconvenience. Once the release of LS is out, I will work on qsampler, so it covers all the possibilites given by the current version of LSCP. CU Christian |
|
From: Mark K. <mar...@gm...> - 2005-01-01 20:47:20
|
On Sat, 1 Jan 2005 21:03:04 +0100, Christian Schoenebeck <sch...@so...> wrote: > Es geschah am Samstag 01 Januar 2005 19:14 als Mark Knecht schrieb: > > > Can gigdump extract certain samples from the gig file? Maybe I could > > send a single sample and you could figure it out from there. Or tell > > me how I might investigate this more here and I'll give it a try. > > Not with gigdump, but with gigextract you can extract samples as .wav files > (man gigextract). If you just want to extract certain sample(s), then look at > the output of gigdump, and use the repective sample number(s) as shown there. I have extracted one of the samples. It playing incorrectly in alsaplayer and sounds jsut like it does in LS so this should tell you what I'm hearing. I'm sending you the zipped sample off list. It's about 200K bytes. Can gigextract extract the sample without uncompressing it? If so I can send you the actual sample and you can attempt to find the problem. gigextract is very cool. Good work! - Mark |
|
From: Mark K. <mar...@gm...> - 2005-01-01 21:32:55
|
On Sat, 1 Jan 2005 12:47:13 -0800, Mark Knecht <mar...@gm...> wrote: > On Sat, 1 Jan 2005 21:03:04 +0100, Christian Schoenebeck > <sch...@so...> wrote: > > Es geschah am Samstag 01 Januar 2005 19:14 als Mark Knecht schrieb: > > > > > > Can gigdump extract certain samples from the gig file? Maybe I could > > > send a single sample and you could figure it out from there. Or tell > > > me how I might investigate this more here and I'll give it a try. > > > > Not with gigdump, but with gigextract you can extract samples as .wav files > > (man gigextract). If you just want to extract certain sample(s), then look at > > the output of gigdump, and use the repective sample number(s) as shown there. > > I have extracted one of the samples. It playing incorrectly in > alsaplayer and sounds jsut like it does in LS so this should tell you > what I'm hearing. I'm sending you the zipped sample off list. It's > about 200K bytes. > > Can gigextract extract the sample without uncompressing it? If so I > can send you the actual sample and you can attempt to find the > problem. > > gigextract is very cool. Good work! > > - Mark > Hi, I just noticed this message in the qsampler message window: Engine error: Failed to load instrument, cause: Mono compressed samples not yet supported If that's the case (not sure if this bass library is mono or stereo) Then it would seem this is the cause. Can it be supported? GSt treats it like it's stereo AFAICT. Thanks, Mark |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 21:27:46
|
Christian, > Vladimir, you are right regarding the disk thread. Of course it makes sense to > share one single disk thread between all instances of the same sampler engine > type. I also planned to change that long ago, but did not do it yet due to > priorities. The engine concept should also be changed a bit, but I propose to > do these things after the upcoming release. For most configurations it is better to have a single disk thread, but in some configurations it might not be as good. Remember in the early days we had those ideas about the client/gui machine connecting to a dedicated rack mounted LS and some samples could possibly be located on the client machine and shared over the network. In these scenarios disk IO will suffer from network being slow or the other way around. Anothe example is just having two or more HDDs and gigs stored on different ones. Then if we have a single thread it means we'll not be 100% efficient. So i don't really know what is the right thing to do here. I need to think it over. Regards, Vladimir. |
|
From: Mark K. <mar...@gm...> - 2005-01-01 21:34:53
|
On Sat, 1 Jan 2005 16:27:30 -0500, Vladimir Senkov <ha...@gm...> wrote: > Anothe example is just having two or more HDDs and gigs stored on > different ones. Then if we have a single thread it means we'll not be > 100% efficient. > > So i don't really know what is the right thing to do here. I need to > think it over. > > Regards, > Vladimir. > This is the way I'm running. I have gigs on multiple drives. Most folks with really large libraries have to do this. It's easy to end up with 100's of Gigbytes of gig files.... (Expensive, but easy!) ;-) - Mark |
|
From: rensinghoff <lui...@fr...> - 2005-01-02 10:05:38
|
Good Morning List ! Ok this is a script to use multiple channels in linuxsampler, i just dont understand where and how to run it, or if i have to put in in some resource file ? Its a shame there is not a little documentation, but i know your guys are so involved in hacking i guess.... So what happens id i run this script and open qsampler later on ? Does qsampler show or report the newly defined outputs ??? some more questions: 1) You mentioned gigdump and gigextract, i guess these are programms to extract and build gig-files, right ? So i can create my own gig-files from any collection of wav-files ? That would be great..probably a bit complicated, because of the velocity-mapping and so on, or ist it manageable ? 2)You mentioned Worra's place for gig-samples, but yesterday the server was down...how about exchanging some gig files (i know i am becoming illegal ;-)) but i think i will have the "good" ones in a couple of days, when i start working again and meet my criminal colleagues ;-) You know its just for research ;-) > # load audio and MIDI driver > CREATE AUDIO_OUTPUT_DEVICE JACK > CREATE MIDI_INPUT_DEVICE ALSA > > # increase the amount of output channels of the LS's Jack client e.g. to 4 > SET AUDIO_OUTPUT_DEVICE_PARAMETER 0 CHANNELS=4 > > # connect to MIDI keyboard > SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='72:0' > > # set up 1st sampler channel (using default output channels, that is 0 and 1) > ADD CHANNEL > LOAD ENGINE gig 0 > SET CHANNEL AUDIO_OUTPUT_DEVICE 0 0 > SET CHANNEL MIDI_INPUT_DEVICE 0 0 > LOAD INSTRUMENT '/home/me/ns_kit7free.gig' 0 0 > > # set up 2nd sampler channel (using output channels 2 and 3) > ADD CHANNEL > LOAD ENGINE gig 1 > SET CHANNEL AUDIO_OUTPUT_DEVICE 1 0 > SET CHANNEL MIDI_INPUT_DEVICE 1 0 > LOAD INSTRUMENT '/home/me/freepiano.gig' 0 1 > # this will alter the audio channel routing > # connect the engines output channel 0 to JACK clients output 2 > SET CHANNEL AUDIO_OUTPUT_CHANNEL 1 0 2 > # connect the engines output channel 1 to JACK clients output 3 > SET CHANNEL AUDIO_OUTPUT_CHANNEL 1 1 3 > > # not necessary, just to see our setup > GET CHANNEL INFO 0 > GET CHANNEL INFO 1 > A Big hug to all the linux-hackers Ok: i sacrificed a whole night, but and the end of the day, i will have a free-surround-steinway and hopefully a string orchestra, and thats great, thanks to your effort Regards Luigi > |
|
From: Mark K. <mar...@gm...> - 2005-01-02 19:49:35
|
On Mon, 28 Feb 2005 11:08:26 +0100, rensinghoff <lui...@fr...> wrote: > Good Morning List ! > > Ok this is a script to use multiple channels in linuxsampler, i just > dont understand where and how to run it, or if i have to put in in some > resource file ? > > Its a shame there is not a little documentation, but i know your guys > are so involved in hacking i guess.... A basic Linux problem I think. Developers are authors of code, not books... ;-) > > So what happens id i run this script and open qsampler later on ? Does > qsampler show or report the newly defined outputs ??? > > some more questions: > > 1) You mentioned gigdump and gigextract, i guess these are programms to > extract and build gig-files, right ? So i can create my own gig-files > from any collection of wav-files ? That would be great..probably a bit > complicated, because of the velocity-mapping and so on, or ist it > manageable ? These are tools for looking at existing gig files. To build gig files we would need other tools. I do it using GEdit which comes with GigaStudio. (GSt) > > 2)You mentioned Worra's place for gig-samples, but yesterday the server > was down...how about exchanging some gig files (i know i am becoming > illegal ;-)) but i think i will have the "good" ones in a couple of > days, when i start working again and meet my criminal colleagues ;-) You > know its just for research ;-) It's up this morning. It's a bit slow. http://www.worrasplace.com/ I have no good way to share free gig files as I do not run a server. Sorry. > > Ok: i sacrificed a whole night, but and the end of the day, i will have > a free-surround-steinway and hopefully a string orchestra, and thats > great, thanks to your effort > Sounds great. We look forward to try out new stuff. - Mark |
|
From: rensinghoff <lui...@fr...> - 2005-01-02 10:07:44
|
By the way, just a questions..are you in touch with Fernando from Planet CCRMA and the Agnula-people ?? I think linuxsampler should definetly be part of these distros !! |
|
From: Mark K. <mar...@gm...> - 2005-01-02 16:06:14
|
On Mon, 28 Feb 2005 11:10:12 +0100, rensinghoff <lui...@fr...> wrote: > By the way, just a questions..are you in touch with Fernando from Planet > CCRMA and the Agnula-people ?? > > I think linuxsampler should definetly be part of these distros !! > Hi, I am certainly in touch with Fernando, although I am not a developer but more like a very dedicated tester. I am sure that Fernando will support LS and qsampler when we can show it's ready. I would imagine that this would be in the next few months. In the meantime I find this toolset to be one of the easiest to build, and I'm running it on an FC2 PlanetCCRMA machine so I expect it will be easy for Planet users to build until the time we get it into his flow. Stick with us. You're getting here at a fun time! - Mark |
Thanks for helping keep SourceForge clean.
X