Hi my apologies again. I did read the section on the linux build requirements and it seems that Alsa is recommended and there are steps. I'm going to try and work with that and see if I can get things running. Thanks and apologies again for missing that in the install.txt

Ok. I don't have a ton of linux experience, or experience building pure data on a raspberry pi. I would think that the install directions would include full directions on how to achieve building pure data on a linux machine, which would include installing the libasound2-dev files.

I've been taking an approach to learning raspberry pi and linux and building pure data from a non-automated perspective. I'd like to learn about each process by doing the manual installs and commands instead of relying on automated build chains and tools at this point. If possible, could you please provide instructions on how to install the libasound2-dev dependency? I've downloaded a debian file https://packages.debian.org/bookworm/arm64/libasound2-dev/download but can't seem to install it on my raspberry pi. I get an error when trying to install that .deb file. Thanks

Also in the install txt file it says

Requirements

Core build requirements:

• Unix command shell: bash, dash, etc
• C compiler chain: gcc/clang & make

Core runtime requirements:

• Tcl/Tk: Tk wish shell

Optional features:

• autotools: autconf, automake, & libtool (if building with the autotools)
• gettext: build localizations in the po directory
• JACK: audio server support
• FFTW: use the optimized FFTW Fast Fourier Transform library

I have the core build requirements * Unix command shell: bash, dash, etc

• C compiler chain: gcc/clang & make installed. It seems there is a missing dependency included in the package I downloaded and that is highlighted when I try to do a makefile build approach and not an autotools approach

Hi,
Which build requirements are you referring to specifically? the documentation says that as an alternative to installing all of the auto tools you can run a make file instead. And it does not specify any build requirements when doing this alternative to auto tools approach.

Makefile Build
Alternatively, and often more simply, to the autotools build, you can use the
fallback makefiles in the src directory:

src/makefile.gnu: GNU/Linux
src/makefile.mac: macOS
src/makefile.msvc: Windows with Microsoft Visual C
src/makefile.mingw: Windows with MinGW GCC
On Linux, for example, run the GNU-specific makefile in the src directory:

cd src
make -f makefile.gnu

Hi again, my apologies, I must have misread the documentation. So on pd-0.56-1 I was able to navigate to the cd directory and find the makefile.gnu and do make -f makefile.gnu install

Alot output then happened in the terminal window, however it did have one compilation error.

s_audio_alsa.c:11:10: fatal error: alsa/asoundlib.h: no such file or directory
11 | #include <alsa/asoundlib.h>
compilation terminated.
make: *** [makefile.gnu:148: s_audio_alsa.o] Error 1

Halp

Thanks oid, I'm having issues running the makefile.am files though, when cd'ing to that linux directory. It seems that .am files rely on auto tools. I was wondering if there is fairly straightforward way to simply run a MakeFile and build PD on a raspberry pi? Or if the now updated versions of PD rely on using auto tools. The documentation seems to suggest that it is possible simply run a MakeFile instead of using auto tools. But perhaps this isn't the case anymore?

Hi,
I'm new to linux and just got a raspberry pi 5. I'm interested in building/compiling pure data from the source code without using the auto tools approach. The documentation says :

Makefile Build

Alternatively, and often more simply, to the autotools build, you can use the
fallback makefiles in the src directory:

• src/makefile.gnu: GNU/Linux
• src/makefile.mac: macOS
• src/makefile.msvc: Windows with Microsoft Visual C
• src/makefile.mingw: Windows with MinGW GCC

On Linux, for example, run the GNU-specific makefile in the src directory:

cd src
make -f makefile.gnu

I don't see any file called makefile.gnu though in the source directories. I see a makefile.am file, but I think those .am files are for using autotools? I'd like to, if possible, download the source for pure data, transfer that to my raspberry pi via a thumb drive and then build and run pure data. Is this possible still?

Thanks!

Hi David,

Thank you for the response. I am seeing my saved settings here: (as you suggested)

HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\

I also just have a windows version of vanilla on my c drive, under program files x86.

Right clicking on the folder does not give me an unblock option. However, if I right click on the pd.exe in the bin and run as administrator it does save the settings. Thank you for the insights as they led me to try running as an adminstrator. Thanks!

Hi,
I'm working with PD vanilla Pd 0.46.7

I have read the documentation on how to save settings for audio settings and for startup paths by reading this: http://puredata.info/docs/faq/pdsettings
After following those instructions and closing PD and reopening, none of the settings or startup paths are stored. I am running on Windows 8. Also when I go to look in the registry there is no PD folder where the above link says there should be
HKEY_LOCAL_MACHINE -> SOFTWARE -> Pd.

Thanks!
-fp

@whale-av Sorry I haven't had a chance to check out the patch, but I finally did and it doesn't seem to work. I load in a wave and then click .5 or .01 to start the sound, and it doesn't loop. Also I noticed you implemented a VLINE object. I am trying not to use envelopes at the beginning and end of the wave file to get rid of the pops.

Instead, my goal is to loop a wave file, of any length, seamlessly. So the wave file will be edited beforehand to loop seamlessly, and I need pure data to play that file back without artifacts, and without envelope fades. Does this make sense? I'm happy to provide a wave file for testing. I am able to do this in Max MSP or PD Extended using the Count~ Object. But I want to do this in PD Vanilla as cleanly as possible. Maybe I need to make an external?

Thanks!

Hey just poking to see if anyone could help provide a solution for this, or let me know if this can't or shouldn't be done this way in PD. I haven't had any luck coming up with anything that doesn't make a pop unfortunately. Any help would be greatly appreciated. Thanks

Yeah I have tried to reset the phase of the phasor by sending a bang to the message 0.01. I've also tried changing that to 0.0, but I still get the click as the loop wraps. The problem is that I am monitoring the accumulated onset, since that is the only way to tell where in the array index I currently am at (that I know so far). The problem with this approach is, it isn't sample accurate. In fact, the accumulated onset is triggered every 100ms from the snapshot~ metro object. I could try to make the metro faster, but I still don't think that will work. Maybe I have to convert all of the Non-signal Logic into Signal Logic, in order to get sample accurate wrapping. But if anyone can help me figure out how to do that I would greatly appreciate it, as I'm not a pure data expert. I've also read the B15.tabread4~ onset.pd and it doesn't really help with the problem I'm trying to solve. I don't fully understand how onset is working with phasor~ signal input in B16, and how to use that to sample accurately loop the file. I think this functionality though would be super useful to PD users if we can come up with a solution. Thanks!

Thank you for the reply. By windowing do you mean enveloping with a fade in & fade out? If so I'm trying to avoid doing that. My loops are edited so that they loop seamlessly (in a daw) without any pops or clicks and without the need of enveloping or ending/starting at the zero crossing.

I'm looking for away to sample accurately loop the file. This works fine with smaller files using Tabread4~ and Phasor~. And it works with larger files, but for the larger files you get the nasty artifacts if you just simply run your phasor into a multiplier and then into a Tabread4~. That's why i really like the B.16 Example, it gets rid of the artifacts by polling the phase. Any help in figuring out how to build a sample accurate loop component into this patch without enveloping would be much appreciated! Thanks!

Hi,

Does anyone know how to turn example B.16.long-varispeed.pd into a seamless looper? Meaning, I just want to loop a long .wav file, with varispeed control, and not have it make any pops or clicks when it loops.. I have modified the patch to loop, but it always clicks at the loop point, and I made sure to check that my .wav loops seamlessly with no clicks or pops in audacity. Thanks!