Vember Audio Surge is now open-source

[BBFG#]

Only Windows Audio and Direct sound available in these standalones.

[Surgo]

No ASIO on the standalones...
Oh well.

Yes, you'll need to build it yourself if you want ASIO due to how the ASIO licensing works. Nothing we can do about that. See https://github.com/surge-synthesizer/su ... t-for-asio

[martiu]

the mistake was intentional

[baconpaul]

No ASIO on the standalones...
Oh well.

ASIO does not have a GPL3 compatible license.

https://github.com/surge-synthesizer/surge/issues/6283 Explains the options if you wish to personally accept the SDK license and build a non distributable binary for personal use.

If you are a steinberg customer who uses their forum I have a thread here https://forums.steinberg.net/t/asio-lic ... are/696630 but they have never responded to my request for clarification or a fix.

[baconpaul]

FYI we released 1.2.2 on Monday (1.2.1 was out Sunday night with one irritating error - oops!) which fixes a couple of problems which were somewhat irritating to linux users and people with odd block sizes in their daw. Changelog and binaries in the normal place. If you are running 1.2.0, 1.2.2 is a recommended point upgrade.

[Nug Wrangler]

thanks

[Iu Gob]

FYI we released 1.2.2 on Monday (1.2.1 was out Sunday night with one irritating error - oops!) which fixes a couple of problems which were somewhat irritating to linux users and people with odd block sizes in their daw. Changelog and binaries in the normal place. If you are running 1.2.0, 1.2.2 is a recommended point upgrade.

Thanks a lot!!

[Milkman]

If I missed this anywhere in this thread, apologies: has anyone used an Arturia Microfreak to play Surge, specifically using Surge's poly AT and/or MPE features?

Just bought the microfreak, and I find using it as a poly AT midi controller works but only in some synths. Poly AT doesnt seem to work in Surge, no matter how I configure it. Poly AT is working in Pigments and the Imagine synth, so far, and my DAW sees and reads/writes the poly AT coming from the freak so it isnt a DAW issue.

I have an email chain with Rhizomatic software right now because Plasmonic also wont accept the poly AT coming from the microfreak. Looks like Plasmonic's presets were coded in a way to try to make them compatible with MPE or poly AT, but for some reason the freak doesnt like it.

Anyone have any experience with this gear connected to Surge? Thanks!

[EvilDragon]

Poly AT messages definitely work with Surge, however you cannot be in MPE mode for them to work (channel aftertouch takes over then, since it's the MPE spec).

[ThomasHelzle]

Yeah, that is a total bummer.
The MPE spec should have allowed both kinds of Pressure/AT.

Now we have a very strange landscape that is even more confusing for the user than before, where you can't use many of the plethora of MPE capable synths and presets with the growing number of Poly-AT capable devices in a straightforward fashion.
Switching modes and changing presets can be done of course, but why?

Since MPE is about per-note modulation and Poly AT is also per note, no sane human will follow if you try to explain that no, for MPE you use mono/channel-pressure.
You then explain for half an hour about channels and why in a certain way it made sense for that committee to only use channel-based information...
Which leaves you with those stares of total WTF, how disconnected from reality can you be?
I had that discussion several times now.

More flexible devs allow for "whatever pressure", but yeah, the specs are the specs, right?

[EvilDragon]

Well there are some slight differences between poly AT and MPE. MPE is per channel but poly AT is per key. With MPE you can theoretically get the same key playing with different expression, with poly AT you cannot. So they are not exactly fully interchangeable.

It is very much true and it was apparent from the get go that MPE is just a hack. Proper implementation of this sort of multiple per note expression controllers that is not channel-bound can be found only in MIDI 2.0 as it stands.

[ThomasHelzle]

Well, since PolyAT is also per channel, I think it is possible to use both kinds of pressure in a way that does not create issues, even if you play the same key twice (which is a fringe-case in Midi 1.0 no matter what you use).
But allowing for both pressures definitely makes the whole thing more transparent for the user.

Bitwig adapted that in it's internal pressure expression.

But yeah, I'm sure in another 20 or 40 years we'll all happily use Midi 2.0...

[Tj Shredder]

Its simply the responsibility of an MPE capable synth to interpret both… An MPE controller would send channel pressure, a poly aftertouch keyboard sends that on a single channel. Where would be the problem? Its not against any specs…
A smart sound designer would modulate a given parameter with both, then it would work with MPE as well as with PA…

[EvilDragon]

A smart sound designer would modulate a given parameter with both, then it would work with MPE as well as with PA…

This too.

[ThomasHelzle]

Its simply the responsibility of an MPE capable synth to interpret both… An MPE controller would send channel pressure, a poly aftertouch keyboard sends that on a single channel. Where would be the problem? Its not against any specs…
A smart sound designer would modulate a given parameter with both, then it would work with MPE as well as with PA…

Exactly.
It's about making expressive playing as painless and approachable as possible, not about following specs blindly...