• KMETE

    Great! Thanks
    Regarding the callbacks - shall I just keep it untick?

    posted in I/O hardware diyread more
  • KMETE

    Thank you for the explanation regarding the "save all settings" in the audio settings. Now I understand why is needed to check for the desired card and choose it when the patch is loaded.
    Regarding the block size - I don't have my pi running at the moment but I remember that last time I run it I needed to set the block size to 512 because lower then that was producing some undesired clicks. Does it make sense?

    I would like to have the ability to change the block size when patch is loaded and therefore I will be happy if you can show me how to do that in that patch whenever you can.

    Thanks for all the explanations!

    edit: If we are already in that topic; I have seen two parameters I don't get in the audio setting menu - callbacks and delay(msec) what are the two for and what they should be?

    posted in I/O hardware diyread more
  • KMETE

    Thank you very much. it seems to work! So basically with that patch even if for some reason my Pi is listed my desired device in a different index in the list, every time I'm opening pd it will choose that device no matter what index is at right?


    I've try to set the block size via the params message but I'm getting an error:
    am I mistaken in the way I'm doing it?
    Screen Shot 2023-01-27 at 10.05.59.png

    another question I've got is - why not just using the "save all setting" in the audio preferences? if I choose my desired output and sample rate and block size then pressing "save all setting" ---> "apply" ; Every time I will open pd it should open it with my saved setting? if so - it is legit way of saving the same sound-card isn't it?
    why to choose one method over the other?

    Screen Shot 2023-01-27 at 10.10.07.png

    posted in I/O hardware diyread more
  • KMETE

    @whale-av said:

    https://forum.pdpatchrepo.info/topic/13217/save-and-recall-midi-settings-in-a-project/8

    This patch seems a little complicated. I'm not sure what is all those pipe needed for? as well as the [ASIO..] message at the top.
    I only will need to setup the interface and its output as I don't have any inputs

    posted in I/O hardware diyread more
  • KMETE

    Exactly!. Thank you very much

    posted in I/O hardware diyread more
  • KMETE

    Does it make sense my way of banging ?
    first symbol, then the message to the left side of symbol and last to the listofdevices ? do I need to use del ? or I can just do [ t b b b] to bang in order ?
    shall I also bang other params such as samplerate and blocksize?

    efit: [params @blocksize 64] won't work for some reason

    order of action.png

    posted in I/O hardware diyread more
  • KMETE

    from which library the object marked in red is from?

    list-compare.png

    posted in I/O hardware diyread more
  • KMETE

    I would like to send multiple outputs to inputs using the same name for send~ and receive~ but when I have multiple send/receive with the same name pure data give me warning and it won't send my audio. is there any work around?

    Screen Shot 2023-01-21 at 13.04.10.png

    posted in technical issues read more
  • KMETE

    I am building a patch that will scale the gain of multiple sf-play2~ object based on the number of tracks that are playing.

    If only 1 track is playing - gain is 1. if 2 - gain of each track that playing is 0.5 etc etc
    my idea seems to work but I was wondering if there is more simple solution for my above?

    Screen Shot 2023-01-21 at 11.59.03.png sf-play2 scaling example.pd

    posted in technical issues read more
  • KMETE

    @whale-av said:

    https://forum.pdpatchrepo.info/topic/11179/pre-selecting-audio-interface-when-patch-opens/2

    Thanks! what library the object [add2] is part of?

    What is a recommended buffer size (block size in pd) for playback audio files?

    posted in I/O hardware diyread more

Internal error.

Oops! Looks like something went wrong!