I confess that I stopped using SM when this bug surfaced last year; it comes and goes with little rhyme or reason; many people reported it along with various "fixes" that sometimes worked and other times did not (but I suspect that the erratic nature of the bug was why people thought they had found a fix). KV331 could not reproduce it on any of their systems.
I like the synth. It can be made to sound gritty, aggressive, or clean and smooth, and it's very versatile. But not knowing if I could save my work discouraged me greatly.
How are we doing with the "save" bug?
-
- KVRAF
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
Unfortunately we could not reproduce it. and our sound designers could not reproduce it either.
So, still no progress
So, still no progress
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
-
- KVRist
- Topic Starter
- 61 posts since 28 Feb, 2013
Well, today I installed SM 2.7.2 on both of my DAW computers (nice update, by the way), and tried a little editing, then doing "save as", and encountered no problems. So, either the bug has gone into hiding temporarily, or something in the update fixed it inadvertently.
I am cautiously optimistic.
I am cautiously optimistic.
Studio One 3.5.6 Pro
Win 7 x64
Core i7 3770 3.4 GHz
Behringer UMC404HD
No talent.
Win 7 x64
Core i7 3770 3.4 GHz
Behringer UMC404HD
No talent.
