PHARLIGHT Asio/CPU discussion

I think it shows time needed to process an audio buffer, similar to Ableton Live. This will never match how Task Manager shows things. It might also depend on how Kontakt's multicore option is set up, etc.

 

Then there shouldn't be written CPU. With these three letters anyone understand the processor with hundreds of pins attached to motherboard. But not something theoretical. Kontakt options have Multiprocessor option (I have 8 cores selected), but it isn't multi core option (there is difference), but in any way it works in the way I really don't understand. My CPU is free enough to launch multiple SpaceX super heavy rockets at once, but cannot work properly with such "a simple" library

P.S. Loaded 3 instances of Pharlight, muted Delays + loaded 1 instance of Straylight. All default presets. Kontakt shows 50% CPU usage, Task Manager shows 30% CPU usage.

Just testing But these testing steps gave me some nice ideas for my upcoming album.

 

Multiprocessing option = Multicore option. Semantics in this case. Even supported by Wikipedia, if you will ("there are many variations on this basic theme, and the definition of multiprocessing can vary with context, mostly as a function of how CPUs are defined (multiple cores on one die, multiple dies in one package, multiple packages in one system unit, etc.").

CPU can be measured in a number of ways. Depending on context and requirements, either of them are valid.

 

Okay. I guess many of us here have their own conclusion use or not to use Pharlight/Straylight in line with upgrade or not upgrade hardware. But if both ignoring libraries and upgrading hardware are impossible, just mute some Replika delays in preset.

There are 4 Replika Delays in a preset:
1. Grain layer Effectts
2. Sample Layer Effects
3. Master
4. Send FX

I'm sure the same or similar richness in sounding we can achieve by using Raum Reverb. So for me Pharlight and Straylight are good libraries with their funcionality (grain, layering, filtering), but let FX chain are up to everyone's taste outside of library. IMHO

 

It's more than often the case of poor coding when the ASIO/realtime peak starts going like crazy IF you have half decent machine. Now I'm running 16-core AMD 3950x and my thinking is if I have an empty session open and I open any plugin VSTi the ASIO/cpu should not go on red - Or something is off. THere are certain plugins etc. which have their flaws, but often can be worked around with JBridge, session management, plugin version etc. Usually the workaround is either JBridge or VEP. I just opened up Kontakt and loaded Pharlight - Alchemist patch and ASIO meter jumps to red immediately when play a 3-5 note chord. Asiobuffer size is 64. Try again this time Kontakt JBridged version and... Alchemist patch with all the FX included. ASIO meter jumps on a 4note chord around 37% and fades gently down to 6-12%. CPU usage in Task Manger shows between 6-7%. Turning off the delay FX cuts usage in half. I keep Kontakt (plugin) settings multicore support always OFF. And I open up a new Kontakt instance for the next instrument ---> This let's Cubase/windows allocate to other processors, the usual stuff.

Btw. when I turn off the delay fx in Kontakt/Pharlight the ASIOMETER immediately spikes to 100% and comes down... Same on both delay FX. This kind of things - ASIO spiking - often happened with plugins that had poor coding and "too high cpu usage" and often after a while there came an update and some microcode something was updated and now it's much lower cpu usage. Atleast that has been my experience. Ok, time to dig in Komplete sounds...

 

EvilDragon , you are wise and perfectly know the theory of hardware and a little programming ( ). But are you a composer? For us - composers - the best and fastest way to get to the target is not to upgrade hardware every year.

I decided to upgrade from K12UCE to K13UCE just to have solo strings. Thank God Cremona Quartet is without FX and Sequencer pages

 

And where exactly did I suggest hardware should be upgraded every year?

One more jab at my person and you will be getting an infraction. Don't hide behind emoticons, it's pretty obvious you're not joking here.

 

This has been a very interesting thread to read. Thanks all for the insights on using Pharlight and Straylight. My DAW, custom built, has Core i7 5820K, 32GB DDR4, program drive is SSD, samples drive is HDD. (Was planning a grounds up rebuild this year, but global semiconductor supply issues have thrown a wrinkle into those plans), DAW is Bitwig, just upgraded Komplete to 13 Ultimate.

Hyperthreading disabled, 6 cores run at 3.3Ghz. I tried O/C'ing, helped a bit, but not enough to keep it there, so went back to base freq. I tried moving Pharlight and Straylight directories to faster SSD, that didn't help much. I've ended up settling on three things: temporarily increasing buffers to 512 (normally set at 256; SR is 48Khz), slightly decrease voice limit in Grain layer (eg, if 8, decrease to 6), and deactivate Delays in FX.

 

Just for an info.
After updating Studio One to the latest version 5.4, there has been a big improvement regarding NI Pharlight, Straylight and Etheral Earth. No more issues with CPU inside Kontakt (version 6.5.1). No more noise, dropout, etc. I have tested not all patches but most CPU intensive and only 1 patch reached 100% of CPU for a half second (Pharlight: Vox Plains), but without any noise. I'm still converting each instrument to audio like before, but...finally they are totally usable and playable. My PC is: CPU i7-7700HQ 2.8GHz and 16GB of RAM

 

For info.
I may run six instances of Pharlight's Vox Plain preset each using 4 voices in Maschine. My miniPC ASRock DeskMini X300 has AMD APU Zen 7 5700G (8C/16T, TDP 65W) running at 4.1 GHz, 64 GB RAM, Win10. It is small size computer (volume of six cans of beer) that can be easily transported. Sort of compromise between notebook and big PC. I have two 1 TB SSDs and space for two more 2.5" SATA discs if needed.

I am to install better cooler instead of the stock AMD's one, so I might be able to reach even seven instances as seven works fine for a while now, till CPU gets too hot....

I am pretty happy with the setup and it cost only a bit over 1000 EUR. I may write more details, if someone interested.

 

The real problem is a simple lack of transparency from Native Instruments.

If Native Instruments simply posted that to run efficiently Pharlight needs multiple cores running at 4.0+ this entire issue would have been avoided.

If this had been done all the frustration and confusion over this issue would have never happened.

I understand that such honesty might have cut into sales, but it would have been the ethical thing to do.

 

Well, I was able to run one instance of Pharlight on 10 years old i7 notebook 2.1 GHz.... But, just one note, one patch and with buffer 2048....
So, 4 GHz is not a must.
I agree, that techspec should be more precise. Maybe minimum requirements and recomended configuration. Or at least warning, that it is CPU very hungry and buyers are wellcome to test demo before purchase.....

EDIT. Actually, there is a note, that it requires fast CPU, at least at techspec for AshLight plugin.

 

Mac M1 chip-
Does anybody else have experience using the new M1 chip with Pharlight?

 

Have you read the previous posts in this thread? To run the more demanding Pharlight presets you need multi chores running consistently at a base of 4.0 +

Your 2011 Macbook does that?
Do most people’s machines handle that?

 

AMD 65W Zen 7 5700G can handle it. And it is not top CPU, by far. I assembled PC with this CPU, 64GB RAM and 2 TB SSD for about 1000 EUR.