+1gentleclockdivider wrote:I don't get it why the 32 bit version isn't available .
It was on his website for years .... just a pointer to that download is all it takes .
C'mon claes
Edit: Nevermind, I see it on page 4.
+1gentleclockdivider wrote:I don't get it why the 32 bit version isn't available .
It was on his website for years .... just a pointer to that download is all it takes .
C'mon claes
Mac and Windows 32bit versions.forestrip wrote:open at least 32bit version for mac please
Exactly. Really wonder how anyone could be surprised when something so old won't work in modern setups.aMUSEd wrote:Because it was brilliant when it was out and actively developed. Now it's just outdated so possibly could be unstable in some hosts, especially flaky ones like Waveform.tatanka wrote:Really wonder how this ever could be sold for 100 bucks, kills waveform 9.2.1 instantly while only changing a preset. Evry time.
So far the latest version 1.6.0b3 seems to run stable in Live 10 Suite and Cubase 9.5 Pro on Windows 10 64-bit.Russell Grand wrote:Exactly. Really wonder how anyone could be surprised when something so old won't work in modern setups.aMUSEd wrote:Because it was brilliant when it was out and actively developed. Now it's just outdated so possibly could be unstable in some hosts, especially flaky ones like Waveform.tatanka wrote:Really wonder how this ever could be sold for 100 bucks, kills waveform 9.2.1 instantly while only changing a preset. Evry time.
Wavetable folders with *.wt files in Windows 10 are found at C:\users\*yourname*\AppData\Local\Surge\wavetables
Just for everyones info; this file contains an error. Under 0-3 it says that the header string of Surge wavetables is 'wavt', which certainly sounds plausible since it seems to stand for wave+table. But thats not actually correct. The correct string is 'vawt', which probably stands for 'Vember Audio WaveTable'. Wavetables with 'wavt' as the header string will >not< load, so if you intend to use that file (wt fileformat.txt) for reference you should change the 'wavt' to 'vawt' ASAP so you dont have an incorrect header string mentioned in there.Ingonator wrote: In the folder mentioned above there is a text file that explains the *.wt wavetable file format that is used for the wavetables.
Good news for you: Some guys are already working on it.aMUSEd wrote: Is it possible to build a Mac version from the sources?
Thats how i found out about the wavt/vawt thing.Ingonator wrote: So far i never tried to use my own wavertables with Surge but the free Audio Term tool includes a dedicated wavetable export format for Surge.
For assigning Modwheel to certain parameters Midi learn does not really seem to be necessary.synzh wrote: ↑Thu Sep 27, 2018 7:25 pm Great thanks - looks like the right-click context menu is working now also (and can assign modwheel)
[edit] not sure how it was working before, but appears you can assign MW directly (via learn) to each target, but the overall modwheel assignment (which is already assigned to multiple targets in some presets for example) doesn't appear to be working
Sorry if this has been asked before but my other studio pc is win xp sp3 32bt. How can I get the last 1.5 version that was stable on win xp (obviously an unlocked version with no serial codelayzer wrote: ↑Tue Sep 25, 2018 10:08 pmENV1 wrote:Thats an XP incompatibility then. It works fine (see note below) in Win7. Its also perfectly safe to move the .dll and/or the .vst3 to your desired location, the only thing thats important is to leave the resources in local appdata because the plugin absolutely expects them there. (Otherwise it will throw an error message and then start with only 'Classic' available in the oscillators, and of course no presets.)layzer wrote:no go. i get some error about entry point not found in shell32 or something using the v1.6 dll.... ah well, i guess i'll stick to v1.5.
Note: So far it starts fine and seems to work fine, (more testing required to be sure), but what i can already say is that in 99% of the cases it crashes the host upon removal or upon exiting the host with it still running. Not a good sign, but only tested with VSTHost so far. Will do some more checking tomorrow.
yeah, no XP for v1.6 i guess, but you know, v1.5 works perfect. no crashes ever on closing or anything. so, no biggie sticking to v1.5 for me
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement