• atux

    Hi all,

    is there any way to use the ELSE library in Purr-Data?
    I fixed the folders and paths correctly, but it doesn't work (comes out the usual ... error: couldn't create "else ..."). It would seem incompatible.

    P.S .: in Purr-Data is there a way to install a library automatically? When I used PureData in the menu there was "Find externals", here in Purr-Data there is not (or maybe is there an alternative way that I don't know?). So I find the libraries on the net and insert them by hand.

    [I use Purr-Data version 0.28.1 compiled against Pd-l2ork version 2.17.0, compiled against Pd version 0.48.0 on Ubuntu 18.04.]

    Thanks,
    a.

    posted in technical issues read more
  • atux

    @whale-av said:

    @atux I think [bendout] is the object you are looking for.
    It takes values from -8192 to 8191 so 16384 steps including 0.... no bend.

    Hi,

    by performing a MIDI discrete glissando, for example starting from the midi note 60 and going upwards: when you go from 60.99 to 61, from 61.99 to 62 and so on... there is a downward leap.
    I understood (by trial and error) that by replacing 8191 with 4095 (which is the whole part of 8191), the problem is solved and the glissando is regular and without discontinuity.
    But I didn't understand the reason.

    Bye,
    a.
    midi3.jpg
    midi3.pd

    posted in technical issues read more
  • atux

    @whale-av said:

    I think [bendout] is the object you are looking for.

    Thanks, it works perfectly in Purr-Data.

    This is my initial patch with your add:
    midi_pd.jpg
    midi2.pd

    Soon I will study your link "Raw midi + midiout" to understand how to "fix" the microtonal informations in a midi file.

    Bye,
    a.

    posted in technical issues read more
  • atux

    Hi all,

    in this patch non-integer numbers between 60 (C4, 261.63Hz) and 61 (C#4, 277.18Hz) are generated:
    midi.jpg
    midi.pd
    If it is run, the same 60 note is always played (as expected, in the midi logic there is no middle ground between 60 and 61).
    But is there a way to "bend" the sound to match the exact value? (practically with the exact frequencies coming out of [mtof]).

    When in puredata I write a midi file, is there any parameter to take into account these micro-variations in pitch to be used later in a DAW in which I import the .mid file (for example Ardour)?

    Thanks,
    a.

    [I use Purr-Data + Qsynth and Ardour DAW on Ubuntu 18.04]

    posted in technical issues read more
  • atux

    @whale-av said:

    So.....
    [route /curve]
    |
    [route 3 4]
    | |
    [unpack s f f f f f f] [unpack s f f f f f f]

    and duplicate your audio generator after each [unpack]

    It works!
    Using [print] I saw that x, y come out of the second and third outlet:
    07.jpg

    Now I hear both branches in glissando at the same time, as I wanted.
    Soon I will study the things you advised me.

    Thanks,
    a.

    P.S.:
    Yes, I purposely differentiated the ID of the two branches because, in more complex scores, the aim is to have control of the timbre (and other things) of each part.

    posted in I/O hardware diyread more
  • atux

    @whale-av said:

    So after a [route curve/] the unpack should in fact be [unpack f s f f f f f f]

    Yes, now output is error free. This is the beginning of the branching:

    06.jpg

    Now I try to get the simultaneous output of multiple curves.

    Thank you,
    a.

    posted in I/O hardware diyread more
  • atux

    @jameslo said:

    @atux I don't know IanniX, but I'm guessing that the data for the upper and lower traces have to be identified in the OSC messages. Can you show the print output from the console?

    Ok, there are errors in all the output.
    This is the part where the bifurcation begins:

    gliss.jpg

    posted in I/O hardware diyread more
  • atux

    Now it works fine, both for triggers and for curves and cursors.
    One question: using curves in IanniX, for example this bifurcation made of two different curves, the horizontal segment + the ascending segment has ID 3; the descending branch has ID 4:

    04.jpg
    in puredata how do i get both branches in output?
    If I convert to sound in Purr Data (sine wave oscillator), I can hear the horizontal segment and then only the descending branch. In general, how can I "sort" the data of all overlapping curves the cursor encounters, so that I can then hear the sound of them all?
    Maybe I need to add something to [unpack s f f f f f f]...

    This is the current patch:
    05.jpg

    Thanks,
    a.

    posted in I/O hardware diyread more
  • atux

    @jameslo said:

    @atux I think @ingox is suggesting you try changing [route /curve] to ]route /cursor] to match the path that's printed in the Purr Data console.

    You're right, thank you... :D

    Now replacing [route /curve] with [route /cursor] it works. Sound is fine too.

    I was just wondering how I can control the distance between one point and another so that the glissando always remains continuous and does not become, in some parts, a rapid scale of discrete values.
    How can I get this?

    Thanks,
    a.

    posted in I/O hardware diyread more
  • atux

    @ingox said:

    @atux Because it is /cursor in the message, not /curve?

    [cut]

    EDIT

    Thank you, now it work fine.

    Bye,
    a.

    posted in I/O hardware diyread more

Internal error.

Oops! Looks like something went wrong!