Scope 7 Bug List

[garyb]

you would be better served just writing in to support with your findings. nobody here or on the testing site can do anything about it anyway. the guys who were running the test site and reportuing to SC, are long since over doing that, sorry, but it wasn't their job, so they can quit when they wish to.

generally, you should NOT overwrite newer files with old. if the old file works and works better, then that is something for SC to know, and of course, using the old file makes sense then.

[t_tangent]

Ok thanks, I'll email support as well. Yes that lean testing site seems a bit pointless really then. At least reporting a possible bug here as well as sending to support means other users can first confirm if it also happens on their setup or if it is not an issue with them, as I guess the devs have enough on their hands without bug reports coming through that are in fact user error or incorrect setup. Anyway, cheers.

[garyb]

yes.

[babaorum]

Not really a bug but I have noticed that when I install a new release of Pro Tools and so HD ASIO driver from PT, my system becomes unstable , I have to uninstall the Pro Tools HD ASIO drivers (which are not required for Vanilla version) there is certainly a conflict with the ASIO scope in my opinion but I don't know why ...

[babaorum]

Actually I ask to myself if it's not the v7 scope which is very unstable with Cubase (9.5) because it freezes Cubase very often ... even I removed the HD PT ASIO ...

[garyb]

not here....

[faxinadu]

gary afaik holger is still using the bug tracker system, maybe check with him before deleting.

after the initial setup there that i did it doesn't really need me too much, users can log bugs and holger can edit there.

[garyb]

great!

i wasn't in any hurry to delete anything.

[faxinadu]

anyways the only thing on my side that changed is that fernando and i are taking a break together, we are still friends and things calm down naturally so never say never on anything in the future i am still alive and will do anything needed in terms of maintaining the tracker if/when needed.

[Liquid EDGE]

anyways the only thing on my side that changed is that fernando and i are taking a break together, we are still friends and things calm down naturally so never say never on anything in the future i am still alive and will do anything needed in terms of maintaining the tracker if/when needed.

I don’t know where you get your energy from. It’s quite amazing, your relentless. It’s almost too much. You always seem to have something cooking. If you were a chef no one in the world would go hungry, infact everyone would be obese.

[faxinadu]

anyways the only thing on my side that changed is that fernando and i are taking a break together, we are still friends and things calm down naturally so never say never on anything in the future i am still alive and will do anything needed in terms of maintaining the tracker if/when needed.

I don’t know where you get your energy from. It’s quite amazing, your relentless. It’s almost too much. You always seem to have something cooking. If you were a chef no one in the world would go hungry, infact everyone would be obese.

hahahaha good question <3

[t_tangent]

I have just reinstalled Scope 7 for both PCI and for XITE on Windows 7 64bit , and when I load a device that uses Midi Clock input, it reports an incorrect midi clock timing in the display when set to use external midi clock. I previously installed Scope 7 on Windows 7 32bit and this had the same issue, which I was able to correct by replacing the dsp file called TIMECLK3.dsp with the one from Scope 5.1 and I reported this on the thread on 27 Jan.

If anyone can confirm this is happening on their devices when using external midi clock, I would appreciate it. Thanks. For example try loading up SB404 and set to trigger from external clock. The timing does seem to be ok, but the display is incorrect. But when I replace that dsp file it reports correct timing on display. Other devices also.

[jeezs]

Hello,

Just realize I have the same problem trying to sync my scope’s to an external midi clock.
I Just replace the dip as you said and now it works.
I check a bit more to see if there is no side effect.
let you know if I found any.

Cheers

[nebelfuerst]

I have to add the following bug in Scope 7 with Xite on Win7:

Loading a project where some device is not found automatically.
The find window pops up.
Now I press "options" and I am doomed !!

The whole scope-window is frozen and every mouseclick moves the complete window.
I found no other way than taskmanager to get scope working again.
please fix.

[garyb]

just use browse to find the proper location.

it's because you are loading an old project that had a different directory.

[Music Manic]

I found dragging a delay into the main scope page crashed it. Loading as an insert worked fine. I will check other ones tomorrow.

[nebelfuerst]

just use browse to find the proper location.

it's because you are loading an old project that had a different directory.

I loaded a project with optimaster. Although I have optimasterX in my default search path, I have to point to the optimasterx.
The critical part of my bug is that if you hit options by accident, your work since last save is lost.
For this reason I save often, in the hope to survive

[garyb]

resaving the project once should end all that. optimasterx is an XITE device. optimaster is a PCI device. you must be loading a PCI project to your XITE. that will certainly make the system ask for device locations, since the project is saved with PCI file locations. needing to constantly save projects indicates a stability issue in the machine.

[nebelfuerst]

I use a centralised network drive to store my projects. To this project directory, I can access from an XP-Pc with Scope5.1 ( PCI), my actual main-machine with Win7/Scope7(PCI) and my next machine Win7/Xite, which I currently use for testing to consolidate my migration to xite.
So no instability here, just a nerdy setup

[garyb]

except that when you open projects made in PCI with the XITE, or vice versa, or if you open a project made in a different version of Scope, then you will be asked to locate files. that's how it works.