New patch: Picostudio

Last summer, I spent quite a bit of time working on a four-track looper inspired by the Teenage Engineering OP-1 and Tascam’s Portastudio series.

There are a few bugs that I’ve wanted to iron out before I shared it with other people but I simply haven’t had the time to do so, and since it works well enough that I am still using it, I thought it might worth sharing now, anyway.

It is available both on Patchstorage and GitHub (where the issues are listed).

I hope you’ll find it useful.


Oooooh. Really looking forward to checking this out!

I hope you are going to like it. I’d love to hear your thoughts on the patch when you find the time to give it a try.

It’s great! Nice idea and interface. Love the screen art. The first time i tried it was yesterday and i had it in orac as an EE module. Was working well aside from track speed adjustments did not seem to work. I’ll try it standalone and get back to you. Thanks for sharing it :slight_smile:

I had some fun yesterday with this patch (thanks for sharing :wink:

If I can make suggestions:

  • add a key to Mute main input
  • add Track Mutes (using keys an octave higher maybe?

Nice first test today. Some suggestions as well:

  • using the footswitch to enable a recording.
  • is it possible to use like double tab or triple tap with the footswitch to launch different actions?

Thanks for the new patch.

1 Like

Thank you for all the kind feedback. I greatly appreciate it!

Wannop: I spent far too much time on the screen art so I am glad to hear that you like it. I haven’t had the time to give Orac 2.0 a spin but I’ll take a look at the issue when time permits. I am also curious to see how the patch works together with all the other modules.

keymanpal: I am happy to hear it. This would definitely be useful. Adding a “Mute input” button next to the “Bounce mode” button seems reasonable to me. Do you have any suggestions as to how it could be visualized so the user knows that the main input is muted? Track mutes would certainly also be a nice addition.

nicolasbulb: I’ve been wanting to use a footswitch to start recording for quite a while now as well, and it should be fairly easy to add so I am definitely going to implement this feature. I haven’t looked into it but it might be. Do you have any specific actions in mind?

1 Like


Thanks for your nice and precise answer.
What actions are available for the footswitch?
Is it possible to have a simple tab to record to track1 and double tab to track 2 and so on?

Four taps should be easy to handle though, I’m a drummer. :wink:

P.s. Lovely screen art. Is it possible to add animation to it? How do you work with graphic in PureData? Does it handle SVG or GIF for small animation? If so, I can help with that, I’m an independent full-time designer.

1 Like

Maybe you already know this, sorry for that;-)
You can mentioning someone using @username and that will give a notification;-)
example @majjoha

Glad you liked suggestions, a picture is worth…

For starters, you could “cancel” the input meter bar (left one) so if non existent, well its muted? Don’t change input meter bar… maybe a big pop-up message? AUDIO INPUT MUTE / AUDIO INPUT or used the screen 5 line?

Sorry for the slow reply but thank you once again for sharing your thoughts. I’ve updated the patch and pushed a new version to GitHub and Patchstorage. The new version adds an input mute button next to the “Bounce mode” button. I’ve also added support for a footswitch which essentially does the same as hitting the Aux button. I hope you like the updates.

@nicolasbulb: To the best of my knowledge, the footswitch only provides on/off values (unless you use an expression pedal). This means that the patch would have to track how many taps have occurred within a given time frame. I’ve opted not to implement this because it adds a layer of complexity that I want to avoid.

I am glad you like the screen art. I considered animating it but I abandoned the idea because it felt too time-consuming compared to the other features I wanted to build, and I feared that the patch would take a performance hit. Unfortunately, it sends messages to the OLED display in order to draw the graphics so you cannot use GIFs or SVGs. You can find a demo patch using graphics here if you are interested:

@keymanpal: Ah. Thanks! As mentioned above, I’ve now added a mute button for the input. Regarding muting separate tracks, I am still not sure how I want to approach it. To keep the behavior consistent with the other actions, I think I’d prefer if they can be muted only when selected. This, of course, means that you would need to change tracks to mute them but I think it would be a little bit more intuitive, and it should not take much longer to mute the tracks this way I believe.

I’ve experimented with hiding the VU meter but I cannot find a way to only disable the input meter (or make it reappear once the VU meter has been removed), so I haven’t implemented any visual feedback yet that shows if the input is muted. Do you know how I would go about only hiding the input meter?

1 Like