Polybuffer~ public beta 3

    Feb 17 2011 | 2:02 pm
    A third beta is now available.
    Main changes: - when embed is on, the order is preserved - you can instantiate multiple "polybuffer~ toto" in your patch which share that same data - writetofolder: export the current sound files to a folder - getshortname: output buffername and sound file without the extension - JavaScript access (you can instantiate a PolyBuffer() in js)
    Installation: - move polybuffer.mx(o|e) to C74:/extensions - move polybuffer~.mx(o|e) to C74:/msp-externals - move polybuffer~.maxhelp to C74:/msp-help - move maxclasswrap.js to C74:/jsextensions
    Note that you need to have the latest version (5.1.8), which is currently in public beta: - macintosh: http://www.filepivot.com/projects/maxmspjitter/files/beta_mac - windows: http://www.filepivot.com/projects/maxmspjitter/files/beta_win
    And as usual, the bug reporting guidelines:
    Please report any problems you experience with clear and complete information, including steps to reproduce, software and system information, and where possible, an isolated example patch and crash log. Something like the following would be ideal. This makes it easier for us to find and fix the problems you experience. Without such clear and complete information, it is less likely we will be able to.
    Summary: Provide a descriptive summary of the issue.
    Steps to Reproduce: In numbered format, detail the exact steps taken to produce the bug.
    Expected Results: Describe what you expected to happen when you executed the steps above.
    Actual Results: Please explain what actually occurred when steps above are executed.
    Regression: Describe circumstances where the problem occurs or does not occur, such as software versions and/or hardware configurations.
    Notes: Provide additional information, such as references to related problems, workarounds and relevant attachments.

    • Feb 26 2011 | 9:52 pm
      Hello Emmanuel, congratulations on the polybuffer~ object, it is a wonderful tool! Just a small detail: where should I place the [polybuffer˜-test.js] file? Another thing: with the beta 3 version I keep receiving the message "requires Max 5.1.8 or higher". What is that? Thanks in advance.
    • Feb 27 2011 | 11:06 am
      Hi Belquer,
      polybuffer-test.js needs to be next to the help file or somewhere in your search path. It's just to demonstrates the use of polybuffer in JavaScript.
      Do you have 5.1.8 installed from the link I posted above? It's required because of some changes made in buffer~ to notify properly the UI of polybuffer~.
    • Feb 27 2011 | 2:04 pm
      Sorry, Emmanuel, I didn't notice the link. Following your orientation:
      Summary: Provide a descriptive summary of the issue.
      I get the following message:
      js: polybuffer~-test.js: Javascript ReferenceError: PolyBuffer is not defined, line 0 poly~: no patcher polybuffer-sampler jpatchline_completeconnection: index out of range. jpatchline_completeconnection: index out of range. jpatchline_completeconnection: index out of range. poly~: jpatchline_new: index out of range jpatchline_plugin: box missing outlet number 2 poly~: jpatchline_new: index out of range jpatchline_plugin: box missing outlet number 1
      and I don't find the polybuffer-sampler patch as referenced in poly~.
      Steps to Reproduce: In numbered format, detail the exact steps taken to produce the bug.
      Just open the help file via polybuffer~ object.
      I have all the files positioned as oriented, and also the Max 5.1.8 version. The object works fine, just the [p Sampler] doesn't work.
    • Mar 13 2011 | 9:40 pm
      js: polybuffer~-test.js: Javascript ReferenceError: PolyBuffer is not defined, line 0
      #1 it looks like that you didn't put the maxclasswrap.js into C74:/jsextensions.
      #2 polybuffer-sampler.maxpat is in the archive so make sure you put it next to polybuffer~.maxhelp or anywhere in your search path.
    • Mar 25 2011 | 11:22 am
      I wonder if it is possible to write samples from the various buffer~ objects in polybuffer~
      Like sample 1 = buffer1 from 100-400ms etc
    • Mar 25 2011 | 11:04 pm
      That's a typical job for mxj buf.Op.
    • Mar 26 2011 | 6:52 pm
      Can this be done without java? Looking at the help I'm not sure how to approach it : /
    • Mar 30 2011 | 12:41 pm
    • Mar 31 2011 | 3:24 pm
      you can do that with uzi and peek~/poke~. Something like that:
      there's a couple third party object for this as well.
    • Apr 04 2011 | 12:04 pm
      Is it possible to set the buffer size in sample and to fix the sample rate of buffers separatelly?
    • Apr 05 2011 | 4:29 pm
      Thanks EJ, great solution as always :)
    • Oct 15 2011 | 8:16 pm
      FYI, he Max 6 Public Beta ( https://cycling74.com/forums/max-6-public-beta-is-here ) now includes polybuffer~.
      If you have any reports or problems, we will be funneling them in with the rest of the Max 6 feature set so please use the form @ https://cycling74.com/max6betabug_form/
      Thanks for all the feedback.
    • Feb 09 2012 | 3:23 pm
      Can someone explain the functionality of the "quiet" attribute of polybuffer~ (in Max 5)? I've done some searching, but to no avail.
    • Feb 29 2012 | 10:37 am
      it suppresses the warning printed in the Max window, when you use embed polybuffer~ with the same name (telling you it'll use the new embed content).
    • Mar 15 2012 | 2:09 pm
      thanks for this very useful object !
      I have some trouble using polybuffer~ with max 5:
      - there is no bang in the right outlet when using drag and drop in the polybuffer~ window (I think this used to work with the previous beta).
      - the buffer list is not updated when using 'send i replace' messages. For example if I drop 2 sound files in the polybuffer~ window and then replace one, the 'dump' message returns the list of the original sound files.
      Is that normal ? Thanks in advance,
    • Mar 15 2012 | 5:23 pm
      I can confirm the 2 issues. It will be fixed for an incremental release of 6.x.
    • Mar 24 2012 | 5:17 am
      I have a big problem with polybuffers in my patch. There are 8 polybuffers in action, with groove~ reading their files. So far, so good. But if I load, with a new folder, a non-playing polybuffer : the audio is turning off, the time to load the folder…
      Am I missing something ?
      Thanks for any help.
    • Mar 24 2012 | 4:50 pm
      Are you using Max 6? polybuffer~ doesn't do that in 6.0.4 as far as I can tell.
    • Mar 24 2012 | 5:59 pm
      Max 6.04 MacOS X6.8 Macbook 2.4/4G RAM
      I've gone deeper a little bit. There was a problem with the dump of a coll somewhere else in my patch. I've put a deferlow after the dump message and things are better : the first time, one of my 8 polybuffer is loaded, all is fine and audio goes on without being interupted but… if I want to load a buffer already loaded, once again the sound is off, roughly the time for the polybuffer to be loaded. I've tried to put once again a deferlow somewhere but all my trials were unsuccessful…
      Is there a way to load a polybuffer already loaded, i.e. clearing and loading after that, with a low priority ?
      Thanks for your help.
    • Mar 25 2012 | 7:22 pm
      Ok, here is an example.
      I can't load a polybuffer without a little cut of the sound produced by the cycle object, even the first time I load it.
    • Mar 28 2012 | 9:44 pm
      Am I the only one to have the audio engine turning off during the loading of a polybuffer ?
    • Apr 02 2012 | 2:53 pm
      I've replaced the polybuffer~ by 32 buffer~ and loaded all of them in one go (with uzi and umenu) and there isn't any interruption in the sound of the cycle~ playing at the same time.
      So, I'm sure now, there's a bug in the polybuffer~
    • May 24 2014 | 5:33 pm
      Not sure if this is correct place to post as I guess polybuffer~ is not beta anymore. I have a problem in that the "dump" message does not send the "path of the sound file". According to the documentation it should. OSX 10.9.2, Max 6.1.7
      Thanks Alan
    • May 24 2014 | 7:29 pm
      I think it's a mistake in the docs and should read, "name of the sound file" instead of "path of the sound file". Here's a way to get the path using [absolutepath] as long as the sound file is in your file preferences.
    • May 24 2014 | 7:44 pm
      Hi Rick, thanks for the patch. I'll have to check with a friend of mine. We are working on the same patch but he is on PC. I got the impression he was getting the file path from sending it a dump message. I'll post my findings.
      Thanks Alan
    • Jun 23 2014 | 3:54 pm
      Hi Rick
      Sorry for the delay in getting back. I have just checked the PC versus OSX version of polybuffer~. Both receive the same message and load the audio files but the information they display, and consequently dump is different. Image attached.