Hey everyone !
I'm proud to share to you a really simple abstraction i made today named "glitch~.pd", wich I created to reproduce typical sounds of breakcore/IDM artists like Autechre, Squarepusher, Venetian Snares, etc..

The idea of this abstraction came from youtube channel "Sound Simulator", who did this excellent videos about how to make glitches with PureData

It's only a begining, do not hesitate giving your feedback / advice about it !

https://github.com/izeKake/glitch-/tree/main

Screenshot of glitch_help.pd :

@izecake Fun stuff, I still have my old DD-3 delay sitting about for doing this the old fashioned way. Couple notes, add a $0 to you delay names so you can have multiple instances of abstraction in use without multiply defined errors, [delread~ $0glitch 50] and [delwrite~ $0glitch 500] or the like. Once you do that your [print] is going to irritate you, nice information but every instance of the abstraction is going to print it and spam the log when you load that patch with 83 instances of your abstraction. Make it a comment so people can open the abstraction and instantly know what it is even if they don't have the help file.

Thank you very much for your advice !

Effectively, you're totally right about the print message,
It is not a great solution for explaining what is the abstraction.

I simply deleted it and remplaced it by a comment (it will be fine)

Il also added the $0 to the patch so now we can load multiple glitches into a project

What is the idea behind the two [*~ 1] objects in the patch? You realize that these do not do anything?

@dreamer They are clearly vestigial from when the abstraction's logic was being sorted out and were probably deleted and brought back many times and their deletion or addition often breaking the abstraction for some incomprehensible reason; they served no purpose and you stared at the before and after for an embarrassing amount of time trying to figure out why it works with such a useless operation that does nothing until you finally see the obvious and delete them once and for all. Then you realize you actually needed a [* 0.5] there, so you put it back and nothing works even though a [* 0.5] should not break anything, just decrease volume or something, but nothing works. Back to staring for an embarrassing amount of time. Delete them, still doesn't work. Put them back and make them [* 1], works. More staring. Learn not to tempt providence and call it good enough. Finally realize what is going on and fix the actual problem but really don't want to tempt providence, just want to make music, so leave them. Isn't this the standard pd work flow? I have at least one [* 1] or [+ 0] or the like in most of my patches.

@oid said:

Isn't this the standard pd work flow?

It is not for me

@oid Not looked at the patch, but my best guess is that it had a slider attached at some point, and that was removed without removing the audio operator....?!
David.

@whale-av They are serial with signal branching off between so were probably playing with phase, possibly a yet implemented/sorted out or dropped feature. But my explanation was mostly a joke and not the sort of joke which will carry well over the internet with its very broad and global demographic. I was reliving the experience of making the first abstraction that I shared, I wish it was as clean as @izecake's, I seem to have gone out of my way to obfuscate the useless operations it contained.