When changing the snapshot with arrows in the main (upper, standard) portion while key(s) on MIDI keyboard are pressed, the right side of the instrument (sample/arp) stops working. I found some posts on the net about this problem but none were answered.

It is mainly evident on "pulses". After that the sample/arp of any preset does not work again until you reload Ashlight.

Can someone confirm? Here is the video:

Latest Kontakt on Win10 etc.

 

I only found that - does it help?

If by "another zone" you mean loading another instrument in the multi, then that is normal, and is not scripting related. Whenever you load a new instrument, audio engine is reinitialized, this is just how Kontakt is. You are not supposed to load new NKIs while others are already playing.

Your best way of doing that would be setting other instruments to a different MIDI channel then, making sure that the instrument with the arp receives over its own MIDI channel. You should have no interruptions www.native-instruments.com/forum/threads/arp-stops.323418/

 

@BEAT16, I don't know what you mean. Just one instance of Ashlight. Here is the thing simplified:

1. Load Ashlight

2. Select snapshot Pulses -> Bosporus
3. Press the right arrow to go to the next snapshot while holding a MIDI note

4. Press the left arrow to go to Bosporus again

5. The "Sample" on the right side of the instrument does not play anymore (but the "Grain" part on the left does)

6. The whole instrument is the affected the same way until Ashlight is reloaded

 

Last edited: Sep 13, 2021

Looks like a bug, have you updated yet?

 

Yes, it seems so. Everything is up-to-date (I even re-downloaded the Ashlight ISO and reinstalled it today to check).

The workaround is to use the Ashlight's "preset manager" and not the snapshots.

BTW, Straylight and Pharlight work OK.. even when changing snapshots

 

If you are a customer, write an e-mail and report the error to the company.

 

Yeah, you know how that works, lol. It's already on NI's support forum for quite some time. Mentioned by two guys. That's why I checked.

In fact, I did not buy Ashlight yet. ;) But I wanted to.. It's the last day to get it for 99€, if you own Stray/Pharlight..

..now I will rethink before giving them that money.

 

Last edited: Sep 13, 2021

Yes i understand. Support desert - once again saved money. I would look for alternatives.

Top 4 Granular VST Plugins & Granular Synthesis Explained

THE MANGLE - Granular synth/sampler plugin
http://sound-guru.com/software/mangle/

 

Just checked the NI Kontakt forum. Seems that the issue I was talking about was solved. Ashlight updated to 1.0.1

..credit where credit's due!

Do these guys read this or theirs forum, lol. sometimes I have this strange feeling..

 

I get that there may be a bug too, but your initial problem was strange generally to me.
Having have used MIDI since 2 years after it arrived, I would never imagine trying to change patches whilst an arp is playing and expect it to work.
The initial MIDI note that triggered it will often not carry over, if you see what I mean.

 

I learned it around the same time and you are spot on for the greater part because of the inherent note on/note off in all MIDI. It also opens a door if not timed perfectly to MIDI note loops (infinite annoying sustain) because it received no note-off message and often requires a purge/reload /stop if it is really bad. It can be done but takes a little manual checking/editing so the note off message is received before the patch change message and the trigger as suggested would have to be restarted with the program change. Seamless? Depends on the sound of the trigger if constant or dynamic.

 

Hey guys, new here, hi everyone
So i bought Ashlight yesterday and I have this problem. I just looked which version I have and it is 1.0.0.
Which is strange since I bought it yesterday.
Should I just reinstall it in Native Access for 1.0.1??
Thank you in advance

 

Yes please use the Native Access and UPDATE PRODUCTS
You can always find all available updates on a single screen.
With the one-click update process, you can perform updates for all of your installed products quickly and easily

 

Hi @ARKKA
As the Original Poster, I can tell you that the bug is solved in version 1.0.1

At the time I was testing it, I downloaded the DEMO from NA website and when bought it, just inserted the serial. It was still v.1.0.0. Seems to me, they forgot to update it on that server.. (maybe that's your problem).

So - uninstall it (maybe with Revo), get rid of all the files and download and install with Native Access.

Good luck!