Hi! @giuliomoro, @nescivi , would it be possible to make objects similar to s.meter, print, etc work in or via the IDE (maybe back to the PD or SC-app?) while running supercollider on Bela? It would be a big help to troubleshoot on the spot. Or is there an ease way to connect Bela to PD as an arduino, for example (so that you can do the trouble shooting the other way arond)? Or are there any other advices you guys have for using a GUI for metering audio and other signals on Bela? Thanks again,
Dianne

Found the print possibilities in PD! 🙂
The s.meter function for audio would be awesome to have too, though 😉

    For printing in supercollider you can use .poll() I think. That prints back in the Bela IDE or terminal (depending on what you are using).
    We are planning to implement support for the Bela Scope at some point, as it is more advanced than Supercollider's built-in scope and less resource-intensive.

    Make sure you use the latest version of supercollider, you can get it here.

    dianneverdonk on Pd you can print using [snapshot~]---[print], however it is much more convenient to use the Bela scope to visualize your signals.
    You can send any signals to [dac~ 27 28 29 30] and they will show up on the Bela Scope, which you can reach at http://192.168.7.2/scope/ . There are a couple of examples among the PureData ones that use the scope.

      2 years later

      @giuliomoro thanks for your reply on this. I never succeeded to get any printed numbers in the Bela IDE, though.. 🙁 also, with the instructions above, the plot/scope remains empty. Is there another easy way to output numbers to be able to debug and log with PD in the IDE? Thanks again,

      Dianne

        Dianne have a look at the patch below which shows how to print in a couple of different ways from Pure Data on Bela.

        alt text

        On the left hand side there is the typical method for printing signal rate data. This is used if you're wanting to see a value that's coming from an object with a ~ at the end.

        In this case we are printing the value of the analog input. I've also sent the signal to the first channel of the scope for visualisation.

        On the right hand side there is the typical method for printing control rate data. Here we have a simple counter that increments up to 10 and resets. A message is printed every time the value changes, and you don't need to worry about using the [snapshot~] object.

        In the print object itself you can also add an argument, in this caseSIGNAL-RATE: and CONTROL-RATE: which will prepend whatever you print.

        Hope this clarifies for you.