PlanetZ forums - scopeusers.com

Midi-Monitor
error-message when press "clear"
OK, you can live with this~~

not here...

corrupted project...

Give it a bit Spielraum, Spielraum
not every error, warning or weird behaviour is a 'bug'...
I wouldn't put it in the subject so fast, as it looks so 'confirmed' already, you see?

it'd be hard to find a new bug anyway, after all those years without any system or gui changement

I get this too, have been for a long time.(Scope 5.1 Win7 64bit and Scope 5.0 Win 8.1 32bit) Happens at random intervals when clicking on the clear button. Small annoyance yes but not a showstopper.
Thought it might be due to active sensing but I have my midi routed through a midi filter and into the midi monitor

hubird - any tips on how to get rid of it since you don't seem to get it? What are you doing different?

What version of Scope are you on?

What OS?

@Spielraum: This might be something common to both of our setups and not Scope's fault at all. My main keyboard sends out the nasty active sensing data that cannot be turned off so I use the Scope midi filter but there might be something else involved. Are you using Copperlan?

no problems with midi monitor here...

yayajohn wrote: hubird - any tips on how to get rid of it since you don't seem to get it? What are you doing different?

What version of Scope are you on?

What OS?

Sorry, i forgot I'm on old mac OS9 running just the boards, so not really comparable.
At least I never noticed the problem of Spielraum in my old setup running the DAW and the boards on one mac.

I just know you should be careful with old synths continuously spitting out 'hand shakes' or something on the Midi port. Or Midi exclusive streams.

If I had problems with Midi it always came from Opcode's OMS midi manager, not from Scope.

OMS...OMG...that alone was worth OSX

well that's really strange then. The fact that it's happening on 2 different machines with both 32bit PCI and 64bit Xite makes me want to think it's either my keyboard or my Midex8 or Copperlan.
Oh well, click to close the popup and move on....

Midi_Monitor-ERROR_but_NO_Crash (WinXP_SP3_x86-XITE1_Scope5_1).JPG

since scope 5.0 x86
up to scope 4 was no error... on same system

v5.1, perfect here.

garyb wrote:v5.1, perfect here.

WinXP_SP3_x86-PCIpulsar_Scope5_1
also perfect

Spielraum wrote:
WinXP_SP3_x86-PCIpulsar_Scope5_1
also perfect

then why the bug report?

garyb wrote:

Spielraum wrote:
WinXP_SP3_x86-PCIpulsar_Scope5_1
also perfect

then why the bug report?

please note
XITE1:
PCIpulsar:

is it possible that the midi monitor is loading from the PCI folder?

garyb wrote:is it possible that the midi monitor is loading from the PCI folder?

seperate systems with seperate install,
but will check your tip...

same error on
Win7 x64+xite1+scope5.1

I know this guy too

I think it can happen
a) after heavy midi controller tweaking or
b) if something is wrong with the midi routing (fb)

roy thinnes wrote: a) after heavy midi controller tweaking or
b) if something is wrong with the midi routing (fb)

...mmh
fresh project and only the midimonitor,
just the same ~ try and error...
but only with xite...

Don't bother about this. It's "normal" and no serious.

Its an overflow on the buffer.

Always wanted a large MIDI Monitor for Scope that expanded to page size.

Just clearing the buffer an extra time works for me.

Would love to see a drag down capability though since I use one on every input and output of the project.