purr-data | Purr Data - Jonathan Wilkes' cross-platform Pd-l2ork version | Animation library

by agraef C Version: 2.19.3 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | purr-data Summary

purr-data is a C library typically used in User Interface, Animation, Qt5 applications. purr-data has no bugs, it has no vulnerabilities and it has low support. However purr-data has a Non-SPDX License. You can download it from GitHub.

Pure Data (aka Pd) is a visual programming language. That means you can use it to create software graphically by drawing diagrams instead of writing lines of code. These diagrams show how data flows through the software, displaying on the screen what text-based languages require you to piece together in your mind.

Support

Quality

Security

License

Reuse

Support

purr-data has a low active ecosystem.

It has 552 star(s) with 64 fork(s). There are 48 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 7 have been closed. On average issues are closed in 501 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of purr-data is 2.19.3

Quality

purr-data has 0 bugs and 0 code smells.

Security

purr-data has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

purr-data code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

purr-data has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

purr-data releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 633593 lines of code, 202 functions and 267 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of purr-data

Get all kandi verified functions for this library.

purr-data Key Features

No Key Features are available at this moment for purr-data.

purr-data Examples and Code Snippets

No Code Snippets are available at this moment for purr-data.

Community Discussions

Trending Discussions on purr-data

How do I make sure that an instance of an abstraction updates its heights when the subpatch's height changes (purr-data)?

QUESTION

How do I make sure that an instance of an abstraction updates its heights when the subpatch's height changes (purr-data)?

Asked 2018-Mar-09 at 12:47

I have made a drum machine abstraction that allows you to choose any number of tracks and make them visible for editing. Here is an example of the patch in use (the object being created is [rhythmbox 5] but the whole point is to be able to enter any number and see that number of tracks with the object height adjusted accordingly).

The problem is that I can't get the created instance to update, the result being that no tracks are visible:

The tracks are generated correctly in the subpatch and are visible in the subpatch:

Once I close that subpatch window, the update happens and the instance looks like the first image.

The main abstraction consists of another abstraction called drumcontrol.pd which is the section that is always visible in the instance (containing preset handling and a time line), and a dynamically-patched subpatch. As you can see in the 3rd image, I am resizing the subpatch GOP area and the main abstraction GOP area, using [donecanvasdialog].

I have read everything that I could find about the resizing process and I have tried sending a [map 0, map 1( refresh message to the main window right after the [donecanvasdialog] message to the main window. This caused purr-data to hang (the patch opened and was blank, so I assume map 0 clears it and then it can't recover but I haven't yet found documentation for this).

I experimented too (unsuccessfully) with using [coords] instead of [donecanvasdialog] but still had the same issue (not impossible that I was using [coords] incorrectly though).

...

ANSWER

Answered 2018-Mar-09 at 12:47

I was using [coords] incorrectly. I removed the [donecanvasdialog] messages and replaced them with corresponding [coords] messages:

This was a little hard to identify because purr data generated its own coords message in the pd file every time I edited it, which caused the file to hang on reload. Watch out for that (v 2.4.9).

Source https://stackoverflow.com/questions/49168062

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install purr-data

Purr Data is usually built by just running make in the toplevel source directory after checking out the sources from its git repository. This works across all supported platforms (Linux, Mac and Windows at this time). The Makefile also offers the customary targets to clean (make clean, or make realclean to put the sources in pristine state again) and to roll a self-contained distribution tarball (make dist), as well as some other convenience targets (please check the comments at the beginning of the Makefile for more information).
Remember to update your packages: sudo apt-get update && sudo apt-get upgrade
Install the dependencies (please note that the packages may be named slightly differently for different Linux distributions; the given names are for Debian/Ubuntu) sudo apt-get install bison flex automake libasound2-dev \ libjack-jackd2-dev libtool libbluetooth-dev libgl1-mesa-dev \ libglu1-mesa-dev libglew-dev libmagick++-dev libftgl-dev \ libgmerlin-dev libgmerlin-avdec-dev libavifile-0.7-dev \ libmpeg3-dev libquicktime-dev libv4l-dev libraw1394-dev \ libdc1394-22-dev libfftw3-dev libvorbis-dev ladspa-sdk \ dssi-dev tap-plugins invada-studio-plugins-ladspa blepvco \ swh-plugins mcp-plugins cmt blop slv2-jack omins rev-plugins \ libslv2-dev dssi-utils vco-plugins wah-plugins fil-plugins \ mda-lv2 libmp3lame-dev libspeex-dev libgsl0-dev \ portaudio19-dev liblua5.3-dev python-dev libsmpeg0 libjpeg62-turbo \ flite1-dev libgsm1-dev libgtk2.0-dev git libstk0-dev \ libfluidsynth-dev fluid-soundfont-gm byacc
The gui toolkit may require installing the following extra dependencies sudo apt-get install gconf2 libnss3
Clone the Purr-Data repository (2 to 10 minutes) git clone https://git.purrdata.net/jwilkes/purr-data.git
Compile the code (5 minutes [light] to 1.5 hours [full]) to build only the core: make light (5 minutes) to build the core and all externals: make all (20 minutes to 1.5 hours) to build everything except Gem: make incremental (10 to 20 minutes)
If you're using an apt-based Linux distribution and you have the necessary Debian packaging tools installed, there should now be an installer file in the main source directory, which can be installed as usual. Otherwise, run make install to install the software, and make uninstall to remove it again.
Install Homebrew (15 minutes) (asks for password twice-- once for command line tools, once for homebrew)
Install the dependencies (10 minutes): brew install wget brew install autoconf brew install automake brew install libtool brew install fftw brew install python brew install lua brew install fluidsynth brew install lame brew install libvorbis brew install speex brew install gsl brew install libquicktime brew install pkg-config
Clone the Purr-Data repository (10 minutes) git clone https://git.purrdata.net/jwilkes/purr-data.git
Change to the source directory cd purr-data
Build the OSX app and the installer disk image (.dmg file) (15 minutes) make
There should now be a .dmg file in your current directory, which lets you install the app in the usual way
Download and install msys2 (5 minutes) There are two installers-- one for 32-bit Windows systems (i686) and one for 64-bit Windows (x86_64). Be sure you know which version of Windows you are running and download the appropriate installer. Note: don't run the shell after installation finishes. You'll do that manually in step 3.
Download and install the inno setup Quickstart Pack which includes the Script Editor (5 minutes)
Run the "MSYS2 MinGW 32-bit" shell (less than a minute) msys2 adds three Start Menu items for different "flavors" of shell: MSYS2 MinGW 32-bit <- click this one! MSYS2 MinGW 64-bit MSYS2 MSYS
Install the dependencies (5-10 minutes) Once the shell opens, we need to install the dependencies for building Purr Data. First we need to update all the packages: pacman -Syu After closing and reopening the shell as prompted, you may need to do it again: pacman -Syu Now everything should be up-to-date. Issue the following command: pacman -S autoconf automake git libtool \ make mingw-w64-i686-dlfcn mingw-w64-i686-fftw \ mingw-w64-i686-fluidsynth \ mingw-w64-i686-SDL2 \ mingw-w64-i686-ftgl mingw-w64-i686-fribidi \ mingw-w64-i686-ladspa-sdk mingw-w64-i686-lame \ mingw-w64-i686-libsndfile mingw-w64-i686-libvorbis \ mingw-w64-i686-lua mingw-w64-i686-toolchain \ mingw-w64-i686-libjpeg-turbo \ mingw-w64-i686-speex \ rsync unzip wget
Download the source code (3-6 minutes) Issue the following command to create a new directory "purr-data" and clone the repository to it: git clone https://git.purrdata.net/jwilkes/purr-data.git
Enter the source directory (less than a minute) cd purr-data
Finally, build Purr-Data (45-80 minutes) make
Look in the top level source directory and double-click the setup file to start installing Purr Data on your system or run ./"setup file name" in MSYS2 shell.
Install the mingw64 packages for the dependencies. These should be the same as the i686 packages listed under dependencies above, but with x86_64 instead of i686 in the package names. Here's the current list you can copy and paste for convenience: pacman -S autoconf automake git libtool \ make mingw-w64-x86_64-dlfcn mingw-w64-x86_64-fftw \ mingw-w64-x86_64-fluidsynth \ mingw-w64-x86_64-SDL2 \ mingw-w64-x86_64-ftgl mingw-w64-x86_64-fribidi \ mingw-w64-x86_64-ladspa-sdk mingw-w64-x86_64-lame \ mingw-w64-x86_64-libsndfile mingw-w64-x86_64-libvorbis \ mingw-w64-x86_64-lua mingw-w64-x86_64-toolchain \ mingw-w64-x86_64-libjpeg-turbo \ mingw-w64-x86_64-speex \ rsync unzip wget
Use the MSYS2 MinGW 64-bit shell (rather than the 32-bit shell) to do the build.