Scope6/open scope vs 5.1 bug fixing

[next to nothing]

A thought popped up in my head. Now that Open Scope/S6 is introduced, what is the status on the development of scope 5.1? Are all resources geared towards the next main release, bringing 5.1 bug fixing/development to a full stop? Is OSX for 5.1 cancelled?

Personally i would feel a bit "tricked" if bug-fixing and further development is being stopped, like getting proper wave drivers and proper 64-bit support for those devices who lacks it. But if Scope 6 was months away and didn't require a huge upgrade price my mood would be a lot better.

Whats Your opinions? And ofcourse, if anyone actually know SC priorities it would be good to get them as well.

[siriusbliss]

We'll hopefully know more after NAMM this weekend.

My assumption is that all development is moving to Scope 6, and that most if not all these bugs will be resolved going forward.
I can also foresee even better DSP management for Xite as well.

We're also dealing with Microsofts' Win7 and 64-bit issues which are not all SC's fault (having read other forums from other developers STILL dealing with Win7).

There's also Windoze 8 coming, and perhaps MacOS development looming.

I doubt Scope 6 will cost much if anything for V5.1 owners.

SC is still a small company, so we'll see...

So far IMO the wait has been worth it. A LOT of upside starting this year.

Greg

[next to nothing]

I agree to everything you say. However, i think they dived into the 64bit era with a bit of bad focus.

In example, there wasn't (and isnt?) any disclaimer clarifying what works and what isnt working, which should be fair to publish. "Small" errors like wave source being stereo reversed isn't being fixed (not to mention its bad performance), and i doubt you can blame that on MS. They still doesn't mark devices like sample players as "not working in 64bit" which should be fairly easy, and in three years they haven't managed to present a 64-bit compatible Mod 4 installer.

These might seem like small issues, which some of them are, but when you cant even fix the easy things (ref. mod4) then i get a bit irritated.

[dante]

Personally I would expect all development to be on the new platform (64 bit bug fixes being a part of that). Since ParseQ and its device automation would be an in-house scheme where (as Julian Schmidt put it) the sequencer 'knows whats happening in the DSP space' then I imagine life would be a lot easier for the coders. I wouldnt envisage any more time being spent on the old XTC mode for example, since ParseQ would offer much tighter integration/automation etc.

[siriusbliss]

Yeah, but if XTC, wav drivers, and even STS worked in earlier betas, then it should've remained for the official release???
(although my last .wav test with Samplitude was successful, and XTC - although shaky, sort of worked - but I never use it anyways)

I expect that these will be re-resolved.

Yes, I'm personally ready to move on from antiquated XTC, and look forward to an updated STS (at some point).

I'd personally rather see any remaining DSP distribution issues or old .vxd /.sys issues be resolved with the big synths (such as Zarg).... but that's me.

I have evil plans

Greg

[garyb]

there will be a few fixes whether you go to v6 or not, is my understanding. a rising tide floats all boats...

[Liquid EDGE]

From what i gathered from the "The new world of music" forum is that fixes and updates will still be applied to 5.1

[siriusbliss]

Excellent!

At least the other 95% of the program works great!

Greg

[Polarity]

will ever XTC and normal Scope environment (so to use STM mixers) be present and usable at same time??
I know this would be very appreciated by many users here.

[garyb]

parseq would be that app, i think.....

[the19thbear]

Yep... i talked to the parseq developer, and he even thought of making parseq a vst plugin, that way you could load scope stuff within any vst sequencer!!! no more need fore XTC mode!
YEAH!

[vascomusic]

That's very interesting...

...does that mean that you load a sequencer(Parseq) into a VST host sequencer?
Or does it provide the possibility to access the (Open)SCOPE environment and to load + route SCOPE plugins inside that VST plugin ? (without using Parseq's sequencer functionality)