[hazza]

in reply to: Disk streaming issues #42874

Hi Sebastian

Thanks for the reply. After bashing my head against a wall for a week I eventually made a breakthrough this afternoon . I went over all of the multiprocessor settings and when I changed Kontakt 4 from 16 cores to off everything suddenly got snappier again and I was up to150 voices. I have to assume K4 and K5 were somehow fighting each other.

Yes all VE Pro plugins decoupled (which is why I was confused about the disconnect time), Logic is 64-bit.

Interested in your multiprocessing suggestions, I currently have Logic @ 16 threads, VEP @ 16 threads, Kontakt @ multiprocessor support off, KMS off. I queried these settings with NI this morning actually, interestingly they suggested that I switch KMS on and leave the preload buffer at factory setting. How do these settings compare with your system? So many variables!

Cheers
Harry

[hazza]

in reply to: Disk streaming issues #42872

Oh yeah, forgot to say:
– VE Pro takes ages (10-15 secs) to connect disconnect from my 5 LASS Kontakt instances even though they are disconnected
– I get “out of memory” errors occasionally when I try to open the VE Pro plugin, even though I have 4GB of free RAM!

Could Logic of VE Pro be somehow messing things up? I’m confused

[hazza]

in reply to: Disk streaming issues #42871

Thanks for the suggestions Soulofsound. My latency is 256kb, x2 for VE Pro. I have been experimenting with various settings. In Kontakt standalone I can get the voice count higher (up to about 100) before the disk meter starts to ramp up. But that only equates to about 4MB/sec, surely it shouldn’t be breaking a sweat at that rate? While hosted in VE Pro or Logic at 60kb buffer I get about 80 voices before drop-outs, at 24kb it’s more like 48 voices. The disk meter overloads seem to correspond with CPU rises, as the notes are held the screen refresh on Activity Monitor freezes, and after each cut-out as it recovers I can see the VE Pro CPU usage has jumped up to 600%. But the cores all hover around 10-25% each.

I can’t get my head around what’s going on here. I would have thought my machine was capable of more than this, but my old template + full LASS (still well within RAM) is just falling apart now. What would be considered a reasonable voice count from a 450MB/sec SSD over SATA-II? Any idea why these disk spikes are happening?

Many thanks for your help guys.

Harry

[hazza]

in reply to: LASS stuck notes #38807

Hi Sebastian – email sent.

Not sure what you mean, yes of course this behaviour was happening without the mute/unmute test, with everything playing there are stuck / wrong notes all over the place . But I’m sure it was working fine (with this level of arrangement) before now, I cannot think of anything that has changed though. I have only recently started using LASS as a full orchestra, obviously keen to get this working!

Many thanks
Harry

[hazza]

in reply to: LASS stuck notes #38805

And just discovered that deleting all the CC01 data results in everything playing correctly (and boringly . So looks like some kind of MIDI data overload issue?

[hazza]

in reply to: LASS stuck notes #38804

Nope Auto Arranger definitely off, no pedal.

I am finding I can help the situation to a certain degree by shifting unison lines away from each other, so that FC/A/B/C aren’t all moving at the same time. But the offset needs to be quite big (eg semi-quaver), and then as soon as I unmute a couple more tracks some of the desks get stuck again.

[hazza]

in reply to: LASS stuck notes #38802

Thanks Andrew – CPU is running at 10-20%, HD isn’t registering at all. The voice count when problems start is around 30-40. Nothing else in the arrangement running.

VE Pro is out of the equation now so just Logic hosting Kontakt AU.

Cheers
Harry

[Author]

Posts