pottering | 4 months ago | on: VST3 audio plugin format is now MIT
pottering's comments
pottering | 4 months ago | on: VST3 audio plugin format is now MIT
On the other hand, there is not a single DAW that only loads CLAP.
That's the same problem Steinberg faced with VST3 years ago, every host/DAW/plugin supported VST2 (including Cubase), there was no reason for devs to switch to VST3.
Steinberg forced the issue killing the VST2 licenses, any new plugin and host had only access to the VST3 license, even then devs resisted, only recently Steinberg announced future Cubase/Nuendo versions won't support VST2 anymore (plugin devs may hate Steinberg, but they won't simply leave Cubase/Nuendo users without support, they are not to blame for Steinberg's stupidity).
CLAP can't force the issue the same way Steinberg did with VST3, there is no CLAP-only DAW either.
pottering | 1 year ago | on: Twenty Years of FM Synthesis Inside Ableton Live
pottering | 2 years ago | on: Ableton Push 3
pottering | 2 years ago | on: Ableton Push 3
pottering | 2 years ago | on: Get started making music
pottering | 2 years ago | on: Get started making music
pottering | 2 years ago | on: Get started making music
pottering | 3 years ago | on: Ableton Note – A playable iOS app for forming musical ideas
The status bar in the bottom will say if you have "Time Selection" (Start, End, Length) or "Note Selection" (Time, Pitch, Velocity, Probablity).
Arrangement has a similar distinction between selecting time or Clips.
pottering | 5 years ago | on: Ableton Live 11
pottering | 5 years ago | on: Ableton Live 11
Sidechain is not mere grouping/routing like the chain PaulDavis described with ASCII art (different from Sends too), with sidechain the plugin needs the audio from the other track for actual DSP processing, that's why sidechained tracks become a single thread "dependant" signal flow.
That page also mentions Live can use one thread per Chain if needed (for non Live-users, Chains are internal routings inside one single track), so it clearly states Live can use more than one core for one single Track.
Also, plugins like u-HE's use multicore just fine for a single instance, if you disable their own multicore handling (which conflicts with Live's multicore handling).
For Live's own devices, I'm pretty sure multicore works just fine, just tested again with Groups and Sends.
Don't know what problem you have, but it is not simply Live's multicore handling, it is some specific scenario you hit upon.
pottering | 5 years ago | on: Ableton Live 11
pottering | 5 years ago | on: Ableton Live 11
Are you sure? Because since your theory is based on grouping tracks, it is easy to test, by simply grouping all tracks in a Set with 20 or so tracks that use a decent chunk of CPU. Then all their CPU should shift from several cores into one single core/thread (according to your theory). Of course, being easy I already tested this with a Set that used Live's native devices (no CPU usage change), but I can't test with VSTs right now (none installed). Maybe VST hosting has that problem, but processing of audio summing, Live's own devices and M4L doesn't have any major problem with multi-core.
pottering | 6 years ago | on: Ableton Connection Kit (2016)
You mean Max standalone?
Max For Live sure does "give you access to Ableton's UI or API".
pottering | 6 years ago | on: Ableton Connection Kit (2016)
https://cdm.link/2019/10/mutateful-free-live-coding-ableton/
https://github.com/carrierdown/mutateful/
pottering | 6 years ago | on: Ableton Connection Kit (2016)
https://docs.cycling74.com/max8/vignettes/keycommands
https://docs.cycling74.com/max8/vignettes/quickref
https://docs.cycling74.com/max8/vignettes/shortcuts
https://docs.cycling74.com/max7/vignettes/javascriptinmax
https://docs.cycling74.com/max8/vignettes/00_N4M_index
https://docs.cycling74.com/max8/vignettes/lua_in_max_topic
https://docs.cycling74.com/max8/vignettes/gen_overview
https://cycling74.com/tools/max-toolbox
http://www.music.mcgill.ca/~ich/classes/mumt402/MaxMSPExtern...
http://www.interactionlab.biz/v2/wp-content/uploads/2010/09/...
https://steinbergmedia.github.io/vst3_dev_portal/pages/VST+3...
https://steinbergmedia.github.io/vst3_dev_portal/pages/VST+3...
It is the same, there is only the pre-2018 licenses.
(But a few hosts that avoided VST3 due to licensing may implement it now due to this change.)