@raynovich I am not sure if this might help your situation but the concept sounds similar. I was reading the op from this thread:
https://forum.pdpatchrepo.info/topic/14112/mimba-physical-modelling-synth

Once somebody had posted a problem about trying to figure out an error produced by the patch and posted a screenshot, I wondered if I could find the problem by searching through the Pd files used using a text-based search. If you read through the thread, you will see the context of the discussion. But you will probably have to become familiar with how Pd's text-based representation relates to the GUI.

It is not a wholly GUI based solution.

@Orangery I have been reading the new posts for a while now. This looks interesting. Are you tied to VSTHost with your project? There are free DAWs out there that will run plugdata.

@jamcultur I have been getting the error messages but I never had a problem with the sound and did not look at the Pd console for a problem. Looking at your screenshot from a few posts ago, I thought I might be able to find the cause of the error by using grep. I have yet to be able to use the whole expression. It is probably just some syntax in the command that I need to look up.

I see whale-av presents what might be a solution. That could be interesting.

Figuring out Pd is something I really want to do so I am trying to learn a lot as I go along. It all seems to working out this time but it is taking longer than I would like. Oh well.

@jamcultur I am wondering if there is a quick way to search through the files using a text based search. I know you can open Pd files as text files and there is a syntax to them. I think you can edit them as well and produce working Pd patches.

So here are the results from a search on the MacOS cli:
mimba-092b % grep "sin" *
mba.pd:#X obj 1201 543 r $1-mmbsintkeybp;
mba.pd:#X obj 319 354 r $1-mnbsinidelall;
mba.pd:#X obj 347 454 r $1-$2-mnbsinidelalldd;
mba.pd:#X obj 348 493 r $1-$2-mnbsinidelallml;
mba.pd:#X obj 1704 4618 r $1-mmbsinidelsensi;
******************* MY ADDED TEXT TO HIGHLIGHT THE LINE*****************************
mba.pd:#X obj 595 437 expr sin(w$0)sinh(ln(2)/2$f1w$0/sin(w$0));
MY ADDED TEXT TO HIGHLIGHT THE LINE**********
mba.pd:#N canvas 0 83 1920 997 sineIm 0;
mba.pd:#X restore 160 538 pd sineIm;
mba.pd:#X obj 323 536 sin;
mba.pd:#X text 505 456 alpha = sin(w0)/(2Q);
mba.pd:, peak gain = Q) b0 = sin(w0)/2 = Qalpha b1 = 0 b2 = -sin(w0)/2 =
mba.pd:#X text 530 678 b0 = sin(w0)/2 = Qalpha;
mba.pd:#X text 530 759 b2 = -sin(w0)/2 = -Qalpha;
mba.pd:#X obj 125 383 sin;
mimba.pd:#X msg 59 488 ; $1-wtable-ramp3 sinesum 515 1 -1 0.5 -0.5 0.33 -0.33
mimba.pd:#X msg 51 296 ; $1-wtable-ramp2 sinesum 515 1 0 -0.111111 0 0.04
mimba.pd:#X msg 52 88 ; $1-wtable-ramp1 sinesum 515 1 0.5 0.33 0.25 0.2 0.16
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X msg 875 315 ; $1-wtable-z1b sinesum 515;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X text 509 510 rising saw;
mimba.pd:#X text 35 274 soft sine 2;
mimba.pd:#X text 20 201 soft sine 1;
mimba.pd:#X msg 521 916 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:#X msg 522 853 ; $1-addiwaves read sine-noisy1.txt;
mimba.pd:#X text 165 339 (3) soft sine 3;
mimba.pd:#X text 1334 643 soft sine 1 with octave louder;
mimba.pd:#X obj 171 780 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X obj 679 864 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X text 193 158 0 soft sine 4;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 42 374 s $1-mmbsintkeybp;
mimba.pd:en filders te 'clearen' in tien voices tegelijkertijd. Oplossing: tussen
mimba.pd:elke stem bv. 100ms steken , zie oplossing aan de rechterkant van
mimba.pd:#X msg 1041 471 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:per wavetable)(de langste sinesum messages -zoals 37- hebben nu 36
mimba.pd:#X text 36 318 alle lage tonen maximum 36 harmonieken in sinesum ,
mimba.pd:doen met global previous pitch (en toggle voor aanpassing van vorige
mimba.pd:#X msg 59 488 ; $1-wtable-ramp3 sinesum 515 1 -1 0.5 -0.5 0.33 -0.33
mimba.pd:#X msg 51 296 ; $1-wtable-ramp2 sinesum 515 1 0 -0.111111 0 0.04
mimba.pd:#X msg 52 88 ; $1-wtable-ramp1 sinesum 515 1 0.5 0.33 0.25 0.2 0.16
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X text 509 510 rising saw;
mimba.pd:#X text 177 311 soft sine 2;
mimba.pd:#X text 162 238 soft sine 1;
mimba.pd:#X msg 521 916 ; 1-addiwaves write sine-noisy1.txt;
mimba.pd:#X msg 522 853 ; $1-addiwaves read sine-noisy1.txt;
mimba.pd:#X text 227 363 (3) soft sine 3;
mimba.pd:#X obj 171 780 list prepend sinesum 1024;
mimba.pd:#X obj 147 824 list prepend sinesum 1024;
mimba.pd:#X obj 147 791 list prepend sinesum 1024;
mimba.pd:#X obj 679 864 list prepend sinesum 1024;
mimba.pd:#X obj 100 1319 r $1-mnbsinidelall;
mimba.pd:#X obj 624 1290 r $1-mmbsinidelsensi;
mimba.pd:#X obj 11 591 hsl 128 15 0 508 0 0 $1-mnbsinidelall $1-mnbrinidelall
mimba.pd:#X obj 829 17 bng 15 250 50 0 $1-mmbsinfopifqin empty i 17 7 0 10
mimba.pd:(read) variations ; 31 = read once with small sine (read) variations
mimba.pd:; 32 = read once with bigger (read) sine variations ; 33 = normal
mimba.pd:#X obj 306 22 r $1-mmbsinfovelom;
mimba.pd:#X obj 555 28 r $1-mmbsinfopifqin;
mimba.pd:#X obj 29 231 r $1-mmbsinfodetails;
mimba.pd:#X obj 416 137 bng 15 250 50 0 $1-mmbsinfovelom empty i 17 7 0 10
mimba.pd:#X obj 907 94 hsl 121 10 -1 1 0 0 $1-mmbsinidelsensi $1-mmbrinidelsensi
mimba.pd:the pitch detuning caused by bypassing/crossfading APF delay., f 66
mimba.pd:#X obj 22 622 r $1-mmbsinfoafterfiltrin;
mimba.pd:#X obj 1016 539 bng 15 250 50 0 $1-mmbsinfodetails empty xtra_details
mimba.pd:#X obj 1650 601 bng 15 250 50 0 $1-mmbsinfoafterfiltrin empty i 17
mimba.pd:; mmbsimplvl ; mmbsxfadeapf ; mmbsxnoilop ; mnbsinidelall ; mmbsxnoistaval
mimba.pd:'drastische oplossing: default naar alle voicespecific send-receives
grep: presets: Is a directory

I am going to refine the search method to include the relationship/equation from the error message to see what happens.

@jamcultur it is good to see you found your source of the error. Does that tell you why? And I am curious how you found it.

@jamcultur have you edited the original files in any way? In the cases where I have tried [mimba], it has worked, as far as the interface goes. I have a hard time doing anything in Windows with it as I can only play one note and sometimes, not even that before I get static crackling type sounds.

Do you have access to another computer where you can try using Pd? Or an iPad where you can install Plugdata? I wonder if it might be your computer if Pd might be conflicting with something. I am taking guesses, really, as I do not know a whole lot about Pd beyond what I have learned from the book I am reading, and I am not even a third of the way through that.

If you can try it on another Windows computer and it works, it might be something on your computer causing the problem. There are other methods of using your computer with another operating system, such as using a Linux Live CD, but you have to be very careful when using that to not overwrite your current OS by mistake.

@playinmyblues btw, Pd does not work very well on my PC but I could get the patch up looking like it was fine. I just could only play one note at a time and even then it was crackling at time. My PC is not great for this type of thing.

@jamcultur looking at your sreenshot, I do not know. Is that what you get when you open main-mimba.pd?

@jamcultur I was really commenting about hansr's question about his patch and how it worked on his computer. I saw shortly after that the op was from three years ago. But I am going to have a look at my old Windows PC to see if I have any problems with Pd.

I gave it a brief go in Bitwig using Plugdata. It seemed to play acceptably well with 3 notes, Static crackling with 4 notes, even with increasing the sample block size to 512. But again, it seemed to run fine in Pd standalone.

@hansr No problems mashing the keys with a MacBook Pro, M3 Pro, 32GB RAM. I like the instrument, btw. I am just a noob here. Still working my way through a book on Pd but I am really enjoying it.

It has been a while since I have updated the repository but here is my latest batch. I have been doing some work but also kind of got into SuperCollider again. Too many interests but I oscillate.

https://github.com/playinmyblues/Working-Through-Pure-Data-Programming-Fundamentals-Vol-1

And I made a new drum machine in miRack. You can check that out on Patchstorage if you are interested. Synth Drums 5.

@alexandros Thanks for the tips.
Much appreciated!
I knew about the [declare -patch Gem] use and with other externals/libraries, stuff usually that you are taking from libraries on a piece by piece basis. But I probably needed a reminder. I may have incorporated the declare without thinking about it. I am working through a book on Pd at the moment and am using my Raspberry Pi for a lot of it, seeing if I can get it to work.

@ddw_music Thank you so much. That helped immensely and was much easier than I thought once I knew where GEM installed.

It was as simple as:
$ sudo apt install gem
// Then just to see what came up:
$ apt show gem
// Then to see that gem installed where you said it would:
$ dpkg -L gem
// and /usr/lib/pd/extra showed. I hope it does not cause any problems there.

Sorry about the hacked together reply with odd formatting. I do not know how to add the blackbackground formatting yet. I imagine there is a sticky somewhere about that.

From there I opened Pd, went to Preferences > Edit Preferences > Path > New > went to the root and selected /lib/pd/extra/Gem.
Then went to the Startup tab > New > typed in Gem + Enter > OK.
Then I closed and opened Pd and it showed GEM loaded. I opened a basic example from the Browser and it ran. I see now what you meant by [declare -lib Gem]. I am very new to Pd and have also been learning SuperCollider. A lot of the things get forgotten until I get into the relative platform environment. In that example, [declare -lib Gem] was there. It looks just like it does on the Mac.

@willblackhurst if you get to work, can you please provide the commands you used to install it? It would be greatly appreciated. I have tried several things to install it.

In my op, I provide what I used to install it but I think that was just for Ruby. I could not find the library anywhere on my Raspberry Pi and as I searched for the answer, I think what I did was install gem for Ruby. I do not have Ruby installed so I could not even get that to run and I am not looking to figure that out to even see if that would have any benefit for me. Not at this point anyway. In the end, I uninstalled gem.

Maybe the problem is with the current Raspberry Pi OS, Trixie.

When I type gem in the deken - Find Extenrals window, search field and click Search, I get the following:

Searching for "gem"...
Searching on http://deken.puredata.info/search...
Searching on http://deken.puredata.info/search returned 21 results
"gem": Found 0 usable packages (of 20 packages in total).
It appears that there are no matching packages for your architecture.

Maybe it just will not work with the Raspberry Pi at this time.

Hi. I am trying to install the GEM external for Pure Data on my Raspberry Pi. I have always found installing source code troubling as I do not know nearly enough about programming to work with all the options during the install.

I did find out that you can install GEM with the command line so I did that:
sudo apt install gem

I cannot find where it installed to and typing $ gem
gives me nothing but $ sudo apt install gem
gives me:
gem is already the newest version (1:0.94-8+b5).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1

I can point Pure Data to a normally installed external when I know where it is. How do I find GEM so I can point Pd to it?

There are some more patches up in the "Working-Through-Pure-Data-Programming-Fundamentals-Vol-1" repository on GitHub: https://github.com/playinmyblues/Working-Through-Pure-Data-Programming-Fundamentals-Vol-1/tree/main

Hi. I have created a new repository that I consider patches that are more of my own exploration of Pure Data. I am currently working through Maurizio Di Berardino's book that I have mentioned before, which is pretty good. But these patches are a lot of my own explorations of Pd and figuring out some stuff on my own while I do that. The is a fair amount of jumping ahead of the book but that is fun too. I also started using my Raspberry Pi Zero W again, figuring out things on that in preparation of the idea of turning my cheap Barracuda bass into a synth bass.

Here's the repository if you are interested:
https://github.com/playinmyblues/Patches_Along_the_Way

@alexandros & @whale-av, thanks for the replies.