PlanetZ forums - scopeusers.com

10, 9, 8,7.................... and the no1 winner is...........


now seriously. this might also make a list for the priorities for next update.

Intel-OSX support.

there is really not much that I don`t like.

its the minor things:

- when clicking on the voice box of a synth in the sidebar to raise the poly of a synth by moving mouse up and down, it always goes into curser mode(textinput). not a big buck but that really sucks.
- bug with the delaytimes on the fx stuff, that the tempo calculation only works fine at highest asio latency
- mod patches are not allowed to be plugged into the insert slots...

btw it would be great to have an insert fx modular host with just two audio ins and outs...
so you could plug-in a mod shell into an insert and then start cableling and add stuff like adern distortion and so. (This should be in the device/wishlist)

VDAT bugs

It does not help my musical miss-skill

enormous loading time for large projects

stardust wrote:improvement potential:

GUI speed
patch/preset/project load time
overload handling and DSP load distribution
OSX support
latency down to 1ms fo a simple loop through VST Host
96kHz internally on all devices
rock solid midi implementation
All bug fixes
An easy to use multi segment envelope with beat sync
warps hall algorithm
OSC support
fair bundling strategy
etc.

seconded, modular4 with a good MVC, undo, stuff like that would rock too.

XTC mode that works with dual core & Vista. Modular that works fully under XTC mode.

Things I don't like about Scope :
(1) MIDI clock / timing issues
(2) STS series


Things I like about Scope :
<Your message has exceeded the limit of 40,000 characters and will be truncated>

Things I like about Scope :
<Your message has exceeded the limit of 40,000 characters and will be truncated>

handling of MIDI controls....

maybe fixing the mod preset bug would be nice.

lack of Mackie control...

Never enough DSP's

i do not like the slow way you load projects and play with synths.
too many mouse moves in order to connect.... to set polyphony... to choose midi channel to unload and reload another synth.. takes to much time.
there should be atleast keyboard shortcuts.
also the use of sdk is not that simple if i whnat to make prloaded midi asinged the synths.
pot movement1 bug with 12 o'clock jump.
midi problematic syncronization.

the19thbear wrote:lack of Mackie control...

1. Lack of real automation implementation like HUI protocol.
2. Preset bug
3. Slow GUI response

In no particular order:
- Phase issues between dsps & stdm interconnects (the newer AD stuff should fix this between DSPs, not sure about the stdm latency)
- Needs an updated UI codebase for the next version. Look & feel could use some refinement although I'll admit to being rather comfy with it
- fix the Active Sensing issues
- fix 96k (&192k?) for users who really want it
- new devices should be able to sense the samplerate & adjust internal oversampling, also perhaps user selectable oversampling
- a MADI daughter/side card once the entire new line is complete

valis wrote:In no particular order:
- Phase issues between dsps

I find this to be my main concern in Scope, especially given the 'smart' allocation of devices.

valis wrote:stdm interconnects (the newer AD stuff should fix this between DSPs, not sure about the stdm latency)

Interesting regarding the new AD stuff, but as for the stdm side of things, I'm not so sure that'll ever be latency free. I honestly think that the most future proof direction would be a powerfull single card with (hopefully) zero latency between dsps in a cluster.

The question isn't zero-latency. I don't see that being achievable given modern digital technology & laws of physics. Perhaps string theory or some unthought of GUT will get us past relativity but for now...

The question is phase-coherence. There are ways to lock specific processing blocks on the same dsp now, but I think that the newer AD stuff does it at a lower level. I didn't plumb through the entire devkit (which u can download a demo of) but I did read through some of the technotes for the newer Kits & Sharc releases and confirmed some form of support for phase compensation when Red mentioned it to me a while back. I'm sure Frank (and hopefully SC) know a lot more about it than I. I just don't know where the STDM interconnects fit into the overall scheme of things, since u can't just open up Scope.exe in the devkit and see what Creamware sees. I'm sure they can figure it out though...

by latency in this sense I meant the delay introduced when sending a signal from one dsp to another (IE currently min 2 samples), didn't mean to confuse the issue.