• oid

    @high_output-5000 I generally use dynamic patching for such things. Here is one for a 10x10 grid which I yanked from on of my patches, gives unique send and receive symbol to each. Just hit the bang and open the subpatch to see your toggles. No time to go into detail but you should be able to figure it out and how to tweak to your needs without much effort.
    togglepatch.pd
    Untitled.png

    posted in technical issues read more
  • oid

    @Zygomorph lsmod could offer some insights, perhaps not all the required kernel modules are being loaded. Use a here statement >> to redirect the output to a text file lsmod >> patchbox-modules.txt so you can compare the Wheezy and Patchbox kernels. ps -aux or top could also be helpful, something may just be eating up the cpu and or ram, ps is a little more useful than top since you can easily use here statements to redirect to a text file and keep a record. Comparing the kernel configs can also be helpful, generally you can find the config at /proc/config.gz, just copy it and decompress, if you have the kernel source you can also put the config there and run make menu config and get an interactive program to browse it that offers easy access to help/descriptions/references to all the kernel options and modules.

    The old pi should not be a deterrent here, the Patchbox kernel may not support it well but that is not an issue for you since you want to build your own, even the bleeding edge kernel supports the old pis, you just need to sit down and figure out what is different between the two kernels/systems.

    If you want to go towards custom kernels and optimizing things it might be worthwhile to investigate a more simple distro that can be more easily be stripped down, Slackware and Crux are good for this since their lack of systemd means everything is less tied together and changes in one spot have less chance of affecting other things. Linux From Scratch would not be a bad exercise for learning more if you want to go all out.

    posted in technical issues read more
  • oid

    @KMETE The average/mean of 1 and 2 is 1.5. Put an [i] after the change and it will round to the nearest integer.

    Edit: actually [i] does not round, it just strips the decimal so 1.5 becomes 1. [expr round($f1)] will round.

    posted in technical issues read more
  • oid

    @EMR66 If memory serves I saw a bug report about slow gui introduced in 0.52, don't recall the details but you could check the github. I also have such issues on linux but they are not so bad, fairly certain I just decided to accept them because I saw the bug report and figured that it would eventually be dealt with but perhaps not. Have yet to get around to upgrading to 0.53 either. For me it is just a slight sluggishness in response of the GUI in even small patches but I tend to make very large patches of the sort which have always caused issues with pd so this slight sluggishness was never much of an issue for me.

    posted in technical issues read more
  • oid

    @jameslo said:

    Hmm, but you can't set the receive~/catch~ source at audio rate, right?

    I started out making a solution much like yours, I am not sure what happened,

    posted in technical issues read more
  • oid

    @gentleclockdivider [send~] and [receive~], just use use [receive]'s [set( message to select which [send~] it receives from. [throw~] and [catch~] will let you route a single source to multiple outputs. These have the nice side effect of often producing easier to read/neater patches than solutions like [selector~]

    posted in technical issues read more
  • oid

    @tungee You need a newer pd, listbox was added in 0.52, it is like a float/symbol box where you can type in the new value or scroll through floats but it handles lists. The connections are getting screwed up because nothing is getting created for the listbox objects so the object count is messed up. If you can not go to 0.52 than you can open the patch in a text editor and change all listboxes to a made up object like obj x y lasdkjfl and then the patch will open properly with proper connections and broken objects for the listboxes so you can rework that part of the patch to work without list boxes.

    edit: the x and y in obj x y lksjdf is the the first two arguments to the listbox in the pd file, x and y position. In case that was not obvious, so
    #X listbox 100 200 1 2 3 - - - 5 6;
    would become
    #X obj 100 200 laskdjf;
    and so on.

    posted in patch~ read more
  • oid

    @KMETE Trigger also has some undocumented features to ease patching which are not in that link.
    https://forum.pdpatchrepo.info/topic/13944/some-questions-regarding-abstraction-conventions/5

    posted in technical issues read more
  • oid

    @gentleclockdivider said:

    becasue of the zero delay time in the first part of the message

    That is why. How can it know when to start the next segment if you don't tell it? from the help file

    Note that the middle and right inlet (that sets the time and delay) do not remember old values (unlike other inlets in Pd). Thus, if you send vline~ a float without priorly specifying a ramp time and delay and sent, it jumps immediately to the target value. In the same way, a list of two values will not have a delay time if no delay time was priorly set in the right inlet.

    Message sent to objects act exactly the same as the inlets they correspond to.

    The behavior you want is simply achieved in many ways and generally simpler overall than overriding the alternative, which tends to be the way vanilla objects work.
    Untitled.png
    Edit: not sure what I was thinking with that example, oh well no time to fix and I always feel guilty about editing away my failures so it will stay for now.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!