Wirth regards to struggling to max out my CPU, I was referring to an external interface, but the Apple Silicon note, and that Ableton article refer to either.
If you can run at 96KHz a 24 stems session with 40/60 plugins loaded, and with a latency under 9ms and you have plenty of disk space, just do it.
My mac just cannot afford this, also the sound card I/Oās will be cut in half at frequencies greater than 48KHz:
64 channels @32kHz, 44.1kHz, 48kHz
32 channels @64kHz, 88.2kHz, 96kHz
16 channels @128kHz, 176.4kHz, 192kHz
any real reason running 96k vs 48k? I canāt max out my M1 Ultra no matter what I do simultaneously like having docker apps running alongside with obs and whatnot, I probably will be able to do 96k with ease but should I? does working in 96k mean I donāt need to do oversampling on plugins like Pro C2 or L2?
on that note, any real reason recording .aif (set by default) vs .wav?
You may get better latency running at 96k. A lot of interfaces I have used have lower latency at higher quality. I wonder if downsampling to 48k or 44.1k slows it up a little bit and adds latency?
I already have 3.67ms RTL with 64 samples / 48k, donāt think I need better then that
but if that means that I donāt need to turn on oversampling for every plugin then maybe itās worth itā¦
Shoot for negative numbers! You might just go back to the future.
will try!
āTo calculate milliseconds from samples, simply divide the number of samples by the sample rate . For example, 512 samples/44.1 kHz = 11.7 ms.ā
Thus, higher samplerate = less time needed to calculate the 512 samples = lower latency buffer
Couldnāt have said it better myself.
Fascinating! Thanks.
ok this is really cool thing I did not know about, you know how you preview a .adg
file and you have this little clip playing for drum rack or instrument rack or whatever, but thereās no midi clip so when you drag it creates a new midi channel but without the preview thing?
well, apparently these previews are pre-recorded wav files and they all saved in /Library/Caches/Ableton/Cache/Decoding
(or the equivalent windows path I assume), if you have any packs installed then you probably have lots of these preview files in there, loops, instruments, lots of hq samples you can browse, throw into the granulator or simpler and slice 'em upā¦
Stable ?= drop outs with how many tracks running ?
Need to test again for a track number count before I get drop outs.
The test I did was just to see the CPU usage amount difference by switching 44.1Khz to 96Khz.
Stable was referred to the variability of the CPU usage value when using one setting or another.
EG: In certain setup cases I had firm 10%, in other settings it wasnāt firm at 10% but varied quickly between 10% and 14%.
Update to my own post. The APC40 MKII seems to be out of stock everywhere in the US. Some dealers show a backorder date of May, but that could be fake news. Could it mean a MKIII is coming? I just want one, MKII or MKIII. All the used ones Iāve found are disgustingly used, so I was hoping for a fresh one.
This is possible but I know they are also having supply issues. Iāve had parts for mine backordered for over a year now.
I figured that might be the case. Itās a way less fun scenario. Iām only hopeful because they released new versions of their other APC controllers.
To be honest a MK3 would be great and I do hope one is coming soon!
Just out of curiosity, what would you like as improvements to a mk3?
I like the way mk2 works generally but some things Iād like in a mk3 might be:
- detent on the faders at 0db so itās not so easy to move them above 0 if you donāt want to (instead of software workarounds to set the top of travel to 0)
- detent in the middle of the crossfader
- user mappable configurable overlays and knobs while using the Ableton control script. Currently limited to 8 I believe. Imagine hitting that button and having use of any knob you want!
- user mappable buttons while using Ableton control script (while in User mode)
- more buttons for more than 5 clips per column
- RGB LED rings to color code with your macros or tracks
Edit: clarify user mappable buttons