[gvalasek]

in reply to: LASS Sord Quirks #37021

@noiseboyuk wrote:

D’you know, swallowing any vestiges of pride and just turning up Chord Detect waaaay up to 100ms really makes it more reliably playable to me. Most passages with AA will be pretty slow anyway I suspect.

Again Rohan, I adore that piece. The strings really shine. I think pretty much any remaining thoughts of getting a competitor’s product have been pretty much banished!

I know that it may not seem too appealing at first if you are used to the standard function of the sustain pedal, but have you tried AA with the sustain pedal down? I am a really hopeless keyboard player but that makes things a lot easier for me, playing “plucking” style like Andrew did in the AA teaser video. Of course it might make fast forwards/rewinds a bit harder to manage because you will need to start from/touch the beginning of the new chords, but maybe it still accommodates your workflow.

[gvalasek]

in reply to: ART sustain pedal #37233

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

[gvalasek]

in reply to: ART sustain pedal #37231

@agodzillau wrote:

hi thx for info
ok it’s because of the AA.
yeah when AA is off it works this way.
i guess there’s no way to have both AA + ART + pedal working this way ?

Actually it already works together with ART the way you want, but it will not work with certain sustain pedals. Nevertheless, if your sustain pedal is not just a switch (only transmitting on and off values), that is it sends a 7 bit value of its state on CC channel 64, then all you need to do is not to push the sustain pedal all the way down, just gently, “less than half down” (so it generates values smaller than 64). This way ART is still triggered but AA key sustains won’t happen.

Some sustain pedals can operate both with the 7bit “continuous” data and the simple switch-like mode, there should be a switch on them somewhere that toggles between these. If yours is not such then the best you can do is to assign a CC fader to 64 and manually move it slightly upwards when you want to play like that and let the pedal take over when that is needed. Hope this helps!

[gvalasek]

in reply to: Relationship between sustain pedal, note-on and note-off? #36335

@Mahlon wrote:

@soulofsound wrote:

Also remember that when playing legato you need to have the keys you play overlap in order for the legato to play back correctly. With AA it’s the other way around, and you cannot have two notes overlap if you want these to be play sequentially without odd behaviour.

I wonder if this might be the problem that folks have mentioned with the auro arranger seemingly not working correctly. I thought something was wonky until I realized that (while using AA) an overlapped note in series will create some weirdness. For instance, in a three note chord where only voice 1 will move and voice 2 and 3 remain stationary, if voice 1 is played legato style with overlapping, voice 3 stops playing and jumps up to voice 1, (thus eliminating voice 3) and voice 1 disappears altogether.

So in other words, there can only be three voices playing at one time. When the overlap happens, AA thinks there are four notes playing and so cuts out one?

Is this right? If so, that may be what people are thinking is the AA getting wonky.

Mahlon

Technically speaking there can be an overlap, one that lasts less than the chord detection threshold, but we can pretty much consider that non-existent in practice So you are correct, as a general rule of thumb do not overlap legato when AA is on or else the overlapping notes will be considered as a part of the new chord and when you release the notes they will exit the chord and mute their voices – without “Retrigger divisi” the new chord state won’t be evaluated upon note releases. This is also why AA is easier IMHO with the sustain pedal down: just pluck down your chords and let AA do the rest.

As Sebastian suggested you can set up more polyphony using the sub-rules if you need them, the all section AA multis have some examples of these on the presets that allow e.g. 6 note polyphony in the higher sections (vlas + vlns I + II). I forgot which ones are these (maybe preset 2), but the docs have them listed.

[gvalasek]

in reply to: Sustain Pedal with AA works randomly #36003

@Sebastian K wrote:

@BertBamber wrote:

Also, sorry if I’m asking a dumb question here but I’m interested in getting AA to work but with normal pedal behaviour, as I’m an experienced pianist so the way it’s implemented by default gets in my way more than it helps me, esp in light of the above difficulties. Any tips on this?

When you say you’d like to get AA working with normal pedal behavior… what are you referring to? If you’d like to phrase with the pedal, unfortunately that is not a possibility when using the Auto Arranger. If you turn AA and legato mode off (or load a sustain patch) you can certainly play it that way… but the legato functionality is dependent on maintaining a voice count… so sus pedal overlaps don’t really work in a traditional way.

Depending on what you mean by normal behaviour it might be also worth trying out the retrigger divisi feature, probably on a new preset copied from the default one so you can switch it on and off by switching the two.

[gvalasek]

in reply to: Problem with Delay and Humanization Script #36092

Hi Thorsten,

the delay portion has no problems with accumulated notes, it wasn’t put into the final release, but even seconds long delays worked without any overlap issues. The sustain pedal however does have some buggy behaviour when AA is not engaged. For example on legato patches you’ll have to keep the note pressed for a little bit longer than just hitting it after the first one and on non-legato patches the pedal doesn’t really work (the latter was fixed for 1.6). When AA is on, even if you just quickly hit keys, it will be sustained when the sustain pedal is on.

I think it is easier (and safer) to set the MIDI CC data before entering notes, that is to push down the sustain pedal before the first note, dial up CC30, etc. Though I’m not sure if you want to do re-bowing or just tightly repeating notes, but for the former you don’t really need AA on, especially because most likely it is creating the lost-note issue here: if the next note overlaps with the previous one within the release ms threshold, then the patch won’t play the “new” note if it coincides with the previous one (at least currently, but it can be changed for 1.6), so you’ll have to dial down the release threshold to make tighter passages.

If you need AA on for this, then engage the Retrigger divisi button, hold down the sustain pedal and keep it pressed (CC64 >= 64) all along the passage – your note will be repeated as you press the same note again.

If you don’t need AA then Souldofsound’s suggestion is a very good one, keep down the sustain pedal all along and don’t cut the notes too short.

Best,
Gábor

[gvalasek]

in reply to: Volume control #36079

Oh, I see! But wouldn’t it make “more” sense to omit the ART functionality? I suppose in notation software such “untraceable” (from the host’s point-of-view) MIDI things are less desirable, though I’m merely speculating here. Strictly speaking there’s only one “volume” control on the short articulations and that is the velocity.

[gvalasek]

in reply to: Volume control #36077

As an alternative approach you can simply change CC111 and CC1 in your DAW on the ART channels. With your current approach the use of CC1 will remain twofold though: it will control the attenuator and it will also shorten the length of the samples (so the sequence will feel tighter). If you want you can simply set up on the Delay and Routes page some other control to take the latter role from CC1 (route anything to CC1, see documentation on details).

[gvalasek]

in reply to: keyswitches #36081

If you mean the preset keyswitches for ART and AA, then they will be shown in the 1.6 update. Prior to K4 you couldn’t colour the keys from scripts, especially not dynamically

[gvalasek]

in reply to: Sustain Pedal with AA works randomly #35995

@[email protected] wrote:

I play within range, live and even if my sustain pedal is on, the AA would not work (notes don’t hold). So I stop playing, release the pedal and start again. I hold the pedal, play a few notes, it doesn’t work. I stop, realese and start again. Hold the pedal, play and this time (maybe!) it works. Sometimes I have to do it 5 times, sometimes it works for a while.
It happens when I play live or when I playback as well. This is weird…
Thanks for your help

Ouch, that doesn’t sound right. With which patches do you experience this? If AA is engaged even the ART patterns will be held. Have you tried this in standalone mode? Is it working there? Also, it’s trivial, but please make sure that AA is engaged (CC30 is dialed up).

[gvalasek]

in reply to: Stupid question maybe? #36073

There used to be a Komplete upgrade, that allowed you to upgrade to Komplete from Kontakt (among others), but I can’t see it in the NI webshop. However, it can be found at Thomann and Sweetwater, etc. so it should be still valid.

[gvalasek]

in reply to: Tuning issues in Kontakt #35855

Have you checked whether they are both running on the same tuning? In Play click on the Settings button and see if tuning is set to 440. In Kontakt the master editor shows you your tuning info (see attached screenshot). If both are 440Hz, then it’d be worth launching both Kontakt and Play in standalone and see if there are tuning issues present when they are both in standalone. If not, there might be something in your DAW, but I don’t know what you are using.

[gvalasek]

in reply to: Tuning issues in Kontakt #35853

@cdsymphony wrote:

Okay I got it. I had to increase the Tune control to 1.00 in the LASS interface. Then I had to decrease the Master Tune contol to 417.00 for the Kontakt player. Now they sound in tune. All the library’s are like this as well. I wounder why it’s like that.

This looks more like a strange different sample rates issue, as Andrew suggested, though these numbers don’t really fit the 44.1/48KHz scenario. Are you sure everything is running on the same sample rate?

[gvalasek]

in reply to: pitch bend range LASS/KONTAKT 4? #35828

Hi, just add a pitchbend modulation to the desired groups in Kontakt. For a screenshot, check out this thread: p=4448#p4448.

[gvalasek]

in reply to: Dealing with Longs vs. Shorts in Banks : Verb #35819

I think this might help you: p=6483#p6483

[gvalasek]

in reply to: Staccato and Dynamic Control. #35802

You are welcome! Regarding the programming in Full vs. Lite: the scripts are identical, so you have the same features – Lite only lacks the divisi and FC samples. I just don’t have the Lite docs handy so I wasn’t sure if it’s the same as the Full docs too due to this, hence my remark on not knowing the exact place of this.

[gvalasek]

in reply to: Staccato and Dynamic Control. #35799

I don’t know the page in the Lite docs, but in the full it can be found on page 30: you only have to go the Vel Atten pg. and input whatever CC you’d like to have for velocity attenuation

[gvalasek]

in reply to: Instrument Banks / Layers #35745

@chimuelo wrote:

Older libraries are locked inside of the Instrument Banks..
Any work around for those…??

I’m glad the output info was helpful Unfortunately, I don’t have good news about this, it is not something that can be remedied. If the developer decides to lock the editing of the library then that’s it, there’s nothing you can do about it with banks. If NI would implement a patch performance view within banks it could be a solution, but that’s for the future to see.

[gvalasek]

in reply to: Instrument Banks / Layers #35740

@chimuelo wrote:

I couldn’t find a way to use seperate outputs of an Instrument from within an Instrument Bank.

Actually there is one, but it is not too “intuitive”, the solution doesn’t really reside where one would expect it to (at least the one that I know of). There are also no easy means to switch outputs on the fly, but if having static out routing within a bank is enough, then after you have created the outputs in Kontakt go into a patch in the bank that you want to assign to some output (by double clicking) and open up the Group Editor.

Make sure to select Edit All Groups and somewhat lower change the Amplifier module’s Output to the one you’d like. Here’s a screenie of it, hope this helps!

[gvalasek]

in reply to: Dropouts in Kontakt 4.1 / 0.7Gb Instance #35684

@pianoman wrote:

many thanks gvalasek – I’ll try that.

It is usually 30 or so voices whilst it is dropping out – Violins 1 & 2 in that instance (A/B/C) playing long slowish legato lines.

I too suspect Quick Load being the culprit here. Those voice counts should not pose any problems, should there be no other streaming activities going on. Roughly speaking QL loads the samples (even the small starting portions for DFD groups) in an on-demand manner: the samples will be kept out of memory until they are required (you hit the key), which could choke things, since it’s a more demanding thing than the normal DFD streaming.

[Author]

Posts