Hi, my debug.log is empty (0 kb).
How does this get used?
Is it possible to write to file from sonicpi using a log method?
Also often I’ll be running code from my workspace and even though I stop the running code, and go to a new clean workspace, nothing gets output to log panel, not even
Is there a log I shoud be checking to see what’s amiss?
and any recovery method other than restart sonicpi?
The debug log is not meant for general the user. It has to be enabled in the util.rb file in the lib/sonicpi folder inside the application. It will then enable a LOT of output to do with the general program operation, and is used for development debugging of Sonic Pi itself.
I don’t quite understand your problem below
Also often I’ll be running code from my workspace and even though I stop the running code, and go to a new clean workspace, nothing gets output to log panel, not even puts 1
The Manual on writing Supercollider synths for Sonic Pi has a section on debugging looking at 5 techniques you can use
Thanks for this, that’s a great guide
I’m having a look at the git commits, playing with a snapshots/replay idea.
- Commits are stored on run
- on stop (either via the gui button or any other method) does SP log anything anywhere?
I’ve tried running a few loops and stopping, but the only filechange I see is in the .sonic-pi\store\default spi file that’s being ran. Nothing in .sonic-pi\log appears to reflect when a stop event occurs
Do I need to enable the (correct!) use_debug flag to identify when stop events occur?
sorry, I dont know. I wrote down everything I found out (yeah the manual is for me so I dont have to remember anything, although it pretends to be for you