Freqscope and Scope can't be used at the same time #580

Closed
muellmusik opened this Issue Oct 5, 2012 · 8 comments

4 participants

@muellmusik

This should be possible. As it is they compete for the same buffer and display the same thing. Post warns: ScopeOut2: Requested scope buffer unavailable! (index: 0, channels: 1, size: 512).

This does not seem to be a problem on 3.5.3 (previous version I currently have installed...) but is on 3.6

@timblechmann

it works for me ... but looking the FreqScope code, i'd expect problems if it is used, while the server is not completely booted

@muellmusik
@timblechmann

i suppose it is a problem that the Server-scopeBufferAllocator is reset and therefore both scope and freqscope try to use the same scope buffer, which is impossible ...

@muellmusik
@telephon
SuperCollider member

It seems that PlusFreqScope:kill is only called when windows are closed, not when the server quits.
Adding
PlusFreqScopeWindow: quit { scope.kill }

and in Server quit:
if(freqScopeWindow.notNil) { freqScopeWindow.quit ;

may solve it?

@timblechmann

the freqscope class should probably be rewritten with ServerActions ... it currently is more a working prototype, and does not play well with server reboots or the like ...

@jleben
SuperCollider member

I think this is not an issue anymore. Can others confirm, especially @muellmusik?

@muellmusik
@telephon telephon closed this Mar 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment