• oid

    @fkberthold Just give the forum a search. All you have to do is save what you want to dynamically patch and then open it up in a text editor, those are the messages you need to send to the subpatch with you dynamically send to. The problem here is that everytime you change the port number you have to clear the subpatch and repatch, not a huge deal but it can easily become less efficient than alternative ways. It is worth learning. Run this like the normal [ctlin] object, argument is initial port number, inlet changes the port, with no argument it defaults to omni just like [ctlin]. After that right click on the abstraction and open it, look in the subpatch [pd $0do] and you will see [ctlin #] connected to [pack f f] which is connected to [s $0output]. We use a [send] instead of outlets directly since creation and deletion of [inlet] and [outlet] is a pain and this lets us just wipe the whole patch which insures things don't get messy, like if you accidentally save the abstraction with something in the subpatch we dynamically patch in.
    Untitled1.png
    controlin.pd

    Edit: Just remembered, we now have actual documentation for dynamic patching as of pd 0.52, open the helpfile for message boxes and then click on the [pd-messages] subpatch bottom left.

    posted in technical issues read more
  • oid

    @fkbertholdUntitled.png
    Edit: Kind of looks like you got this and I failed to read your entire post, maybe? You can do an abstraction with dynamic patching to avoid the filtering, but probably not worth the effort since you would not gain much from it.

    posted in technical issues read more
  • oid

    @whale-av [midiout] can handle a sysex dump so list length should not be an isssue, I assume it is just dripping the list since midi is serial. Probably just need to throw together a simple [makenote2.0] abstraction. I was going to throw one together and try it out, but it seems midi.org decided that with the release of midi 2.0 they also had to update the website as well and I got tired of clicking links and scrolling looking for what I wanted (their old website). Maybe another day if no one beats me too it.

    posted in technical issues read more
  • oid

    @jameslo Per-note pitch bend is part of the new MIDI 2.0 spec, not sure how much stuff supports the 2.0 spec yet but it has been out for over 2 years now so it should be getting out there. 2.0 also supports microtonal tuning in general so no more needing to futz with bending to get microtonal tunings. Now we just need pd to adopt the 2.0 spec.

    posted in technical issues read more
  • oid

    @ryan7585 It seems to me that when the right side of [pd equal-block] sends -1 for no write the left side sends 0 still, you read both indexes, it does not skip over like you want. Perhaps an if statement, when they are equal it outputs -1, else it outputs $v2. I am terrible at pd audio so I could be missing something obvious here.
    Untitled.png
    Edit: fixed. I can't do audio right now so no idea if this solves anything, just throwing out an idea.

    posted in technical issues read more
  • oid

    Linux would generally use jack with one of the various front ends like qjackctl or patchage. I do not believe pd supports pulse audio yet so pavucontrol and other pulse tools will likely have little effect Most of the time we either run jack into pulse if latency is not an issue or if latency is an issue we run pulse into jack/kill pulse and use alsa or start jack in it's place. PulseAudio is the standard linux audio server with little concern for latency.

    posted in technical issues read more
  • oid

    @orangepickle Set the right inlet of the counters [float] to 0. Just a guess since without seeing your patch it is difficult to know what you are actually doing.

    posted in technical issues read more
  • oid

    This is what @ddw_music is getting at. Click a list to add it, click again removes it. Hit the bang on the left and it selects from the lists currently in the [text]. More efficient but can complicate other things, but if it does complicate other things there is a good chance those other things are not being done in the best way and the structure of the patch is worth considering.
    set2.pd
    Untitled3.png

    posted in technical issues read more
  • oid

    @merzben Like this? It rebangs [random] automatically if no output is produced until it gets a hit. Or are we still failing to communicate?
    set1.pd
    Untitled2.png
    Edit: seems this solution was already suggested and I missed it somehow, oh well, different methods at least. This one also will overflow with nothing selected but both mine and @FFW patch can be fixed by running all of the toggles to a [< 1] and have it's output go to the right inlet of a spigot on the feedback.

    N0, [< 1} would not work since turning one off will send 0 to it even if others are on, but you get the ideal, sum them or the like before the [< 1]. Brain has shut down for the day. Good luck.

    posted in technical issues read more
  • oid

    @HollyB Looks like I had a slight error in that patch, forgot to set the initial states for the spigots so it fails if the abstraction is called without an argument. The right one should be [spigot 1]. Not sure why I used [pdcontrol] for that, it is not really needed here. Lots of ways to do it.
    midi-in-args1.pd
    Untitled1.png

    posted in patch~ read more

Internal error.

Oops! Looks like something went wrong!