Loerpert
Senior Member
Perhaps this CPU stuff from Nando is a sophisticated anti-gas technique! In which case - bravo! Or maybe he has an AMD processor...
What's wrong with an AMD processor?
Perhaps this CPU stuff from Nando is a sophisticated anti-gas technique! In which case - bravo! Or maybe he has an AMD processor...
Nothing... I officially retract that joke. AMD-ians please accept my (mostly) sincere apology.What's wrong with an AMD processor?
Gooood.. Good..Nothing... I officially retract that joke. AMD-ians please accept my (mostly) sincere apology.
Make sure you compare like to like, Pacific has by default 2 mics enabled, which means double the cpu load in kontakt. I compared Pacific to SCS violins and it showed a bit more then double the cpu and voices hit of Pacific. enabling a second mic in SCS matched the performance.In my AMD CPU, this patch consumes as much as 4 LASS patches. Yes it is a Kontakt issue, but maybe there was a workaround available to reduce this. If legato were added to this patch, it would basically consume an entire core.
Yes, I spent some time last night comparing to various other libraries I have, such as HZS and SSS. The delicacy at very, very low dynamics is incredible.The sord violins especially at the lower dynamic levels are stunning. Really terrific.
It is when someone has an issue. See every Heavyocity Ascend thread on VI-C (and deservedly so as it can be brutal on CPU).In any case, CPU usage is an important aspect of libraries which I feel isn't discussed that often on this forum
Oof, some of those (beautiful) Spitfire Audio libraries like Kepler sure can hit hard.It is when someone has an issue. See every Heavyocity Ascend thread on VI-C (and deservedly so as it can be brutal on CPU).
I was enjoying this and it just stopped!First 30-60 minutes with the freebie.
Thought I would share, if it sounds bad, it's probably not the library at fault (still a noobie)
View attachment performances samples 1.mp3
Click on the home page. That's where I found it.Is it no longer available?!
Or CinestringsIt is when someone has an issue. See every Heavyocity Ascend thread on VI-C (and deservedly so as it can be brutal on CPU).
I like the celli shorts but found I had to dial back on the delay to make them more responsive. I mentioned this to Jasper. At full default, they sound like the attack portion is slightly ramped up to (almost like a very sharp incline x fade). But everyone has different preferences and ideas of what they think short strings should sound like. I prefer a lot of bow-on-string attacks for shorts.Yes, I spent some time last night comparing to various other libraries I have, such as HZS and SSS. The delicacy at very, very low dynamics is incredible.
Funny enough, I don't really like the shorts. But the sustains could push me over the edge.
For me, one LASS patch consumes 0.4% CPU playing anything. One mic of SCS playing very quickly (with the "Legato (Fast)" patch) consumes 1.9% CPU (one mic) or 2.5% (2 mics), and Pacific sord sustain playing very quickly consumes 1.5% CPU (close mic only), or 2.8% (both mics). IIUC this is coherent with what you said... but just contemplate how many LASS patches we can fit in that! I have always considered SCS to be one of my least performant libraries, would hate to see people considering that normal.Make sure you compare like to like, Pacific has by default 2 mics enabled, which means double the cpu load in kontakt. I compared Pacific to SCS violins and it showed a bit more then double the cpu and voices hit of Pacific. enabling a second mic in SCS matched the performance.
I don't own LASS so can't comment on that.For me, one LASS patch consumes 0.4% CPU playing anything. One mic of SCS playing very quickly (with the "Legato (Fast)" patch) consumes 1.9% CPU (one mic) or 2.5% (2 mics), and Pacific sord sustain playing very quickly consumes 1.5% CPU (close mic only), or 2.8% (both mics). IIUC this is coherent with what you said... but just contemplate how many LASS patches we can fit in that! I have always considered SCS to be one of my least performant libraries, would hate to see people considering that normal.
guess you have a point but not sure if noise has anything to do with QC, for a library to have less noise i think it would need to be processed with FX then you may loose quality and realism, or body, then you may get a sterile sound or clinical sound,I'm kind of tired of people saying "not for purists" as a way of quashing criticism though. Like ok, we've all heard the tagline, let's talk substance now. It sounds fantastic, but the QC can be better, and that's something that can and should be discussed
To remove hiss, yes. To remove all the clicks and bangs and scrapes, not so much. And you can just get a second takeguess you have a point but not sure if noise has anything to do with QC, for a library to have less noise i think it would need to be processed with FX then you may loose quality and realism, or body, then you may get a sterile sound or clinical sound,
Yes there is quite a bit of noise, its the same as Con Moto, when listening to the loop,To remove hiss, yes. To remove all the clicks and bangs and scrapes, not so much. And you can just get a second take
Me too, with the sole exception being the 'sin' of having a noise that is very distinctive and keeps repeating so that it is noticable and annoying. But noise from the players in general I actually like; makes it sound more like a real recording. Cory recently did a video on adding player noise to clean samples to make them sound more authentic.Pacific on the other hand ... ohh the sound, it just flows out of the box. I love the space. I love the dynamics. I love the elegant and lyrical squeakiness of the chairs on the ppppp layers, and I especially love the performances captured and am willing to forgive all manor of other technical sins for it.