pottering's comments

pottering | 4 months ago | on: VST3 audio plugin format is now MIT

AU support grew because Logic Pro only loads AU, Logic userbase is a attractive enough market for plugin devs.

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 | 2 years ago | on: Get started making music

It is not "only workable using ableton", it teaches generic music theory (just the basics), which is usable even without a computer.

pottering | 3 years ago | on: Ableton Note – A playable iOS app for forming musical ideas

MIDI Stretch stretches all linked envelopes, not only the three MPE controllers, if you select TIME not notes, as Live differentiates those types of selection.

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

Oh please, all replies to you here had facts, or at worst fair, informed assumptions.

pottering | 5 years ago | on: Ableton Live 11

I think you may be misreading that FAQ page, it mentions sidechain as the reason for using one thread for "dependant" tracks.

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

C'mon, anyone can easily find dozens of videos that prove otherwise. Also, the Push API is open, anyone can program python remote scripts to access it, that's how apps like Touchable work, completely false you have to buy a Push, don't need hardware nor M4L. Even if you don't know Python you can use ClyphX. And I talk about Live 10.

pottering | 5 years ago | on: Ableton Live 11

"Yes this is what's happening in Ableton"

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)

page 1