Synth1: Bug Reports/Feature Suggestions
-
- KVRAF
- 6241 posts since 26 Sep, 2003 from right here, as you can see ...
hakey,
please add this into the bug report section:
http://www.kvraudio.com/forum/viewtopic ... 78#4080678
please add this into the bug report section:
http://www.kvraudio.com/forum/viewtopic ... 78#4080678
regards,
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
-
- KVRAF
- 3499 posts since 9 Oct, 2004 from Poland
Well...DragonSagoth wrote:128 is kinda unnecessary for this type of synth... 32 is very decent, 64 would be just right.
I like unison
[====[\\\\\\\\]>------,
Ay caramba !
Ay caramba !
-
- KVRAF
- 1763 posts since 1 Aug, 2006 from Italy
I think it would work.Purity Lied wrote:I don't knowhakey wrote: RE: the trancegate idea - wouldn't having a step sequencer available as a mod source achieve the same thing by routing it via the matrix to Env Gain?
As long as it gets the trance gate effect, I'm good.
For a *really simple* gating effect, you could just route a lfo to amp, using a square waveform, set the speed to what you need, maybe sync it to your song tempo (sync it to key if you want it the gate to be retriggered when you play a new note, too) and you get simple pattern... I never tried using two lfo with different speed to get a little bit more more complex pattern, I don't even know if it would work (I only know that I could use the lfo modulation for more interesting modulation than just affect amplitude).
A trance gate, or a routable step sequencer, would be much more appropiate (the step sequencer would open great sound possibilities), but a really simple gating effect has been possible for a long time with the current features.
...
I love synth1, I miss it so much on mac.
-
- Pick Me Pick me!
- 10234 posts since 12 Mar, 2002 from a state of confusion
Same here.. cranking up unison right now with 32 voices means you can only play a couple of notes at a time.. 64 would be nice.. unlimited even better..Mutant wrote:Well...DragonSagoth wrote:128 is kinda unnecessary for this type of synth... 32 is very decent, 64 would be just right.
I like unison
- KVRian
- 1188 posts since 24 May, 2006 from Our Amazing Oasis in Space - USA Section
Not sure if this info is about actual bugs, or just important preferences...
The patch selection screen might be a bit too small. It's now about 730points tall by 635points wide. I think it would be far better if the screen was more like 880points wide to allow far more of the patch name to show.
Also, the current font used for the patch selection screen is about 14 points (which is great for these tired old eyes, but...). I suggest using a 12point or 11point narrow font like Arial Narrow or Helvetica Narrow to improve patch name lengths.
The GUI shows about 22 characters for patch names. It would be preferable if the patch selection screen could show the same, or as close as possible.
It would also be great if the patch names in the patch selection screen could show the descenders (the part of the lower case characters that goes below the baseline) for increased legibility! (right now, "very good organ" = "verv aood oraan")
I'd also love to see more than the 7 colors now available for patch IDing - 16 or 32 would sure be nice and help in classifying patch types.
OK so this all about typefaces and patch names and IDs, which might seem trivial, but I know these changes would make a big difference to me in the day-to-day use of this great synth!
Thanks as always Daichi!
場合は、この情報は、実際のバグか、単に重要な条件であることを確認しない...
パッチの選択画面は少し小さすぎるかもしれません。今では635pointsで730points高さは約幅です。私は、画面は[bのように] 880pointsワイド[/ b]はこれまでのパッチ名の表示にもっとできるようにした場合、それははるかに良いと思います。
また、現在のフォントは、パッチの選択画面に使用される約14点(偉大な、これらの疲れ古い目ですですが、...).私は MS Pゴシック絞込みやHelvetica絞込み[/ b]のように/ b]のパッチ名の長さを改善するために狭いフォント[を11point b] 12pointまたは[を使用してお勧めします。
GUIはパッチ名の約22文字を示します。パッチの選択画面で、または同じ可能な限り近いを見ることができればそれが望ましいだろう。
パッチの選択画面でパッチ名がbの[編集]できればまた、素晴らしいことだ)に増加読みやすくするため/ b]の(ベースラインを下回ると小文字の一部ディセンダの[を見る! (今のところ、"非常に良い臓器"="vervのaoodのoraan"):)
私も7色今パッチのIDing可能 - 16または32は確かにいいだろうとパッチの種類を分類するのに役立つ以上を見てみたい。
[OK]をので、このすべてについて書体とパッチの名前とID、些細なように見えるかもしれませんが、私はこれらの変更を私に、この偉大なシンセの日々の使用には大きな違いを生むと知っている! :)
としていつもありがとう大地!
SciFiArtMan
The patch selection screen might be a bit too small. It's now about 730points tall by 635points wide. I think it would be far better if the screen was more like 880points wide to allow far more of the patch name to show.
Also, the current font used for the patch selection screen is about 14 points (which is great for these tired old eyes, but...). I suggest using a 12point or 11point narrow font like Arial Narrow or Helvetica Narrow to improve patch name lengths.
The GUI shows about 22 characters for patch names. It would be preferable if the patch selection screen could show the same, or as close as possible.
It would also be great if the patch names in the patch selection screen could show the descenders (the part of the lower case characters that goes below the baseline) for increased legibility! (right now, "very good organ" = "verv aood oraan")
I'd also love to see more than the 7 colors now available for patch IDing - 16 or 32 would sure be nice and help in classifying patch types.
OK so this all about typefaces and patch names and IDs, which might seem trivial, but I know these changes would make a big difference to me in the day-to-day use of this great synth!
Thanks as always Daichi!
場合は、この情報は、実際のバグか、単に重要な条件であることを確認しない...
パッチの選択画面は少し小さすぎるかもしれません。今では635pointsで730points高さは約幅です。私は、画面は[bのように] 880pointsワイド[/ b]はこれまでのパッチ名の表示にもっとできるようにした場合、それははるかに良いと思います。
また、現在のフォントは、パッチの選択画面に使用される約14点(偉大な、これらの疲れ古い目ですですが、...).私は MS Pゴシック絞込みやHelvetica絞込み[/ b]のように/ b]のパッチ名の長さを改善するために狭いフォント[を11point b] 12pointまたは[を使用してお勧めします。
GUIはパッチ名の約22文字を示します。パッチの選択画面で、または同じ可能な限り近いを見ることができればそれが望ましいだろう。
パッチの選択画面でパッチ名がbの[編集]できればまた、素晴らしいことだ)に増加読みやすくするため/ b]の(ベースラインを下回ると小文字の一部ディセンダの[を見る! (今のところ、"非常に良い臓器"="vervのaoodのoraan"):)
私も7色今パッチのIDing可能 - 16または32は確かにいいだろうとパッチの種類を分類するのに役立つ以上を見てみたい。
[OK]をので、このすべてについて書体とパッチの名前とID、些細なように見えるかもしれませんが、私はこれらの変更を私に、この偉大なシンセの日々の使用には大きな違いを生むと知っている! :)
としていつもありがとう大地!
SciFiArtMan
- KVRAF
- 4807 posts since 10 Feb, 2006 from Stockholm, Sweden
This got me laughing a bit, but yeah that is a problem with Synth1, and as for more colors to ID patches I fully agree."very good organ" = "verv aood oraan"
- KVRAF
- 24404 posts since 7 Jan, 2009 from Croatia
+1 on changing fonts/reskinning the GUI! 
- KVRAF
- 2841 posts since 23 Feb, 2004 from Planet Earth...for now
Great suggestions so far.
Whatever Diachi chooses to do I hope backward compatability remains no 1 priority, as some of these suggs, although good, could make Synth1 into another synth, but as long as old presets continue to sound the same - no problem.
My simple wishes are:
1. Velocity scaling on filter section (like amp section) rather than on/off
2. LFO control settings like on Roland Jup-8, esp delay/fade in.
Whatever Diachi chooses to do I hope backward compatability remains no 1 priority, as some of these suggs, although good, could make Synth1 into another synth, but as long as old presets continue to sound the same - no problem.
My simple wishes are:
1. Velocity scaling on filter section (like amp section) rather than on/off
2. LFO control settings like on Roland Jup-8, esp delay/fade in.
- KVRAF
- 7018 posts since 19 Apr, 2002 from Utah
I'm with you on the compatibility thing. I would like forward compatibility (continued support for the latest hosts and OS systems), while maintaining backward compatibility with patches. To me, these two are the most important for Synth1's longevity.1-2-Many wrote:Great suggestions so far.
Whatever Diachi chooses to do I hope backward compatability remains no 1 priority, as some of these suggs, although good, could make Synth1 into another synth, but as long as old presets continue to sound the same - no problem.
My simple wishes are:
1. Velocity scaling on filter section (like amp section) rather than on/off
2. LFO control settings like on Roland Jup-8, esp delay/fade in.
All other additions are extra bonuses.
--Sean
-
- KVRist
- 37 posts since 26 Oct, 2008 from Finland
A (minor) bug introduced in the new version:
Unison voicing depends on the voices' absolute position instead of the position inside a unison.
This causes glitches if the number of voices isn't a multiple of the unison number. Sometimes the voice number wrap around to 0 inside one note, and the unison values after the wrap will be those belonging to the start of the unison.
It seems the voicing currently works somewhat like this (probably far from how it's actually structured, but i mean functionality):
Corrected behavior would be to use i where j is now, and skip the j = current_voice % num_unison;.
EDIT: steps to reproduce buggy behavior:
0. choose a simple patch - like raw sawtooth
1. set total voice count to 4
2. set unison number to 3
3. set unison pitch shift to -12 (or anything besides 0)
4. play the same note repeatedly - and every 4th note lacks the sub-octave partial)
EDIT2: bug in my bug report
Unison voicing depends on the voices' absolute position instead of the position inside a unison.
This causes glitches if the number of voices isn't a multiple of the unison number. Sometimes the voice number wrap around to 0 inside one note, and the unison values after the wrap will be those belonging to the start of the unison.
It seems the voicing currently works somewhat like this (probably far from how it's actually structured, but i mean functionality):
Code: Select all
start_note(note, vel) {
current_voice = get_next_unused_voice();
for (i = 0; i < num_unison; i++) {
j = current_voice % num_unison;
freq = get_freq_for_notenumber(note + get_unison_shift(j)) * get_unison_detune(j);
pan = global_pan + get_unison_pan_shift(j);
start_voice(current_voice, freq, vel, pan);
current_voice++;
current_voice %= num_voices;
}
}
EDIT: steps to reproduce buggy behavior:
0. choose a simple patch - like raw sawtooth
1. set total voice count to 4
2. set unison number to 3
3. set unison pitch shift to -12 (or anything besides 0)
4. play the same note repeatedly - and every 4th note lacks the sub-octave partial)
EDIT2: bug in my bug report
Last edited by orbik on Sun May 23, 2010 5:17 pm, edited 1 time in total.
-
- KVRAF
- 6241 posts since 26 Sep, 2003 from right here, as you can see ...
yes, someone should do that ... however, it could be that he kinda lost interrest, seeing his old thread evolving typical kv-like ... let's hope he didn't ...surfingo wrote:Is Daichi aware of this topic? Maybe someone should write him a mail explaining that there's another topic for synth1, just guessing
regards,
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
- KVRAF
- 2458 posts since 18 Jun, 2008 from "nunya"....
Copied from the other thread:
http://www.kvraudio.com/forum/viewtopic ... 32#4103732
1 It corresponded to an external bank (ZIP file).
* It came to be able to read the ZIP file that compressed the .sy1 file.
* It comes to be able to select it from the patch selection window of Synth1 only by putting the zip file on the external bank folder (default is "zipbank").
* Two or more folders can be included in one zip file with the hierarchy.
* It is not possible to write it in an external bank. It is only for reading.
2 The preservation place of the set up information was changed from the Windows registry to the ini file.
* The event that the set up information was not preserved on 64bit OS or it was not possible to refer occurred. I think this event to be ameliorable.
* Therefore, when the setting of existing Synth1 is succeeded, it is necessary to execute set succession tool (reg2ini,exe).
* The reference) The ini file is "APPDATA\Daichi\Synth\synth1.ini" .
3 GUI
* The method of selecting the bank in the patch selection window corresponding an external bank was changed to the tree view form.
http://www.kvraudio.com/forum/viewtopic ... 32#4103732
Version History List:daichi1969 wrote:Good morning, everyone!
I released Synth1 V1.12 just now.![]()
Please check it in the following.
http://www.geocities.jp/daichi1969/softsynth/index.html
best Regards,
1 It corresponded to an external bank (ZIP file).
* It came to be able to read the ZIP file that compressed the .sy1 file.
* It comes to be able to select it from the patch selection window of Synth1 only by putting the zip file on the external bank folder (default is "zipbank").
* Two or more folders can be included in one zip file with the hierarchy.
* It is not possible to write it in an external bank. It is only for reading.
2 The preservation place of the set up information was changed from the Windows registry to the ini file.
* The event that the set up information was not preserved on 64bit OS or it was not possible to refer occurred. I think this event to be ameliorable.
* Therefore, when the setting of existing Synth1 is succeeded, it is necessary to execute set succession tool (reg2ini,exe).
* The reference) The ini file is "APPDATA\Daichi\Synth\synth1.ini" .
3 GUI
* The method of selecting the bank in the patch selection window corresponding an external bank was changed to the tree view form.
KVR >Gear Slutz! Change my mind! 
- KVRAF
- Topic Starter
- 5234 posts since 25 Feb, 2008
I think orbik's unison voice bug has been sorted in the latest release - can anyone confirm this, before I remove it from the bug report list? And if any of the other bugs have been fixed please let me know.
