[gvalasek]

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

How many voices are streamed in that instance when this happens (you can see the number of total voices in the top-center portion, right above the total memory stats)?

This could be some host-related issue (if you are running Kontakt in plugin mode), but if the disk meter overloads it does mean that most likely there are problems with streaming, unfortunately. RAID does not mean you become free of streaming issues, if you are using many divisis and fast legato lines they could still happen (and I suppose your other Kontakt instances are streaming from the same RAID as well).

You could try increasing the Kontakt preload buffer to ease the streaming needs (Options/Memory tab), to e.g. 120Kb, to see if it solves the issue (please keep in mind to check the “Override Instrument’s preload size” checkbox).

[gvalasek]

in reply to: Can’t change keyswitches in ART #35497

Hi, from what you’ve reported it seems to me that you haven’t saved the preset itself: please keep in mind that in order to save your edits you have to save your presets using the A.R.T. preset menu on the interface (“Save > preset “). All edits before saving a preset in A.R.T. are just temporary (so you can revert back to the saved preset if things go south). Hope this helps, let us know if something else is the problem!

[gvalasek]

in reply to: Cubase 5, Midi CCs and a head scratcher… #35492

About CC7’s resetting: by default it’ll be sent the value of the track’s fader from Cubase, if memory serves me right. So whatever you set for the track volume in Cubase will be the patch volume as well on start, unless you disable the standard volume and pan instrument behaviour in Kontakt (open up the patch, Instrument Options/Controller and uncheck “Accept standard controllers for Volume and Pan”).

Cubase used to have a setting called something like “Reset on stop”. If you experience unwanted resetting this might be the thing that could shape things more to your taste, but once again, I’m unfortunately no Cubase/Nuendo guy.

[gvalasek]

in reply to: Lurching effect in legato patch #35469

In my opinion the best way to tame the effect is experimenting with the delay and humanization settings. Andrew made a great video about it, check it out here: p=6132#p6132

[gvalasek]

in reply to: Vlns B Leg LPG #35472

Thanks for the report! I can confirm the noise, it’ll be taken care of in the next update.

[gvalasek]

in reply to: LASS banks for all sections #31713

@ozmorphasis wrote:

Hi gvalasek,

To help troubleshoot for someone a few posts ago, you had them try the keyswitches using Kontakt’s built in keyboard display. I am having the same problem that the other poster had: I have to click on a keyswitch twice in order to make the patch change. Whether I use my own keyboard, or the one in Kontakt, I get the same result…it takes two clicks. Any ideas? I’m using the CPC and Keyswitcher from your original post on page 1.

Many thanks in advance!

O

Hm, it sounds strange, do you experience this in standalone mode too or only in one of the plugin modes?

[gvalasek]

in reply to: using A.R.T. with Logic Pro #35303

Hi Michael,

I suppose you are trying to record your MIDI just like when you are playing in parts. In that case what you see is normal, only those notes will be recorded that have been input by you, the generated notes stay “within” Kontakt unless you check the appropriate settings. Your DAW also has to be capable of receiving MIDI data from plugins, I hope this thread about this will help you: http://www.audiobro.com/forums/viewtopic.php?f=3&t=166

Best,
Gábor

[gvalasek]

in reply to: LASS banks for all sections #31710

@keyplayer wrote:

Perhaps you can clarify where exactly I should be putting the cpcandkeyswitcher file? And how to load a multi into it?

CPCandKeyswitcher itself is a multi, you don’t load another multi into that, you drag your banks into it, like in the video posted earlier: http://www.youtube.com/watch?v=FDzGNNUKuLE (it’s not relevant that this is loading the keyswitcher without the CPC)

You won’t be able to see the keyswitches, currently there’s no way to color the Kontakt keyboard from a multi-script. Nevertheless, the keyswitching should be working. Hope this helps!

[gvalasek]

in reply to: LASS banks for all sections #31705

@bricop wrote:

In the video you opened a ‘keyswitcher’ multi and then the LASS patch. Where did you get the keyswitcher multi from? Sorry, I’m not used to using scripts etc in K4. You also said there were two scripts but I downloaded only one?

That’s the CPC-less version of the multi you can download from the first post. The KS-ing portion is basically the same for the two. CPC is just the second script in the CPCandKeyswitcher multi (hence the name ), you only have to download the one in the first post. Just load up the multi and then load a bank and press notes in the KSing octave, it’ll change slots, like in the video.

[gvalasek]

in reply to: LASS banks for all sections #31703

Hi Brian,

I hope this short video helps: http://www.youtube.com/watch?v=FDzGNNUKuLE. If you want to use your preset-saving approach please keep in mind that the multiscript has two scripts, so you have to save both.

Best,
Gábor

[gvalasek]

in reply to: Auto-Arranger anomaly? #35112

Yes, currently the AA detection ranges are restricted by the patches’ playable ranges, so you can’t extend them. Up until now these weren’t even requested, that’s why I didn’t say these to be included in the next update for sure, but the current test version has the ranges cover the whole strings range.

[gvalasek]

in reply to: Auto-Arranger anomaly? #35110

The problem is that due to the ranges being different, depending on which notes you press down for your chord, the different patches will get different note counts in the chords, so you have to adjust your note-division rules keeping these in mind, but it is possible to remedy this situation to some extent with this. This is what I mean by that you have to think a bit like the section in these situations. If you normalize your playable ranges (they all end up having the same playable range), you can get around this, because they’ll have same note-counts all the time, you just have to get used to the different playable range. I really think that the easiest to get to know this situation is to start exploring AA’s sub-rules pages in the expert edit mode, start out by creating a 1st and 2nd violins multi and gradually introduce the extra sections, then compare your rules with the ones I’ve made for the combined section multis.

[gvalasek]

in reply to: Auto-Arranger anomaly? #35108

I agree that splitting between different sections is important, the note detection range for AA might include the whole range of the strings section in the next update, it could ease up certain aspects of this problem, but stretching out the samples to cover the whole range wouldn’t sound good (and that’s not really the issue here).

When you make combined section multis you have to customize your AA routings, check out the AA multis of this kind in the 1.5 update to get some ideas on how to do this. If you arrange your instrument ranges such that you have two disjunct intervals (one for low and one for high strings) on which the appropriate sections’ ranges agree (with transpositions) the rules can be much more simple than in the case of solving this with all the overlappings.

[gvalasek]

in reply to: Auto-Arranger anomaly? #35106

I couldn’t follow your example, and without knowing the exact notes you’ve used it’s hard to explain what you’ve experienced, because what happens depends on them a lot (how many sections have those notes in their playable range), but as a general advice, please keep in mind that the 3-part presets are not simply routing out the incoming notes “evenly”: they presume a quarter-quarter-half section, 3-part division, which in not the case in the configuration you’ve listed, so certain note-routes will not be what you’d expect even on the narrow common range of all those sections (see the docs regarding the 3-part and 4-part preset note distributions).

Another important thing to note is that AA only keeps track of notes within your selected instrument range (Lo and Hi value edits on the Divisi Setup tab), anything happening outside of this range won’t have any effect on the note-division (apart from preset changes naturally) and the note count in the chord. The change of played note when you started playing above the basses’ lowest octave was due to you changing the detected number of notes for some patches.

Also, when designing such a multi of multiple sections, you have to take into account the overlapping portions of the sections, because those will change the number of notes in the detected chord for the patches separately, etc., so you’ll have to think a bit like the section ( normalizing the playable ranges for all patches via restricting the playable range and transposing it can be very useful in these situations).

I hope this makes sense and I didn’t make it look arcane

[gvalasek]

in reply to: "Notes not playing" oddity #35093

It’s also worth noting that for sequencing purposes the release time attribute in AA can be set to the minimum (by default it’s 100ms, it means you’ll have to leave longer gaps than that between notes so that AA can recognize them as separate entities). The release ms is only required/handy when you play polyphonic legato lines without the sustain pedal down, it simply makes the release happen latter so that the real legato script can catch the transitions.

[gvalasek]

in reply to: volume pedal take the place of the mod wheel #35046

You might want to turn off the default CC7 reaction of patches too, this way the volume pedal will only control the dynamics and will leave the patch-level volume alone:

[attachment=0:3c8jyjkb]LASSCC7.JPG[/attachment:3c8jyjkb]

[gvalasek]

in reply to: Kontakt Playback #34887

@Nitesail wrote:

no worries, i’ll look into it. Thanks!

-Mike
http://www.nitesail.com

I think this post will help you to solve this problem.

[gvalasek]

in reply to: velocity and dynamic #34837

You are welcome

[gvalasek]

in reply to: velocity and dynamic #34835

@damstraversaz wrote:

You can disable the vel2cc1 conversion via the table on the multi-script’s interface

I’m note shure to understand how the table works ?

damien

If you toggle the multi-script view in the K4 interface, you will be able to see the controls I’ve mentioned, the first line will be table, each entry corresponds to a channel, if you set 0 as a value for an entry, the corresponding channel will receive the velocity/CC data normally.

[gvalasek]

in reply to: velocity and dynamic #34830

If you are using a section multi with AA you don’t have to necessarily open up a new MIDI channel, you can use the “Auto Arranger and DNH” script’s DNH portion to re-route CC1 to other another controller, so you could end up with an extra CC track. But true, for sustained patches this can indeed be a problem, the best temporal solution I can think of is if you add a Velocity external modulator to all group’s Amplifier module, so at least the initial volume can be fine-tuned via velocity and you can still crossfade between layers.

[Author]

Posts