Sunrizer Mac Version + Windows Version released

[EnGee]

I just noticed something else.

There appears to be 3 morph buttons. The ones on top of and below the mod wheel and the one under where it says rate on the bottom left. On INIT, the one under rate is lit as well as either the one above or below mod wheel depending on the position of my mod wheel.

The third button is to enable/disable the FX morphing (effects) according to what is written beside every effect.

I can turn off the one under rate. I can't turn off the one under or above mod wheel.

So here is what's happening.

When I set a parameter with the mod wheel in the lower position, when I then move the mod wheel to the upper position, that parameter jumps back to where it was originally because I only set a morph for the lower position.

I can't turn the morph off for the mod wheel. That's the problem. So any parameter I move, if I use the mod wheel for that patch, it is going to morph each time I move the mod wheel.

There is no question this is a bug if I can't turn off the morph indicator for the mod wheel.

There must be either state A or B. There is no other state. So, the modulation wheel go from a state to another state (which is the same in any other synth if you assign the modulation wheel in the matrix, right?).

You have state A as the default state. you move the wheel to B then change parameters creating another state. Now you can morph (or using the modulation wheel) between A and B. No need for Midi learn for the morhping. If you want to assign Cutoff, for example, click midi learn and then turn a knobe or fader in your controller. Why do you want to assign it to the modulation wheel other than a knob or a fader? You already have this option in the morphing between A and B.

You're not getting my problem.

Let's say I want to create a patch with a slow attack. I always want the attack to be slow. Are you with me so far? Good.

Now, if I decide that for that patch I also want to use the mod wheel to morph say filter cutoff, which means I have to move the mod wheel from bottom to top, if I do this, the attack slider also moves because I am changing the state from A to B. I don't want the attack slider to move when I move the mod wheel. I want it to stay at the slow attack setting.

So, in order for me to do this, I have to use the Reset Morph A>B function AFTER I move the attack slider from the fast to slow position.

I shouldn't have to do this. It''s an extra step that shouldn't be necessary. That attack slider should stay at slow attack at both A and B states.

That, IMO, is a bug. Things I don't want to morph SHOULDN'T morph when I move the mod wheel.

Understand now?

It seems you are the one don't understand. It is a simple synth which has a morhping from A to B. You can't use this morphing AND other automation because the morphing is overwriting that automation.

From the manual:
"A good practice: Before you start editing parameters make sure the modulation wheel is at minimum (A) position.

Parameters automation works only for state A"

I understand that both can't work together and if you want to use your movements (by mouse or controllers), you should leave the morphing at state A.

[wagtunes]

I just noticed something else.

There appears to be 3 morph buttons. The ones on top of and below the mod wheel and the one under where it says rate on the bottom left. On INIT, the one under rate is lit as well as either the one above or below mod wheel depending on the position of my mod wheel.

The third button is to enable/disable the FX morphing (effects) according to what is written beside every effect.

I can turn off the one under rate. I can't turn off the one under or above mod wheel.

So here is what's happening.

When I set a parameter with the mod wheel in the lower position, when I then move the mod wheel to the upper position, that parameter jumps back to where it was originally because I only set a morph for the lower position.

I can't turn the morph off for the mod wheel. That's the problem. So any parameter I move, if I use the mod wheel for that patch, it is going to morph each time I move the mod wheel.

There is no question this is a bug if I can't turn off the morph indicator for the mod wheel.

There must be either state A or B. There is no other state. So, the modulation wheel go from a state to another state (which is the same in any other synth if you assign the modulation wheel in the matrix, right?).

You have state A as the default state. you move the wheel to B then change parameters creating another state. Now you can morph (or using the modulation wheel) between A and B. No need for Midi learn for the morhping. If you want to assign Cutoff, for example, click midi learn and then turn a knobe or fader in your controller. Why do you want to assign it to the modulation wheel other than a knob or a fader? You already have this option in the morphing between A and B.

You're not getting my problem.

Let's say I want to create a patch with a slow attack. I always want the attack to be slow. Are you with me so far? Good.

Now, if I decide that for that patch I also want to use the mod wheel to morph say filter cutoff, which means I have to move the mod wheel from bottom to top, if I do this, the attack slider also moves because I am changing the state from A to B. I don't want the attack slider to move when I move the mod wheel. I want it to stay at the slow attack setting.

So, in order for me to do this, I have to use the Reset Morph A>B function AFTER I move the attack slider from the fast to slow position.

I shouldn't have to do this. It''s an extra step that shouldn't be necessary. That attack slider should stay at slow attack at both A and B states.

That, IMO, is a bug. Things I don't want to morph SHOULDN'T morph when I move the mod wheel.

Understand now?

It seems you are the one don't understand. It is a simple synth which has a morhping from A to B. You can't use this morphing AND other automation because the morphing is overwriting that automation.

From the manual:
"A good practice: Before you start editing parameters make sure the modulation wheel is at minimum (A) position.

Parameters automation works only for state A"

I understand that both can't work together and if you want to use your movements (by mouse or controllers), you should leave the morphing at state A.

Then this is a glaring oversight and makes this synth useless to me.

I never heard of such an asinine way to program a synth. So I can't use the mod wheel to move filter cutoff from low to high and at the same time keep my attack setting at slow without having to go through the Reset A>B for every parameter I want to stay the same for both A and B states?

That's crazy. That's absolutely crazy. Who programs a synth like this?

At least the IOS version has an A+B state where any changes you make are the same for BOTH states.

How hard would it have been to include this in the Windows version?

Unreal.

[wagtunes]

You know what? Forget it. None of it matters. This thing is so buggy all I did just now was move the filter cutoff while playing my keyboard and it locked up.

When they get most of the bugs out of this thing, maybe then I'll consider purchasing it. Right now, it's a programming and operational disaster.

[EnGee]

It is strange and funny

I knew about this synth because of you in your thread looking for a synth to buy. I checked it back then (just how it looks and sounds because there was no Windows version). I told myself "Nah! I don't need another synth" and I wasn't so positive while you were positive about it and waiting for it.

Now we stand at the opposite sides!

I think the reason is I don't have iPad, so I just first tried the Windows version which I like and understood the limitations (which doesn't bother me really). You on the other hand is comparing it to the iPad version and expected the Windows version to be even better maybe or at least equal to iPad.

btw, I don't have yet any problem with its stability inside Studio One, but I didn't try it yet in Cubase.

[bftucker]

Yep. Strange until you get to know him but always funny.

And "forget it" and "none of it matters" is excellent advice.

Meanwhile, enjoy!

[Robmobius]

Yep. Strange until you get to know him but always funny.

And "forget it" and "none of it matters" is excellent advice.

Meanwhile, enjoy!

More funny 'weird' as opposed to 'Ha ha'.

[dwozzle]

If I'm understanding what you're saying (haven't played with Sunrizer yet), this morphing limitation sounds similar to Morphox, where you can't unhook the mod wheel from morphing. You can have it do other things in addition, but it will always do that.

It is a annoying and IMO short-sighted limitation that I hope will be removed at some point, but I still enjoy Morphox very much.

[wagtunes]

If I'm understanding what you're saying (haven't played with Sunrizer yet), this morphing limitation sounds similar to Morphox, where you can't unhook the mod wheel from morphing. You can have it do other things in addition, but it will always do that.

It is a annoying and IMO short-sighted limitation that I hope will be removed at some point, but I still enjoy Morphox very much.

So there are other synths that have this limitation?

Interesting. This is the first one I ran into.

And for the record, I still love the sound of this synth. That is why i am so annoyed at the bugginess and the quirkyness of the morph feature.

I may yet end up getting it anyway someday. That's how much I love the sound.

[bftucker]

Buggy?

You keep using that word. I do not think it means what you think it means.

If it works as intended, then it is a feature! What you call its quirkiness is part of its character, though you may wish it were different. If you are waiting for it to become a different synth, then I am afraid (and hope) you can add it to your list of outstanding disappointments since I like it the way it is.

[phdsg vn chfhn]

typo in "utils" drop-down: swap morph gorups

[wagtunes]

Buggy?

You keep using that word. I do not think it means what you think it means.

If it works as intended, then it is a feature! What you call its quirkiness is part of its character, though you may wish it were different. If you are waiting for it to become a different synth, then I am afraid (and hope) you can add it to your list of outstanding disappointments since I like it the way it is.

No, it's buggy. No question about it.

Turned filter cutoff while playing keyboard and keyboard froze. Stuck notes. Sound totally cutting out with no apparent cause (keyboard not frozen) and needed to reload VST.

I'm glad you like it the way it is. And I can learn to live with the awkward programming (though Beepstreet just confirmed that they are considering putting A+B mode back in at a later update) but what I can't live with is a plugin that forces me to either reload it or completely restart my DAW every 10 minutes.

Yes, it's buggy.

[itoa]

Could you drop an email to info@beepstreet.com with short description - Windows version, DAW, buffer settings, sample rate, test case ?

Its our first plug on Windows. Its been heavily tested, but as I see there are still some issues on certain configurations. We will do our best to fix it asap.

[andrew71]

How long before the introductory offer ends? It would be nice if it lasted until at least the end of the month...

[itoa]

It will be

[wagtunes]

Could you drop an email to info@beepstreet.com with short description - Windows version, DAW, buffer settings, sample rate, test case ?

Its our first plug on Windows. Its been heavily tested, but as I see there are still some issues on certain configurations. We will do our best to fix it asap.

I'll be happy to do this. Honestly, not sure where to find buffer settings and sample rate info. It's Cubase 7.07 and it's been a very long time since I've needed this info and don't remember where it is stored. Test case. I'll need to go back and try to recreate as I don't remember the exact steps for each problem. I only have an overall experience report that I can give. So it's going to take some time for me to get all this info to you.