Vember Audio Surge is now open-source
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
What do you mean? What's your screen resolution? Any screenshots?
-
- KVRian
- 845 posts since 25 Dec, 2018
Are you using Live 11? And if so, does the Live device MPE mode match the Surge device MPE mode?andrewbrewer wrote: ↑Mon Mar 01, 2021 4:30 pm I’m not sure if I found a bug, and how to best report a bug. I’m noticing that monophonic playback, legato style, can cause the surge synth to almost infinitely sustain (it does eventually stop but after a long time). This goes away with poly mode or mono mode with envelope re-trigger
-
- KVRist
- 126 posts since 5 Dec, 2009
Are you using Live 11? And if so, does the Live device MPE mode match the Surge device MPE mode?baconpaul wrote: ↑Wed Mar 03, 2021 11:13 pm [quote=andrewbrewer post_id=8044763 time=<a href="tel:1614616251">1614616251</a> user_id=221065]
I’m not sure if I found a bug, and how to best report a bug. I’m noticing that monophonic playback, legato style, can cause the surge synth to almost infinitely sustain (it does eventually stop but after a long time). This goes away with poly mode or mono mode with envelope re-trigger
[/quote]
I am using live 11! I will check the MPE setting
-
- KVRist
- 126 posts since 5 Dec, 2009
This worked, thanks for the tip!baconpaul wrote: ↑Wed Mar 03, 2021 11:13 pmAre you using Live 11? And if so, does the Live device MPE mode match the Surge device MPE mode?andrewbrewer wrote: ↑Mon Mar 01, 2021 4:30 pm I’m not sure if I found a bug, and how to best report a bug. I’m noticing that monophonic playback, legato style, can cause the surge synth to almost infinitely sustain (it does eventually stop but after a long time). This goes away with poly mode or mono mode with envelope re-trigger
-
- KVRian
- 845 posts since 25 Dec, 2018
No problem. We’ve been in touch with live devs also, and in the next Live 11 point release, we think that surge and live will cross synchronize this state properly.andrewbrewer wrote: ↑Sun Mar 07, 2021 2:29 amThis worked, thanks for the tip!baconpaul wrote: ↑Wed Mar 03, 2021 11:13 pmAre you using Live 11? And if so, does the Live device MPE mode match the Surge device MPE mode?andrewbrewer wrote: ↑Mon Mar 01, 2021 4:30 pm I’m not sure if I found a bug, and how to best report a bug. I’m noticing that monophonic playback, legato style, can cause the surge synth to almost infinitely sustain
-
- KVRian
- 1454 posts since 2 Mar, 2005
This is my new music video I made, and the song includes all instruments & sound effects made with Surge. Thanks Surge team for keeping this alive for people like me!
https://www.youtube.com/watch?v=oA_r7kxZ2Eg
https://www.youtube.com/watch?v=oA_r7kxZ2Eg
I read more than post = I listen more than I talk
-
- KVRian
- 845 posts since 25 Dec, 2018
OK I found and fixed this bug tonight. Should be in a nightly in a couple of hours and will be included in our 1.9 release in late-April early-May.
If you are interested here was the problem. The VST3 API has a parameter point "getDisplayValue(param, float for-value)". It has another API point which is basically "setParam(value)". (very roughly). The getDisplayValue should use the features of the param but the value handed in. Surge was making the mistake of using the current value of the slider for the string.
So if you went setParam / getDisplayValue it worked. If you went getDisplayValue/setParam it would use the prior value to make the *string* even though the value was correct.
So ultimately Bitwig was setting the right value on surge but surge was telling it the wrong string to display. All the other DAWs I tried seem to do set / get but that doesn't mean that Surge was correct.
Once I found it it was a 20 character fix.
- KVRAF
- 18558 posts since 16 Sep, 2001 from Las Vegas,USA
-
- KVRist
- 126 posts since 22 Jan, 2010 from Oregon, U.S.
Thanks for the heads up and explanation!
-
- KVRian
- 845 posts since 25 Dec, 2018
Hi Folks.
Today we decided to start calling the nightly "1.9 Beta". 4 new oscillators, 16 new effects, loads of micro tuning changes, and a lot more. If you have been running 1.8.1 and are interested on testing, grab 1.9 beta from the surge-synth web page and give it a spin! Bug reports here or on our discord or GitHub if poss. Thanks!
Today we decided to start calling the nightly "1.9 Beta". 4 new oscillators, 16 new effects, loads of micro tuning changes, and a lot more. If you have been running 1.8.1 and are interested on testing, grab 1.9 beta from the surge-synth web page and give it a spin! Bug reports here or on our discord or GitHub if poss. Thanks!
- KVRAF
- 18558 posts since 16 Sep, 2001 from Las Vegas,USA
Just downloaded the beta. Make sure you back up your data first as it appears to overwrite files at least in the Skins folder. I don't remember if I've done any patches on this system or not so can't say if those would have been deleted.
I get this issue in Reaper and Cakewalk by Bandlab when left clicking on the patch name area:
The list extends well beyond the boundaries of the GUI. Seems like it's displaying horizontally instead of vertically ? Win 10 64 bit.
With all the great new FX it makes me ask will the Effects Bank ever have themes or can the interface be changed now? Not seeing any files for it.
I get this issue in Reaper and Cakewalk by Bandlab when left clicking on the patch name area:
The list extends well beyond the boundaries of the GUI. Seems like it's displaying horizontally instead of vertically ? Win 10 64 bit.
With all the great new FX it makes me ask will the Effects Bank ever have themes or can the interface be changed now? Not seeing any files for it.
You do not have the required permissions to view the files attached to this post.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Hmmm cannot confirm that issue in Reaper over here (W10). What's your system config (including GPU, monitor size, display scaling etc)?
FX bank doesn't have themes and isn't skinnable as of yet.
By the way, the factory data folder is not safe for user data. This is why there's a completely separate user data folder where you're supposed to put your own patches, skins, FX presets, wavetables etc. Stuff placed there isn't touched by the update installer.
FX bank doesn't have themes and isn't skinnable as of yet.
By the way, the factory data folder is not safe for user data. This is why there's a completely separate user data folder where you're supposed to put your own patches, skins, FX presets, wavetables etc. Stuff placed there isn't touched by the update installer.
- KVRAF
- 18558 posts since 16 Sep, 2001 from Las Vegas,USA
This is my test/internet system an i5 3470 with onboard intel graphics and sound. 24" Monitor 1920x1080. System scaling at default 100%.
The last release version worked fine on this system. I haven't installed the beta on my studio computer.
Where is the other user data folder that is safe to save in ? I backed up my current skin file so nothing was lost as far as I know.
The last release version worked fine on this system. I haven't installed the beta on my studio computer.
Where is the other user data folder that is safe to save in ? I backed up my current skin file so nothing was lost as far as I know.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRian
- 845 posts since 25 Dec, 2018
In the menu under data and patches there’s an open user data menu item which will take you thereTeksonik wrote: ↑Thu Mar 25, 2021 9:22 pm This is my test/internet system an i5 3470 with onboard intel graphics and sound. 24" Monitor 1920x1080. System scaling at default 100%.
The last release version worked fine on this system. I haven't installed the beta on my studio computer.
Where is the other user data folder that is safe to save in ? I backed up my current skin file so nothing was lost as far as I know.
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia