In my previous tutorials, the [line] object used for [*~] are typically connected to a number box. Since number box is NOT a signal object, you can simply ignore that number box and connect [line~] straight into [*~].
Exactly as you said! To be honest, I don't even remember in which video you had that fault. Really! You generally do amazing work and I didn't realize you missed this audio to audio rate connection. If it was SuperCollider project, you wouldn't do this. 😊 Ty for your time. Keep going on!
Thank you for the support! Hahaha, yeah definitely. I guess it is best to have only one function that generates envelope instead of like 3 separate ones (and one of them is not even for audio like [line]).
Oh my!! I tried so many workarounds to the noisy sound... and the frustration of not knowing what was going on! But I don't blame you S2 It made for some spurts of creativity! Thanks for the correction, I'm sure this will never be forgotten, now!
I also tried to get rid of the noise in different ways too! The solution was actually easy, but we did both end up trying out different things in the process!
You use line instead of vline because of hardware compatibility. I use line instead of vline because I'm a noise addict. We are not the same. XD Great vids m8. Helping me remember the basics after a decade and a half away. Much obliged.
lol yup I followed your tutorial and that stumped me for a while. Figured it out, but I also kind of like it, so I saved it as my 'cranky env'. Pd is great for happy accidents.
Afaik both [line~] and [vline~] work at sampling frequency. [line~] gets evaluated for every block (so, by default, every 64 samples [line~] will get evaluated and output the 64 samples corresponding to said block, not just one value per block). I never truly understood [vline~] but its evaluation seems to work different in a way that manages block boundaries more accurately.
Yeah, it's kinda confusing. I didn't look too deep into cuz I'm not planning on using an attack time that's 0.1 ms. I'm sure it's helpful/crucial for specific tasks.
@@SoundSimulator Yes absolutely, I used to put [vline~] into everything because I thought it was better, but unless you're working closely at the block level or making some laboratory stuff you really can't tell the difference in the sound. It's cool that [vline~] takes that extra delay argument tho, then it's worth it.
Great to see a man admitting to previous misunderstandings and taking action to not only correct but apologizing to others for any inconveniences as well.🙏 So, I have my PD GUI designed and laid out on the touchscreen, with dark canvased modules and sliders. But, I can't figure out how to get rid of all the patch cords, while also displaying the values in the number boxes, which I need to monitor and manipulate. Do I need to upgrade to Max MSP? Thanks.😎
Thank you for the kind words! Yeah, that is a tricky situation. Max does allow you to turn the patch cords invisible. Cycling 74 has a free trial so it could be worth the try. That said, I have seen people make amazing GUI with Pure Data. Mike Moreno may be happy to answer this question. The Lira-8 VST looks great!
@@SoundSimulator Cool! Thanks for the pointers. Knew you'd know. EDIT: 🤯 Liar-8 is almost the exact same layout as my current GUI and has exactly the same appearance as what I'm shooting for. Awesome!! 🙏
@@SoundSimulator Yeah well, we can't support _all_ the modules, but I hope we can slowly expand what's available. A very big one on the wish-list is [expr], but it's anything but trivial to add it ..
@@SoundSimulator Not very surprising when you realize the implementation is extremely non-trivial. And we also don't know if it could negatively impact performance. In regards to Daisy I'd like to get midi i/o done soonish. Started to have a look but it seems pd2dsy currently doesn't have any midi configs yet.
can you please explain how to change the values in the message objects using sliders? i am biulding a hardware synth, and need to be able to route sliding potetiometers, and not have to manually type in the value each time. thnx
Message object that says [1 $1] will work fine. But that will trigger every time you change the value so you have to find a work around. It's something along the lines of [pack 0 0] with a button connected on the first inlet and a [number] on the second. And the outlet of [pack 0 0] is connected to message [1 $2] or something along that line.
I'm a bit confused because line~ won't let you connect an output to a number. it's fine for volume envelopes but I'm unable to use it to modulate a lowpass filter.
Yeah! I just checked that [lop~]'s second inlet only takes in control-rate signal and not audio-rate signal. In that case, you gotta use [snapshot~] :/
In my previous tutorials, the [line] object used for [*~] are typically connected to a number box. Since number box is NOT a signal object, you can simply ignore that number box and connect [line~] straight into [*~].
thank you! You are my first introduction to Pure Data. I really appreciate your correction and comments. Cheers.
It's important to own up to my mistakes and provide accurate info as best as I can :)
Exactly as you said! To be honest, I don't even remember in which video you had that fault. Really! You generally do amazing work and I didn't realize you missed this audio to audio rate connection. If it was SuperCollider project, you wouldn't do this. 😊
Ty for your time. Keep going on!
Thank you for the support!
Hahaha, yeah definitely. I guess it is best to have only one function that generates envelope instead of like 3 separate ones (and one of them is not even for audio like [line]).
Oh my!! I tried so many workarounds to the noisy sound... and the frustration of not knowing what was going on! But I don't blame you S2
It made for some spurts of creativity!
Thanks for the correction, I'm sure this will never be forgotten, now!
I also tried to get rid of the noise in different ways too! The solution was actually easy, but we did both end up trying out different things in the process!
You use line instead of vline because of hardware compatibility.
I use line instead of vline because I'm a noise addict.
We are not the same.
XD
Great vids m8. Helping me remember the basics after a decade and a half away. Much obliged.
Hahaha, 100%
If you're a noise musician, you HAVE to use [line] to get that noisy artifact.
No worries dude, really appreciate the lessons!
Thanks!!
Nice dude. Thanks for the update.
lol yup I followed your tutorial and that stumped me for a while. Figured it out, but I also kind of like it, so I saved it as my 'cranky env'. Pd is great for happy accidents.
I'm glad to hear that you figured it out before this video came out!
Hahaha, yeah, noise adds character!
nice xD keep on going, the error is part of the journey my friend!
It is indeed!!
Thank you Igor!
Thanks sensei
Afaik both [line~] and [vline~] work at sampling frequency. [line~] gets evaluated for every block (so, by default, every 64 samples [line~] will get evaluated and output the 64 samples corresponding to said block, not just one value per block). I never truly understood [vline~] but its evaluation seems to work different in a way that manages block boundaries more accurately.
Yeah, it's kinda confusing. I didn't look too deep into cuz I'm not planning on using an attack time that's 0.1 ms. I'm sure it's helpful/crucial for specific tasks.
@@SoundSimulator Yes absolutely, I used to put [vline~] into everything because I thought it was better, but unless you're working closely at the block level or making some laboratory stuff you really can't tell the difference in the sound. It's cool that [vline~] takes that extra delay argument tho, then it's worth it.
Great to see a man admitting to previous misunderstandings and taking action to not only correct but apologizing to others for any inconveniences as well.🙏
So, I have my PD GUI designed and laid out on the touchscreen, with dark canvased modules and sliders. But, I can't figure out how to get rid of all the patch cords, while also displaying the values in the number boxes, which I need to monitor and manipulate.
Do I need to upgrade to Max MSP?
Thanks.😎
Thank you for the kind words!
Yeah, that is a tricky situation. Max does allow you to turn the patch cords invisible. Cycling 74 has a free trial so it could be worth the try.
That said, I have seen people make amazing GUI with Pure Data. Mike Moreno may be happy to answer this question. The Lira-8 VST looks great!
@@SoundSimulator Cool! Thanks for the pointers. Knew you'd know.
EDIT: 🤯 Liar-8 is almost the exact same layout as my current GUI and has exactly the same appearance as what I'm shooting for.
Awesome!! 🙏
It also seems you do not need the number object under the line~ object.
Maybe we can have [vline~] in the future, but for now it's best to just use [line~] indeed :)
I hope so! I see too many people not getting into embedded audio cuz of all the unsupported Pure Data objects...
@@SoundSimulator Yeah well, we can't support _all_ the modules, but I hope we can slowly expand what's available. A very big one on the wish-list is [expr], but it's anything but trivial to add it ..
@@_DRMR_ I was really surprised to see [expr] unsupported...
@@SoundSimulator Not very surprising when you realize the implementation is extremely non-trivial. And we also don't know if it could negatively impact performance.
In regards to Daisy I'd like to get midi i/o done soonish. Started to have a look but it seems pd2dsy currently doesn't have any midi configs yet.
can you please explain how to change the values in the message objects using sliders? i am biulding a hardware synth, and need to be able to route sliding potetiometers, and not have to manually type in the value each time. thnx
Message object that says [1 $1] will work fine.
But that will trigger every time you change the value so you have to find a work around.
It's something along the lines of [pack 0 0] with a button connected on the first inlet and a [number] on the second. And the outlet of [pack 0 0] is connected to message [1 $2] or something along that line.
I'm a bit confused because line~ won't let you connect an output to a number. it's fine for volume envelopes but I'm unable to use it to modulate a lowpass filter.
Yeah! I just checked that [lop~]'s second inlet only takes in control-rate signal and not audio-rate signal. In that case, you gotta use [snapshot~] :/
@@SoundSimulator Thanks for the help!
Your sins are forgiven, brother. Because we are all children of Satan and he forgives all sins. 🤣Joke. Keep it up, Sound Simulator.
\m/ 🐐 😏
Thanks for watching, Abraham!