set recording path for sfrecord~
How do I change the record path for aif files I create using sfrecord~. By default the files are ending up in max's extra's folder. I want them on the desktop for easier access. I've attached a photo of my patch.
Thanks in advance!
Jean-Paul
Help! Does anyone have any ideas on how to solve my problem???
On Dec 9, 2008, at 2:55 PM, Jean-Paul Perrotte wrote:
> How do I change the record path for aif files I create using
> sfrecord~.
Open them with a path and not just a file name.
-C
Chris Muir
cbm@well.com
http://www.xfade.com
Just send the "open" message sfrecord~ instead of "open filename". That way, it will open a file browser, you browse to the folder you want, type a filename, hit OK. Then you can record as usual and it will go to the place you just selected.
No good. There are too many steps. I don't want to select a drive then type a title for the file on stage. There MUST be a better way to set a recording path like ever other DAW Logic, Protools etc... to store the file on the desk top if that is where I want it.
More ideas...?
Jean-Paul
On Dec 11, 2008, at 12:26 AM, Jean-Paul Perrotte wrote:
> No good. There are too many steps. I don't want to select a drive
> then type a title for the file on stage. There MUST be a better way
> to set a recording path like ever other DAW Logic, Protools etc...
> to store the file on the desk top if that is where I want it.
I really don't see what is so hard about sending the message open with
a full path, as opposed to open with a file name. In your example, you
have a message box with a file name in it. Just add the path to where
you want to put it. It would be easy enough to have an abstraction
that prepended the path to file names that you pass in to it.
I think it's also worth pointing out that Max is a programming
environment, and not a DAW, per se.
- C
Chris Muir
cbm@well.com
http://www.xfade.com
maybe something like this?
HTH
ole
Yes Chris and oe7 that's along the lines I was looking for. I realize that Max is a programing environment but I guess I was wondering why does the sound file end up in the extras folder in Max in applications as a default. Is there any place to change the path in DSP status or preferences. To set a new default.
Thanks,
Jean-Paul
On Dec 11, 2008, at 9:01 AM, Jean-Paul Perrotte wrote:
> I realize that Max is a programing environment but I guess I was
> wondering why does the sound file end up in the extras folder in Max
> in applications as a default. Is there any place to change the path
> in DSP status or preferences. To set a new default.
I don't think new files are going to the Extras folder specifically. I
think it's going to the last folder accessed, which for you is the
Extras folder, maybe because you routinely open an Extra?
At any rate, it's good practice to prepend a path so that files are
placed where you expect.
- C
Chris Muir
cbm@well.com
http://www.xfade.com
You are right Chris, I set up a meter In to monitor audio input. That makes sense. Setting up the path w/ an argument like oe7 did works for me.
Thanks everyone for your help!
Jean-Paul
> Just send the "open" message sfrecord~ instead of "open filename".
> That way, it will open a file browser, you browse to the folder you
> want, type a filename, hit OK. Then you can record as usual and it
> will go to the place you just selected.
well - the problem is really that you cannot set a path for the file
you want to record in - was trying to use 2 filenames for swapping
recording and playback and it is really a drag... (somehow we want our
machines to behave like autonomous machines and functioning while we
artists can sleep) seems like sfrecord~ is saving the files in the
folder you ever last opened from max (in the middle of the help files
for instance, this is baaaadddd) bweeeeeee help?
Quote: givan bela wrote on Thu, 11 December 2008 17:07
> well - the problem is really that you cannot set a path for the file
> you want to record in
Sure you can. You just have to do a little work first. I imagine that most Max programmers have their own way of managing file paths. I've done it several ways for different projects. Ole posted an abstraction earlier in this thread that you might find helpful.
If that one doesn't work for you, I'll extract something from one of my patches.
- C
Quote: JPP wrote on Fri, 12 December 2008 12:51
----------------------------------------------------
> I've tried using date as ole wrote earlier but the files would record over each other.
> Jean-Paul
----------------------------------------------------
??
It is very easy to simplify what I suggested. But I have to admit that I do not really understand what you are after.
ole
I find that, all too often, I tend to forget things I'm "not supposed to do
in order for a patch to work"--like not opening a help file. How about a
simple startup message connected to a dummy [sfplay~] that forces you to
"set the record path" anytime you perform with this patch? Bulletproof
performances are a rarity in the Max world...I try to put these kinds of
safeguards in all the time now, after being burned more than a few times. :)
--Brennon
On Dec 12, 2008, at 3:51 AM, Jean-Paul Perrotte wrote:
> I'll keep trying other options... What do you think?
Here are a couple of sub-patchers (in the same patcher for mailing
list ease) that manage a very simple path preference system.
This was hastily extracted from a larger patch, and not really tested
in this form. It should work, but let me know if it doesn't.
-C
Chris Muir
cbm@well.com
http://www.xfade.com
On Dec 12, 2008, at 7:21 AM, Brennon Bortz wrote:
> I find that, all too often, I tend to forget things I'm "not
> supposed to do
> in order for a patch to work"--like not opening a help file. How
> about a
> simple startup message connected to a dummy [sfplay~] that forces
> you to
> "set the record path" anytime you perform with this patch?
> Bulletproof
> performances are a rarity in the Max world...I try to put these
> kinds of
> safeguards in all the time now, after being burned more than a few
> times. :)
There isn't a list of things you're "not supposed to do in order for a
patch to work", but there is a list of things that you _are_ supposed
to do when programming your patch to make it reliable.
Max is a programming environment. If you program it correctly, it will
work correctly.
- C
Chris Muir
cbm@well.com
http://www.xfade.com
Quote: Chris Muir wrote on Fri, 12 December 2008 19:09
----------------------------------------------------
> There isn't a list of things you're "not supposed to do in order for a
> patch to work", but there is a list of things that you _are_ supposed
> to do when programming your patch to make it reliable.
You say potato...
> Max is a programming environment. If you program it correctly, it will
> work correctly.
Are you seriously claiming that Max is bulletproof? I can't count the number of times it hasn't worked correctly--both with my patches and those of others.
In the end, though, what I was proposing WAS something to make a patch more reliable...wasn't it??
On Dec 12, 2008, at 11:23 AM, Brennon Bortz wrote:
> Quote: Chris Muir wrote on Fri, 12 December 2008 19:09
> ----------------------------------------------------
>> There isn't a list of things you're "not supposed to do in order
>> for a
>> patch to work", but there is a list of things that you _are_ supposed
>> to do when programming your patch to make it reliable.
>
> You say potato...
I don't think we _are_ saying the same thing, actually. I'm saying
that you can use the existing Max file rules just fine, you just have
to program it in.
>> Max is a programming environment. If you program it correctly, it
>> will
>> work correctly.
>
> Are you seriously claiming that Max is bulletproof? I can't count
> the number of times it hasn't work correctly--both with my patches
> and those of others.
There is no piece of software that is bulletproof. Max is a piece of
software. Therefore, Max is not bulletproof.
What I am saying, is that if you program a patcher correctly, this
file path problem just goes away.
I have shared many patchers. I have used many other people's patchers.
There have been problems with some of them (mine and other people's),
but mostly because something wasn't properly catered for. Overall, Max
can be a pretty robust environment.
If you find a bug or missing feature in another program (e.g.
ProTools), do you blame the C compiler that generated the program, or
the person/company who wrote the program? In this example Max is
closer to the C compiler than ProTools, I think. It's up to Max
programmers to do the right thing.
> In the end, though, what I was proposing WAS something to make a
> patch more reliable...wasn't it??
It seems to me that you were suggesting a potentially significant
change to the way Max deals with file paths generally, to work around
this specific sfrecord~ file path thing, when you can easily program
correct path behavior yourself. This sfrecord~ file path thing is just
not a hard problem, IMO.
-C
Chris Muir
cbm@well.com
http://www.xfade.com