SynthMaster 2.0.3.3 - Post bugs here!

[rectus_dominus]

Bulent, could you reproduce the freezing bug I previously mentioned? You know, the one I did while forging a hypersaw patch.
Synthmaster is getting more and more stable by the way. Tomorrow I'll toy around with some d&b and dubstep sounds to hear the lower end.

Just a note: When using maximum cutoff for example a LP filter, it is rather disturbing to see the visual 'disappear'

[kv331]

Bulent, could you reproduce the freezing bug I previously mentioned? You know, the one I did while forging a hypersaw patch.
Synthmaster is getting more and more stable by the way. Tomorrow I'll toy around with some d&b and dubstep sounds to hear the lower end.

Just a note: When using maximum cutoff for example a LP filter, it is rather disturbing to see the visual 'disappear'

No I couldnt reproduce it yet. I can fix the visual though!

[rectus_dominus]

Btw, is it possible to do "glowing" things in the gui?
The Nexus's dark-gold gui is really inspiring, those Glowing Leds...

[Hlis93]

[quote="rectus_dominus"]Btw, is it possible to do "glowing" things in the gui?
The Nexus's dark-gold gui is really inspiring, those Glowing Leds... [quote]

It really depends on what you want to do. You can add anything you want into the editor. It depends on what you make and how you want to organize it. If you look at Bulent's post of the defualt GUI in the editor you will see a skin that is easier to change the color of.

Of course there are certain problems and limitation that come with a gui that you like but want to change part of it most of which has to do with sort through layers and finding that thing you want to change or groups of thing that you will need to change. Say for example that you like the GUI that I'm doing but wanted a different color for a part of something like the lcd type readout area on the nexus pictre. You would have to to go into the Skinman file and change all of this layer by layer, export the image and then load it into the GUI editor in the correct place. It depends on how much you want to change that could make it slow going. For example on of the layers area only that I have for the GUI it has 100+ layers that you would have to change to do this, you have to change the the color of and the opacity etc etc. I made a quick example, on the left is my version and on the right I just spent about 10 min changing to it to another color. I only did a very a small part so I could take a screenshot to edit. To achieve a very spefic look you would certainly spend a great deal more time, it would also require knowledge of Skinman.



Here an screenshot of the tree in skinman from one of the partial mock ups that I did, the GUI has grown since then, yet I have also organized it so that managing it should be easier for those that find themselves wanting to edit part of it.

[rectus_dominus]

o.O that's many :O
How many alternative skins will you include in the first skinned version of Synthmaster?

[acousticglue]

Btw, is it possible to do "glowing" things in the gui?
The Nexus's dark-gold gui is really inspiring, those Glowing Leds...

I don't know but I like this skin with the LED style. Nice.

[Lotuzia]

Hi Bulent

In version 2.....25 I had some major bugs under Cuabase while browing the presets. Sometimes the presets would just go silent ( then sometimes the sound returns if I use many times the previous/next gui arrows), and sometimes it would just crash my host and pc thoroughly

I dont know if it can be related to the fact that I maintained my old personal preset folder in the install folder.

Some presets might be duplicated if they exist under different versions in different folders ? (As you cant see the folders in the preset browser)

Else a lot of patches (including mine that you added in a precedent version, but not only these ones ) are heavily clipping in all my hosts ( Including Cubase aso). Sometimes they'll clip when you play a single note, and more than often when you play a simple 4 note choed at full or even medium velocity.

My personal opinion is that these minor details should be fixed before too much people make tracks with the synth and the clipping instruments.

Also Cubase doesnt retain the patch when the plug is disabled/enabled. When you enabke the plug again the default patch is present/playing. Also Cubase doesnt show the right selected preset name : It always displays the default preset name.

Besides of this all is cool

Cheers,

LtZ

[Xenos]

***Bug Report***

I've experienced sounds cutting off in mono legato mode when applying an envelope to the filter. You can run through my current bank update I submitted, particularly in the basses category, and you'll see some occasional odd behavior when playing a run of 16th notes.

BTW, Hils93, that little GUI snippet looks NIIIICE! . Man, this is gonna be a HUGE improvement over the previous version's look.

[rectus_dominus]

Easy controls don't work for me (using two layers) I mapped the two layer's cutoff to EZ1 and it does nothing
Layer 2 visuals don't show themselves
Changing resampling can alter the skin (no shadows when using 2x and 3x resampling, some buttons are misplaced and stuff)
When changing presets, the Ableton's little preset window still shows the initial starting patch (tension seq)
EQ isn't working properly, once used it emits a really high output volume with crackles and stuff (I was using a 2osc 2filtered (LP+AP) detuned saw preset). Also, after that the synth keeps having a constant output sound (not hearable)

Just a feature-request. The resonance knob needs to have a narrower scale. It can go whistle with only a few percents.

(Btw the saw has a strange digital 'chipping' sound in the lower octaves)

[Hlis93]

Btw, is it possible to do "glowing" things in the gui?
The Nexus's dark-gold gui is really inspiring, those Glowing Leds...

I don't know but I like this skin with the LED style. Nice.

well, thats why there is GUI editor.

Perhaps instead of making a 2nd completely different skin which I was planing on I should create different color options.

Heres an example of the osc which I was working on this morning, 2 versions of each...

[rectus_dominus]

It's good to have color options. In my opinion, a skin is complete when it has these.

[seismic1]

Just ran through all presets with SM2 stand-alone Beta25. No crashes when switching between them! I'll have a play with the VST tomorrow.

I think it's time to go public about SM2! Just missing the screenshot for the new GUI for the press releases

And the "EQ on Layer2 -> Mute" - Bug...

Tried all presets with Beta25 VST running in EnergyXT2.5.1 - no crashes whilst just playing with the presets, but after I finished I decided to play with the TG Classic Trancegate preset. I clicked on SM2 in EnergyXT to activate the SM2 Gui and XT2 crashed. I also had to unload the Oxygene 49 and Pod UX2 drivers. No reboot required I think that even with this crash, this represents a big improvement in stability measured against earlier versions. I don't have a clue how to reproduce this (short of another 2 hours spent going through all of the presets).

Which other seqeuncers have been tested so far?

[kv331]

Hi Bulent
Else a lot of patches (including mine that you added in a precedent version, but not only these ones ) are heavily clipping in all my hosts ( Including Cubase aso). Sometimes they'll clip when you play a single note, and more than often when you play a simple 4 note choed at full or even medium velocity.

My personal opinion is that these minor details should be fixed before too much people make tracks with the synth and the clipping instruments.

Also Cubase doesnt retain the patch when the plug is disabled/enabled. When you enabke the plug again the default patch is present/playing. Also Cubase doesnt show the right selected preset name : It always displays the default preset name.

Besides of this all is cool

Cheers,

LtZ

Thanks Laurent!

As for Cubase 5 not retaining settings: I cant debug that as I dont have Cubase But maybe we can debug the issue by turning debugging on from the SynthMasterConfig.txt file. I might ask for some help on this.

As for clipping: I think you are experiencing this as you have duplicate presets. I normalized almost all of the preset that we distribute with SM2. For mono sounds I normalize around -4 dB max, for poly sounds: I play 3 voice C Major Chord and again normalized the max around -4 dB. Does that sound right?

[kv331]

***Bug Report***

I've experienced sounds cutting off in mono legato mode when applying an envelope to the filter. You can run through my current bank update I submitted, particularly in the basses category, and you'll see some occasional odd behavior when playing a run of 16th notes.

BTW, Hils93, that little GUI snippet looks NIIIICE! . Man, this is gonna be a HUGE improvement over the previous version's look.

Hi Brian,

I actually noticed that one yesterday as well and made an internal bug entry in my database for that Hopefuly I'll fix it tonight.

[kv331]

Easy controls don't work for me (using two layers) I mapped the two layer's cutoff to EZ1 and it does nothing

My bad: I set the default modulation for EZ parameters to MIDI CC 22-29. Try setting modulator for EZ controls to nothing, then it'll work.

Layer 2 visuals don't show themselves

Will fix that with the new GUI.

When changing presets, the Ableton's little preset window still shows the initial starting patch (tension seq)

I'll probably fix this one when I have time in the next week. Just delaying it as it's a low priority bug for me.

EQ isn't working properly, once used it emits a really high output volume with crackles and stuff (I was using a 2osc 2filtered (LP+AP) detuned saw preset).
Also, after that the synth keeps having a constant output sound (not hearable)

Will debug that. For me EQ works OK, and also Martin's presets has a lot of EQ they work just fine.

Just a feature-request. The resonance knob needs to have a narrower scale. It can go whistle with only a few percents.

Try lowering the Distortion. I should set its default value to zero actually.

(Btw the saw has a strange digital 'chipping' sound in the lower octaves)

I think it's time to increase the default wavetable size to 2048 from 1024. That should help us. Will do it this week.

Bulent