@oid said:

Give a read through the help files for messages and graphical arrays.

I shall... it's a lot of details to read, test and understand, but I'll get there soon enough (;
THanks

No issues at all here, just dropping some lines to register how easy is to use this forum, such a clean UI and the text editor is just delicious.
Congratulations to whoever did it this way.

I'm reading the Pd manual (it's great!) and I've found a link pointing to a page that does not exist anymore on that URL, even though the page itself still exists (talking about the Pd mailing list).
How can I notify the person responsible for the manual so they can fix it?

Pd is my first open source piece of software and I'm still learning how to do things, so any advice will be gladly received.

@oid That is good to know. I will try it later today.
Do you know if I can use a variable for the array size message? Something like: array size $1
I'm running faster than I can read the manual, so there is a lot of gaps inside my brain right now (;
Thanks!

@jameslo wow, your idea is so much better than mine hehehe

I'm still learning the basics of Pd and signal processing, so I haven't installed Gem or other externals yet, just using the pure vanilla until I understand it.
I downloaded your patch and bookmarked this thread for easy future reference.
Thank you very much!

Disclaimer:
I'm a musician, just installed Pd a few weeks ago and quickly realised that I need to better understand the underlying math of it all.

The small idea:
I'm learning Pd by reading help files and the manual while trying to build a synth where I can change the shape of the osc~ wave via AM, FM and folding. This part is going great so far.

The big idea:
I wish I could display the wave form and how the shape changes while being modulated, folded, clipped, etc... It's useful, plus super fun!
However, I thought of a "static display" that shows only one cycle of the wave. It works "fine enough" if the frequency is 48 and the size of the array is 1000, but as soon as you change the frequency it starts showing more cycles or less, as one would expect, of course.

The questions:

• It works at these values (48hz and size 1000) because my sample rate is 48k. Is this correct?
• Is there a way to do what I want? If so, what would you advise me to study?

Note:
I've got the inspiration to do so after using Glänta, a M4L device by Fors. I don't know how they do it, but the visual aspect of their  devices is usually customised with JS stuff. I don't believe that is a "true" wave, but an animated representation of it. But again, don't quote me on that, it's just a hunch (;

Files:

• a Pd patch with an example of the display idea mentioned above
• a txt file with the array values as list. You can see that is not perfect, but close enough (;

capturingOneCycle.pd array1_list_values.txt

I created a loop between a nbx and a hslider because I thought I could "mirror" each other's values...
Then I've got a bunch of stack overflow messages each time their values were changed...
Then I found this post...

Now it's solved, and I can finally sleep!
Thanks!

Hello!

This is my condition:
I'm visually impaired so I'm determined to learn how to code in order to make Pure Data accessible to my (and maybe others) needs.
Hacking into stuff to adapt them to my condition is not something new to me, but I'm not a programmer, meaning I can not write something from scratch but I usually can snoop around the source code and find what I need to change.

Now my question:
I'm under the impression that C would be the way to go, but I would like to receive input from developers that can advise me what is the best learning path in order to reach my goal, which is first to be able to build Pd from source with the "right" colors and then some...

Note: I know about Pd Next and other solutions that deal with Pd's GUI limitations but as my sight condition is very specific, so are my needs.

Thanks!