Vember Audio Surge is now open-source

[EvilDragon]

Depends. We want to shift our focus to Shortcircuit for a while. 1.1.2 might be a few months away - tentative "deadline" for the milestone is end of year. But we can always change our mind in either direction regarding that.

[mabian]

Depends. We want to shift our focus to Shortcircuit for a while. 1.1.2 might be a few months away - tentative "deadline" for the milestone is end of year. But we can always change our mind in either direction regarding that.

You may consider a transitory "bug fix only" mode when, after a few days have passed and no new bugs are reported an update is released that only addresses the known issues that are not too "expensive" on the dev side.

Imho this would help tremendously to increase the perception of "Surge care" (pun intended) towards stability. And personally, I'd much appreciate the attitude

- Mario

[baconpaul]

It seems 1.1.1 won't have a long life

- Mario

Ha. Well we are sort of in the mode of bug fixes to surge while we push on the other items like short circuit so 1.1.2 .3 and .4 is kinda the plan now. Probably well sweep up bug fixes and patches every 30-45 days or so and do a point.

I think this one goes all the way back to 1.7 thoigh!

[EvilDragon]

We basically are in bugfix only mode now. But that doesn't mean there will be a release every two weeks.

At any rate, Surge is very stable overall. Please use it. The bug that Chris reported was always there and nobody ever reacted since they never attempted to do the same thing. But it doesn't really make Surge crash. Plenty of people use it in their productions all the time and we really don't get a lot of instability reports very often (when we do, they are always resolved as priority 1 as soon as possible). So I don't know why you're still on the fence.

[baconpaul]

Depends. We want to shift our focus to Shortcircuit for a while. 1.1.2 might be a few months away - tentative "deadline" for the milestone is end of year. But we can always change our mind in either direction regarding that.

Yeah that’s right. A release is pretty well automated now so we will see what’s in the nightly and do them as we need. My guess is 112 happens in sept or Oct with a smallish change log as people bang out a few more edge cases and we tweak in a few more micro features or upgrade an underlying tool or some such

[baconpaul]

Depends. We want to shift our focus to Shortcircuit for a while. 1.1.2 might be a few months away - tentative "deadline" for the milestone is end of year. But we can always change our mind in either direction regarding that.

You may consider a transitory "bug fix only" mode when, after a few days have passed and no new bugs are reported an update is released that only addresses the known issues that are not too "expensive" on the dev side.

Imho this would help tremendously to increase the perception of "Surge care" (pun intended) towards stability. And personally, I'd much appreciate the attitude

- Mario

Would welcome tbis working mode and if you want to join in and squash some of the smaller 11x issues happy to merge and ship them. I have no conceptual problem with there being an xt 1.1.17 if we have that many bugs (we don’t) and that many devs (which we would love!)

[mabian]

We basically are in bugfix only mode now. But that doesn't mean there will be a release every two weeks.

At any rate, Surge is very stable overall. Please use it. The bug that Chris reported was always there and nobody ever reacted since they never attempted to do the same thing. But it doesn't really make Surge crash. Plenty of people use it in their productions all the time and we really don't get a lot of instability reports very often (when we do, they are always resolved as priority 1 as soon as possible). So I don't know why you're still on the fence.

... Because my brain works oddly?

Actually, I'm already using Surge, but - just like hardware modules - I like the idea of having few - but rock solid - tools that I can rely on and with little or no hurdles around creative flow. Same reason why I could never get well with S*nthM*ster 2 - it's a beast but I often see bug reports - and I also experienced some directly in the past - waiting for months for fixes - if any.

This is what could and should make Surge different from many other instruments around - even commercial: fast reaction in addressing issues. Which, for bad brains like mine, is an important choice factor

Honestly, I'm happy that Surge will stay for a while without significant improvements other than bug fixes, I'll have more time to get to know it as it is now.

- Mario

[Andreya_Autumn]

... Because my brain works oddly?

Everyones brain is different, all good there. Mine is weird in its ways too.

I just wanna say, I've been in touch with a few software devs before about bugs, feature requests etc etc... And personally I have *never* seen quickness to adress bugs/issues, and eagerness to discuss development ideas, like I have from the Surge Synth Team.

Now, I recognize a commercial team has to move a little more slowly and want to give all devs in that situation due respect. Many of them have also come through for me over the years. But this has been on a different level tbh.

Not trying to say you should feel different Mabian. It's all good. I just felt like sharing my own experience in that regard.


For full disclosure I also wanna say that I'm happy to consider myself a part of the team nowadays. Helping out with the development in whatever little ways I can with my non-existant programming. This has been an experience I can whole-heartedly recommend! So in case there's anyone more skilled than me who's been on the fence about BaconPaul and EvilDragon's invitations to contribute, I just wanna say go for it!.

[Bojo34]

Reaper 6.66, Windows 10. Surge XT doesn't pass audio. I often have midi and audio on the same track, and Surge "eats" the audio. Mentioned before and confirmed?

[Chris-S]

Confirmed.

[GaryG]

Not a technical response but isn't this the nature of Surge? That fact in can accept audio, process it, use it to excite the String osc etc means it needs to surpress it if it's not being used?

[EvilDragon]

This is AFAIK because Surge now has a proper sidechain input implementation with VST3. Use Audio In oscillator if you need to pass audio through Surge, I suppose?

[Andreya_Autumn]

Is the "eaten" audio on the first pair of channels, or is it a sidechain you want to pass through in parallel?

When you make the additional channels for sidechaining in reaper, Surge will automatically have those checked (with the separate scene A&B outputs). Make sure to uncheck those if you want to pass other audio through on those channels.

And indeed, Surge can pass audio straight through, if you bring up the audio input oscillator.

[Bojo34]

Is the "eaten" audio on the first pair of channels, or is it a sidechain you want to pass through in parallel?

When you make the additional channels for sidechaining in reaper, Surge will automatically have those checked (with the separate scene A&B outputs). Make sure to uncheck those if you want to pass other audio through on those channels.

And indeed, Surge can pass audio straight through, if you bring up the audio input oscillator.

No sidechaining, no additional channels. I simply apply fx to some midi parts and let them stay on the track for convenience's sake. My other vsts work fine with this, no need to set anything, it just works. I'll check out that input oscillator. Thanks.

[baconpaul]

Surge has a sidechain so yes will put the audio on the sidechain input not the main pass through. That’s the desired behavior for a synth with audio input.

The reaper pin diagram will let you re route if you want. But that will probably make the audio in not work.