SB404 - Step Editor not working properly

[rhythmaster]

Hi!

Has anyone discovered this also??
I'm able to make changes in the Editor but they don't take effect .....

Switching presets also doesn't work ...

And many of the Main-Presets from Sb 404 also have the same sequences ...
somethings wrong ....

SONICCORE Please!!!!!!!!!!!!!!!!!

System: Windows 7, latest SCOPE v5.1.2709 32 Bit

Thanks
Harry

[pwhitmaker]

Yes, I noticed this also just the other day.
Strange.

[Mr Arkadin]

A few of the presets do have the same sequence Presets 3 & 4 and 19 & 20 for example. Make sure you haven't got Freeze Preset enabled in the Step Editor.

Other than that I can't say what it could be as I've not had any problems and I used it extensively to make some new presets so I think I would have noticed. I'm on Scope 5.0 so maybe that has something to do with it.

[HUROLURA]

Also noticed this while making some rapid test the other day with the Xite-1 and scope 5.1.
Never tested this device before but the scope synth preset thread made me open it for the first time.
I was quickly tempted to play with the built-in stepseq but this "feature" prevented me to go further.
Something to check for you SC wizards ...

[rhythmaster]

I wrote a mail to S|C to check this behaviour.

Hopefully we'll get a patched SB 404 for 5.1.2709

Harry

[Mr Arkadin]

So is this a Scope 5.1 bug but OK in 5.0?

[jksuperstar]

I don't have 5.0 accessible for a bit. Can someone post the SB404.dev and we can see if it was just a bad .dev file?

[edit] - forgot to say, that I have the same problem in 5.1 32bit Win XP sp3.

[nitri]

any solution?

[rhythmaster]

I dont understand why SONICCORE doesnt fix this. It's a fantastic plugin.
What are they waiting for? I cant use it for over one year!!!!!
Why cant there be a patch - why?

Will it be out with Scope 6 (any release date for this??)

THX

[next to nothing]

AFAIK they stopped fixing plugins months/years ago, and i don't think anything will change until Scope 6 (and i am not saying they will suddenly start working then either).
SC haven't indicated any timeline for scope 6, but if I am not mistaken V5 was released early 2009, V5.1 was released late 2010 or similar and is still like a beta-release, so things doesn't move fast around there.

I'd be positively surprised if we see any Scope 6 related releases this year. In example, when they introduced scope 6 they collected mail adresses from people who wanted more info or wanted to participate in beta. they have not communicated anything since then, so i guess they haven't even reached beta stage yet.

[rhythmaster]

Thanks for the info.

So then I expect Scope 6 to be a giant step for the platform for me with total integration in a sequencer e.g. Cubase with no
"hanging notes" and stuff like that and within this year ...

[Casper]

And to make things worse:
The step sequencer in WC Pro~One isn't working
The step sequencers in the Modular are'nt working.
The step sequencers in the whole 5.1 Scope are dead as can be.

Another big bug and has nothing to do with the devices it self. Rather the modules at the core are just not working.
You'd say this would be an easy fix since you'd be fixing all the devices at once if one fixes this module.

A well, waited a year already, but no updates fixes or the so called Revolution is taking place.
No communication on the Sonic core Website.
What a horrible situation this realy is.

[rhythmaster]

And to make things worse:
The step sequencer in WC Pro~One isn't working
The step sequencers in the Modular are'nt working.
The step sequencers in the whole 5.1 Scope are dead as can be.

Another big bug and has nothing to do with the devices it self. Rather the modules at the core are just not working.
You'd say this would be an easy fix since you'd be fixing all the devices at once if one fixes this module.

A well, waited a year already, but no updates fixes or the so called Revolution is taking place.
No communication on the Sonic core Website.
What a horrible situation this realy is.

Totally agree!

[rhythmaster]

An critical issue with extent should be solved within a week.
Here is nothing within 1,5 years.

Hey. What's going on?

I need the Sb404

[garyb]

sorry, it just doesn't work like that.

it's not fundimentally broken. Mattomatt works. those plugins' sequencers are broken. this will be addressed in v6, which should benefit v5 users as well.

[rhythmaster]

It's no matter of v5 v6 etc.
The fact is sb404 doesnt work well since v5.1 (1,5 years ago) and no fix.

Give me v6 whatever and dont announce a revolution when you're not able to do your homework. I'm the greateat fan of SC. I love the system and idea but some important things the misinformation and partly chaos drives me crazy.
So for the 65th time:

"when will v6 be out"

Thanks.

[Fluxpod]

And to make things worse:
The step sequencer in WC Pro~One isn't working
The step sequencers in the Modular are'nt working.
The step sequencers in the whole 5.1 Scope are dead as can be.

Another big bug and has nothing to do with the devices it self. Rather the modules at the core are just not working.
You'd say this would be an easy fix since you'd be fixing all the devices at once if one fixes this module.

A well, waited a year already, but no updates fixes or the so called Revolution is taking place.
No communication on the Sonic core Website.
What a horrible situation this realy is.

+1 Thats what keeps me from Upgrading.Its working in v5 but there are also some very annoying bugs that are present since....2007 or so.
I want to go 64 bit someday,not pressing but i really like win7.
And i wont pay 129€ for a broken update from v5.
Those are simple fixes....its basic interface stuff.But hey its a small team bla bla bla....its been frikkin years.

[Casper]

sorry, it just doesn't work like that.

it's not fundimentally broken. Mattomatt works. those plugins' sequencers are broken. this will be addressed in v6, which should benefit v5 users as well.

Fact is , all previous devices with sequencers in them are broken.
They were all working before, so how come they all break at the same time?
Because something that they all share is not working properly.
So it still is a "fix one issue" and as a result fix all devices case. Fundamental or not.

Unless a new way of hooking things up was introduced in which case it would be logical for new devices such as the mattomatt thingies to be working.
5.1 was just a big mistake, and I traded my rocksolid super pulsar in for the Xite. And since then can't do squad productions with the damm thing.

May I remind you:
-the DSP (auto)management is broken
-Samplers give you blue screens in 64x and in 32x they are full of bugs (don't play on load, after x programms you get only part of the keys playing etc)
-Any other device that use samples give bluescreens in 64x. Most work in 32x!
-Mixers have bugs that were there from years ago.. (sidechain channels after more that x connections for instance)
-UI dialogs are more annoying than ever (death grip messages when an overload takes place)
-Loading presets on a lot of devices don't set the knobs and sliders.
-Inconsistent behaviour on dsp load all together. (nr of voices and switching presets combination)
Etc , etc.

Be that as it may, the worst thing is, there is no statements beeing done at WHEN to expect a better version.
Does sonic core even want us to be customers or what?
You want to sell me a new Mattomat device, but what good is that if the rest isn't working properly.
Who cares about fundamentals Gary?

Maybe instead tell us when V6 is going to be released?
What will be fixed, and honesly state what is not fixed.

Regards,
Casper

[Fluxpod]

^ I agree.But please write it to sc.Gary cant do anything about that.He gets the flag for sc´s shitty customer response behavior but is not in the position to deal with that off hand.Which i feel is not fair from the sc side aswell.

Write them a mail! Make it Brief and clear.I guess i do that too next week because i am tired of that non responsive Behaviour.Moving forward is nice but the base of your Movement should be a mostly bug free codebase.And the 5.1 upgrade is a piece of shit really.No excuses.Going 64 bit and leaving so much of the Plattform unresolved is not ok.

[Casper]

^ I agree.But please write it to sc.Gary cant do anything about that.He gets the flag for sc´s shitty customer response behavior but is not in the position to deal with that off hand.Which i feel is not fair from the sc side aswell.

Write them a mail! Make it Brief and clear.I guess i do that too next week because i am tired of that non responsive Behaviour.Moving forward is nice but the base of your Movement should be a mostly bug free codebase.And the 5.1 upgrade is a piece of shit really.No excuses.Going 64 bit and leaving so much of the Plattform unresolved is not ok.

Don't get me wrong , I thing Gary is a very nice guy
He always responds and helps were ever he can.
But me mailing SC would, if i'm not mistaken, land in Gary's mailbox anyway