sfrecord~ patch problem

    Jul 22 2011 | 8:24 pm
    I'm having a strange problem when i put a message in sfrecord~ to create a audio file to record, it creates instantly the file somewhere inside cnmat folder that i have...i'm not even using Cnmat objects in this patch and i would like it to create in the folder of my patch, is this possible?...

    • Jul 23 2011 | 6:26 pm
      that's odd... does the [sfrecord~] helpfile do it as well?
    • Jul 25 2011 | 5:46 pm
      I tested now, in the helpfile creates in max folder...makes sense...
    • Aug 26 2011 | 6:35 pm
      Anyone can help with this, perhaps it's a bug or something... Today i tested again in a new patch, this patch is saved in a folder inside Documents, when i create a audio file now goes inside max folder in Applications, i really need the audio file to go to the same directory of the patch, any ideas how to do this?
    • Aug 27 2011 | 3:38 pm
    • Aug 27 2011 | 7:09 pm
      as it states in the [sfrecord~] documentation: "The word open without a filename argument brings up a standard Save As dialog allowing you to choose a filename. ... If open is followed by another symbol, it creates a file in the current default volume. An existing file with the same name will be overwritten. The format symbol (e.g., aiff) can follow the optional filename argument."
      the 'default volume' must be set to your prefered location. for this you would set a complete filepath + name.
    • Aug 27 2011 | 7:37 pm
      pid points to the correct relevant documentation.
      The default path when you first start Max is the Max application folder. After that it's the path of the most recently loaded patcher, I believe. You can ensure what folder the file is saved in by providing the complete path with the filename.
      pid's example shows how to ensure that the file is saved in the same folder as the patcher, by attaching the path of the patcher before the name of the file. One possible emendation of pid's example patch is that you might want to take steps to avoid problems caused by spaces in the pathname, such as "Macintosh HD/..."
    • Aug 28 2011 | 12:22 am
      Thank you very much for the help, pid and Christopher! Problem solved now! :)