The title says it all.
Still a work in progress.
http://www.irishacts.com/lionstracs/lapcgen.htm

Regards
James

amazing!!!!!!!!!!!!!!!!!!!!!

good to see how easy it works.

can you maybe create a software or include with this something to edit gmgigabank_Lionstracs file to?



[This message has been edited by AFG Music (edited 04-27-2010).]

Yes... will do.
In time it will evolve into a full editor and librarian too.

Regards
James

Excellent James...As always if you need some beta testing done. I am happy to help

Dennis

\thanks

Lovely project James....

Welcome to the open source fammily

some update..
just commited a new version of the sampler..
now we read direct the all sounds mapped from the LSCP file and displayed on the Giga GM/GS gui, without read the txt file on presets:
rev1924: * Groove GUI:
- get patch list for Giga GM via LSCP from LinuxSampler directly instead of reading a separate definition file.

In this way you can develope how many new soundbank under your tools and we read it automatically, without any external txt files to edit and asap testing under our interface.
( gmgigabank_lionstracs.txt located on Preset folder)

Great news,

you made it easier, especially for people who do not know how it works

Hi Domenico.
I just sent you that file for mapping 16 GM Categories down to 10. Hope it's what your looking for. If so, I will rewrite my own program so the sounds are displayed internally the same way. Right now it just displays program change numbers which is not exactly helpful to the end user without a GM table to work off of, so that's something I'll correct.

So are we saying that going forward that your system only needs the LSPC file and from the program change number in the file and the 10 Bank table I sent you, the system will know what category to assign each sound to?

Also what are you picking up the Patch Names off of? The file name, or are you changing how the LSPC file is structured to allow for a freely definable text name.

Regards
James

[This message has been edited by Irishacts (edited 05-03-2010).]

Ciao james
yes, I get your email, but was to late.. Feature already made, SVN rev 1924:


Here the example c++ code that we wrote how to display the all GM and GS sounds on the 10 Groove/MS family patch sounds:
Patch_Source_GMGIGA::~Patch_Source_GMGIGA() {
}

static QString _getFamilyName(int iProgram) {
if (iProgram < 0)
return "Invalid";
if (iProgram < 4)
return "Piano GIGA";
if (iProgram < 16)
return "Electric Piano GIGA";
if (iProgram < 24)
return "Organ GIGA";
if (iProgram < 32)
return "Guitar GIGA";
if (iProgram < 48)
return "Strings GIGA";
if (iProgram < 64)
return "Brass GIGA";
if (iProgram < 72)
return "Reed GIGA";
if (iProgram < 80)
return "Flute GIGA";
if (iProgram < 96)
return "Synth GIGA";
return "FX & ORIENTAL SOUNDS";
}

#define LINUXSAMPLER_HOST "localhost"
#define LINUXSAMPLER_PORT 8888

void Patch_Source_GMGIGA::reloadPatchListByLscp() {
category_array.clear(); // clean old data (if any)

// we add the categories first here, so they are in the order we need,
// because the order is linked to the sequence of category buttons on
// the Groove keyboard panel
add_category_internal("Piano GIGA");
add_category_internal("Electric Piano GIGA");
add_category_internal("Guitar GIGA");
add_category_internal("Strings GIGA");
add_category_internal("Brass GIGA");
add_category_internal("Flute GIGA");
add_category_internal("Organ GIGA");
add_category_internal("Reed GIGA");
add_category_internal("Synth GIGA");
add_category_internal("FX & ORIENTAL SOUNDS");
add_category_internal("Drum Sets GIGA");

So, you can use for your tool too.
Another new...now on LSCP file we can also include the all variation ( programs) sounds inside the .gig file and the MS display under GIGA GM/GS will display too.
here the new shot:

Where:
073 Piccolo Std = original name of the .gig file, if you edit the name of the original file, will display there.
[0] = sound program inside the .gig file ( all my ,gig sounds have only one sound inside, it mean Prg 0

PRG= program change number
VAR = GS Variation
TYPE = GM/GIG .gig format.

MAYBE tomorrow we include another NICE Info feature:

This you have when you select the GIGA solo and then EDIT mode.
Will include the GIG sound info when you select it, with:
Giga File Size: Mb/Gb
Active Voice: Voice that are current in use xxx
Active Disk Stream: HD voice in use xxxx
Memory RAM available: 61Mb ...
Memory RAM Used: 59Mb ....

How I told, NOT sure that tomorrow is included, first we ahve to fix some other bug/feature on list...BUT if we include, now is more interesting.

Good work Dom,

Is that to be in OS 4.2? Or as an incremental RAR upgrade?

Not being a programmer I am looking forward to James' new software librarian/editor. Your work in this is making huge moves towards making the MS/Groove so easy to use and operate.

Good Stuff!!

Dennis

Before 64studio will burn the new ISO 4.2, I continue make OS upgrade..or prefer that i make some pause and wait?
tomorrow I release again one current binary folder that you there can test and enjoy too.

Terrific Thats great news again Dom...

Thanks.

By the way, the new OS from 4 up is beautiful!!

Way better imagery, speed and ease of operation. As you know my last OS was 3.1. OS 4 is a HUGE development, even Diki could figure it out

Dennis

when we have this update: http://www.nvnews.net/vbulletin/showthread.php?t=150574
and this OS: http://www.kubuntu.org/
then we are all happy.
xorg 1.8 is for the multiple display outs!

Wow! so its in testing now!! Cool won't be long

Also looking at the 10.4 almost makes one want to give up windows altogether....

If I could sell all my Sonar software I would be seriously tempted....

Thanks for the links Dom...the good news keeps coming

Dennis

Hi Domenico and friends.
Got a new screen shot for you and an update.



1: Reworked GUI so display is cleaner and more efficient.
2: Added ability to set Sound Volume.
3: Added ability to create new folders to store and manage more than one library of sounds in a single database.
4: BIG update......Added full Drag & Drop function that allows you to drag and drop sounds from other libraries into each other.

For example...... By default a standard GM Bank uses variation 0 and programs 1 to 128. This leaves you with variation 1 to 127 X times the number of program sounds to assign additional sounds to your default GM bank without effecting the working order and function of the GM bank. In short you can merge any library you want through drag and drop with the GM bank without effecting it's function.

5: Too many bug fixes to mention but at this point the program is rock solid and super stable.

As soon as I write the code that gets the program to generate a 100% working LSCP file I'll issue the first beta so you guys can all take it for a test drive.

Phew.... Won't be long.

Kind Regards
James.

All I can say James is WOW!!!!

This is great, no, awesome work!!! And it will be well appreciated I am 100% certain.

You are certainly going to help us non-programmers navigate through the MS in a major way...

As I said I am happy to beta test for you. I might not be much good at programming, but I certainly know how to put a program throught its paces

Dennis

Just one thing I would mention, the actual MIDI standard defines it as 0-127. For all numbering.

Probably won't make any difference, and I assume you already knew that, but I thought I would mention it

Not trying to teach a granny how to suck eggs, if you get my meaning

D

Hi Dennis.

Thanks mate. Comments like that make the amount of effort it takes to write stuff like this worthwhile.



That's all any programmer could ask. A good beta tester is priceless.



From what I gather, and correct me if I'm wrong here because this is not every day programming for me. There's a -1 vale that needs to be written into all code when dealing with GM.

The Program change values are from 0 – 127, but the standard program names are from 1 to 128. So for example if you wanted Piano 1, that's called program 1, but the actual Program Change value is 0.
http://en.wikipedia.org/wiki/General_MIDI

Do you agree with that ?

Cheers
James

yes,becouse you most have 0 in computer programimming and "0" is programchange for drums to as you know


[This message has been edited by AFG Music (edited 05-03-2010).]

Yes 100% correct. All the majors write that into their patch banks as a matter of course.

number one patch is always the piano and it is alwasy listed as CC0 0, CC32 0, Patch # 1.
But in real terms (MIDI spec-wise) it is patch # 0.

Why all CC's use numbering from 0-127, BUT patch uses 1-128 I really don't know, but as Roland were one of the main instigators of the GM spec, and they used banks of 8...16 banks of 8 = 128????

Maybe it made it easier for the early instruments with higher bank levels....

D

Hi all.
Here's one last video preview. Next time you see the program in a video it will be finished.

Beta Preview 2

Since recording the video I've fixed the Print function you see in the video.

Can you think if anything else you need at this point ? If there's nothing left to add, I was going to start writing the code for generating the LSPC file.

Regards
James

Screen shot of the printouts now working.


Regards
James.

Amazing,

can users change the real giga file name in box that you have created with name Giga File Name?

is great,

now await response from Domenico. I think he will say that this is complete.

I must not forget to say:

thank you

Yes, but Lionstracs are pulling Patch names that will be displayed on the screen from the actual giga file names.

It's a shame we didn't work together on this when Lionstracs were making changes to Linux Sampler because the way it's been implemented now you must make sure your file names make sense as the file name will be displayed as the Patch name on the screen.

Where if we had of worked together on this, we could have made use of my editor to allow you to freely name a Patch on the screen without even caring what the actual Giga file name was.

Regards
James

i think, if you change names it most work from lscp to. becouse qsampler instument editor has this function already. it is a part of LSCP file. what Domenico means that
gmgigabank_lionstracs.txt inside preset folder is not more need.

because previously we had to edit this file for sounds from lscp file to see on MS/Groove screen.

maybe I'm wrong,we can better wait for a response from Domenico.


[This message has been edited by AFG Music (edited 05-04-2010).]

lol...all is calculated..
on your LSPC system you have to add the last fild after the Persistent/ On Demand, you have the filename.gig that this one will displayed on the MS GUI.
here the LSCP string example that I made for you:
# MIDI instrument map 0 - Chromatic
ADD MIDI_INSTRUMENT_MAP 'Chromatic'
MAP MIDI_INSTRUMENT 0 0 0 GIG '/home/mediastation/GigaLibrary/SoundbankGM2/001Acoustic\x20Grand\x20Piano/GrandPiano.gig' 0 0.9 PERSISTENT 'Open Platform!! [0]'
MAP MIDI_INSTRUMENT 0 0 1 GIG '/home/mediastation/GigaLibrary/SoundbankGM2/002\x20Bright\x20Acoustic\x20Piano/BrightPiano.gig' 0 0.9 ON_DEMAND_HOLD 'James... [0]'
MAP MIDI_INSTRUMENT 0 0 2 GIG '/home/mediastation/GigaLibrary/SoundbankGM2/003\x20Electric\x20Grand\x20Piano/003\x20Electric\x20Grand\x20Piano.gig' 0 0.9 PERSISTENT 'Edit your LSPC [0]'
MAP MIDI_INSTRUMENT 0 0 3 GIG '/home/mediastation/GigaLibrary/SoundbankGM2/004\x20Honky-Tonk\x20Piano/HonkyTonk.gig' 0 0.9 ON_DEMAND 'Editor, the last.. [0]'
MAP MIDI_INSTRUMENT 0 0 4 GIG '/home/mediastation/GigaLibrary/SoundbankGM2/005\x20Electric\x20Piano\x201/05-00\x20E\x20Piano\x201.gig' 0 0.9 ON_DEMAND 'name sound.. [0]'

Here is the update Gui with the new text:


so..just add this filed on your application and you are able to write and see on GUI what you like.
is good?
Now I upload the new Current update with the fixed velocity engine, new Performance combi and some else..
let me know

[This message has been edited by LIONSTRACS (edited 05-04-2010).]

I knew you thought about this before to start
change everything,becouse qsampler instruments editor do this, it is a part of lscp file as i said before, lol

thanks

[This message has been edited by AFG Music (edited 05-04-2010).]

lol.... Nice one Domenico...!!!!!

Just ran into a big problem on my end. Allowing the program to actually store the Giga files within the database is not going to work. I'm storing everything attached to the program within a single file and because the files we will be attaching can be anywhere from hundreds of megabytes in size to gigabytes, my database file is too big.

Once you exceed the 4GB mark Windows doesn't like it and the entire system slows down to a crawl. I've even tried to write in a function that limits the database file to 2GB and when you exceed that it creates a second file that can also accept 2GB and so on.... But it's too slow as the files are just too big. Your hard disk will take too long to open and search the database.

So.......

To get around this problem I've had to remove the ability to attach files, but you still won't have to type in paths or file names. I've added a “Get Path” option that pulls in the path to your selected giga file and it populates the relevant fields.

Ultimately it does the same thing, the files are just not attached to the database. They are just sitting in a folder on your hard disk and the program can extract the information it needs when you select the file.

Regards
James

Looks sweet James.

Dennis

Some clever lateral thinking there James

Seems like a perfectly workable solution. As you say, has the benefit of keeping the file size more compact...And in the end the exact same result is achieved.

Dennis

Thanks james.
I suggest you to modify your tool, that not embedded the all gig files but create only the complete .lscp file.
remember that the OS code will loading automatically your all new sounds only IF the LSCP file is located inside the Presets folder.
The allowed LSCP file names are only:
MS-02-instruments-1.lscp
MS-02-tyros.lscp
MS-02-oriental.lscp

Only this 3 script will be loaded automatically on Restart players and reboot system.

About your tool, dont need to embedded the all giga file, make the hyperlink to the path .gig file and over.
The BEST then is that you add one button feature, like we made on Jsampler for VST version.
After you have created your own bank, the Create bank folder will COPY the all .giga files used to the all around directory and put all on ONE master directory.
After copied all, the tools have to UPDATE the all path directory to the new one.

IF then you will use this all new giga sounds bank under the MS and GROOVE, remember that the tool have to written the correct linux directory path.
Must be always start from:
'/home/mediastation/GigaLibrary/here your master sounbank directory / and inside the all files/subfolders.

EXAMPLE of your final path:
'/home/mediastation/GigaLibrary/JamesBank1/001Acoustic\x20Grand\x20Piano/GrandPiano.gig' 0 0.9 PERSISTENT 'GrandPiano.gig [0]'

So..when one new soundbank is created, all must be inside, including one copy of the LSCP file to MOVE/COPY to the Preset folder.

In this way you can share ( or sell) your complete soundbank, the user have ONLY to copy the sounbank inside the GigaLibrary folder, copy the LSCP file on Preset folder and..Restart... game over.
Get the idea?

When your tool is nice working, finally Nedim can use it and sell new Oriental giga sounbank without buy one Groove.
(for make the same for the Audya..have to buy one Audya... )

James..just a littel question...
but the all other brands..give the same OS support and features request that I give you?
second question...I know that I still have bugs around on my OS and must to be fixed ( I try to make my best when I can..) but..(with included this some bugs), is the MS a nice products ot not?
You have now started understand how is working my OS and about the all features around...give now fun or not?
I'm just curious, because you had on your hands MANY keyboards...
How you fell now with the MS?
Honest, don't worry....Diki will not reply here...

I know your question was referred to James.

but you and others know my opinion about you and lionstracs-lionstracs products and lionstracs team

Hi Domenico.



Thanks for the advice. I've just implemented all that. Now when you press the button Write LSPC you can see 3 options, one for each type of file.



Yes, that's done now and I'm much happier. Keeps the size of the program down and it operates lightening fast too.



I have the program now generating this code for every sound in the library. It scans the database for actual sounds you have completely setup correctly and then writes the LSPC file.

If you make a mistake and don't link to a file, the progarm will skip that sound and not include it in the LSPC file.



Yep.... In time I can get the progarm to actually move files and folders on the Mediastation too, so it makes no difference where all the files are. The program will move everything to the right folders.



Yep...



Flipping heck your right. Anyone can assemble a library with it without the need for a MS/Groove by using this tool.





Regards
James.

[This message has been edited by Irishacts (edited 05-04-2010).]

It's certainly quite a different experience from closed keyboards that's for sure. The amount of freedom and flexibility you get from the system is quite amazing. Even a simple thing like being able to load Gigabytes of samples on the keyboard still blows me away. With closed keyboards I'm forever running out of ram or hitting some other sort of limitation.



Can't tress how happy I'm with the system. Honestly, it's seriously good and super flexible. It's hard to explain, it's like I have all the benefits of a DAW, but at no point do I feel I'm working with a PC, it always feels like a musical instrument and for me that's extremely important. How the systems seamlessly implemented make this true pleasure to use.



lol... I think it's safe to say that the vast majority of what is said in this part of the forum far exceeds his understanding and ability so unless he's looking to Troll here too, I don't expect to see him ever posting here.

Cheers
James.

Hi all.

I know I said in my last video you won't see the prgoarm again until it was finished, but with all the changes that had to be made.... well here's another preview.

I'd appreciate your feedback guys.

Beta Preview 3

Regards
James.

G'day James,

looking good

On the LSCP file on the MS, where you have the 127, it has 0 0.9 instead, and this is repeated for all 127 patches.

As you said, if Dom watches the vid (and he will) its one for him I reckon

I also notice you have a "variation" tab. What control method are you (Lionstracs?) using to access the higer banks, if there any to access?

Controller 0, Normal method, controller 127,

In the GM2 spec there is provision for higher banks, usually accessed by sending CC 0, (MSB) CC32 (LSB) and then a Patch Change event selecting the actual patch number.

It is probably a moot point however, as a lot of VSTs only allow the one bank anyway, all accessed by the standard CC 0.

I am not sure about Giga banks as I have not a lot of experience with them.

One last question, will your editor eventually be able to do the same if a user wanted to use VST instruments, instead of GIGA? And if its a yes, will a new format (not LSCP) be needed to do so? Or from your knowledge can the LSCP be amended?

Dennis

Hi Dennis.



Yeah... I'll need Domencio to explain how his value relates to volume. I need to know what are the defined ranges. I had assumed it was normal midi, but it's clearly not.

Also... why are there 3 values in the LSCP file ?
0 0.9 ? and why not just 0.9 for volume ?

Linuxsampler.org is not clear on this either. They don't define the ranges at all.



From what I understand {1,127,127} is just how Linux Sampler reads the data. There's no MSB/LSB as such.

In {1,127,127} the first number defines the type of sound it is. 0 for Instrument, 1 for Drum Kit. Second number is the variation or the so called MSB/LSB 0-127, and the last number is the program number 0-127.

I could be wrong on the MSB/LSB 0-127 though. Need Domenico to explain how this is implemented.



Right now the 3 files the program can generate are totally specific to Linux Sampler and Giga files. You can't use this file to call up other things as the only program reading from the files will be Linux Sampler.

To edit VSTi's assigned to Programs would require the program to be expanded to edit and generate other files in other folders on the MS/Groove which are specific to VSTi's.

All of which is totally possible. I've designed the program that when I want to update it or add entirely new functions, all I need to do is issue you guys with an update patch. You open the program, go to “File” and select “update” and load the patch issued through the menu displayed at this point. This will update the entire program without it even needing to be restarted

Regards
James.

Hi Domenico.

Inside the LSCP file there are two lines that say the following......



Do I have to include those two lines in the file ?

As you know after “MAP MIDI_INSTRUMENT” the first number defines the sound as an instrument or a percussion sound. 0 being an instrument and 1 being a drum kit.

So why the need for the two lines above ?

I'm only asking because of the drag & drop ability of my program the data needs to be dynamic for each sound in the database, but those two lines are not dynamic and they are also not headers. They need to be in an active area of my progarm, but being static they are causing me problems.

If I have to write them in, then will the MS/Groove read the information like this....



And even have Drums and Instruments mixed together in a list like that.

I think it should work, but hey... you will know for sure. I'd prefer to not have to include it at all, but if the MS/Groove will read the file this way, then I can proceed.

If not... I have to come up with a new way of handling data internally.

Regards
James

Excellent, now if we can work on how we can get VST libraries included on the MS/Groove data base......

Dom are you listening???? LOL

Thanks James....Can't wait to put it to work!

Dennis

Hi Guys.
Ok, here's the first beta release for review.

I do not recommend loading the LSCP file this program generates into your Mediastation until Domenico gets a look at how I've implemented all this.

beta-v0.9.exe

The program outputs the LSCP file to your c:\ folder.

Vista and Win7 users...
If when you press the button no file is generated, please run LSCP Gen as Administrator.

Regards
James

[This message has been edited by Irishacts (edited 05-05-2010).]

PS: When you install the program there will be a few files listed in the GM bank from my own library. Just delete those if you want to add your own.

Thanks so much James...I will download now and give it a try-out.

Great work m8...Truly appreciated

Dennis

Bravo James
I have download right now and the tool is working.
I have to test first if is missing some that match with the original lscp file.
I will make tomorrow because now I just terminated the OS 4.2 Update, for now I think is enough.
How promised, also update the sampler GIGA solo Gui, under EDIT mode:

The info you can read yourself..

I wait now this friday the Wine,org release the new Wine and then we burn the ISO 4.2
Just some days patience..
I'm also uploading the new currentOS4.2rev1931 on gFTP server ( bookmark Lionstracs)

James, I was re-looking at the volume settings....I wnet and had a look at a file sent to me by Zmago, and in it he also uses the 0.0 system, so I think that may be the way the Linux sampler looks at volume??

Zmagaos actually had variations, mostly 0.05 and 0.09.

The default Lionstracs one is all 0.09, but then if you look at all the volume for each patch, they are ALL at max (127).

I did not get the chance to fully check Zmagos list, but I bet the ones at 0.05 are probably at volume levels of about 75-80??

What do you think?

Dennis

very good piece of software,
works well. now just wait and see if your LSCP file is good enough when tested by Domenico.

because you see some things different. if you compare your file and file from qsampler instrumens editor.

In short, you did a good job.

[This message has been edited by AFG Music (edited 05-05-2010).]

Hi Dennis.



Yep.. but if you look here.... http://www.linuxsampler.org/api/lscp-1.4.html#SET%20CHANNEL%20VOLUME


So a value of less than 1.0 is a decrees in volume, and a value higher than 1.0 increases the volume. This does not make any sense to me as it does not relate to any scale I know of and they do not even define the range of this set of values.



Are your numbers correct there ? I haven't looked at any other files than the default GM bank and the numbers in there are not formatted like that. The volume is displayed as 0 0.9 and not 0.09
There is a space between the first number and the second two, plus look at the decimal point.

So either the information Domencio posted on structure of the file is wrong and the first digit is for something else entirely, or this is one crazy way to specify volume.

Regards
James.

Yes.... if you look at the last post on page 1 of this thread, I've posted a question for Domenico about this.

The documentation on linuxsampler.org is awful.

Regards
James.

I'll send it to you via email...

Oh and sorry m8, yes it was a typo(well I just abbreviated it)...they ARE 0 0.9 and
0 0.5

Dennis

James,
on qsampler instruments editor you can change volume only with percentage. when you save LSCP file you get 0 0.9
so,0 is for giga patch bank this if you have some giga instruments and you save it for example with extremsampler editor in one giga bank, here you can select then the nummber. for example you 5 instruments saved in one giga bank here can select from 0 to 4.

0.9 is for 90% volume

maybe, i am wrong Domenico can better answer this.


[This message has been edited by AFG Music (edited 05-05-2010).]

If thats the case, then why is it when you select a giga instrument, the volume slider is at maximum?

I think 0 0.9 IS the max looking at it as a 0-9 numerical scale, not a 1-10 numerical scale...

Dennis

this is the volume from lionstracs mixerboard.

they most do this to have good output sound.


to see that i am right about this, just open qsampler chage your master volume with qsampler volume slider read on the bottom of screen the messages.

for example
9% volume = 0.09
90% volume= 0.9
100% volume= 1.

this is the way linuxsampler volume works



[This message has been edited by AFG Music (edited 05-05-2010).]

Hi guys.
So then the first number has nothing to do with volume at all ?

That makes so much more sense. If it's to call up Giga sounds in a Giga Library file, then my program doesn't even address this and I will have to add this function. What are the ranges that need to be defined ? Is it 0 -127 ?

As for the second and third numbers, so are the ranges that need to be defined 0.0 - 1.0 or are we saying it's 0.0 to 0.9 ?

I think it's an ugly way to present volume to the end users so I'm going to leave my program display volume as 0 – 127 but I'll write a formula that outputs the information into the LSCP in the format 0.0 to 0.9 or whatever the range is supposed to be.

0-127 for volume just makes more sense as every keyboard displays sound like this.

Regards
James

Thanks AFG, yeah I can see the sense in that

Dennis

One of the reasons GM was conceived...uniformity. Not something that well known in the Linux world

Dennis

0% = 0.
1% = 0.01
2% = 0.02
........
........
........
99% = 0.99
100% = 1.

maybe this help

Thanks guys.
I'm going to implement those changes then. I'll add a GIGA Library selector for the first value, and for the second and third I'm going to use the following formula to convert my 0 – 127 standard midi volume values to LSCP decimal values.

1.0 / 127 X Volume Set (0-127) = LSCP Decimal Volume.
This way the end user will get to see normal values but the LSCP gets what it wants too.

Regards
James

[This message has been edited by Irishacts (edited 05-05-2010).]

Thanks James, for us "normal MIDI" guys that would be helpful, although as AFG explained it, it does not take much getting used to.

Actually, if we are to become more adept at running Giga samples and Linux Sampler, it may be better TO get used to the terminology.

It is all a learning curve, this MS....One really needs to dispense with ALL the old accumulated knowledge and approach with a totally open mind to new methods.

They may seem strange at first, but I am sure there are good reasons.

AFG has kindly shown us, well me at least, and after he explained it, it makes perfect sense

Dennis

Hi Guys.

CLICK HERE to download an update patch. 130KB download.

To apply the update.....
1: Launch LSCP Gen.
2: Click on File.
3: Click on Update Database and select the patch you just downloaded.
4: Click Open to load the patch.
5: Click Yes to apply the patch.

Your now running on ver 0.91

Changes made.....
1: The Volume 0 to 127 is still displayed but the program now outputs in decimal format to the LSCP file as required by Linuxsampler.

2: Added the ability to select different sounds in Giga Library files. If your giga file only has one sound in it, please select 0 as the default option .

Finally, if you have started to add your own sounds to the program please select each sound and change the volume to a different setting and then back to your original setting. This will refresh your files and get them to output in decimal format as they predate the patch.

Regards
James

Thanks James...Quick work!!!

Well done!

Dennis

A couple of things...It would be nice if the top line data under LSCP was constant, ie it stayed the same when selecting to create a new patch. That way the user can just change the fields as they apply...

Also if the path can remain constant (unless changed)...Saves going through pages when I think usually the user will be sourcing most of the time from one giga folder.

Thats so far James....still working with it

Dennis

Hi Dennis.



Yes good idea. I'll add a mouse right click option that allows you to “Set as Default” the current state of the display.

So if you create a new patch and set everything as you want, just right click and click on “Set as Default” and every new patch created from that point onwards will retain the settings you took a snap shot of.



I'm a little confused as to what you mean here. You never have to navigate to the same folder twice as it stands right now? If you launch the program and add a new patch, you have to navigate to the folder where your giga files are. You only ever need to do this once per session using the program.

Add a second patch and it should jump directly to the folder where you pulled the last file in from.

Regards
James

[This message has been edited by Irishacts (edited 05-06-2010).]

Indeed when I OPEN the program it defaults to the disk location last used, but when I click "add patch" it changes to "Not Set" and asks me to re-enter the path to giga file. And does this for each subsequent "add patch"..

Dennis

[This message has been edited by miden (edited 05-06-2010).]

Hi Dennis.



Sure, but you must tell the program what file your working on for each patch you create. Without this it cannot tell the Mediastation / Groove what files to load.

Or am I misunderstanding you here ?

Regards
James.

[This message has been edited by Irishacts (edited 05-06-2010).]

I think you may be misunderstanding me

All the giga sample files are in the one folder on my hard drive.

When I select "add patch" for the first new patch I enter the path to the file. d:\media station resources\giga file\library

all fine...enter all my details for the patch, save it, then click on "add patch" for the second patch I want to do.

Instead of the path just coming up by default as I have already entered the desired hdd location and folder for the previous patch, I have to re-enter the full path again to load the next giga file which is in the SAME directory/folder as the previous one.

Dennis

Hi Dennis.



he..he.. Not to worry, I'm sure to have a “Light Bulb” moment at any point.



That's not a working path though and the progarm won't generate something like that. Are you typing in formation or something ?

A working path will include the actual file and the progarm will generate this from just selecting the file. A path should look like this for example.

d:\media station resources\giga file\library\piano.gig



Hmmm this doesn't sound right. I have a feeling your typing information into the program rather than pressing the Browse button which will return you every time to the last folder you opened.

Have a quick look at this new video for example. http://www.irishacts.com/lionstracs/lscp-q1.htm

Are you doing something different than me, or am I just totally off the mark here altogether.

Regards
James

[This message has been edited by Irishacts (edited 05-07-2010).]

Ahh, using the browse button, that then loads the last folder...

It ws ME who was misunderstanding....

All good. I was expecting the last file path to automatically come up, rather than click on browse. No matter its no problem to click browse.

By the way that IS the file path, I just shortened it for the point of the example...

In my case the full path is D:\MEDIA STATION RESOURCES\GigaLibrary\GIGAT2\GUITAR\Campfire Gtr.gig



Thanks James.....So its just the original request then about holding the data in the boxes under the LSCP

Dennis

Hi Dennis.

Cool.... phew,

I've just added that right click / set as default option so I'll issue an update patch soon. Just need to fine tune a few other little things first.

Regards
James.

Cheers m8, that will be handy I think. So far I have not been able to put a dent in its operation..Everything works as the brochure says
But I have a few more little tests to go

Dennis

Thanks Dennis.

The only outstanding question surrounding the program now is does having the following line before every sound that needs to be loaded make a difference to the keyboard.

ADD MIDI_INSTRUMENT_MAP 'Chromatic'

If not, then the program should be 100% compatible with the next OS Domenico is releasing. I'm assembling my own bank with the program now so that when the next OS goes live I'll be able to dump in my new GM Bank at the same time.

If it is a problem I'll have to rewrite quite a bit of the program.

Either way there's nothing stopping anyone from proceeding to populate the program with their sounds right now. Any issues that pop up can be fixed with update patches.

Regards
James