• oid

    @fishcrystals At 2000 bpm I get under 13% cpu usage on wish with my cpu's governor set on powersave, I started up gimp and took the screen shot while it was running and gimp took no longer than normal to start up. This is on a X13 thinkpad. I think you got something going on or the Windows wish is not very good.
    Untitled.png

    posted in technical issues read more
  • oid

    @whale-av said:

    Stopping the [metro 10] that is banging [snapshot~] seems to relax Pd.

    I have no issues with this patch on linux, patch peeks out at 5% cpu when I adjust tempo and no lags or drop outs or issues editing. This could be a bug in the Windows version of pd or perhaps just an issue with how Windows schedules and manages jobs? I assumed it was one of those issues with ASIO that you help people with so often so did not respond before.

    posted in technical issues read more
  • oid

    @FFW We can get object arguments with [iemguts/canvasindex].
    Untitled.png

    posted in technical issues read more
  • oid

    @svanya I kept on fiddling and ended up doing a major rework, have yet to sort out the disconnect logic but it is more efficient and now connects when you are within 25 pixels of the left outlet instead of left inlet, it is more predictable in connecting and disconnecting in general. Also got rid of the cyclone dependency and made it so it only does its thing when you click on the abstraction and not on any click so no collisions between canvases. Also added a print too the right outlet of the [inlet~] so you can use it to probe non-audio non-float stuff. No idea when I will fix the disconnect, at this point it only disconnects when it makes a new connection, which is not a terrible setup and perhaps more ideal.

    mvu-2.pd
    Edit: Oh yeah, I forgot the multichannel stuff, had a plan for that but don't recall what it was.

    posted in abstract~ read more
  • oid

    Brought this up in another thread, noticed a simple refinement. If you replace [send watchvmu] with [iemguts/sendcanvas 1] you don't need the [namecanvas] and there is no worry about collisions if you are using this abstraction in multiple patches.

    posted in abstract~ read more
  • oid

    When you need to make connections to a subpatch you are doing dynamic patching in it is generally easier to just use [send]/[receive] and the like in place of [inlet]/[outlet].
    Untitled.png

    posted in technical issues read more
  • oid

    @jameslo I don't really know [clone] very well so I could be missing what you are going after, but can't you just use [clone]'s [set( method combined with -send msg instead of dynamic patching since all you are trying to do is set the index?

    posted in technical issues read more
  • oid

    @atux Your terminal example has the &&, second command will not be run unless the first command returns zero. In pd you just execute each command without care if the first has completed, delay gives enough time for it to complete. Generally if I need to do compound commands like these I either put them into scripts and just execute the scripts instead so the shell can handle it all or I use multiple instances of [command].
    Untitled.png
    Scripts are easy and reliable but it is not all right there easy to work with and see in the patch. Multiple instances of [command] gives a bit more flexibility since we can use the output of each individually and well as run it into the next {command].

    For your problem, is it always consistent? certain apps always display the behavior or is it a sometimes things? Does it work from the terminal in this case? Have you tried having it click twice? xev could be of help, it will provide a good test window for your mouse manipulation since all it does is print those events to terminal.

    Xnee is another program you might find useful for your project, it can record and playback mouse/keyboard events, might be more suitable for your needs than xdotool depending on what you are doing.

    posted in technical issues read more
  • oid

    @atux If it does not need to be the literal cursor you could fake a cursor. I just used a unicode arrow as the label for a white canvas and send it some movements I recorded with [iemguts/receivecanvas]. This way you can just use pd's own mouse movement and click messages in tandem with the fake cursor. Possible nice side effect is no collisions between programmed input and user input, you can always return the real cursor to where the user last left it.
    cursor.pd

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!