Vember Audio Surge is now open-source

[baconpaul]

The SurgeEffectsBank VST3 in the 64bit 1.7.0 windows installer appears to be 32bit instead of 64bit. Is anyone else getting the same issue?

Yeah sorry about that. I fixed this today and you can grab the nightly if you want the SFXB right now on windows (Https://surge-synthesizer.github.io/nightly). We will probably do a 1.7.1 release late this weekend or early next week to sweep in some of these environmental things folks found (and thanks for all the reports). Sorry for the error - it’s a lot of platforms to support and test and we just had one flag set wrong in our build pipeline.

[baconpaul]

Bitmap support is still inside the codebase but commented out. It doesn't allow continuously variable zoom levels with any degree of quality, but for 1.7.2 it will be reinstated and things will be limited to fixed zoom levels then (i.e. 100%, 150%, 200%, 300%, 400%, that's it). Of course that would require separate assets for each zoom level.

That's disappointing. I find 100% too small, but 150% is too big.

Evil meant e.g not i.e. When we had PNG support if I recall we did 100, 125, 150 , 200, 250, 300, 400 (so basically 100 - 200 with HDPI support) but when we restore the feature skin authors will get to choose which assets to provide. If a skin only has 100 then zoom will be constrained. (If you want to see what that is like, you can go download Surge 1.6.0 beta 6 I think, where I had zoom working but no scalable assets. I don’t recommend it!)

[FrogsInPants]

That's disappointing. I find 100% too small, but 150% is too big.

Evil meant e.g not i.e. When we had PNG support if I recall we did 100, 125, 150 , 200, 250, 300, 400 (so basically 100 - 200 with HDPI support) but when we restore the feature skin authors will get to choose which assets to provide. If a skin only has 100 then zoom will be constrained. (If you want to see what that is like, you can go download Surge 1.6.0 beta 6 I think, where I had zoom working but no scalable assets. I don’t recommend it!)

Ah, that's not as bad. Continuous zoom levels are better still, as far as I'm concerned. Will that still be available if the skin's assets are all vector graphics?

[baconpaul]

Ah, that's not as bad. Continuous zoom levels are better still, as far as I'm concerned. Will that still be available if the skin's assets are all vector graphics?

 

Yup that’s why we did the work to go to svg at 160beta9. Bitmap continuous zoom was too unreliable. The problem is our svg renderer is incomplete so there’s some tricks you can’t do which designers want ... always a trade off

[planetearth]

Open source is never discontinued, though. Anyone can pick it up at any time.

It's anyone's guess what might happen if, say, Synth1 gets open sourced, but I'm quite sure Surge Synth Team would take it on, add the microtuning and MPE capability, update the GUI, add VST3 so that things can be more cross-platform, and so on. Just like we took Dexed and added microtuning and rudimentary MPE to it.

Not to derail this thread, but was there a fork for Dexed? Many of us have been waiting over a year for an update (and some bug fixes) -- or even a version 1.0. I was working with the dev on some issues before he disappeared, and he hasn't responded to my emails asking if he's okay.

If there's a fork, maybe someone could mention it in the Dexed thread here? I didn't even know about the MPE support, and I've been following the thread for a few years.

Thanks.

Steve

[beltrom]

If there's a fork, maybe someone could mention it in the Dexed thread here? I didn't even know about the MPE support, and I've been following the thread for a few years.

Interesting news, mentioned it in the Dexed thread:

https://surge-synth-team.org/dexed/

[andrewbrewer]

The SurgeEffectsBank VST3 in the 64bit 1.7.0 windows installer appears to be 32bit instead of 64bit. Is anyone else getting the same issue?

Yeah sorry about that. I fixed this today and you can grab the nightly if you want the SFXB right now on windows (Https://surge-synthesizer.github.io/nightly). We will probably do a 1.7.1 release late this weekend or early next week to sweep in some of these environmental things folks found (and thanks for all the reports). Sorry for the error - it’s a lot of platforms to support and test and we just had one flag set wrong in our build pipeline.

[planetearth]

If there's a fork, maybe someone could mention it in the Dexed thread here? I didn't even know about the MPE support, and I've been following the thread for a few years.

Interesting news, mentioned it in the Dexed thread:

https://surge-synth-team.org/dexed/

Maybe I'm misunderstanding what you mean by "mentioned it in the Dexed thread", but there has been no mention of the fork this year, other than the post you just put in the Dexed thread on KVR just two minutes before you posted this reply to me. I've been trying to help out on that thread for the past several months, but there have been no comments from anyone developing the original plug-in or any forks.

Still, I appreciate you mentioning it and pointing to the file on github.

Steve

[FrogsInPants]

Ah, that's not as bad. Continuous zoom levels are better still, as far as I'm concerned. Will that still be available if the skin's assets are all vector graphics?

 

Yup that’s why we did the work to go to svg at 160beta9. Bitmap continuous zoom was too unreliable. The problem is our svg renderer is incomplete so there’s some tricks you can’t do which designers want ... always a trade off

Gotcha. This is just swell, then. I misunderstood him to mean that it would be limited to fixed zoom levels period, rather than only when bitmap assets are used.

[beltrom]

Maybe I'm misunderstanding what you mean by "mentioned it in the Dexed thread", but there has been no mention of the fork this year, other than the post you just put in the Dexed thread on KVR just two minutes before you posted this reply to me. I've been trying to help out on that thread for the past several months, but there have been no comments from anyone developing the original plug-in or any forks.

Still, I appreciate you mentioning it and pointing to the file on github.

Steve

I meant precisely the new post, this was news to me as well. But did a google and found the page.

[FotoxBr]

I did not know about the existence of Surge until a few days ago when 1.7.0 was mentioned on several news sites. I downloaded and installed on my iMac mojave OS. Everything looks and sounds very nice. I am impressed. One problem though. Only the AU synth plugin shows up in my Live 10. Not the VST3 although it is present in my plugin directory. The FX VST3 does show up.
Someone else experience this too ?

[baconpaul]

I did not know about the existence of Surge until a few days ago when 1.7.0 was mentioned on several news sites. I downloaded and installed on my iMac mojave OS. Everything looks and sounds very nice. I am impressed. One problem though. Only the AU synth plugin shows up in my Live 10. Not the VST3 although it is present in my plugin directory. The FX VST3 does show up.
Someone else experience this too ?

 

Yeah sorrry this will be fixed in 171 in the next few day and is fixed in the nightly now. Mac live did a check no other daw did and we didn’t pass that check. We found it after the release

[baconpaul]

Dexed: we did a fork and added micro tuning support and some mpe. That fork has been merged back into the main branch and we are now both on par with each other. I’m not sure when the plan is for a next formal release but like all our other synths and products we make nightly builds of our betas available, but the formal release will come from pascal who merged our changes back. We don’t want to maintain a divergent fork of such an important synth!

What is “the dexed thread”? (Edit: found it!)

[Dandruff]

When reappearing from being hidden, mouse cursor is restored to the position from which the drag was started

This is not a nice change. Cursor should be restored at current drag position but not outside of fader width (when cursor is hidden while dragging). Say I drag Cutoff fader fully to the right (but the drag itself even goes behond), the mouse cursor should be restored at the right edge of the Cutoff fader when mouse button got release. Currently it jumps back to the left - why? Looks and feels weird.

[EvilDragon]

Bitmap support is still inside the codebase but commented out. It doesn't allow continuously variable zoom levels with any degree of quality, but for 1.7.2 it will be reinstated and things will be limited to fixed zoom levels then (i.e. 100%, 150%, 200%, 300%, 400%, that's it). Of course that would require separate assets for each zoom level.

That's disappointing. I find 100% too small, but 150% is too big.

There has to be some boundary somewhere, plus it all depends on how the GUI is designed at 100%, too.

At any rate - it's open source, you can make it work however you want for yourself

EDIT: Also yeah, I was only talking about the case when bitmap assets were used in a skin, not SVG!