[gvalasek]

in reply to: AA play closest #50681

Hi agodzillau,

I may not have followed your example completely, but one important thing about the range setup is that the instrument becomes ‘blind’ outside of it. So whenever a note is pressed below the lowest note or above the highest one, it simply does not register for the given instrument. The closest note rule applies only to the notes held down within the set up range of the instrument. Is it possible that this is what causes the problem in your example?

[gvalasek]

in reply to: Any way to change CC Routing Section via ARC? #46726

Currently, there’s no such batch facility in ARC, so the best workaround I can think of is to use your DAW’s CC routing capabilities to achieve controller swaps, if they are frequent.

[gvalasek]

in reply to: Noobie with some questions. #42730

@Ethanfox wrote:

I should just say, running nothing in reaper but the five instances of Kontakt, each with 4 articulations and the shaws redemption preset, it goes up to about 30% – does that seem right? (Before I had it as part of a template).

No prob! Can’t say for 100% sure, I’m running a much more modest setup, but it does sound about right that you have 30% CPU usage when all 5 instances are playing with S&C engaged. IIRC Sebastian said something along the lines that on a modern 4 core CPU each instance of SC patch elevates the usage only by cca. 1%, but if I’m wrong he will feel the ripples in the Force and will correct it in like 5 minutes

The standalone havoc might be caused by having ‘Send MIDI to outside world’ enabled for everything in Kontakt.

Have you tried increasing your ASIO buffers in Reaper so that you can get away with higher CPU usage before the crackles start?

[gvalasek]

in reply to: CC list #42760

Page 8 of the LASS 2 Patches Manual details the CCs used for LASS but you can also find a topic here on the forum that lists them HERE. Hope this helps!

[gvalasek]

in reply to: Noobie with some questions. #42728

The load-up pops are normal, Kontakt is background loading the samples.

If you bypass the Stage and Color and everything becomes tame then it’ll be a CPU/DAW issue. All I can think of is to try this in standalone to eliminate Reaper as a culprit.

[gvalasek]

in reply to: Noobie with some questions. #42726

@Ethanfox wrote:

– Will doubling ram and getting a SSD help me run these 5 instances without issue or, if it is a CPU issue, not at all?

If it is a CPU issue, then neither the extra RAM nor the SSD would help much. Though you have a pretty powerful CPU, if the sections are in separate instances it should be able to handle the load. Have you tried reproducing this in standalone (no DAW, just 5 separate instances of Kontakt)?

@Ethanfox wrote:

– Is there a way to only run one instance of the reverb/stage but route it to all instances? Would that make any difference?

Unfortunately you can’t do that, the different patches are processed differently in Stage and Color.

[gvalasek]

in reply to: Noobie with some questions. #42724

I’d advise to check which one is the bigger obstacle in your setup: the CPU or the HDD. There are two activity monitors on the main Kontakt display for them around the top-right corner, labelled “Cpu” and “Disk”, check them out when the pops occur. There’s also an Engine tab of the Kontakt Monitor screen (on the left of the interface) which will give you more precise read-outs. You can also enable the CPU Profiling mode there, which will give you per-patch details of CPU consumption.

Nevertheless, judged by your description it sounds like a CPU bottleneck due to the convolution engine. A 50% CPU usage is high (that’s 2 cores maxed out of the 4) – try disabling the Stage and Color on all the patches to see if the pops go away. If the pops persist, you can try to increasing your DFD buffers in Kontakt (please refer to the Kontakt manual regarding this).

[gvalasek]

in reply to: How much disk space do I need for LASS 2.0? #41555

You can delete the old files, but please keep in mind that when you are trying to load older projects, you’ll get a “missing samples” dialog. If you check the “Allow alternative file types” checkbox there and browse for the new sample folder, Kontakt should be able to load up your patches, just don’t forget to resave the project so that the new file path references will stay in effect (you may also want to check “Keep search mode and selected folders for the current session” checkbox when dealing with the missing samples dialog too).

[gvalasek]

in reply to: *** LASS 2.0 UPDATE *** #38519

@Mahlon wrote:

This is really exciting news. One question, if you have the time; Is there any functionality to replace needing to use the Kontakt CandP Keyswitcher Bank approach to keyswitching?

Thanks
And Congrats on this baby.

Mahlon

Yes, there will be! It’ll be a more LASS-ified thing than the old CPC+KS was and much more flexible – you will even be able to mix normal patches and banks if you want to

[gvalasek]

in reply to: Effective use of humanisation within ART #38335

Not surprisingly, Sebastian is right as always The Rnd Time in ART is measured in 1/10th of a millisecond, so you have a 10 times bigger resolution when setting random delay times in ART than a millisecond. When ART itself is engaged (with the sustain pedal) it will put notes before _and_ after the precise beat, randomly, so you won’t have to set negative time offsets in that case to your MIDI track, ART will take care of that already. Hope this helps!

[gvalasek]

in reply to: Voices dropping out #38291

If playback is fine when you are playing the cue right from the start and your problems only manifest when you start playback from random positions, then the usual suspect is CC64 data tracking. Try to insert a CC64 new data point on the automation lane from when you are trying to play back, that might solve this (depends on your DAW, even in this case it may not send Kontakt the “pedal down” message).

If playback seems to be “random” right from the start and you are not using the sustain pedal, then there’s a good chance overlaps are causing you problems. Either “hard” overlaps, the visible ones on the piano roll, in these cases try to drag back the note endings so that they finish before the new note starts (and leave a gap as well between the repeated notes), or “soft” overlaps, when the gap between note ends and note beginnings is too small (smaller than the release ms).

2.0 will let you tell the patches how to handle overlaps, it should provide some improvement both in pedal and non-pedal playing and playback situations.

Hope this helps!

[gvalasek]

in reply to: LASS LS Violas A "acting up" #38275

Hi,

please email the Logic file to [email protected] , that might be the best way to get the file through.

I can only speculate, but a second or so long transition sounds very “not right”. Is it something like when you are trying to use a purged sample and Kontakt loads it (but ultimately fails to deliver in time for first use)? I.e. oddly timed transition-note trigger with interrupted playback, etc.?

Please note that due to the wedding it might take longer to get back to you this weekend, but Andrew will be checking in later. Thank you for your understanding!

Best,
Gábor

[gvalasek]

in reply to: Auto Arranger/Divisi How to Simplify Workflow? #37399

You are welcome! The playback related things depend on the host, a stop should clear everything though. The pause button on the other hand could make things more complicated, that could be more prone to producing odd things. Does the situation improve if you click on the stop button twice?

[gvalasek]

in reply to: Auto Arranger/Divisi How to Simplify Workflow? #37395

@strytten wrote:

⁃ sometimes the playback is as if the sustain pedal is off, even though it is clearly on; I believe Logic “chases” the status of sustain because I’ve never had this problem with keyboard patches that I use; problem more frequent when playing multiple tracks than when playing one track; I can reduce (but not eliminate) the frequency of the problem by entering sustain codes along the way as I work, so that I don’t have to worry about “chasing”

Chasing CCs in DAWs can get a bumpy ride. It might be worth to check your CC lane on CC64 and insert a node on the curve of value 64 or greater at the desired point of playback to see if that helps your trouble with the sustain pedal.

@strytten wrote:

⁃ sometimes the playback does not play all of the divisi notes, as if AA/divisi function is off, even though it is clearly on; problem more frequent when playing multiple tracks than when playing one track; works much better when using sustain pedal and short notes; and I mean really short, like an eighth or quarter note even though duration is whole note; I tried “just a little bit shorter” to allow for the humanization factor, and that wasn’t as reliable as “really short.”

The usual suspect in situations such as this is overlapping notes, as well as having the note-offs being too tightly walled to the successive note-ons. Try shortening your notes a bit. Though there could be another thing: too long chord time-spans, when the notes of the chord arrive in a longer time than your chord detection threshold. In those cases a chord meant to be one will be interpreted as two. This could happen by an accidental MIDI note timing randomisation (or even quantizing if that splits up a chord). It’s best not to use any MIDI humanisation on LASS AA tracks from within your DAW (AA will negate them anyway).

@strytten wrote:

⁃ Based on my conclusion that AA works better with short notes, and since I like to see the actual durations when possible, I have started turning AA “off” when I am not in divisi. I use controller 30 to turn auto arranger “on” and “off” for certain sections; I have been learning the nuances of exactly where to insert the on/off codes for auto-arranger in the middle of passages, there is a bit of an art to it;

When you are working with the sustain pedal “plucking”-style you are getting around the aforementioned release/overlap related issues, so if you find things easier that way they could indeed be the cause for some of your problems. But I’d suggest you to try some chord detection and/or release time values other than the default ones, to see if there are settings that suit your playing style and workflow better. Hope this helps!

[gvalasek]

in reply to: How does velocity work? #37372

@Guido Negraszus wrote:

But isn’t that the same as just using MIDI volume or even expression? Is there a difference doing swells with either volume, expression or modwheel (apart from the modwheel advantage)?

There can be a huge difference: with CC7 you are merely changing the volume, essentially you are using the very same dynamic layer all along, changing its volume only. Most instruments sound recognizably different at various dynamic layers, brass is an obvious example, but so are strings.

With CC1 you are changing the actual dynamic layer, not just the volume in LASS. For percussive and short notes velocity control of the dynamic layer is perfectly fine, but for sustained instruments where several dynamics transitions can happen within a very short time-span it’s just not the way to do it in my personal opinion.

[gvalasek]

in reply to: LASS LITE …Sustain pedal and Auto Arranger? #37364

@DocMidi657 wrote:

Hi Gabor,
For the first patch what should I choose for the “if not present portion”?
Thanks,
Dave

Hi Dave,

it doesn’t matter. There’ll always be a highest note in any given “chord” (including a single note), so you can leave that at default.

Best,
Gábor

[gvalasek]

in reply to: LASS LITE …Sustain pedal and Auto Arranger? #37363

Hi Dave,

I’ll chime in a bit too. The most important thing about AA is that it will make a patch behave like a singular entity, that is after switching AA on that patch will be playing only 1 voice out the notes currently held down. So if you want to use AA for polyphonic legato with Lite (or FC for that matter) you’ll first have to decide how much polyphony you are after.

If you want 3 for example (like most – but not all – LASS Full AA multis) then you’ll need 3 separate patches for that. This will bring you to the first compromise you have to make: you either load up 3 instances of the same patch in Lite, or you sacrifice a bit of the playable range and load e.g. Vlns I, II and Vlas and use them for the 3 note division.

When you have the patches loaded all you have to do is to set-up your note distribution rules. You can do that in the advanced edit mode, for the first patch select “Note 1” in the “play from chord” section, for the second patch “Note 2” and either “Play first” or “Play none” in the “if not present” portion (the latter is useful when you want to keep the player-count as minimal as possible), for the second “Note 3” and “Play closest” or “Play none”. Assign them to the same MIDI channel or use your DAW to send the notes to all of them and see if it works like the way you wanted it to.

Hope this helps! If it’s fuzzy please make sure to check out the manual regarding AA rules too and see how changing the role in the main AA screen changes the landscape lower in the pipes (advanced edit and sub-rules page) to get some ideas on how to set things up.

Regarding the sustain pedal, are you referring to the problem that the sustains are not held at all in e.g. the legato patches even when legato is off? If so then that’ll be fixed in 2.0, when AA is off standard sustain pedal functionality will be restored (mostly).

Best,
Gábor

[gvalasek]

in reply to: LASS LS #37341

You are welcome and have fun with LS!

[gvalasek]

in reply to: LASS LS #37339

Hi, thank you for your kind words! For a normal polyphonic functionality simply turn off the legato (either via the button on the interface or using CC111). AA is for a different thing, it will make the patch interpret the actual chord and select a single note from it to play, depending on the patch’s role – it won’t allow playing more than one note in a single patch.

[gvalasek]

in reply to: ART sustain pedal #37236

@Sebastian K wrote:

@gvalasek wrote:

No problem Sebastian! And you are right about that toggle, I forgot it, it’s been a while since I’ve last ventured below the MIDI keyboard

Sounds dirty. :oops:

Oh come on, it did not!

You are welcome Willem!

[Author]

Posts