1. 02 Jan, 2021 1 commit
  2. 09 Sep, 2020 1 commit
  3. 03 Sep, 2020 1 commit
  4. 31 Aug, 2020 1 commit
  5. 19 Aug, 2020 1 commit
    • Albert Gräf's avatar
      Improve bendin compatibility with vanilla. · 772072ec
      Albert Gräf authored
      This adds an option to make bendin use the vanilla range of 0..16383 for
      compatibility. As was observed a long time ago, this is at odds with the
      bendout range of -8192..8191, and was thus fixed in pd-l2ork at some
      point. But Miller Puckette has decided that this bug won't *ever* be fixed in
      vanilla, and this is even documented in vanilla's midi-help.pd patch.
      
      This discrepancy breaks a lot of patches involving MIDI, so a compatibility
      option is needed. It's been possible to use -legacy to get vanilla's bendin,
      but it's better not to conflate legacy iemgui positioning issues with the
      bendin implementation. The former won't usually break interoperability, but
      the latter does.
      
      So, as suggested by Ico Bukvic, we add a flag as an optional second argument
      to bendin instead. If present, this option explicitly denotes the target
      range: zero means the default (pd-l2ork, signed) output range, nonzero the
      vanilla-compatible unsigned range. In addition, there's a new -legacy-bendin
      command line option which makes unsigned output the default for bendin objects
      which don't specify the range explicitly. You'll want to put this into your
      startup flags in the preferences if you need out-of-the-box vanilla
      compatibility.
      772072ec
  6. 06 Mar, 2020 1 commit
  7. 26 Aug, 2019 1 commit
  8. 01 Mar, 2019 1 commit
  9. 09 Jul, 2018 1 commit
  10. 31 May, 2018 1 commit
  11. 29 May, 2018 1 commit
  12. 24 May, 2018 1 commit
  13. 22 Mar, 2018 1 commit
  14. 21 Mar, 2018 2 commits
  15. 04 Mar, 2018 1 commit
  16. 26 Sep, 2017 1 commit
    • Jonathan Wilkes's avatar
      get the "-unique" flag and [pd~] object working in Purr Data · a147dfbb
      Jonathan Wilkes authored
      This patch makes it possible to have multiple running instances of Purr Data,
      and to leverage that interface from Pd-l2ork to get [pd~] working on all
      platforms
      
      Some difficulties required revisions to [pd~] in Pd Vanilla's code
      * use quoted path args for Windows when starting the [pd~] subprocess
      * replace sys_havegui() from Pd Vanilla's recent "threadening" with sys_nogui
      
      The "-unique" flag requires the OSX app bundle to be able to start by calling
      the binary in Pd-l2ork.app/Contents/Resources/app.nw/bin/pd-l2ork. This should
      also make it possible to run Purr Data on OSX both by using an app bundle
      (where the GUI starts the Pd process) and by installing and running from the
      command line (where the Pd process starts the GUI)
      
      The "--user-data-dir" flag sets the directory for various nw.js state used
      by a running instance. To prevent races nw.js requires that each running
      instance have its own directory that is not shared with any other instances.
      
      Setting the value for this flag has two important potential side-effects:
      
      1. If you have a running instance and try to start an additional instance
         that has the same data directory, nw.js will just send an "open" event
         the first running instance and exit the 2nd instance gracefully. This is
         the default nw.js behavior and the default Pd-l2ork behavior as well.
      2. If you have a running instance and try to start an additional instance
         with a different data directory than the first, you'll get a fully
         functional 2nd instance of nw.js running. This is the behavior we desire
         when the user runs pd-l2ork with the "-unique" flag.
      
      In each case we set the data dir explicitly in order to get consistent
      positional command line arguments in the GUI.
      
      In normal mode Purr Data will use the default data dir as specified in the
      nw.js docs for the particular platorm. Since the same default dir is used
      each time Purr Data is run, there will be only one data dir that gets created.
      
      When run with the "-unique" flag, Purr Data will append "-$portno" to the
      default data directory, where $portno is the port Pd chose to communicate
      with the GUI. That ensures that each separate instance of Purr Data can
      get a unique data dir.
      
      A side effect is that users may end up generating multiple data dirs that
      don't get deleted on exit. But Pd starts searching for available ports in the
      same range each time, and unless the user tries to run hundreds of instances
      at once this directory spam shouldn't be too big of a problem.
      a147dfbb
  17. 29 Jan, 2017 1 commit
  18. 26 Jan, 2017 2 commits
  19. 20 Jan, 2017 1 commit
  20. 09 Nov, 2016 1 commit
  21. 25 Oct, 2016 2 commits
  22. 15 Sep, 2016 1 commit
  23. 08 Sep, 2016 1 commit
  24. 03 Jun, 2016 1 commit
  25. 19 Mar, 2016 1 commit
  26. 21 Feb, 2016 2 commits
  27. 12 Feb, 2016 1 commit
  28. 25 Jan, 2016 1 commit
  29. 11 Dec, 2015 1 commit
    • Jonathan Wilkes's avatar
      port from Pd-l2ork: 7066e0d3495b16491b642373dfd030e916bfe309 · 71cad3e0
      Jonathan Wilkes authored
       *added legacy option for iemgui objects. Starting pd-l2ork with -lega…
      
      …cy flag positions iemgui objects in their old, vertically inconsistent locations for the sake of retaining complete backwards compatibility.
      
      *added sys_legacy global for inclusion of other potential legacy breakages that may develop later.
      71cad3e0
  30. 04 Nov, 2015 1 commit
  31. 06 Sep, 2015 1 commit
  32. 13 Feb, 2015 1 commit
  33. 07 Oct, 2014 2 commits
  34. 01 Sep, 2014 1 commit
    • Ivica Bukvic's avatar
      *fixed segfault at start-up due to faulty allocation of the string length for... · 0b96f889
      Ivica Bukvic authored
      *fixed segfault at start-up due to faulty allocation of the string length for checking for unique instance of pd-l2ork
      *made unique check in pd.tk more robust in respect to relative paths and multiple files by making sure that the script always goes back to the original directory from which it was invoked, so as to ensure that the path (if relative) is valid
      0b96f889
  35. 30 Aug, 2014 1 commit