• oid

    @Johnny-Mauser It is implied by the second, No other gods before me, if you do not know which is second how do you know which is first?

    It is not so much that you should always use [trigger] but that you always need a reason not to use it and those are few.

    posted in technical issues read more
  • oid

    @ddw_music I am/was calm, was just pointing it out for future reference. Beyond it making it easier to offer help it makes the search engine more effective, now this thread will actually be able to be found by those searching for use of this external without having to sift through the massive number of results "counter" on its own would produce.

    posted in technical issues read more
  • oid

    @FFW If you use anything other than vanilla objects you should tell us what those are, I have no idea if [counter] is an abstraction or an external and if it is an abstraction I have no idea what is in it and if it is an external I do not know what package it comes from.

    posted in technical issues read more
  • oid

    @nhouse Does the patch use [pd~]? If so it runs a second instance of pd as a child and top does not do the best job of showing it as a child process, htop is a good replacement for top, press t and you get a tree view, plus it uses colorized output to make things easier to read along with a pile of other handy features like process management. If that is not the case, what is this autostart script? Do you know what program it is part of? Failing that, what is the full path to script and what flavor of linux are you running?

    posted in technical issues read more
  • oid

    @sdaau_ml Font size just sets the font size for new patches, if you want to change the font size of an old patch just open it in a text editor and the first line will be something like #N canvas 584 41 781 712 10;, last digit is the font size, change as needed. PureData does this because it does not reorganize the patch after a font switch, open a patch in a text editor and triple the font size, open it up and PD and see what happens, everything will be an illegible mess because the objects all retain their old positions.

    posted in technical issues read more
  • oid

    @jancsika said:

    That's a good reason to look into adding a "set" method to Pd's [pack].

    What is your reasoning? The closer PD's user experience gets to Max the more people will expect it to be Max and complain about it not being Max.

    inconsistency with [select] and many other core objects which don't autoconvert like this

    This seems consistent from the user standpoint. If an object needs more than one value it will expand the list to get those. [select] can require more than one value if they had no arguments at creation but it would be almost pointless to expand the stream that way. [pipe] is an exception but it makes some sense, would it expand to outputs or to delay time or to both? Which ever you picked there would be people complaining that it should be the other and the help file shows us how to to work around the lack of expansion with [trigger]

    EDIT; You are referring to [select] needing symbols to explicitly be stated with [symbol( or [symbol], not your explicit example using a list. Yes, this is irksome. Number like symbols are just as bad and [f] can not always convert them, like when that number like symbol comes out of [route].

    posted in technical issues read more
  • oid

    @ddw_music The online help is just a quick reference, it is not the manual, it has room for improvement but it will never be a manual. I think it is unreasonable to expect the PD help to endlessly explain how it is different from Max, it would be very tiring and detrimental for those who have not used Max and would ultimately read like a commercial for Max, look at all the features you are missing by using PD instead of Max! You could fork the github and start updating the help, once setup it would take no more time or effort than these posts where you point out the flaws of the help and I would bet they would take almost every update to the help files, push your updates and make the pull request. Not that I am complaining about your complaining, I am certainly not doing the work either, and that is part of the problem with opensource, no one wants to do the grunt work even when it is stupid simple.

    posted in technical issues read more
  • oid

    @ddw_music It is probably not documented because it is the same as all other storage devices, pack is just [float] or [symbol] for lists, hot inlet can always be banged for output. I think This is explained in the documentation, just not in the online help. Seb's is more efficient except when you need a constant like $0 and can just have it live in the first spot.

    posted in technical issues read more
  • oid

    @ddw_music Just do [pack 0 f f f...] and use the hot inlet to bang. follow with a list split if you can not have the leading zero or what ever you put there, good spot for your $0 if you need it. I assume it is not implemented because it is just so simple and more versatile to roll your own.

    posted in technical issues read more
  • oid

    PureData does have limits and it will clip when it reaches those limits, but there is no sane way for it to predict what the user is listening through, is it a 1500watt amp cranked or a 1/2watt headphone amp at moderate volume? You can stick a [clip~] before [dac~], but this just makes it clip earlier than it normally would so you will have to turn the volume down or listen to the clipping. You can patch up a compressor to live before [dac~] with little effort and in the process you will learn a great deal about amplitude and signal flow, but all a compressor does for you is turn down the volume for you when a strong transient happens so you have to turn your volume down bellow the threshold of the compressor to avoid altering the sound. No matter what you do the solution is the same, you turn down the volume.

    It is a system built of user, computer, os, puredata, soundcard, amplifier, speakers, and anything else you put in the chain, you designed the overall system and you are the only one who can make it optimal. Applying blanket standards to all things just does not work, the design of my kitchen knives are sub-optimal because they can cut me, but if they can not cut me they will not be able to cut up my pineapple. Get a book on audio engineering if you are worried.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!