I went and found the skin resources folder on github, which appear to only be available to download as individual files. I don't mind doing that if it's the only option, but is there a zip of all of them?esaruoho wrote: ↑Fri Jan 11, 2019 9:39 pmThere's a process to what they're doing..
1. Re-create the original skin as a vector skin, make it work
2. Enable zooming / increased sizes without loss
Then when all that is in place (and hopefully documentation, too) - it could in the future be re-skinned.
A lot of baby steps are being made and have been made for weeks on end, and a lot of patience is required still before it is all ready.
Vember Audio Surge is now open-source
-
- KVRAF
- 11052 posts since 19 Jun, 2008 from Seattle
I'm not a musician, but I've designed sounds that others use to make music. http://soundcloud.com/obsidiananvil
- KVRist
- 297 posts since 4 Feb, 2010 from kontula, helsinki, finland
I'll ask the guys on github ( at http://github.com/surge-synthesizer/surge/issues ) - although would be good that if anyone has any questions relating to surge, or any bug-reports, that they'd post them on the github. Would generally help with fixing the issues and getting better bug-reports in
posted your question at https://github.com/surge-synthesizer/surge/issues/381
- KVRist
- 297 posts since 4 Feb, 2010 from kontula, helsinki, finland
Hi, I would really recommend joining the Surge-Synth Slack and checking out the channel #design and talking there about re-skinning efforts as that is where the guys in charge of re-creating the Original Surge look using Sketch (I think) are and that's where the main talk about the GUI and the Zoom features is going on.Shabdahbriah wrote: ↑Wed Jan 23, 2019 1:46 amI went and found the skin resources folder on github, which appear to only be available to download as individual files. I don't mind doing that if it's the only option, but is there a zip of all of them?esaruoho wrote: ↑Fri Jan 11, 2019 9:39 pmThere's a process to what they're doing..
1. Re-create the original skin as a vector skin, make it work
2. Enable zooming / increased sizes without loss
Then when all that is in place (and hopefully documentation, too) - it could in the future be re-skinned.
A lot of baby steps are being made and have been made for weeks on end, and a lot of patience is required still before it is all ready.
Here's an invite!
https://join.slack.com/t/surgesynth/sha ... mNhYzQ3NTU
-
- KVRAF
- 11052 posts since 19 Jun, 2008 from Seattle
Thank you, will do.esaruoho wrote: ↑Wed Jan 23, 2019 9:35 amHi, I would really recommend joining the Surge-Synth Slack and checking out the channel #design and talking there about re-skinning efforts as that is where the guys in charge of re-creating the Original Surge look using Sketch (I think) are and that's where the main talk about the GUI and the Zoom features is going on.Shabdahbriah wrote: ↑Wed Jan 23, 2019 1:46 amI went and found the skin resources folder on github, which appear to only be available to download as individual files. I don't mind doing that if it's the only option, but is there a zip of all of them?esaruoho wrote: ↑Fri Jan 11, 2019 9:39 pmThere's a process to what they're doing..
1. Re-create the original skin as a vector skin, make it work
2. Enable zooming / increased sizes without loss
Then when all that is in place (and hopefully documentation, too) - it could in the future be re-skinned.
A lot of baby steps are being made and have been made for weeks on end, and a lot of patience is required still before it is all ready.
Here's an invite!
https://join.slack.com/t/surgesynth/sha ... mNhYzQ3NTU
{aside: the post I saw had an 'Affinity Designer' project extension, which is what I use, so that would be cool}
I'm not a musician, but I've designed sounds that others use to make music. http://soundcloud.com/obsidiananvil
-
- KVRer
- 8 posts since 30 Dec, 2004
I only tried in cubase, let me investigate further
- KVRist
- 297 posts since 4 Feb, 2010 from kontula, helsinki, finland
oh yes. the "does audio input works or not?" conversation on the slack resulted in guys realizing that Cubase does not seem to directly support Surge's audio input possibilities. There's a ticket about that feature and it'll probably be done sooner or later. (p.s. Logic Pro X & Ableton Live = Surge AudioInput confirmed working btw).
-
- KVRAF
- 9133 posts since 6 Oct, 2004
I think a separate Surge effects .dll would be great, like what
Cakewalk did with z3ta + 1.5
The audio input is always ready, regardless of the
selected preset, and it takes daw vagaries
out of the equation. Thanks for putting my idea
about linux binaries at the GIT area.
Hope things are going well
Cakewalk did with z3ta + 1.5
The audio input is always ready, regardless of the
selected preset, and it takes daw vagaries
out of the equation. Thanks for putting my idea
about linux binaries at the GIT area.
Hope things are going well
-
- KVRAF
- 2802 posts since 31 Aug, 2011
Unless that capability was removed from post 1.5.2 builds you can simply make a copy of Surge.dll and name it Surge_FX.dll
In the host it will then automatically show up as an FX, complete with a different Unique VST ID.
(A Surge.dll identifies itself as 'cjs3' while a Surge_FX.dll will identify itself as 'cjsx' so there will be no VST ID clashes.)
According to the dev thats the recommended procedure should you need a FX DLL so the worst thing that can happen is that it wont work with the open source builds.
-
- KVRAF
- 11052 posts since 19 Jun, 2008 from Seattle
Good to know, thanks.ENV1 wrote: ↑Thu Jan 24, 2019 3:32 pmUnless that capability was removed from post 1.5.2 builds you can simply make a copy of Surge.dll and name it Surge_FX.dll
In the host it will then automatically show up as an FX, complete with a different Unique VST ID.
(A Surge.dll identifies itself as 'cjs3' while a Surge_FX.dll will identify itself as 'cjsx' so there will be no VST ID clashes.)
According to the dev thats the recommended procedure should you need a FX DLL so the worst thing that can happen is that it wont work with the open source builds.
I'm not a musician, but I've designed sounds that others use to make music. http://soundcloud.com/obsidiananvil
-
- KVRAF
- 2802 posts since 31 Aug, 2011
Youre welcome.
(I would have been more than happy to check whether it still works with the open source builds but since nobody seems interested in offering/maintaining a 32bit build im afraid i cant be of any help with this one.)
EDIT: I just remembered that there was one unofficial 32bit build of 1.6.0b1 provided by NothanUmber. I just tried it with that and it still works fine so im pretty sure it will work fine with the newer builds as well.
(I would have been more than happy to check whether it still works with the open source builds but since nobody seems interested in offering/maintaining a 32bit build im afraid i cant be of any help with this one.)
EDIT: I just remembered that there was one unofficial 32bit build of 1.6.0b1 provided by NothanUmber. I just tried it with that and it still works fine so im pretty sure it will work fine with the newer builds as well.
-
- KVRAF
- 9133 posts since 6 Oct, 2004
In Reaper win7, can't get a peep out of the effects using the
Audio Input option from the oscillator menu. And if I did, it would
still go away when a different preset was selected. Probably
needs some major work, if Cubase and Reaper are both an issue.
(the renamed .dll didn't change results in my case)
I prefer an effect plugin to be receiving audio input
from the get-go, like so many normally do.
Cheers
Audio Input option from the oscillator menu. And if I did, it would
still go away when a different preset was selected. Probably
needs some major work, if Cubase and Reaper are both an issue.
(the renamed .dll didn't change results in my case)
I prefer an effect plugin to be receiving audio input
from the get-go, like so many normally do.
Cheers
-
- KVRAF
- 2802 posts since 31 Aug, 2011
Yes, Audio Input will stop working when you select a preset that doesnt have it selected.
(Its kinda inevitable.)
But with Audio Input selected you can definitely make it work, i just checked in VSTHost and there are 2 ways.
1) Trigger/Gate Surges Amp EG by sending Note-MIDI to Surge. Since in this case Surges Amp EG is active, make sure that it has some Sustain or Decay so the Amp output is audible. Works with both the normal and the FX version.
2) If sending MIDI to Surge isnt possible or wanted, set Surges voice handler to 'Latch' and the Sustain of the Amp EG to full. Since in this case the Amp EG is inactive except for the Sustain stage, whatever goes into Surge will come out without needing to trigger or gate anything. This too works with both the normal and the FX version.
- KVRist
- 297 posts since 4 Feb, 2010 from kontula, helsinki, finland
Hi, the way Surge is organised is that one of the three oscillators can be an Audio Input. If you have one set up as an Audio Input, and change to another preset, with it's own three oscillators set up, there will be no audio.
If you want to have continuous sound out from Surge, set one oscillator to Audio Input, and click on Latch.
- KVRist
- 159 posts since 25 Sep, 2013 from Zaragoza (España)
Thank you very much for continuing to develop this awesome synthesizer. Today one of the best. You are an example sharing your work in Open Source. These things make you have faith in people again.
Receive my respect and admiration.
Regards
Receive my respect and admiration.
Regards
La Selección "Definitiva" de Software Musical Gratuito
https://selecciondefinitiva.wordpress.com/
https://selecciondefinitiva.wordpress.com/
-
- KVRAF
- 9133 posts since 6 Oct, 2004
Thanks ENV1 and esaruoho for clearing up
the Surge Audio Input routine for me !
Lots of controls there to use on guitar this weekend
Cheers
the Surge Audio Input routine for me !
Lots of controls there to use on guitar this weekend
Cheers