Hey dreamer, thanks so much for listening to the album and leaving a comment, I'm glad you liked it!

Hello everybody!

A few days ago I released an album on the Detroit Underground label (detund).
The album, except for the mastering which was done by the detund team (thank you very much), I did it entirely with Pure Data, without DAW and recording live.
Martin Brinkmann's work (thank you very much Martin!) was essential, I used his patches a lot, especially "virtual(virtual)devices". Modifications of these, own patches and reverbs from Acreil and Bocanegra. Oh and some ELSE filters. Well and of course, thanks to Miller Puckette. I hope I didn't leave anyone out.
I would like to leave here the link to the album on Bandcamp and if anyone on the forum is interested in downloading it, please send me a message in the chat so I can give you a free download code. I still have some.
Thank you all very much, really, you guys are great!

https://detund.bandcamp.com/album/pacto

In case anyone can use it on linux, Dexed's compilation instructions are practically valid to compile this same project, more or less.

I would love to try them, but although I have cmake installed and have done some testing, I don't know how to compile them on linux.
Any hint, please?

I must be missing something, but both blow and strike parameters have always worked flawlessly for me without having made any changes to the code.

I just noticed a few days ago, that shortly after commenting on the forum or even at the same time, a couple of externals (brds and rngs) were updated on TheTechnobear's GitHub.
They can now run at their original sample rate and if not, a message like this now pops up in the console:
"brds~.pd is designed for 96k, not 44100.000000, approximating pitch".

One thing to keep in mind with these externals (unless you have modified them, which I don't know how to do) is that they were created/adapted for use in Organelle, that is, at 44.1K and 16 bits.

The original hardware modules have different and very varied sample rates. In short, I think clouds uses 32k, rings 48k, braids 96k, etc...

They are great externals, I managed to compile them in Linux after looking for some information and since then I haven't stopped using them.

@Nicolas-Danet said:

QWERTY keyboard! Does it works if you add following code?

    event add <<NewObject>>                 <$mod-Key-1>
    event add <<NewMessage>>                <$mod-Key-2>
    event add <<NewAtom>>                   <$mod-Key-3>
    event add <<NewSymbol>>                 <$mod-Key-4>
    event add <<NewComment>>                <$mod-Key-5>
    event add <<NewBang>>                   <$mod-Key-6>
    event add <<NewToggle>>                 <$mod-Key-7>
    event add <<NewDial>>                   <$mod-Key-8>
    event add <<NewArray>>                  <$mod-Key-9>

There < https://github.com/Spaghettis/Spaghettis/blob/master/tcl/ui_bind.tcl#L106 >.

Yes, that worked.

@Nicolas-Danet said:

Have you tried to create object (ctrl + 1) with the shift key also? It is always laborious to get it works on all platforms < https://github.com/Spaghettis/Spaghettis/blob/master/tcl/ui_bind.tcl#L94

I only get four objects using Shift+Control.
Shift+Control+1 = Dial
Shift+Control+2 = Atom
Shift+Control+6 = Object
Shift+Control+8 = Comment

. And could you tell me what you get for $OSTYPE value in a terminal/bash?

echo $OSTYPE

linux-gnu

@Nicolas-Danet said:

On GNU/Linux Spaghettis uses JACK as backend, but contrary to Pd vanilla it is not connected by default (i use a permanent patchbay with qjackctl on my laptop).

That was, as I always start jack from the terminal I hadn't noticed.
Now it works and I have sound.

I have to read more before I ask. I overlooked that you were using dpkg-query, but I could have imagined it because in the documentation you clearly say that the compilation tests have been done in Ubuntu.
I removed that part of the script and it compiled without problems.
But... I can't get it to sound and I have some problems with the keyboard. I can't do Ctrl+ 1, for example.
I think I'll try it better on a virtual machine or a mac.

Thanks Nicolas.

Hi Nicolas.

I'm trying to compile from Arch Linux.
I have tk8.6 installed (tk-8.6.10-1), but I get the following error:
buildLinux sh: tk8.6 package required

Any idea?

@EEight said:

If you're on linux, I just hack something using xinput and open source control...
Let me know if you're interested.
Cheers

I'm a little late, but could you explain how you do it?
Thank you EEight.

You're welcome, I'm glad it works now.
You can also download them manually (and compile) if they are not in the repository or if you don't find them with Deken.
Greetings.

If I'm not mistaken and I understand you correctly, you must compile the externals for ARM.
Maybe did you copy them from an Intel computer?

The good thing about Pd is that you can really use it as software, but you can also turn it into hardware and design your own instruments.
And now that there are so many SBC's around and increasingly at better prices, it's much easier to create a dedicated instrument. You just have to learn something about GNU/Linux, maybe Arduino and basic electronics. Something you can learn in a very short time.

According to the patch of course, I like to go down to 32kHz. Lo-fi sound.

I agree with you. One of the most common problems is having too much. Less is more.
It's easy to say, not so easy to put into practice.

Ok, I just realized how old the post is. But anyway...

Hello and excuse me if I repeat something that has already been said.
Think of pd as an instrument, it does not depend only on its complexity to offer good results. It always seems that something more complex is needed to obtain better results, but it is not true. Even a crystal glass can be a musical instrument.
Forget about the screen and concentrate only on the sound.
Try building a very simple instrument and assign everything to external controllers. If you play a violin, for example, you have access to all its parts, the same thing. Musicians don't look at their instruments while playing.
Practice all you can and don't record it, it's easier to be yourself when you know there are no records. You'll have time to do it later.
Everything influences, the place where you work, the light, people, etc... It helps, but it's really a mental thing.
And most importantly for me, do it like nobody's ever gonna hear it.
Good luck Liam.

Check the CPU load. Maybe (and I'm not sure) you can make it work with a RPi 3, but not with any previous ones.