[gvalasek]

in reply to: volume levels of all patches (excluding FC’s) #31119

Play around with the CC Table script. Select Layer Vol from the menu on the right and increase the lower part of the table.

As feature request it would be nice to have some presets there and some editing options like back to default, linear, etc.

EDIT: and move the modwheel once you changed the values to hear them taking effect.

[gvalasek]

in reply to: Instrument Bank in Kontakt triggered by keyswitches? #31063

No problem guys

[gvalasek]

in reply to: Instrument Bank in Kontakt triggered by keyswitches? #31060

You can read a longer thread about this here. You can download a multi from here where the notes between midi values 12 and 23 (C-1 – B-1) will be used to send program change messages to the first 16 instrument banks in the multi and the CC values will be carried over as well.

[gvalasek]

in reply to: Setting up all of LASS #30260

The majority of the samples indeed won`t be streamed but there`ll be still a fair amount (cca. one third) that will come from the harddrive. If you are using Kontakt then you could try setting all groups` source module mode into sampler to see if skipping the DFD will help.

[gvalasek]

in reply to: Setting up all of LASS #30258

@bluejay wrote:

In my main template I replaced all of the LASS legato patches with LPG Speed patches so that they can’t use DFD and I’m still getting ASIO spikes.

What do you mean by not using DFD?

[gvalasek]

in reply to: Setting up all of LASS #30256

What is your latency? If it`s too small then it can lead to spikes/crackles/whatever.

[gvalasek]

in reply to: Setting up all of LASS #30254

@bluejay wrote:

Hi people,

So I have my LASS installed on a drive (let’s say Samples).

To split them I just did the same as someone else her and copied the lot to another drive (Samples 2).

If I load an instrument on Samples 2, will it point to the samples on that drive (i.e. using a relative path) or will it still be pointing back to the original install location and using the original drive (i.e. using an absolute path)?

Thanks in advance.

The references to the samples are relative but did you copy the nki instrument files along with Samples 2? If you change the location of the samples (like moving them to another drive) and leave the nkis where they were then the relative locations will be different.

If you haven`t moved the nkis then you`ll have to browse for the missing sample`s new location, at least I had to, you can read about it here – though of course there can be more convenient solutions than mine.

If you moved the nkis with the samples and the directory structure is the same as in the original installation then they`ll load all right just make sure to copy LA Scoring Strings_info.nkc and LA Scoring Strings_info.nkx too because that`s where the skin file is.

[gvalasek]

in reply to: Weird Bug Of Uncertain Origins #31024

Have you tried using this multi? It`s my keyswitcher script plus Nickie`s CPC slightly modified so that the program changes won`t be delayed.

It does actual keyswitching, the notes between 12 and 23 (C-1 – B-1) will be used to send program change messages to the first 16 instrument banks in the multi.

[gvalasek]

in reply to: A naive chord-splitter/auto-divisi #30501

Dial up CC66 above 64 and it will sort of work the way you want Of course this is a pretty limited splitting script and could be made more user-friendly (and usable) but this is how far I got with it in my spare time.

EDIT: so by default (CC66`s value is <64) the script distributes the notes of the latest chord only amongst the divisis. If CC66 is dialed up (>=64) then the script will distribute the notes of the most recent, still held notes. Maybe the latter would have been a better choice for the default behaviour.

[gvalasek]

in reply to: CC 11…WHAT´S ITS STANDARD??? #30973

The default values depend on what patch you are using. For the L/LP/LPG patches the default value of CC11 seems to be 127. You can check these on the amplifier modulation tab:

screenshot here

[gvalasek]

in reply to: LASS and harddrive hardships… #30903

@Andrew K wrote:

NI fixed Batch Resave after K2.2.4

Cheers,

AK

:oops: Erm… my trust is hard to earn (back)!

[gvalasek]

in reply to: LASS and harddrive hardships… #30901

@Andrew K wrote:

I think the trick into saving on multiple drives might be Batch Resave.

Of course, always backup your LASS Instruments folder somewhere else because Batch Resave overwrites the patches your a “resaving”.

Cheers,

Andrew K

Oh yes, backups are always handy. I didn’t think of batch resave since my initial bad experiences with it I don’t know how long ago, thanks for the tip!

[gvalasek]

in reply to: LASS and harddrive hardships… #30899

1. I know everybody hates this answer but: it depends. What MB you have, what HDDs you get, how much traffic goes on the FSB not related to the streaming etc. I have 3 SATA drives on my Core2Duo without problems and i7 is a much more capable processor but this is more dependant on your MB than you CPU.

2. I am spreading it over 2 drives but I’ve only checked how it’ll go, didn’t have time to finish off the work.

3. It’s more tricky here, though I have no idea how it would work in KP because it involves browsing for missing files (and resaving, though that’s not necessary, just makes things more convenient in the long run). I copied the nkx and nkc files where I wanted then I rebuilt my database (Kontakt’s database for the Kontakt content on my machine). After that I loaded up the nki-s that were referring to samples from those nkx-es. Kontakt gave a “missing files” dialog and I let it search it’s database for the missing files (I could have browsed for them manually, I guess that’s what you have to do in KP), and once it finished I resaved the patches. I doubt that you can save in KP but ideally you’ll have to do this browsing only for your template’s Kontakt instances.

[gvalasek]

in reply to: Help – creating a Key Switch for Instruments Bank in K 3 #30423

AFAIK anything out of a byte’s reach (0-127) is not really standardized in CCs. In Kontakt the “midi command” of program changes is 192 for example. Also some hosts may catch the program changes too by default.

[gvalasek]

in reply to: Delay and Humanization #30467

Stu: Kontakt Script Language Manual.pdf, in your Kontakt 3’s Documentation folder Of course it won’t tell much background on how are functions (like random) implemented, you’ll have to ask NI people for that.

[gvalasek]

in reply to: Help – creating a Key Switch for Instruments Bank in K 3 #30411

You are welcome but Nickie’s CPC code is much more complicated than the keyswitcher, so she should have the credit for the bulk of the work

[gvalasek]

in reply to: Help – creating a Key Switch for Instruments Bank in K 3 #30408

I`m not familiar with it but judged by their manual it looks like you even have 2 options to get that “-1″th keyswitch octave: you can either transpose or add another zone to your keyboard wherever you want and set it to the -1th octave

[gvalasek]

in reply to: Help – creating a Key Switch for Instruments Bank in K 3 #30406

That depends on your midi controller. What midi keyboard do you use?

[gvalasek]

in reply to: Help – creating a Key Switch for Instruments Bank in K 3 #30404

That`s because I put the keyswitches one octave lower than the lowest note of the bass so you`ll have to transpose the keyboard an octave lower (EDIT: it`s really unstandardized how we call that octave, in Kontakt the lowest C`s octave (midi value of 0) is noted as “-2”, so the keyswitch zone is the “-1″th octave). If it`s a problem I can make it user definable but you`ll need some midi messaging for that.

[gvalasek]

in reply to: Anyone Using the CPC script with K3.5? #30558

@tripit wrote:

@gvalasek wrote:

Merging scripted multis is unfortunately not handled well in Kontakt so you have to manually load the scripts into a multi. I put the two scripts into this multi and I also had to make some changes on CPC so that program changes won’t be delayed until note-off, I hope Nickie won’t mind.

Thanks again. How are you editing multi scripts?

You are welcome! Multi scripts are somewhat untamed beasts, I’ll have to refer to this thread at VI control which explains how you can access them: http://vi-control.net/forum/viewtopic.php?t=6994. Once you can see those extra script slots it’ll be more straightforward but be advised, multi scripts can get pretty crash-prone so be prepared for some Kontakt crashes

[Author]

Posts