• cfry

    Hi,

    I am trying to create some abstractions that would create the basic waveforms in the control domain. I figured this would be cheaper than using signal objects with snapshot to alter control values, when for example setting the frequency of an [osc~] object.

    If this really is better I do not know.

    I have been fooling around with [sin], [line], [metro] and [delay] to create sine, triangle, saw, square and pulse width control messages, but I would be happy if I could get an example on how to do it.

    Or maybe it would be better to do it in tables?

    Thanks!

    posted in technical issues read more
  • cfry

    Hi,

    obviously if you use [pack] with [ctlin] you can miss some data, with turns into problem if your patch expect to get 0 or 127 consistently.

    I solved it like this:

    Skärmavbild 2020-07-10 kl. 10.12.21.png

    But how would you do it with pack? Or another less objectimessy way?

    posted in technical issues read more
  • cfry

    Hi,

    I would like to simulate, for a starter, objects that rotate around an axis. Trigger them to start at a specific speed, simulate friction that progressively reduce frequency, and also bias them with weights to make uneven rotation. (I will use this to drive synthesis in Pd).

    I have seen that there are some libraries on the theme, like pmpd,

    What would be a good starting point for exploring this?

    The purpose is to control sound, a visual representation would be nice but is not necessary.

    Thanks!

    posted in technical issues read more
  • cfry

    @whale-av
    thanks, that [expr_scale f f f f] object is golden, with a few edits it now works perfect.

    posted in technical issues read more
  • cfry

    Hi, thanks for the input.

    I decided that adding new throw/catch variables is quite comfortable after all. If I want it very visual I can even just put the objects side by side.

    @Balwyn I tested to make an abstraction and also tried to clone it but I did not succeed. Probably I would just need to spend some more time on it.

    @paresys I could not install the zexy library from deken, maybe I have messed up my paths. Will try later.

    posted in technical issues read more
  • cfry

    I adapted that abstraction to make an attenuator of loudness depending on midi pitch, using the scaling parameters to set a start and stop point of the scaling. But the I just got stuck on the easiest part, the control the amount of scaling. Brain freeze.
    Skärmavbild 2020-07-04 kl. 15.59.54.png
    midiscaler.pd

    When the midi pitch reaches the "soft" value the reduction of velocity should be in the range of no reduction (original velocity) to full reduction (velocity 1) depending on the setting (amount/scale/attenuation whatever the best name would be).

    :/

    posted in technical issues read more
  • cfry

    Hi,
    I would like to be able to connect a cable from [outlet~] -> [*~] -> [inlet~], without using an object like [catch~]

    The reasons is that each time I duplicate the subwindow I get duplicated feedback lines, errors. I would like to not need to change the name all the time (feedback2, feedback3...).

    Or if there is another better way to make it possible to just connect without getting the DSP loop error. I want to connect by cables since that suits my workflow in this case.

    Skärmavbild 2020-07-02 kl. 16.57.00.png

    operator.pd

    Thanks!

    posted in technical issues read more
  • cfry

    Hi, thanks for the reply.

    I am rebuilding a pd project file quite often and it happens after a while, so I should be able to narrow it down.

    posted in technical issues read more
  • cfry

    I get this error message. Everything seems to work. But what does it mean? Should I fix it?

    Thanks!

    (Tcl) INVALID COMMAND NAME: invalid command name ".x100235de0.c"
        while executing
    "$tkcanvas itemconfig $tag -text [::pdtk_text::unescape $text]"
        (procedure "pdtk_text_set" line 2)
        invoked from within
    "pdtk_text_set .x100235de0.c .x100235de0.t1003abd40 {-5.08 }"
        ("uplevel" body line 4)
        invoked from within
    "uplevel #0 $docmds"
    

    posted in technical issues read more
  • cfry

    thanks!

    posted in I/O hardware diyread more

Internal error.

Oops! Looks like something went wrong!