Can you show us your hardware specs, please?
Same goes for what drive you installed your programs and plugins onto.
From where did you try to import your sample? An HDD? SSD? External HDD/SSD?
What process is causing a full load on your CPU?
Also if one or more of your drives have been running for a few years already it would be cool to check their health just in case. (I highly doubt that it is a factor in this case but, just make sure.)
Here is a video showcasing how it happends (and the specs of my pc)
https://www.youtube.com/watch?v=5pQHwj8aeZU&feature=youtu.be
I am getting the samples in the video from another hard drive, than the one Nimble Kick is on.
After some testing it seems like having the samples on the same hard drive as nimble kick dont help
It seems like when using big samples the CPU goes crazy.
My HDD's health seems fine
I have 16 GB DDR3 Memory and my speed is 2133 MHz, I use 4 slots, my form factor is DIMM and my hardware reserve is 122 MB.
If thise is not the information your looking for, then i dont know what you mean about my RAM blocks
My concern was the health of those blocks.
Same goes for what process is the culprit of using up your CPU, since you state that its outside FL Studio. You should be able to see that in the task manager, no?
I only somewhat experience these issues you're having by loading large ass sample files longer than 50 (ish) seconds, but my system never freaked out like that, nothing outside FL Studio is throttled to the max, etc, it just freeze for a few seconds and then it works fine afterwards, I can run a session for hours with no issue.
The samples you've shared so far worked fine here, not sure what else to ask. :/
Seems like the stretch tool, pith tools, loading samples in and playing samples are what causes CPU problems mostly.
Also my FL crashed after using a 4 sec sample for 15 min. It happend when i pitched the sample inside Nimble Kick. There were only short term 100% CPU problem while using that sample, in those 15 min.
Yes, one thing that's important to note is that Nimble Kick is not made for samples that long. Consider using shorter samples instead (for example, each beat in a regular 150bpm hardstyle track is 400ms, so if you want your kick to span at most 2 beats you'd make samples that are roughly 800ms long.)
