• alexandros

    I was once suggested the following hack:
    In your patch (probably abstraction), put this:
    initbang_hack.png
    When you're done with your abstraction, open it in a text editor, and at the very bottom of the file add the following line:
    _initbang bang;
    Mind that you shouldn't put any characters like #X or anything like that, just the line above.
    Note that whenever you edit your abstraction, this line will be deleted, so you'll need to write it every single time you change something.

    Also note that [initbang] is available through deken in the iemguts library.

    posted in technical issues read more
  • alexandros

    Youd patch used only a UDP connection, no OSC format in messages sent. Even though you typed an OSC-style address in a message, that's not an OSC format. OSC format is bytes that are not so human-readable. You need to incorporate the native OSC objects that come with vanilla, [oscformat] and [oscparse].
    Here's a screenshot that does what you probably want (note that the OSC address in [oscformat] can omit the forward slashes, but since this is a standard OSC-style address, I kept them there):
    myfirstosc.png

    posted in technical issues read more
  • alexandros

    If I got it right, you want [clip]s to bang only when a value is within these two ranges, right?
    Check this arduino-test.pd
    I've changed one [change] with two comparison objects, [>= 50] and [<= 55], a [&& ], and a [sel 1] This will bang only when the incoming value is between 50 and 55. Do the same for the other range and you should be good to go. Take care to use [t f f] correctly (like in the patch I've uploaded).

    [Edit]: Add a [change] between [&& ] and [sel] so you don't get massive bangs, since the Arduino will be sending data in the set baud rate.

    posted in patch~ read more
  • alexandros

    Either upload a screenshot of the patch (helpful if the patch is not very complex), or upload the patch (if it's rather complex), or you can even post an ASCII version of it. An ASCII example is this:

    [osc~ 440]
    |\
    |  \
    [dac~]
    

    This is an oscillator object connected to a dac object.
    Messages in ASCII look like this:
    [this is a message(
    And numbers like this:
    [0\

    posted in technical issues read more
  • alexandros

    Actually I don't know any software that does what you want, I just suppose that there might be something around. I'm using Pd for almost all the stuff I do...

    posted in technical issues read more
  • alexandros

    Well, there might be some program around that does what you guys want without needing to deal too much with programming. Since you're a programmer though, you shouldn't have problems with programming concepts. Still, Pd is a visual programming language that quite some "traditional" programmers don't like.
    Sure Pd can do what you want, but you have to learn a bit of Pd programming before you can actually make what you want.
    Cyrille Henry has made a very nice abstraction for cue lists. You can find it here http://www.chnry.net/ch/spip.php?article291

    Haven't used it myself, but it looks pretty good for this kind of stuff.

    posted in technical issues read more
  • alexandros

    You can find hcs with deken, and it should included [sys_gui]. I have it on my Debian machine.

    posted in technical issues read more
  • alexandros

    Ctl+Shift+L (or Cmd if you're on OS X).

    posted in technical issues read more
  • alexandros

    You could also write a script with the command you want to use and launch it with [shell]. Python scripts have worked quite well with [shell] for me.

    posted in technical issues read more
  • alexandros

    Not entirely sure about the math of the whole thing, but what I know is that when you use Jack as your audio server, you don't change your audio setting in Pd, but only in Jack.
    Check this, start Jack (in the image you posted, the sampling rate is at 48KHz), then start Pd and open its audio settings. Most likely it will read a 44.1KHz sampling rate. Don't change that, open a new patch and put a [samplerate~] connected to a [print]. Bang it and see what it prints. It should print 48000 and NOT 44100. This is because Jack's sampling rate is at 48000 and that's the sampling rate Pd is using, even though its settings read 44100.
    What happens, I guess, is that when you change Pd's audio settings you force a different sampling rate between the client (Pd) and the server (Jack), which causes this frequency difference, which probably occurs due to two different samplings of the same frequency.
    The only thing you should probably set in Pd's audio settings (if I'm not mistaken), is the number of channels of your sound card.

    posted in technical issues read more
  • alexandros

    I guess # is a special character in Pd. If you open a Pd patch in a text editor, you'll see that all lines begin with #. I tried what you describe (I just set the name "test#" through canvas' properties, didn't send a symbol to it) and it's true indeed. I did save a test patch and then edited it in nano (terminal based text editor) like this:

    #N canvas 343 280 450 300 10;
    #X obj 107 93 cnv 15 100 60 empty empty test\# 20 12 0 14 -233017 -66577 0;
    

    Notice that I put a "" before # which is an escape character for special characters. Now, when I open the patch, the canvas reads "test#".
    I tried to simulate this in a patch by sending the message "list 92 70 35" to [list tosymbol] (these values are ASCII "", "F", and "#") and then to a message "set label $1", which is sent to an empty message, but this results in "\F#", and when sent to a canvas, it results in "\F$".
    I think # (and ) is out of the question for use inside Pd patches, but if someone can prove me wrong, I'd be happy to see that.

    posted in technical issues read more
  • alexandros

    use [snapshot~] and [bang~]. Still, I think you'll get clicks.

    Note: it's not helpful when people post the same thing twice, in two different places of this forum. Please post only once, people will see it.

    posted in technical issues read more
  • alexandros

    What's the output of the shell command? Usually shell works on the root directory, so you should probably specify the path to the directory you're after... just a thought..

    posted in technical issues read more
  • alexandros

    This is computer imprecision caused by floating point numbers. The greater the float, the more likely it is to get these type of errors. If you think about it, 0.399994 is veeery close to 4, but not entirely. This is because your computer (and every computer) fails to represent great floats with perfect precision.
    Maybe this can clarify some things...

    posted in technical issues read more
  • alexandros

    Not sure why you can't create [moog~]. Actually I'm not even sure if it's vanilla. It's help patch doesn't look vanilla to me.
    Which version of Pd are you running on the Organelle?
    You might want to try a couple of vanilla filter abstractions I made, based on Mike Moser-Booth's [filtercoeff.mmb~] and [biquad.mmb~] abstractions. You can get them here https://github.com/alexdrymonitis/filter_abstractions
    They'll definitely work, as they're vanilla. I just tested my [omniFilter_abs~] against [moog~]'s help patch, and it sounds pretty similar (only a bit louder), so it might work for you.

    posted in technical issues read more
  • alexandros

    You can also run two processes of Pd without [pd~], but just by launching Pd twice. On a Mac this is done from the terminal.
    Launch the terminal and type:
    /Applications/Pd-0.47-1.app/Contents/Resources/bin/pd
    Then open another terminal window and type the same thing. This should launch two separate instances of Pd.

    BTW, posting the same thing twice won't really help you, especially in this forum where unread posts are being highlighted to signed in users.

    posted in pixel# read more
  • alexandros

    I guess it's better you send to the mailing list as Martin Peach (the author of the object) is very likely to see your message and respond.

    posted in I/O hardware diyread more
  • alexandros

    The author of the object was following conversations about it on Pd's mailing list, and he might have released a version after this issue made its appearance, I'm not sure though.
    Search the mailing list archives, you'll might find a solution there. Does it work OK with the Arduino IDE?

    posted in I/O hardware diyread more
Internal error.

Oops! Looks like something went wrong!