KVR Audio

EvilDragon · Post by **EvilDragon** » Tue Dec 24, 2019 7:06 am

No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.

brok landers · Post by **brok landers** » Tue Dec 24, 2019 10:29 am

still wish for the phase retriggering/phase start editing per osc waveform... pretty please... to me that's all that's badly missing.

EvilDragon · Post by **EvilDragon** » Tue Dec 24, 2019 10:57 am

That one is more likely to happen in Surge++ which is a heavy WIP. Don't expect it to happen in the current 1.6.x codebase. It all depends on baconpaul and his efforts for S++, so as a liberal assumption, I'd say late 2020 is when you might expect something like osc phase happening. But again, it all depends on baconpaul.

brok landers · Post by **brok landers** » Tue Dec 24, 2019 11:13 pm

EvilDragon wrote: Tue Dec 24, 2019 10:57 am That one is more likely to happen in Surge++ which is a heavy WIP. Don't expect it to happen in the current 1.6.x codebase. It all depends on baconpaul and his efforts for S++, so as a liberal assumption, I'd say late 2020 is when you might expect something like osc phase happening. But again, it all depends on baconpaul.

ah ok... well... i'll have to wait a little longer then i guess...

merry christmas y'all...

Auplant · Post by **Auplant** » Fri Dec 27, 2019 10:43 pm

Can anyone tell me what the "FX1 Return" and "FX2 Return" sliders are for? There isn't really anything written in the manual about them.

edit-
They seem to control the output of FX1/FX2 sends

Auplant · Post by **Auplant** » Fri Dec 27, 2019 10:49 pm

I'm finding it difficult to be imaginative with this synth in terms of making some textured effect sounds, if anyone has some some presets that I can play around with...feel free to upload

Halonmusic · Post by **Halonmusic** » Mon Dec 30, 2019 9:06 pm

EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.

Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really

baconpaul · Post by **baconpaul** » Sat Jan 04, 2020 10:18 pm

Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really

https://github.com/surge-synthesizer/surge/issues/190 There’s the github issue. it has some information about how to debug it. Oh and I think that layzer uses the 1.5 vintage still, which works in ext, and the 1.6 vintage does not, but I’m not 100% sure on that.

On windows daw issues and windows behaviors, it’s really hard for me to debug them. I have a VM not a proper machine, I haven’t done windows dev in about a decade, and my environment is really tailored for the Unix-like environments. I know windows has come a long way with WSL and so on but I just don’t have any of that working. So certainly my least easy to debug platform.

Of all the things that would be a lovely new years gift, an experienced windows C++ developer deciding to join the surge synth effort would be the best. The folks who seem attracted to the development side seem mostly to be linux or mac folk. We have loads of people in the surge team using windows who do testing, keep documentation up to date, and contribute content - all of which are super important for the effort - but the C++ devs seem to all gravitate towards the unixen.

baconpaul · Post by **baconpaul** » Sat Jan 04, 2020 10:22 pm

brok landers wrote: Tue Dec 24, 2019 10:29 am still wish for the phase retriggering/phase start editing per osc waveform... pretty please... to me that's all that's badly missing.

There’s this issue https://github.com/surge-synthesizer/surge/issues/867

If you could make sure it contains the behavior you would like I’d really appreciate it. Looks like it has start but not retrigger so getting the full spec clear would help. (Github accounts are free so you can just make one and comment on that issue). Generally if things are logged as github issues, I’ll at least know they aren’t getting done and won’t forget that. Please feel free to add or comment to issues freely with ideas for the synth!

Evil is right though - to add the parameter will require an upgrade I’m working on in 2020 to the core engine. There’s a few nasty bugs I want to fix for a 1.6.5 release in February but it’s on my list.

Thanks, and happy new year!

baconpaul · Post by **baconpaul** » Sat Jan 04, 2020 10:26 pm

Auplant wrote: Fri Dec 27, 2019 10:43 pm Can anyone tell me what the "FX1 Return" and "FX2 Return" sliders are for? There isn't really anything written in the manual about them.

edit-
They seem to control the output of FX1/FX2 sends

There’s 8 effect slots, which is the diagram up top. 2 inline for each of A and B, 2 inline for the master (A+B), and 2 which act like a bus with a send/return.

Each scene separately sends to the FX1/FX2 based on the send level, and then the FX are mixed into the output scaled by the return. There’s a few modulation cases where separating this way is useful, and some effects like a large input and an attenuated output, hence the difference.

We should update the manual! I’ll flag this comment over on our slack. Thanks!

layzer · Post by **layzer** » Sat Jan 04, 2020 10:46 pm

Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really

hi Hal,
i use the older v1.5 version of surge in EnergyEXT2 under XPsp3 and it works fine.

could never get v1.6 to work though.

its ok, v1.5 still gets the WT job done with stability.

Halonmusic · Post by **Halonmusic** » Sun Jan 05, 2020 12:10 am

baconpaul wrote: Sat Jan 04, 2020 10:18 pm
Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really
https://github.com/surge-synthesizer/surge/issues/190 There’s the github issue. it has some information about how to debug it. Oh and I think that layzer uses the 1.5 vintage still, which works in ext, and the 1.6 vintage does not, but I’m not 100% sure on that.

On windows daw issues and windows behaviors, it’s really hard for me to debug them. I have a VM not a proper machine, I haven’t done windows dev in about a decade, and my environment is really tailored for the Unix-like environments. I know windows has come a long way with WSL and so on but I just don’t have any of that working. So certainly my least easy to debug platform.

Of all the things that would be a lovely new years gift, an experienced windows C++ developer deciding to join the surge synth effort would be the best. The folks who seem attracted to the development side seem mostly to be linux or mac folk. We have loads of people in the surge team using windows who do testing, keep documentation up to date, and contribute content - all of which are super important for the effort - but the C++ devs seem to all gravitate towards the unixen.

layzer wrote: Sat Jan 04, 2020 10:46 pm
Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really
hi Hal,
i use the older v1.5 version of surge in EnergyEXT2 under XPsp3 and it works fine.
could never get v1.6 to work though.
its ok, v1.5 still gets the WT job done with stability.

Ok thanks guys

gonna try v1.5 in energyxt then

baconpaul · Post by **baconpaul** » Sun Jan 05, 2020 5:16 pm

Halonmusic wrote: Sun Jan 05, 2020 12:10 am
baconpaul wrote: Sat Jan 04, 2020 10:18 pm
Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really
https://github.com/surge-synthesizer/surge/issues/190 There’s the github issue. it has some
So I was in windows anyway since I wanted to run our unit tests in CI and while I was in there I looked at energyXT, doing the debugging output I suggest in the issue above.

Basically: energyXT is never dispatching the `effEditOpen` message to surge. So we never open a window. There's no canDo which it sends which we are ignoring either. I saved my instrumented version in a branch. But basically: do any of you know the energyXT devs and would you like to invite them to hop onto that GitHub issue? I don't see anything I could do to fix it otherwise.

baconpaul · Post by **baconpaul** » Sun Jan 05, 2020 5:16 pm

baconpaul wrote: Sun Jan 05, 2020 5:16 pm
Halonmusic wrote: Sun Jan 05, 2020 12:10 am
baconpaul wrote: Sat Jan 04, 2020 10:18 pm
Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really
https://github.com/surge-synthesizer/surge/issues/190 There’s the github issue. it has some

So I was in windows anyway since I wanted to run our unit tests in CI and while I was in there I looked at energyXT, doing the debugging output I suggest in the issue above.

Basically: energyXT is never dispatching the `effEditOpen` message to surge. So we never open a window. There's no canDo which it sends which we are ignoring either. I saved my instrumented version in a branch. But basically: do any of you know the energyXT devs and would you like to invite them to hop onto that GitHub issue? I don't see anything I could do to fix it otherwise.

baconpaul · Post by **baconpaul** » Sun Jan 05, 2020 5:16 pm

baconpaul wrote: Sun Jan 05, 2020 5:16 pm
baconpaul wrote: Sun Jan 05, 2020 5:16 pm
Halonmusic wrote: Sun Jan 05, 2020 12:10 am
baconpaul wrote: Sat Jan 04, 2020 10:18 pm
Halonmusic wrote: Mon Dec 30, 2019 9:06 pm
EvilDragon wrote: Tue Dec 24, 2019 7:06 am No changes on eXT front. I wouldn't expect any changes there, unless somebody who's a Windows-focused programmer shows up in the Surge team.
Sorry i didnt see your post until now. Thanks for the information. I know layzer is using ext and its working for him, but not for me. Well i got Reaper anyway and its working there so no problem really
https://github.com/surge-synthesizer/surge/issues/190 There’s the github issue. it has some

So I was in windows anyway since I wanted to run our unit tests in CI and while I was in there I looked at energyXT, doing the debugging output I suggest in the issue above.

Basically: energyXT is never dispatching the `effEditOpen` message to surge. So we never open a window. There's no canDo which it sends which we are ignoring either. I saved my instrumented version in a branch. But basically: do any of you know the energyXT devs and would you like to invite them to hop onto that GitHub issue? I don't see anything I could do to fix it otherwise.

Vember Audio Surge is now open-source