Closed jwaldmann closed 3 years ago
Ok, I've investigated this topic.
noTrace
- sets message level to minimum, but unfortunately it still shows
the preamble of setting things up, though it does not show any notes or midi trigers.
There is option in csound called --logfile=FILE
and we can set it to null.
This way it supresses all debug output from csound.
But unfortunately right now it's not possible to use it since it works only if it's passed to csound command line directly and right now this part is hardcoded.
With data type Options
we can control only options that are set within the .csd file.
i was not aware that --logfile needs special treatment. I'll try to fix that.
If you need it I can add specific options that are passed to csound during invokation.
I've fixed that. Now on it's default behavior. To print no trace info. To get it back use setTrace.
Great! I confirm that it works (csound-expression-5.3.4 from hackage of today)
To be precise - works with pulseaudio, but does not silence jack output.
Hi. When I use jack output, I am getting a ton of messages each time I call
dacBy
fromghci
it's no different when I add
<> noTrace
.I don't want these messages - I just want to see the expression that I just typed in ghci.
I understand that it's good to have the messages available (e.g., for debugging), and I understand that there are use cases where the messages don't hurt (e.g., when you mainly want to work with a GUI, not the console). But my application is for teaching - just evaluating an expression: while the sound is playing, students should study the expression. I can get this by scrolling back several pages - that's entirely possible, but inconvenient.