Sunrizer Mac Version + Windows Version released

[wagtunes]

So...what do you think?

(I am surprised by the lack of response)

Honestly, I'm a little disappointed. Mostly in the MIDI learn feature. Without any mention in the manual, it took forever to figure out how to use it. The process is not at all intuitive. It doesn't work the way you'd expect. You essentially have to map two points, say using mod wheel. You map one point with the mod wheel in the upper position and then you map another point with the mod wheel in the lower position and you have your mod range. At least that's how it works in my DAW.

The sound is fine and the GUI is simple and easy to navigate. But right now, and this is the biggest part for me, Windows 64 bit is buggy as hell. I guess I should have expected this but wow. I mean this is really bad. With one patch, after assigning MIDI learn to JUST the mod wheel for filter cutoff, suddenly resonance and ADSR started going crazy when I moved the mod wheel.

So yeah, it has bugs that need to be addressed. Until they are, I don't think I'll be investing in it. I'd rather pay $80 for the relatively bug free version than $50 for something that, right now, is just about usable.

[juffi]

I am quite impressed with the sunrizer, totally love the sound (have it on ipad as well) , even better than sylenth1 imho. Filters are killer and that sound is rich and lush. What is completely overwhelming is the ultra low cpu comsumption. Never saw this low cpu in AGES!!! Couldnt believe my eyes , CPU meter is looking like 1% in Cubase. Only polyphonic pads will rise CPU of course.

Midi learn works as expected. Nice thing is morphing and that arpeggiator. My new #1 sylenth1 replacement and definitely 100% buy.

One problem i encountered several midi hang notes. Maybe a demo problem? Cubase 8 pro, Win 7 64bit.

[EnGee]

Bought!

I won't bore you with how/why this synth is great! Instant buy for just 10 mins demo for someone doesn't need any more synth tells a lot

[bftucker]

So...what do you think?

(I am surprised by the lack of response)

Honestly, I'm a little disappointed. Mostly in the MIDI learn feature. Without any mention in the manual, it took forever to figure out how to use it. The process is not at all intuitive. It doesn't work the way you'd expect. You essentially have to map two points, say using mod wheel. You map one point with the mod wheel in the upper position and then you map another point with the mod wheel in the lower position and you have your mod range. At least that's how it works in my DAW.

The sound is fine and the GUI is simple and easy to navigate. But right now, and this is the biggest part for me, Windows 64 bit is buggy as hell. I guess I should have expected this but wow. I mean this is really bad. With one patch, after assigning MIDI learn to JUST the mod wheel for filter cutoff, suddenly resonance and ADSR started going crazy when I moved the mod wheel.

So yeah, it has bugs that need to be addressed. Until they are, I don't think I'll be investing in it. I'd rather pay $80 for the relatively bug free version than $50 for something that, right now, is just about usable.

I am not surprised. Unless you are familiar with the original IOS version, the way Sunrizer works might be confusing initially. And if you are finding it '"buggy as hell" then, yes, invest your money elsewhere.

As for me, i like Beepstreet and his apps and I am confident that, though this may be his first venture into the wild world of Windows, he will solve any problems. EDIT: FWIW I have been using the demo as a standalone with Savihost 64 and have yet to encounter any bugs.
I think it's worth "investing" in...just need to raise the capital. Until then, I dream of reaping rich dividends in sonic pleasure.

[echopark]

Why there´s no pitch wheel on the plugin versions ? Do I miss something ?

There´s only 36 presets in the demo. Does the fullversion have more ?

[echopark]

Found it ! There are more Presets when you select a different bank.

[elassi]

With one patch, after assigning MIDI learn to JUST the mod wheel for filter cutoff, suddenly resonance and ADSR started going crazy when I moved the mod wheel.

Sounds like you had the morphing enabled (see the lits at the top and bottom of the modwheel image in the UI)...

[wagtunes]

With one patch, after assigning MIDI learn to JUST the mod wheel for filter cutoff, suddenly resonance and ADSR started going crazy when I moved the mod wheel.

Sounds like you had the morphing enabled (see the lits at the top and bottom of the modwheel image in the UI)...

If that's the case, I have no idea how I enabled it. I took a blank INIT patch, moved the filter cutoff to make position and mod wheel all the way up and set that, then I moved the filter cutoff to the lowest position and the mod wheel all the way down and set that. For a while, everything was fine and then suddenly Res and ADSR started going crazy. So if I enabled morphing I did it via telepathy.

I'll try it again this morning and see if I can duplicate the problem.

[wagtunes]

Okay, here are the exact steps that I just took.

Step 1) Started DAW.

Step 2) Loaded Sunrizer

Step 3) Set patch to INIT

Step 4) Set filter 1 to LP.

Step 5) Moved filter 1 cutoff to max position.

Step 6) Moved mod wheel up to top position.

Step 7) Turn on MIDI Learn.

Step Clicked on Filter 1 cutoff.

Step 9) Moved mod wheel.

Step 10) Clicked off MIDI Learn.

Tested to make sure mod wheel moved filter cutoff from low to high setting. So far so good. Nothing else moving.

Repeated steps 4 - 10 for filter 2, using Formant.

Tested to make sure mod wheel moved both filter cutoffs from low to high setting.

Now, I then moved the res dials for both filters from low to mid way. I made sure the MIDI Learn light was off when i did this. It was.

When I did this and started moving the mod wheel, the res dials moved from low end to mid way as if the MIDI Learn was still on and I had highlighted both res dials and did a learn maneuver.

I then had to actually do a MIDI Learn for both res dials to get them to stay where I wanted.

There is no question this is a bug.

[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.

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.

[wagtunes]

Chord function also doesn't record properly. No matter what chord I play, it plays back a major 7. I tried major, minor, augmented, doesn't matter. I get the same chord played back no matter what I do.

I have to wonder how much they really tested this for Windows before they put it out there.

Very disappointed.

[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.

[wagtunes]

Here are the instructions right out of the manual.

→ Hold the CHORD button with one finger and press all piano keys that you want to store
in chord memory.

I use a mouse on Windows but that's not the problem. In Windows, the order of operations is wrong.

You have to play a chord and THEN click the Chord button. I finally figured this out after trying every other logical thing I could think of.

A manual for Windows needs to be printed if it's different in functionality from the IOS version.

Using the correct order of operations, this now appears to work.

FTR, this synth sounds great.

[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?

[wagtunes]

Also discovered a major difference between IOS and Windows version (just found what there is of the Windows manual)

IOS actually has an A+B state so that all changes you make are the same for both states and they even suggest you use this setting if you don't want any morphs other than just a few.

The Windows version has no such setting. You get A or B but not both. So the only way to keep the same setting for a parameter for both states is to set it for state A and then use the Reset A>B function to keep it for state B.

If you ask me, this is a glaring oversight and a royal PITA when programming.