wahwah

I was trying out the 'write' command to save results into a text file. I try saving it to "C:Documents and Settings/Administrator/Desktop/Other stuff/Images/output" and it works. However, when i change the pathname to "C:output", it shows an error stating an error in creating the file. Is it impossible to save a file in "c:" directory or is there a way to do it? Can someone enlighten me please?

Hi, 
I was trying out the 'write' command to save results  into a text file. I try saving it to "C:Documents and Settings/Administrator/Desktop/Other stuff/Images/output" and it works. However, when i change the pathname to "C:output", it shows an error stating an error in creating the file. Is it impossible to save a file in "c:" directory or is there a way to do it? Can someone enlighten me please?
Thank you.


how-to-save-text-file-in-c

> I was trying out the 'write' command to save results to to a text 

> file. I try saving it to "C:Documents and Settings/Administrator/ 

> Desktop/Other stuff/Images/output" and it works. However, when i 

> change the pathname to "C:output", it shows an error stating an 

> error in creating the file. Is it impossible to save a file in "c:" 

> directory or is there a way to do it? Can someone enlighten me please?

>
> Hi,
> I was trying out the 'write' command to save results to to a text  
> file. I try saving it to "C:Documents and Settings/Administrator/ 
> Desktop/Other stuff/Images/output" and it works. However, when i  
> change the pathname to "C:output", it shows an error stating an  
> error in creating the file. Is it impossible to save a file in "c:"  
> directory or is there a way to do it? Can someone enlighten me please?
> Thank you.


I tried that already. It' not working either.=(

Quote: wahwah wrote on Wed, 14 February 2007 02:07

----------------------------------------------------

> I tried that already. It' not working either.=(

thats point of the discussion where someone should

recommend him to use a macintosh, read the manual,

Quote: wahwah wrote on Wed, 14 February 2007 02:07
----------------------------------------------------
> Try "c:/output"
>
> jb
>
>
> I tried that already. It' not working either.=(
----------------------------------------------------

thats point of the discussion where someone should
recommend him to use a macintosh, read the manual,
and then do it with javascript.

Quote: Roman Thilenius wrote on Wed, 14 February 2007 11:45

> Quote: wahwah wrote on Wed, 14 February 2007 02:07

> ----------------------------------------------------

> > I tried that already. It' not working either.=(

> thats point of the discussion where someone should

> recommend him to use a macintosh, read the manual,

Quote: Roman Thilenius wrote on Wed, 14 February 2007 11:45
----------------------------------------------------
> Quote: wahwah wrote on Wed, 14 February 2007 02:07
> ----------------------------------------------------
> > Try "c:/output"
> >
> > jb
> >
> >
> > I tried that already. It' not working either.=(
> ----------------------------------------------------
>
>
> thats point of the discussion where someone should
> recommend him to use a macintosh, read the manual,
> and then do it with javascript.
>
> stefan mb?

>
>
> sorry i couldnt resist.
----------------------------------------------------


erm? please tell me I am missing something here.

Sorry for the late reply. My program is here.

I'm using windows XP (might switch to using mac next time),have read the manual and i know Javascript can work. I was just wondering why max's write command cannot write to "c:" directory. Btw, it's she not him. =P

It should work....i'm pretty sure i've got it working before...try C: as windows is not unix based it don't know what the hell a '/' does. one of the little quirks of win32 i suppose. Why suggest to buy a mac. they cost alot and don't do half the things PC's do. Yeh i suppose there is much more max support and externels etc but i get one fine with my windows and linux stuff. Windows most likely won't understand the command c: either.

I'm pretty new to Max/MSP...been learning fora bout 5 months now and i love it... And the Windows version is fine...so the 'buy a mac' answer is pretty pointless as they are really expensive and are just a shiney pc with a glorified version on linux pre-installed which is limited. Anyway the Mac/Pc argument is nver ending.

Windows doesn't know what the hell a '/' is in a directory as it is not unix based. One of the fun little quirks of Win32 i suppose. Use '' instead of '/'.

Good to see more max windows users too. It is worth it...someof the os-x only externals are missing but hey...life can't be perfect.

Oh man...lol..Ive got it working!! Haha..thanks for your advice Macca. 

I've tried or / or \ or // last time and it didnt work last time cause i wrote [write "C:output"]. It should be [write c:output]. (Don't know why the "" matters.)

Anyway, thanks for all the help guys.=) Yeah~ I'm a satisfied and happy Max user.

Oh man...lol..Ive got it working!! Haha..thanks for your advice Macca. 
I've tried  or / or \ or // last time and it didnt work last time cause i wrote [write "C:output"]. It should be [write c:output]. (Don't know why the "" matters.)
Anyway, thanks for all the help guys.=) Yeah~ I'm a satisfied and happy Max user.


> Windows doesn't know what the hell a '/' is in a directory as it is 

You can learn a lot by reading the Max documentation on file paths.

> Anyway the Mac/Pc argument is nver ending.

And thank you *so* much for raising the level of discourse. 

> Windows doesn't know what the hell a '/' is in a directory as it is  
> not unix based.

And thank you *so* much for raising the level of discourse.  
"Glorified version of linux" indeed.

How come when ever a forum post fails cos of servers and what not and then i go back adn re-write it but oviusly different as i have a crap memory it posts both...its makes me rather mad....

of course max knows what a / is...windows KNOWS what a / is but it doesn't when you stick it in a fie path. c:program filescycling74max...etc is valid when c:/program files etc isn't. Its not a negative thing as such...its just simply how its made....so if you tell max to look for file or save a file with /'s in it it won't know what to do as the file system can't search it...its got nothing to do with what max can understand. Plus yes reading the documentation is fine as the max manual etc are great but when you trying to solve a problem for most people it just turns into jibberish and can make the problem worse....hence the reasons for asking questions on forums. I'm pretty much still a newbie at max but i still try to help people out the same way i would hope that others would help me out if i asked a question.

How come when ever a forum post fails cos of servers and what not and then i go back adn re-write it but oviusly different as i have a crap memory it posts both...its makes me rather mad....
Glad you got it working.

of course max knows what a / is...windows KNOWS what a / is but it doesn't when you stick it in a fie path. c:program filescycling74max...etc is valid when c:/program files etc isn't. Its not a negative thing as such...its just simply how its made....so if you tell max to look for file or save a file with /'s in it it won't know what to do as the file system can't search it...its got nothing to do with what max can understand. Plus yes reading the documentation is fine as the max manual etc are great but when you trying to solve a problem for most people it just turns into jibberish and can make the problem worse....hence the reasons for asking questions on forums. I'm pretty much still a newbie at max but i still try to help people out the same way i would hope that others would help me out if i asked a question.


> of course max knows what a / is...windows KNOWS what a / is but it

> doesn't when you stick it in a fie path. c:program

> filescycling74max...etc is valid when c:/program files etc isn't.

> Its not a negative thing as such...its just simply how its made....so

> if you tell max to look for file or save a file with /'s in it it

> won't know what to do as the file system can't search it...its got

> nothing to do with what max can understand. Plus yes reading the

Um... You *totally* need to reread the docs. Max does not necessarily 

handle file paths in the most obvious way possible. It's a 

multi-platform program that is aware of being a multi-platform program. 

There are objects in the standard set designed to deal with precisely 

It's fine to ask questions without doing the research - though it's 

sometimes annoying - but it's not fine to answer questions with a tone 

of authority without having done the (very basic) research.

That said, file paths in Max have been tripping people up since before 

Macca wrote:
> of course max knows what a / is...windows KNOWS what a / is but it
> doesn't when you stick it in a fie path. c:program
> filescycling74max...etc is valid when c:/program files etc isn't.
> Its not a negative thing as such...its just simply how its made....so
> if you tell max to look for file or save a file with /'s in it it
> won't know what to do as the file system can't search it...its got
> nothing to do with what max can understand. Plus yes reading the

Um... You *totally* need to reread the docs.  Max does not necessarily 
handle file paths in the most obvious way possible.  It's a 
multi-platform program that is aware of being a multi-platform program. 
  There are objects in the standard set designed to deal with precisely 
these sorts of problems.

It's fine to ask questions without doing the research - though it's 
sometimes annoying - but it's not fine to answer questions with a tone 
of authority without having done the (very basic) research.

That said, file paths in Max have been tripping people up since before 
Max ran on WinXP.


Quote: dlurk wrote on Sat, 17 February 2007 04:05

> file paths in Max have been tripping people up since before 

yeah, but that's mostly due to the concept of the 'symbol' vs the 'list'. Or in simple words: paths with spaces need quotes before being sent to a prepend read, paths without spaces don't. Before you figure that out (and the fact that to- and fromsymbol are designed to 'solve' that problem), filepaths are hell.

Quote: dlurk wrote on Sat, 17 February 2007 04:05
----------------------------------------------------
> file paths in Max have been tripping people up since before 
> Max ran on WinXP.

Also on a general note files paths in windows are Hell compared to unix anyway. So with it all added together files paths on the windows version of Max = double hell. Windows is a love hate relationship with many people anyway.

And i didn't mean to make a authoritive tone with my statements....its just i had the same problems so i thought i would share my solution.

I just don't like mac/windows hostilities ... when they are equally as powerful in many ways.

I have to deal with shit all the time because im a PC user and in the UK university Music tech scene Macs seem to have some crazt power over everyone.

But at the end of the day im glad your filepath problem was solved and i apologise again for any 'authoritive' statements.

Also on a general note files paths in windows are Hell compared to unix anyway. So with it all added together files paths on the windows version of Max = double hell. Windows is a love hate relationship with many people anyway. 

I just don't like mac/windows hostilities ... when they are equally as powerful in many ways. 

But at the end of the day im glad your filepath problem was solved and i apologise again for any 'authoritive' statements.


I actually think that this qualifies as a bug. The correct syntax 

should be "C:/output". I remember that we've fixed this problem in 

various places in the program. Possibly not in this place, though. 

> Oh man...lol..Ive got it working!! Haha..thanks for your advice Macca.

> I've tried or / or \ or // last time and it didnt work last time 

> cause i wrote [write "C:output"]. It should be [write c:output]. 

> Anyway, thanks for all the help guys.=) Yeah~ I'm a satisfied and 

I actually think that this qualifies as a bug. The correct syntax  
should be "C:/output". I remember that we've fixed this problem in  
various places in the program. Possibly not in this place, though.  
I'll forward the issue to support.

>
> Oh man...lol..Ive got it working!! Haha..thanks for your advice Macca.
> I've tried  or / or \ or // last time and it didnt work last time  
> cause i wrote [write "C:output"]. It should be [write c:output].  
> (Don't know why the "" matters.)
> Anyway, thanks for all the help guys.=) Yeah~ I'm a satisfied and  
> happy Max user.


Ok. Glad that i could help in pointing out a bug.=)

put a windows filepath, for example, "C:program filesCommon FilesCycling '74jsextensions" into a message box and attach it to a "print" object, then, click on the message box [make sure max window is open] to see what max "does" with backslashes.

> put a windows filepath, for example, "C:program filesCommon Files 

> Cycling '74jsextensions" into a message box and attach it to a 

> "print" object, then, click on the message box [make sure max 

> window is open] to see what max "does" with backslashes.

No surprise here, really. Backslash has been the escape character in 

Max forever. Probably going back to Miller Puckette's text-based 

The documentation of this is a little sparse, but there are 

indications in the Punctuation section of Topics.

As any C/C++/Java programmer will tell you, ya want backslashes, ya 

"C:\program files\Common Files\Cycling '74\jsextensions"

If the text is parsed a second time (which can happen), you may need 

to escape the escaped backslashes with escaped backslashes.

"C:\\program files\\Common Files\\Cycling '74\\jsextensions"

And every time you edit your text, it will be reparsed, so don't 

All of this has been discussed in the archives ad nauseum.

It wouldn't be a bad idea to add a note about this in the file path 

section, because people using MS-DOS style path delimiters tend to 

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

On 18-Feb-2007, at 16:03, James wrote:
> put a windows filepath, for example, "C:program filesCommon Files 
> Cycling '74jsextensions" into a message box and attach it to a  
> "print" object, then, click on the message box [make sure max  
> window is open] to see what max "does" with backslashes.

No surprise here, really. Backslash has been the escape character in  
Max forever. Probably going back to Miller Puckette's text-based  
scheduling language, The Patcher.

The documentation of this is a little sparse, but there are  
indications in the Punctuation section of Topics.

As any C/C++/Java programmer will tell you, ya want backslashes, ya  
gotta escape 'em:

   "C:\program files\Common Files\Cycling '74\jsextensions"

If the text is parsed a second time (which can happen), you may need  
to escape the escaped backslashes with escaped backslashes.

   "C:\\program files\\Common Files\\Cycling '74\\jsextensions"

And every time you edit your text, it will be reparsed, so don't  
forget to add those escapes back in.

It wouldn't be a bad idea to add a note about this in the file path  
section, because people using MS-DOS style path delimiters tend to  
get flustered about it.

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

Maybe I should have noted it was just an example for people who didn't understand.

So does this finally classify max as a programming language rather than a performance instrument? ;)

Quote: Peter Castine wrote on Sun, 18 February 2007 17:13

> > put a windows filepath, for example, "C:program filesCommon Files 

> > Cycling '74jsextensions" into a message box and attach it to a 

> > "print" object, then, click on the message box [make sure max 

> > window is open] to see what max "does" with backslashes.

> No surprise here, really. Backslash has been the escape character in 

> Max forever. Probably going back to Miller Puckette's text-based 

> The documentation of this is a little sparse, but there are 

> indications in the Punctuation section of Topics.

> As any C/C++/Java programmer will tell you, ya want backslashes, ya 

> "C:\program files\Common Files\Cycling '74\jsextensions"

> If the text is parsed a second time (which can happen), you may need 

> to escape the escaped backslashes with escaped backslashes.

> "C:\\program files\\Common Files\\Cycling '74\\jsextensions"

> And every time you edit your text, it will be reparsed, so don't 

> All of this has been discussed in the archives ad nauseum.

> It wouldn't be a bad idea to add a note about this in the file path 

> section, because people using MS-DOS style path delimiters tend to 

Quote: Peter Castine wrote on Sun, 18 February 2007 17:13
----------------------------------------------------
> On 18-Feb-2007, at 16:03, James wrote:
> > put a windows filepath, for example, "C:program filesCommon Files 
> > Cycling '74jsextensions" into a message box and attach it to a  
> > "print" object, then, click on the message box [make sure max  
> > window is open] to see what max "does" with backslashes.
>
> No surprise here, really. Backslash has been the escape character in  
> Max forever. Probably going back to Miller Puckette's text-based  
> scheduling language, The Patcher.
>
> The documentation of this is a little sparse, but there are  
> indications in the Punctuation section of Topics.
>
> As any C/C++/Java programmer will tell you, ya want backslashes, ya  
> gotta escape 'em:
>
>    "C:\program files\Common Files\Cycling '74\jsextensions"
>
> If the text is parsed a second time (which can happen), you may need  
> to escape the escaped backslashes with escaped backslashes.
>
>    "C:\\program files\\Common Files\\Cycling '74\\jsextensions"
>
> And every time you edit your text, it will be reparsed, so don't  
> forget to add those escapes back in.
>
> All of this has been discussed in the archives ad nauseum.
>
> It wouldn't be a bad idea to add a note about this in the file path  
> section, because people using MS-DOS style path delimiters tend to  
> get flustered about it.
>


On Feb 18, 2007, at 1:20 PM, Mattijs Kneppers wrote:

> So does this finally classify max as a programming language rather 

> Quote: Peter Castine wrote on Sun, 18 February 2007 17:13

>> On 18-Feb-2007, at 16:03, James wrote:

>>> put a windows filepath, for example, "C:program filesCommon Files

>>> Cycling '74jsextensions" into a message box and attach it to a

>>> "print" object, then, click on the message box [make sure max

>>> window is open] to see what max "does" with backslashes.

>> No surprise here, really. Backslash has been the escape character in

>> Max forever. Probably going back to Miller Puckette's text-based

>> The documentation of this is a little sparse, but there are

>> indications in the Punctuation section of Topics.

>> As any C/C++/Java programmer will tell you, ya want backslashes, ya

>> "C:\program files\Common Files\Cycling '74\jsextensions"

>> If the text is parsed a second time (which can happen), you may need

>> to escape the escaped backslashes with escaped backslashes.

>> "C:\\program files\\Common Files\\Cycling '74\ 

>> And every time you edit your text, it will be reparsed, so don't

>> All of this has been discussed in the archives ad nauseum.

>> It wouldn't be a bad idea to add a note about this in the file path

>> section, because people using MS-DOS style path delimiters tend to

> Interactive audiovisual sampling soft- and hardware

>
> So does this finally classify max as a programming language rather  
> than a performance instrument? ;)
>
> Quote: Peter Castine wrote on Sun, 18 February 2007 17:13
> ----------------------------------------------------
>> On 18-Feb-2007, at 16:03, James wrote:
>>> put a windows filepath, for example, "C:program filesCommon Files
>>> Cycling '74jsextensions" into a message box and attach it to a
>>> "print" object, then, click on the message box [make sure max
>>> window is open] to see what max "does" with backslashes.
>>
>> No surprise here, really. Backslash has been the escape character in
>> Max forever. Probably going back to Miller Puckette's text-based
>> scheduling language, The Patcher.
>>
>> The documentation of this is a little sparse, but there are
>> indications in the Punctuation section of Topics.
>>
>> As any C/C++/Java programmer will tell you, ya want backslashes, ya
>> gotta escape 'em:
>>
>>    "C:\program files\Common Files\Cycling '74\jsextensions"
>>
>> If the text is parsed a second time (which can happen), you may need
>> to escape the escaped backslashes with escaped backslashes.
>>
>>    "C:\\program files\\Common Files\\Cycling '74\ 
>> jsextensions"
>>
>> And every time you edit your text, it will be reparsed, so don't
>> forget to add those escapes back in.
>>
>> All of this has been discussed in the archives ad nauseum.
>>
>> It wouldn't be a bad idea to add a note about this in the file path
>> section, because people using MS-DOS style path delimiters tend to
>> get flustered about it.
>>
>
> --
> SmadSteck - http://www.smadsteck.nl
> Interactive audiovisual sampling soft- and hardware
>

Quote: vade wrote on Sun, 18 February 2007 19:39

> On Feb 18, 2007, at 1:20 PM, Mattijs Kneppers wrote:

> > So does this finally classify max as a programming language rather 

> > Quote: Peter Castine wrote on Sun, 18 February 2007 17:13

> > ----------------------------------------------------

> >> On 18-Feb-2007, at 16:03, James wrote:

> >>> put a windows filepath, for example, "C:program filesCommon Files

> >>> Cycling '74jsextensions" into a message box and attach it to a

> >>> "print" object, then, click on the message box [make sure max

> >>> window is open] to see what max "does" with backslashes.

> >> No surprise here, really. Backslash has been the escape character in

> >> Max forever. Probably going back to Miller Puckette's text-based

> >> The documentation of this is a little sparse, but there are

> >> indications in the Punctuation section of Topics.

> >> As any C/C++/Java programmer will tell you, ya want backslashes, ya

> >> "C:\program files\Common Files\Cycling '74\jsextensions"

> >> If the text is parsed a second time (which can happen), you may need

> >> to escape the escaped backslashes with escaped backslashes.

> >> "C:\\program files\\Common Files\\Cycling '74\ 

> >> And every time you edit your text, it will be reparsed, so don't

> >> forget to add those escapes back in.

> >> All of this has been discussed in the archives ad nauseum.

> >> It wouldn't be a bad idea to add a note about this in the file path

> >> section, because people using MS-DOS style path delimiters tend to

> > Interactive audiovisual sampling soft- and hardware

Quote: vade wrote on Sun, 18 February 2007 19:39
----------------------------------------------------
> Dont get started. *cough*

>
> On Feb 18, 2007, at 1:20 PM, Mattijs Kneppers wrote:
>
> >
> > So does this finally classify max as a programming language rather  
> > than a performance instrument? ;)
> >
> > Quote: Peter Castine wrote on Sun, 18 February 2007 17:13
> > ----------------------------------------------------
> >> On 18-Feb-2007, at 16:03, James wrote:
> >>> put a windows filepath, for example, "C:program filesCommon Files
> >>> Cycling '74jsextensions" into a message box and attach it to a
> >>> "print" object, then, click on the message box [make sure max
> >>> window is open] to see what max "does" with backslashes.
> >>
> >> No surprise here, really. Backslash has been the escape character in
> >> Max forever. Probably going back to Miller Puckette's text-based
> >> scheduling language, The Patcher.
> >>
> >> The documentation of this is a little sparse, but there are
> >> indications in the Punctuation section of Topics.
> >>
> >> As any C/C++/Java programmer will tell you, ya want backslashes, ya
> >> gotta escape 'em:
> >>
> >>    "C:\program files\Common Files\Cycling '74\jsextensions"
> >>
> >> If the text is parsed a second time (which can happen), you may need
> >> to escape the escaped backslashes with escaped backslashes.
> >>
> >>    "C:\\program files\\Common Files\\Cycling '74\ 
> >> jsextensions"
> >>
> >> And every time you edit your text, it will be reparsed, so don't
> >> forget to add those escapes back in.
> >>
> >> All of this has been discussed in the archives ad nauseum.
> >>
> >> It wouldn't be a bad idea to add a note about this in the file path
> >> section, because people using MS-DOS style path delimiters tend to
> >> get flustered about it.
> >>
> >
> > --
> > SmadSteck - http://www.smadsteck.nl
> > Interactive audiovisual sampling soft- and hardware
> >
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
----------------------------------------------------


i see what you mean with the escape backslashes. Doubles send the backslashes through. I would class Max as a program language with can be used a performance tool.

I've always used backslashes for the reason that i've only even been a windows user. When i delved into the black magic of Unix based systems i got realy annoyed with forward slashes.

How to save text file in "c:"?