SynthMaster 2.0.3.3 - Post bugs here!
-
- KVRist
- 211 posts since 28 Dec, 2003 from Gravel Switch, Kentucky
Two things about (full) beta17:
1. With my 512KB of RAM, after loading, Windows Task Manager says my available Physical Memory is only a few KB. SM must take a LOT of memory! After a while, the available PM gradually goes up to around 40 KB.
2. When I'm at the WAVEFORMS screen (only! -- this doesn't occur with the other screens), Windows Task Manager shows CPU usage pegged at 100%. The strange thing is if I click to get (say) a waveform menu, CPU usage drops to a low value, and the same happens while I'm adjusting waveform outlines with my mouse (dragging around curves).
That's all I've seen that's strange so far. I'm not getting big spikes any more on initial loading of SM into Cantabile.
Greg Williams
1. With my 512KB of RAM, after loading, Windows Task Manager says my available Physical Memory is only a few KB. SM must take a LOT of memory! After a while, the available PM gradually goes up to around 40 KB.
2. When I'm at the WAVEFORMS screen (only! -- this doesn't occur with the other screens), Windows Task Manager shows CPU usage pegged at 100%. The strange thing is if I click to get (say) a waveform menu, CPU usage drops to a low value, and the same happens while I'm adjusting waveform outlines with my mouse (dragging around curves).
That's all I've seen that's strange so far. I'm not getting big spikes any more on initial loading of SM into Cantabile.
Greg Williams
-
- KVRAF
- Topic Starter
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
Yes, SynthMaster consumes a lot of memory because of the wavetables. We store copies of waveforms at different sampling rates (that's how our synthesis engine works), so that's why we consume a lot of memory.
I'll check out the CPU spikes though.
Bulent
I'll check out the CPU spikes though.
Bulent
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
- 211 posts since 28 Dec, 2003 from Gravel Switch, Kentucky
Time for me to buy some more memory, I suppose!kv331 wrote:Yes, SynthMaster consumes a lot of memory because of the wavetables. We store copies of waveforms at different sampling rates (that's how our synthesis engine works), so that's why we consume a lot of memory.
I'll check out the CPU spikes though.
Bulent
I just tried the beta in Cantabile version 2 (I had been using 1.2 until now), and the 100% CPU on the Waveforms screen is not there. So I suppose it is a Cantabile 1.2 bug. Unless you see it with another host, not a problem!
Nothing else to report now.
Greg Williams
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
Some more bugs and annoyances:
1. Envelopes. There is a problem with the releases. This is particularly notorious in the Ingo Weidner wavetable pacthes. If you hold the key for some moments, and then release it, you hear clearly what seems like a second attack. If you play staccato, then the envelope release works OK.
2. Effects. I messed up with the chorus, and there seems to be some problem. If I turn it on, it doesn't seem to work., If I mess with some parameters, I suddenly start to hear an echo in the right channel. This happens even if I reset to the default.
Actually, all the default patches seem to either not working, or the settings are to subtle, resulting in unnoticeable changes in sound.
3. Sub-patches storage. I created some envelopes today, and much to my surprise, when I recall the envelopes, I just get the default envelope.
4. Stand Alone is crashing. This is the first time I tried it since a very long time, since I usually use VST Host.
It starts by asking to initialize the waveforms, then to store the user waveforms, and then, after some time, I get a message: "An invalid argument was encountered". It then displays a config window, where there are no MIDI inputs (???) and where I can choose the audio. When I click OK, I get the windows message that the program encountered problem and needs to be closed.
I have it installed in a folder in the path "Program Files\KV331 Audio\SynthMaster2" - the same mother folder where there is the previous version, if this matters.
Annoyance: Why is it need for SM to always initialize the wavetable and also loading the user waves every time it is launched? Isn't it possible to create a kind od cache that will remain until we asked the synth to refresh? This way it takes ages to load.
1. Envelopes. There is a problem with the releases. This is particularly notorious in the Ingo Weidner wavetable pacthes. If you hold the key for some moments, and then release it, you hear clearly what seems like a second attack. If you play staccato, then the envelope release works OK.
2. Effects. I messed up with the chorus, and there seems to be some problem. If I turn it on, it doesn't seem to work., If I mess with some parameters, I suddenly start to hear an echo in the right channel. This happens even if I reset to the default.
Actually, all the default patches seem to either not working, or the settings are to subtle, resulting in unnoticeable changes in sound.
3. Sub-patches storage. I created some envelopes today, and much to my surprise, when I recall the envelopes, I just get the default envelope.
4. Stand Alone is crashing. This is the first time I tried it since a very long time, since I usually use VST Host.
It starts by asking to initialize the waveforms, then to store the user waveforms, and then, after some time, I get a message: "An invalid argument was encountered". It then displays a config window, where there are no MIDI inputs (???) and where I can choose the audio. When I click OK, I get the windows message that the program encountered problem and needs to be closed.
I have it installed in a folder in the path "Program Files\KV331 Audio\SynthMaster2" - the same mother folder where there is the previous version, if this matters.
Annoyance: Why is it need for SM to always initialize the wavetable and also loading the user waves every time it is launched? Isn't it possible to create a kind od cache that will remain until we asked the synth to refresh? This way it takes ages to load.
Fernando (FMR)
-
- KVRAF
- Topic Starter
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
I'll look into this weekend. If you can tell me a "specific" preset to debug, that'd be great though.fmr wrote: 1. Envelopes. There is a problem with the releases. This is particularly notorious in the Ingo Weidner wavetable pacthes. If you hold the key for some moments, and then release it, you hear clearly what seems like a second attack. If you play staccato, then the envelope release works OK.
I noticed a problem with the chorus as well last night. I'll debug it further.fmr wrote: 2. Effects. I messed up with the chorus, and there seems to be some problem. If I turn it on, it doesn't seem to work., If I mess with some parameters, I suddenly start to hear an echo in the right channel. This happens even if I reset to the default.
Actually, all the default patches seem to either not working, or the settings are to subtle, resulting in unnoticeable changes in sound.
Just tested, it's working fine. Maybe it's going into a state where it cant load. need to debug further.fmr wrote: 3. Sub-patches storage. I created some envelopes today, and much to my surprise, when I recall the envelopes, I just get the default envelope.
You have version 1.9.9.17, right? Also I'd recommend to wipe out everything, and then extract 1.9.9.17 rar file again.fmr wrote: 4. Stand Alone is crashing. This is the first time I tried it since a very long time, since I usually use VST Host.
It starts by asking to initialize the waveforms, then to store the user waveforms, and then, after some time, I get a message: "An invalid argument was encountered". It then displays a config window, where there are no MIDI inputs (???) and where I can choose the audio. When I click OK, I get the windows message that the program encountered problem and needs to be closed.
I have it installed in a folder in the path "Program Files\KV331 Audio\SynthMaster2" - the same mother folder where there is the previous version, if this matters.
It actually caches once during the first load, but then at exit time it should write to the config file some settings so that it doesnt rebuild waveform/wavetable caches again. Probably in your case the config file can not be written. Do you have "Write access" to Program Files folder on your system? I should probably write writeable files to a place that all versions of Windows (XP, Vista, 7) can write to.fmr wrote: Annoyance: Why is it need for SM to always initialize the wavetable and also loading the user waves every time it is launched? Isn't it possible to create a kind od cache that will remain until we asked the synth to refresh? This way it takes ages to load.
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
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
I did what you advised (wiped out everything except the license key and copied the files from Beta 17) and it still crashes. There is a change although - this time the config window doesn't appear.kv331 wrote:You have version 1.9.9.17, right? Also I'd recommend to wipe out everything, and then extract 1.9.9.17 rar file again.fmr wrote: 4. Stand Alone is crashing. This is the first time I tried it since a very long time, since I usually use VST Host.
It starts by asking to initialize the waveforms, then to store the user waveforms, and then, after some time, I get a message: "An invalid argument was encountered". It then displays a config window, where there are no MIDI inputs (???) and where I can choose the audio. When I click OK, I get the windows message that the program encountered problem and needs to be closed.
I have it installed in a folder in the path "Program Files\KV331 Audio\SynthMaster2" - the same mother folder where there is the previous version, if this matters.
Regarding the patches where there's a noticeable second attack upon release, you can try both "ConplexNS Wavetable Pad". Although there are others, the artifact is specially noticeable in these.
About the caching. I am running on Windows XP and as administrator, so, yes, I am writing permissions to whatever the place. But I have two SynthMaster installations, as to say, since I had to copy everything to a folder inside VSstPlugIns folder of VST Host, toherwise the synth would not work. This may be (or not) related to the fact I can't run the standalone, and therefore never had access to a configuration.
Fernando (FMR)
- KVRAF
- 11162 posts since 16 Mar, 2003 from Porto - Portugal
Just tried in Vista, and everything seems OK (even the cache thing). Problems just happen in my XP machine. Will try in another XP machine tomorrow.
Fernando (FMR)
- KVRAF
- 12145 posts since 13 Mar, 2009 from UK
I can confirm that tuning is correct in 1.9.9.17 in Stand-alone and VST (running under EnergXT2.5.1). Both running on XP system
- KVRian
- 1305 posts since 26 May, 2003 from im müscha...
i try the beta and have no sound
...after the test the old version has no more tone now either...even installation (version 1.0.5.2) has not helped
...no more preset seems to react...cya
<2°TRo²³
<2°TRo²³
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Did you install 1.9.9.17 beta over 1.0.5.2 ?? They are two totally different programs !!tERMoBLUe wrote:i try the beta and have no sound...after the test the old version has no more tone now either...even installation (version 1.0.5.2) has not helped
...no more preset seems to react...cya
<2°TRo²³
For 1.9.9.17 just copy the "Synthmaster2Beta" folder into your vstplugins folder and make a desktop link for the standalone version.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRian
- 1305 posts since 26 May, 2003 from im müscha...
dude, i'm not a noob
...but i have no sound at booth versions now
...even after a complete cleaning of the registry
...what a pity...cya
<2°TRo²³
<2°TRo²³
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Sorry. This problem sounds really strange to me. Doesn't it work both in Standalone and VST version or only one of the two? Maybe you could write which DAW and OS you use.tERMoBLUe wrote:dude, i'm not a noob...but i have no sound at booth versions now
...even after a complete cleaning of the registry
...what a pity...cya
<2°TRo²³
Your problem seems to be quite new/strange so let's see what Bulent from KV331 Audio will say.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
-
- KVRAF
- Topic Starter
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
I am just back from a 2 day break. Will checkout the issues asap.
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
