PlanetZ forums - scopeusers.com

VRC 128 and VRC - crash the system
STS 5000 registration error
Mod 3 cableing errors and crashes
Mod 2 window layout errors, cableing errors and crashes
Miniscope missing background picture seems to be an intermitent error depending where the device is placed on the screen

Otherwise good stuff - It's sure coming along.


What's the bug report address?

the noise bug on the graph-EQ has been fixed!

it happend when you load it, there was a loud burst noise.
in v5 the problem is solved.

Hmmm.... seems like I'm not able to control any parameter of 'channel' with midi cc's...

Gotta say - having the warp verbs and das gear as stock is amazing value! A good step, i reckon.

STS 5000 fine here - as is miniscope. The miniscope is visible as just buttons & knobs when dragging, but otherwise it's all lush woodgrain & vinyl

wayne wrote:
STS 5000 fine here - as is miniscope. The miniscope is visible as just buttons & knobs when dragging, but otherwise it's all lush woodgrain & vinyl

Same here, although i just noticed it appears as just knobs in the Live Bar thumbnail - so something's going on.

btw has no-one else tried Lightwave v5? i'm sure the output is quieter than the original Lightwave.

I can confirm the SC Chorus_Delay bug....
No problems with the Original made by Warp....

http://www.file-upload.net/download-167 ... g.avi.html

I'm getting error messages everytime I'm clicking on the clear button of midimonitor...
Other strange thing is, the MOut on Midi Remote & -Fader aren't red triangles but white squares?
That midimonitor thingy appears whether the module is connected or not...

miniscope MKII bug confirmed...

BugReport:

Having an already connected sidechain channel on the STM 4896's onboard compressor, and trying to clear the channel,
you cannot just click on item 'none' because nothing happens. Instead you'd have to click on the already connected channel from the popup list so it disconnects.

This is a minor and old little bug.

hifiboom wrote:the noise bug on the graph-EQ has been fixed!

it happend when you load it, there was a loud burst noise.
in v5 the problem is solved.

Excellent. I remembered that

I sometimes have the strange problem that i can't do my routing in the project window...
To solve the problem I have to do routings via the LiveBar or quit scope and reboot. Reloading the project doesn't help.
Then everything is fine again... I really don't know what causes this but it must be something like
loading devices into the project...
I try to use only v5 devices, so far I'm only using space f's notepad and tuner and that cool simple mixer (see below...).
But I don't think it's related to those devices...
Another little old "bug" is, cabling between STM-Auxes is invisible after Project reload until you click on the connected device.
Anyone else here got those problems?

right-click on Scope S/C icon in lower right corner toolbar has suddenly stopped working - forcing me to ctrl+alt+del turn off Scope and start from the start button.

I haven't done any changes in configuration or anything in the past couple days, and suddenly it stopped working.

Scope 4.5 is turned off in startup.

I'm wondering if this is part of the possible registry fix?

Greg

might be...
try running the installer again.

garyb wrote:might be...
try running the installer again.

already did.

Greg

run/msconfig/startup. reenable SFP at startup.
the missing tray icon is probably a very common Windows error.

sloution #2 at this link should fix that....

garyb wrote:run/msconfig/startup. reenable SFP at startup.
the missing tray icon is probably a very common Windows error.

sloution #2 at this link should fix that....

already did that too

My bug:
- Chorus delay surface panel not selectable due to big graphic groups not leaving any space on the panel expect may be 2 milimeters which is not enough. Ungroup the parameters to solve bug


@ Janni:

>>>>Other strange thing is, the MOut on Midi Remote & -Fader aren't red triangles but white squares
not normal, it should be a regular midi out "red" pad ("Midi Remote Fader" it is not one of my device - or i really don't remember it )
This wrong pad type "can" be a bug cause (but it is not always the case because the pad type is set by the user. The white losange generally shows an async "non-audio" signal which is very bad to have at project window level. In the same time, it could be a midi connection and the maker just forgot to assign the right Pad Type (in which case it is only visually wrong, and may not be a cause of bugs).

>>> Cables disapearing / no possibility to connect (and all seems frozen when talking about connections).

According to my experience, it is caused by
- something "not audio" has been connected to an audio input (mixer or else) and can cause this bug (async modulation to sync audio input=can cause this bug in Scope 4.x).
- Device where the module name can be changed by the user. Has been reported by others as one other cause of the connectivity bug.



Device IO Setup: i looked for that one recently... i should add preset lists no (unless it is that yellow led at the top right ? )...

Hey Mehdi!

Sorry I didn't make that clearer: Midi Remote & -Fader are Scope v5 devices by SC (really don't know if they existed before) an can be found here:
Tools/External Devices

So: not YOUR bug...

And: