Will there ever be anything new?

[Sextant]

Could we set up a petition?

[the19thbear]

Haha, yeah! let's do it! I'm sure it will make a HUGE difference

But seriously, if I won the lottery or anything like that and became very rich, I would have a talk with Holger and invest and try to steer things in this direction. I really want to see this tech succeed.

[valis]

I spoke with Holger last week. He wants a list of current bugs, I haven't had time to sit down and collect our current threads and outline how community members can help simplify our existing threads to present to him. I'm sure money will help anyone.

Working 64bit ASIO is everyone's priority request, I think.

[Sextant]

I spoke with Holger last week. He wants a list of current bugs, I haven't had time to sit down and collect our current threads and outline how community members can help simplify our existing threads to present to him. I'm sure money will help anyone.

Working 64bit ASIO is everyone's priority request, I think.

Does he says something about the future of the platform? Is he aware of the community's concerns?

[valis]

He's been developing Scope8 along with one other person this entire time, but Scope is only one of his businesses. I can't speak on his behalf, but we have discussed before in these forums that he also creates devices for theatrical installations and other similar deployments with a sister business (where he is using his DSP knowledge and the Analog Devices chips) and he has his own personal affairs, and this business has gone on for much of his life.

He produced new 6dsp cards at one point, continues to offer Xite units and the storefront is up.

However much of the 'v8 beta' discussions were someone that came along and helped him move the web frontend, and brought that fresh energy to the table, then disappeared. As a community, we see that as a representative of Holger and Sonic|Core, but from Holger's perspective I'm sure he simply felt left in the lurch with someone who made a lot of promises that he still has to deliver on.

The short? He wants a succinct list of bugs from us to address in v8, and was not aware of the frustrations we have with the v7 64bit driver. We need to encapsulate our discussions here spread out over many threads into something more digestible. I was playing around with the idea of leveraging AI/LLM and a single thread to collect everything to our benefit in this regard.

[the19thbear]

Cool. It would be great to maybe summarise the bugs into a list of say, 20 of the most mentioned bugs and then do a poll, here on PlanetZ where people can vote on what bugs should be addressed. That will give him a list and a feeling of what he should prioritise the most, at least from a user end perspective.

I have seen this down with devs before and it works great.

I can see if i can find the time later to format all the pages and feed them into chatgpt and post the results here

[the19thbear]

From chatgpt after I feed it the 9 pages of text.

Don’t know if this is any help but here we go:

Here is a complete consolidated list of all reported Scope 7 bugs from the forum thread:
General Software & UI Bugs
Missing System Tray Icon – The Scope application lacks an icon in the Windows system
tray, leaving an empty space that still responds to clicks.
GUI Glitches – Some interface elements fail to update or disappear.
Parameter Value Display Issue – Hovering over device knobs doesn’t display parameter
values as expected.
Preset Selection Lag – Long delay when selecting presets in certain plug-ins.
Preset Saving Crash – Saving presets upon device removal (instead of using the preset
window) can lead to crashes and loss of all presets for that device.
Audio & DSP Issues
DSP Capacity Limit Error –
"A capacity limit of your DSP cards has been reached" when
loading SB 404 plug-in on Xite-1 (Win 10, 64-bit, 48kHz).
Wave In Crackling – The ‘Wave In’ function causes crackling noises.
ASIO Dropouts – Random audio dropouts with ASIO drivers.
ASIO Driver Crash with SuperCollider – Using ASIO with SuperCollider via PortAudio
results in a BSOD.
EDS 8i Drum Machine No Sound on Load – EDS 8i produces no sound until the main
volume knob is adjusted.
MIDI & Sequencer Issues
MIDI Timing Issues – Irregular MIDI behavior, including timing inconsistencies.
Sequencer Modules Unresponsive – Sequencer settings freeze until a DSP reload or
sample rate switch (affects Solaris, Modular).
Arpeggiator Note Sustain Issue – When the Arpeg device is bypassed or stopped, notes
cut off prematurely instead of sustaining.
Sequencer and MIDI Clock Timing Problems – Devices using sequencers or external MIDI
clocks have incorrect timing. Replacing TIMECLK3.dsp from Scope 5.1 fixes this.
MIDI CC Assignment Recall Problem – STM mixer MIDI CC assignments don’t recall
correctly unless saved in the ‘MIDI Controller’ folder of the presets window.
Routing & Module Bugs
Scope Routing Bugs – Issues with signal flow in the routing window.
"Only One Source/Destination Module Needed" Error – Scope 7 sometimes throws this
error on boot, even when no duplicate modules exist. Seen on multi-card setups.
Sidechain Functionality in Stock Compressors – Sidechain selection no longer works in
stock compressors when inserted into a mixer.
Optimaster Device Loading Prompts – Loading projects with Optimaster prompts users to
locate 'optimasterx' files, even when the file is in the correct directory.
Plug-in & Device-Specific Bugs
SB404 Delay Effect Errors –
"Module SDRAM XiteDelay is not appropriate for this
hardware" error when using the delay effect.
SB404 Preset Loading Error – Loading old SB404 V2 presets causes an error: "Module
SDRAM XiteDelay is not appropriate for his hardware.
"
Lightwave Interface Glitch – The "Note" field remains visible when switching pages and
lacks inner shadow, leading to visual inconsistencies.
SampleOSC Module Issue – Older SampleOSC modules in Modular 2 cause problems;
replacing them with Modular IV’s Sample OSC resolves this.
Modular Flexor Patch Crash – Loading certain Flexor patches in Modular can cause
BSOD (Win 7 Pro x64, Scope/XITE v7.0).
Crashes on Project Load – Some projects fail to load properly, causing Scope to crash.
Hardware & Compatibility Issues
STS Samplers and VDat Compatibility – STS samplers and VDat exhibit issues in Scope
7 x64, performing better on Scope 5.1 32-bit.
External Word Clock Sync Failure – XITE-1 hardware fails to sync with an external word
clock source via BNC input after upgrading to Scope 7.


I suggest we all chip in now, if we want to see updates to this platform. It seems like there is a window of opportunity currently.

A poll here on planetz for the most serious bugs and then we vote. And the 5 top ones or whatever, Holger can work on (if he thinks it’s the right thing to do).

[valis]

Please hold off until I make a dedicated thread, I've been trying to get a demo out the door to a client to land a new project. Once I have mental bandwidth we'll do a proper rollup. You can reference that post then if you'd like, and repost it to where we take this on.

[the19thbear]

Roger. Thanks for your effort.

[Gordon Gekko]

Nan, not ever
It’s gonna get dark
It’s gonna be cold
It’s gonna last for the rest of your life

[bosone]

Hello everyone!
long-time scope user here (since 2000!) and current owner of 2 scope PCI (21 DSPs)

"unfortunately", i now use scope just to route my audio, with the currecnt power of my computer and all the VST stuff I have, there's really no need for me to use Scope FX/synths anymore. No, "better audio quality" is not a must for me, as mine is just an hobby and I have limited time, so saving one single project in Cakewalk Sonar and do everything inside the DAW is much better... many years ago i saved the DAW project AND and the scope mixer project, and I had to render the audio in realtime to make the mixdown. Now i cna just hit "export audio" and in a breeze I have my track in wav!

all these, just to say that i will not change my scope card until they will self-destroy themselves or if I will be forced to a windows upgrade that will not support SCOPE PCI anymore.

Despite i'm still on win10 and know nothing about win 11 compatibility, all I would need for Scope is just a future proof working win11 driver, and I wil happily pay for that!

[Rafe]

I know it's not a bug and not sure it's a software thing but implementing mpe would add to the playability of the synths and modular. The synths which already respond to aftertouch are given extra depth. I feel mpe would get so much more out of them. But I'm probably just farting in the wind and midi is fixed into the hardware

[sepuka]

it seems to be a dying product.

such a dying product that cards released in the last millennium by another company still have driver support... Do you see that often?

[the19thbear]

it seems to be a dying product.

such a dying product that cards released in the last millennium by another company still have driver support... Do you see that often?

No I don’t see that often. I get your point. But I hope you also get my point. There has been nothing substantial happening for quite a lot of years from SC. And almost no people know of their products.

I don’t want to debate this. Either they are around in 5 years or they are not. Time Will tell. None of us know.

[valis]

Scope will be around in 5 years, I don't see that changing. How quickly we can get working drivers and bugfixes via Scope 8 is another question, and one that we're about to work on (here) to help that happen.

[Liquid EDGE]

Def hand over my Xite-1 tips thing.

[valis]

Yep, will digest it too.

[Liquid EDGE]

Yep, will digest it too.

My info lead to sb404 being “fixed” from what I understand. As in holger got inside it and attached the sequencer element to either dsp 1 or 2.
Same with a few of the ocean swift devices (attatched sequencer element to dsp 1 or 2…)

Tbh holger should just sack off the sequencer stuff that doesn’t work on Xite new chips and replace those devices with the sequencer type that does work fine on Xite. And from my understanding from spacef it’s a tighter better sequencing anyway.

Solaris seq element has the same issue. But that hasn’t been updated to have the sequencer part either be attatched to dsp 1 or 2 or replaced with the seq that does work.

[Xite Knight v2.0]

Solaris seq element has the same issue. But that hasn’t been updated to either be attatched to dsp 1 or 2 or replaced with the seq that does work.

I would instabuy a 'Solaris v6' with this fix. Just sayin'

[garyb]

Solaris seq element has the same issue. But that hasn’t been updated to either be attatched to dsp 1 or 2 or replaced with the seq that does work.

I would instabuy a 'Solaris v6' with this fix. Just sayin'

tell John.