Discussion:
[LAD] New(ish) OSS synth plugin
Daniel Swärd
2018-09-25 11:24:53 UTC
Permalink
Hi all.

Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge

Doesn't yet build on Linux, but quoting from the github page:
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."

How about we get it building at the next Berlin LAU meeting?

Cheers

/Daniel
Paul Davis
2018-09-25 12:34:22 UTC
Permalink
Post by Daniel Swärd
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
Which VST3 hosts do you plan to use (on Linux)?
Hermann Meyer
2018-09-25 14:38:24 UTC
Permalink
You could build it as VST2 as well, so, Ardour, for example, will suite
the role as host. :-)
The VST3SDK <https://github.com/steinbergmedia/vst3sdk> hosted by
Steinberg on github doesn't contain the VST2 SDK bits, so if you want
to build the VST2 version you need to download
<https://www.steinberg.net/vst3sdk> that one manually and add those
missing files, they have a script that copies the copying for you.
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
Which VST3 hosts do you plan to use (on Linux)?
_______________________________________________
Linux-audio-dev mailing list
https://lists.linuxaudio.org/listinfo/linux-audio-dev
bernard
2018-09-25 15:50:46 UTC
Permalink
I remember using Surge, it was a really nice synth.
Post by Hermann Meyer
You could build it as VST2 as well, so, Ardour, for example, will
suite the role as host. :-)
The VST3SDK <https://github.com/steinbergmedia/vst3sdk> hosted by
Steinberg on github doesn't contain the VST2 SDK bits, so if you want
to build the VST2 version you need to download
<https://www.steinberg.net/vst3sdk> that one manually and add those
missing files, they have a script that copies the copying for you.
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
Which VST3 hosts do you plan to use (on Linux)?
_______________________________________________
Linux-audio-dev mailing list
https://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
https://lists.linuxaudio.org/listinfo/linux-audio-dev
Daniel Swärd
2018-09-26 08:37:09 UTC
Permalink
Post by bernard
I remember using Surge, it was a really nice synth.
Then we'd better get it building then? Include in the kxstudio repositories
maybe?

/Daniel
Daniel Swärd
2018-09-26 08:36:10 UTC
Permalink
Post by Paul Davis
Post by Daniel Swärd
How about we get it building at the next Berlin LAU meeting?
Which VST3 hosts do you plan to use (on Linux)?
I'm a Bitwig user, so I would use that.

/Daniel
Kjetil Matheussen
2018-09-26 13:07:01 UTC
Permalink
Post by Daniel Swärd
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
I took a quick procrastination-shot at it:
https://github.com/kmatheussen/surge

(first copy various VST directories into the build)
premake5 gmake
make surge-vst2 verbose=1 -j8

ldd -r target/vst2/Debug/Surge-Debug.so
undefined symbol: _ZN6VSTGUI8soHandleE (target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN3Gtk11FileChooser18set_current_folderERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gdk11DragContext12list_targetsB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN4Glib7ustringC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN12SurgeStorage11load_wt_wavENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP9Wavetable
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: __cpuid (target/vst2/Debug/Surge-Debug.so)
undefined symbol:
_ZN3Gtk11CssProvider14load_from_dataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _Z19spawn_miniedit_textPci
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gtk11FileChooser13get_filenamesB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)

So, a little bit work left, but maybe it's enough to link with a newer
version of
gtkmm than I did.

Don't know how well VSTGUI works on linux though. Using
gtkmm as the underlying GUI to implement VSTGUI on top of
seems worrying.
Kjetil Matheussen
2018-09-27 12:43:21 UTC
Permalink
On Wed, Sep 26, 2018 at 3:07 PM, Kjetil Matheussen
Post by Kjetil Matheussen
Post by Daniel Swärd
Hi all.
Just found out that one of the Bitwig devs has released an older (commercial)
project of his as open source: https://github.com/kurasu/surge
"It currently only builds on windows, but getting it to build on macOS again &
Linux should be doable with moderate effort."
How about we get it building at the next Berlin LAU meeting?
https://github.com/kmatheussen/surge
(first copy various VST directories into the build)
premake5 gmake
make surge-vst2 verbose=1 -j8
ldd -r target/vst2/Debug/Surge-Debug.so
undefined symbol: _ZN6VSTGUI8soHandleE (target/vst2/Debug/Surge-Debug.so)
_ZN3Gtk11FileChooser18set_current_folderERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gdk11DragContext12list_targetsB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)
_ZN4Glib7ustringC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
_ZN12SurgeStorage11load_wt_wavENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEP9Wavetable
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: __cpuid (target/vst2/Debug/Surge-Debug.so)
_ZN3Gtk11CssProvider14load_from_dataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _Z19spawn_miniedit_textPci
(target/vst2/Debug/Surge-Debug.so)
undefined symbol: _ZNK3Gtk11FileChooser13get_filenamesB5cxx11Ev
(target/vst2/Debug/Surge-Debug.so)
So, a little bit work left, but maybe it's enough to link with a newer
version of
gtkmm than I did.
The commit was merged upstream.

For anyone who wants to give it a try,
it might be that it's enough just using a
newer version of VSTGUI and gtkmm than I did.
I used gtkmm 3.16 and gtk-3.3, which probably
are some years old old. The VSTGUI I used,
I don't know how hold is, or where it came from.
Robin Gareus
2018-09-27 14:05:09 UTC
Permalink
On 09/27/2018 02:43 PM, Kjetil Matheussen wrote:
[...]
Post by Kjetil Matheussen
For anyone who wants to give it a try,
it might be that it's enough just using a
newer version of VSTGUI and gtkmm than I did.
I used gtkmm 3.16 and gtk-3.3, which probably
are some years old old. The VSTGUI I used,
I don't know how hold is, or where it came from.
Indeed, try to update.

VST3's VSTGUI recently removed all gtk from their toolkit.
That greatly helps to produce distributable plugins (since gtk cannot be
statically linked and also has ABI issues when combined other toolkits).

Cheers!
robin

bill-auger
2018-09-26 18:02:08 UTC
Permalink
derp, the first time i noticed this post i overlooked the egregious
error in the title

one should be mindful to avoid terminology (especially acronyms) that
have multiple interpretations, especially when those alternate
interpretations can relate to the same subject area - that really
should not happen but it does when people give names to new things
without knowing that term is already widely used for something else

in this case i am clearly referring to 'OSS' - in the context of
pro-audio, OSS is the "Open Sound System"; and it has been widely known
as such for about 20 years, and still in use today - that is how i read
this post at first - now i realize it was a short-hand for
"open-source"

regardless of whether or not the OP has heard of the actual 'OSS'
before, confusing jargon like that can be easily avoided simply be
being more specific with the words one chooses - in this case "free
software" or even "open-source" would have been perfectly clear to all
- if one must be so lazy about typing, use 'FOSS' or 'FLOSS' when
referring to "audio software that is freely licensed" to make it clear
that is not referring to the "Open Sound System"
John Rigg
2018-09-26 17:23:41 UTC
Permalink
Post by bill-auger
derp, the first time i noticed this post i overlooked the egregious
error in the title
one should be mindful to avoid terminology (especially acronyms) that
have multiple interpretations, especially when those alternate
interpretations can relate to the same subject area - that really
should not happen but it does when people give names to new things
without knowing that term is already widely used for something else
in this case i am clearly referring to 'OSS' - in the context of
pro-audio, OSS is the "Open Sound System"; and it has been widely known
as such for about 20 years, and still in use today - that is how i read
this post at first - now i realize it was a short-hand for
"open-source"
I too thought it meant Open Sound System at first.

John
Daniel Swärd
2018-09-27 12:42:01 UTC
Permalink
Post by John Rigg
Post by bill-auger
derp, the first time i noticed this post i overlooked the egregious
error in the title
one should be mindful to avoid terminology (especially acronyms) that
have multiple interpretations, especially when those alternate
interpretations can relate to the same subject area - that really
should not happen but it does when people give names to new things
without knowing that term is already widely used for something else
in this case i am clearly referring to 'OSS' - in the context of
pro-audio, OSS is the "Open Sound System"; and it has been widely known
as such for about 20 years, and still in use today - that is how i read
this post at first - now i realize it was a short-hand for
"open-source"
I too thought it meant Open Sound System at first.
I had forgotten about Open Sound System.

/Daniel
Continue reading on narkive:
Loading...