Vember Audio Surge is now open-source

[PietW.]

There have been several claims that Audioterm could not produce well-sounding wavetables. Here is a sound that consists of a wavetable with 5 waveforms. The wavetable was created with serum

https://www.dropbox.com/s/5ljzyjkup9nt9 ... s.fxp?dl=0

i noticed that on your patch, you are not stepping through the partials in the WT.
was that intentional? i wonder how many people use shapable WTs in their patches but
dont realize they are only hearing a single partial unless they step through them with
an LFO or with mod wheel or some other modulator.

ie; left click the LFO1 button for example, the sliders that can be adjusted change color, move the slider the mod amount you want, left click the LFO1 button again.
i do this to the WT shape on almost all my pad patches.

The wavetable in this patch is a simple wave file of 5 waveforms. Audioterm makes a wavetable in wav format by simply interpolating between these 5 waveforms. Then this file will be converted to the surge format. Finished.
I have no idea why you should think about the partiale.
Another question. With which program do you create your wavetables for Surge? If Audioterm is so bad you have an alternative program?

[aMUSEd]

Can someone put the release dates up on the builds site by the downloads links please so people can tell if there is a new one.

[layzer]

The wavetable in this patch is a simple wave file of 5 waveforms. Audioterm makes a wavetable in wav format by simply interpolating between these 5 waveforms. Then this file will be converted to the surge format. Finished.
I have no idea why you should think about the partiale.
Another question. With which program do you create your wavetables for Surge? If Audioterm is so bad you have an alternative program?

Understood. i use audioterm too, i never said audioterm is bad, its just tedius to use.
anyway, i want you to listen to my version of your VS Bells patch compared to your patch
where i actually step through the wavetable wavforms...

https://www.sendspace.com/file/63ntum

i understand you built the wavetable using 5 wavs, then interpolated them. then created the 33 partial WT for surge. BUT you can not simply use the WT and expect surge to cycle through
all 33 wavforms automatically without modulating them with an LFO or other modulator.

right click on the LFO1 button to see how i mapped the LFO to the WT shape parameter.
hold down a note on your patch and hold down a note on mine to hear the way my patch actually
changes in tone as it cycles through the 33 wavforms, yours does NOT..
thats all i'm trying to explain.

btw, if im not mistaken a wavetable partial is the same as a wavetable wavform.

[esaruoho]

Can someone put the release dates up on the builds site by the downloads links please so people can tell if there is a new one.

There's been talk of it, but since the website is static, it would require more code for there to be dates added to it automatically, instead of done by hand. Basically, every time there's additional fixes going in, there's a new build.

The Surge Synth Slack channel #github-repo also posts when a new build has been built and deployed.

I know this is far from ideal - I wouldn't mind the dates being there in the filename itself. But there's still tons of additional things that need to be done before something like this becomes the primary focus

(Like 125% Zoom, Linux builds, storing of User Preferences / settings and whatnot)

Basically, there's been a new build multiple times every single day.

Anyway, there's a ticket about it on https://github.com/surge-synthesizer/su ... /issues/71 now.

[aMUSEd]

Thanks but I can't find anything on the Slack site, just pages of talk. When was the latest Mac 64 bit build?

[esaruoho]

Thanks but I can't find anything on the Slack site, just pages of talk. When was the latest Mac 64 bit build?

http://surge-synthesizer.github.io/#downloads
according to the channel #github-repo on Slack - 9th February 2019 at 6.18pm Finnish time.

i have a PR brewing waiting to be merged in, if that gets merged in, the newest build will immediately trigger, so then the newer will be 10th February 2019.

[esaruoho]

When was the latest Mac 64 bit build?

Actually, if you want to sidestep the whole new website, just check https://github.com/surge-synthesizer/releases/releases which will have date+times of the newest build right next to it

[aMUSEd]

Thanks

[c_voltage]

esaruoho \ folks, i recently try official v152 build from friend, for compare, so, my assumptions were confirmed - by some reason new version load cpu already in initial (idle) stage, just after load plugin (it's a pretty small cpu load, but strange it is). While in v152 absolutely zero cpu usage in the same idle condition. Hmm.
I dont know, maybe i miss something in settings, would be good if you check this too. Or maybe reason is known ?

I've posted this at https://github.com/surge-synthesizer/surge/issues/556

should be interesting to find out what's happening. none of the devs have access to v152 however, so this could take a while before looked at and compared.

Ok, good.

BTW folks, the version 1.5.2 this is was the most latest official version ? Just want to be sure.

[esaruoho]

BTW folks, the version 1.5.2 this is was the most latest official version ? Just want to be sure.

The last commercial version was apparently 1.5.2. We get a great deal of help from one Slack user that can double-check how things worked in 1.5.2 for us and post video + screenshots, it really really really helps - being able to verify how stuff worked with 1.5.2, or 1.5.0, vs. 1.6.0.

f.ex. apparently 1.5.0 showed .wav files in wavetables, but 1.5.2 no longer does.
apparently 1.5.0 allowed for .wav drag to wavetable-oscillator, but 1.5.2 no longer does.

stuff like this.

[esaruoho]

Thanks

You might find this web-update + file-update of interest.. - this is towards the beginning of the website at http://surge-synthesizer.github.io

[Russell Grand]

NEW:
32bit windows VST2,VST3 installer available at http://surge-synthesizer.github.io/
wahey!

[c_voltage]

BTW folks, the version 1.5.2 this is was the most latest official version ? Just want to be sure.

The last commercial version was apparently 1.5.2. We get a great deal of help from one Slack user that can double-check how things worked in 1.5.2 for us and post video + screenshots, it really really really helps - being able to verify how stuff worked with 1.5.2, or 1.5.0, vs. 1.6.0.

f.ex. apparently 1.5.0 showed .wav files in wavetables, but 1.5.2 no longer does.
apparently 1.5.0 allowed for .wav drag to wavetable-oscillator, but 1.5.2 no longer does.

stuff like this.

Hm ok thanks good to know.

[ENV1]

f.ex. apparently 1.5.0 showed .wav files in wavetables, but 1.5.2 no longer does.
apparently 1.5.0 allowed for .wav drag to wavetable-oscillator, but 1.5.2 no longer does.

Dont know who provided that info but its definitely not correct. (Not on Windows anyway.)

Surge 1.5.2 does in fact show WAVs in the dropdown and it also takes them when dragged onto the window from Windows Explorer.

The only exception is when a WAV is an unsupported format, but then thats to be expected.


Note for Clarity: WAVs are listed after WTs in the dropdown, i.e. the alphabetical order starts over after the last WT. So they are not 'mixed in' alphabetically with the WT files, which is good, because it is an excellent way of seeing what is WT and what is WAV.

Example:

- In the 'Generated' folder there are 53 WTs and 2 WAVs

- In the dropdown, the WTs go from 'circle' (first WT) thru 'triangle sineshape' (last WT)

- After 'triangle sineshape' the WAV list starts, so thats where we find 'saw atc' and 'square atc'

So although there are no file extensions to go by in the dropdown, the fact that the alphabetical order eventually starts over if there are any WAVs in the selected folder makes it pretty easy to discern between WTs and WAVs.

[Halonmusic]

NEW:
32bit windows VST2,VST3 installer available at http://surge-synthesizer.github.io/
wahey!

Finally!