|

»

Bugs/Errors with opcodes, strings, filenames and Windows

View: New views

5 Messages — Rating Filter: Alert me

	Bugs/Errors with opcodes, strings, filenames and Windows by Jacob Joaquin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hello Everyone, Ran into a few issues with the last Csound Blog I posted. So far, it seems these issues only affect Windows users, though I have not confirmed whether or not Linux users are having problems. OS X works fine. 1. francibal reported an issue with file names possibly not working with leading numbers. " i don't know why but filename beginning with number are not recognized, or something similar" 2. Opcodes and strings seem to be not working. I've attached opcode_string.csd to this email. I've been using this code for years on OS X and have never run into a problem. It still works. One thing francibal pointed out was that in the manual entry for opcode, it says that String outputs are not supported. It works on my system for some reason. That affects the UDO objget_S. However, even with all code related to objget_S commented out, there are reported issues with objcreate_S and objset_S, which do not output an S value. Best, Jake -- The Csound Blog - http://csound.noisepages.com/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Csound-devel mailing list Csound-devel@... https://lists.sourceforge.net/lists/listinfo/csound-devel opcode_string.csd (1K) Download Attachment
	Re: Bugs/Errors with opcodes, strings, filenames and Windows by richarddobson :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Jacob Joaquin wrote: > Hello Everyone, > > Ran into a few issues with the last Csound Blog I posted. So far, it > seems these issues only affect Windows users, though I have not > confirmed whether or not Linux users are having problems. OS X works > fine. > > 1. francibal reported an issue with file names possibly not working > with leading numbers. " i don't know why but filename beginning with > number are not recognized, or something similar" > Not a Windows problem (unless radically changed in Vista, W7 etc); Windows has file names with leading numbers all over the place, and file names comprised entirely of numbers (or entirely in hex) are far from uncommon. You can have a directory name of all digits too. Not necessarily a good idea, but you can do it. OS X does of course allow a whole tranche of characters in filenames (etc) that Windows (and NAS systems, most tiresome) does not accept; *?:\ among them. Richard Dobson ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Csound-devel mailing list Csound-devel@... https://lists.sourceforge.net/lists/listinfo/csound-devel
	Re: Bugs/Errors with opcodes, strings, filenames and Windows by Jacob Joaquin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The file name in question is "105 Blanketed Lama.wav". The only thing I see that might be a problem is the use of space characters. Are spaces allowed in Windows? Best, Jake -- The Csound Blog - http://csound.noisepages.com/ > Not a Windows problem (unless radically changed in Vista, W7 etc); > Windows has file names with leading numbers all over the place, and file > names comprised entirely of numbers (or entirely in hex) are far from > uncommon. You can have a directory name of all digits too. Not > necessarily a good idea, but you can do it. > > OS X does of course allow a whole tranche of characters in filenames > (etc) that Windows (and NAS systems, most tiresome) does not accept; > *?:\ among them. > > Richard Dobson > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Csound-devel mailing list > Csound-devel@... > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Csound-devel mailing list Csound-devel@... https://lists.sourceforge.net/lists/listinfo/csound-devel
	Re: Bugs/Errors with opcodes, strings, filenames and Windows by Jacob Joaquin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some good news, it seems there is no error with the file name. Francibal reports he had a typo, and that the original file name works. Now it seems the only problem(s) is with strings and udos. Best, Jake On Sun, Oct 25, 2009 at 11:28 AM, Jacob Joaquin <jacobjoaquin@...> wrote: > The file name in question is "105 Blanketed Lama.wav". The only thing > I see that might be a problem is the use of space characters. Are > spaces allowed in Windows? > > Best, > Jake > -- > The Csound Blog - http://csound.noisepages.com/ > >> Not a Windows problem (unless radically changed in Vista, W7 etc); >> Windows has file names with leading numbers all over the place, and file >> names comprised entirely of numbers (or entirely in hex) are far from >> uncommon. You can have a directory name of all digits too. Not >> necessarily a good idea, but you can do it. >> >> OS X does of course allow a whole tranche of characters in filenames >> (etc) that Windows (and NAS systems, most tiresome) does not accept; >> *?:\ among them. >> >> Richard Dobson >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@... >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > -- The Csound Blog - http://csound.noisepages.com/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Csound-devel mailing list Csound-devel@... https://lists.sourceforge.net/lists/listinfo/csound-devel
	Re: Bugs/Errors with opcodes, strings, filenames and Windows by Art Hunkins :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message IIRC, spaces are fine in Windows XP and later, but not in Windows ME and earlier. Art Hunkins ----- Original Message ----- From: "Jacob Joaquin" <jacobjoaquin@...> To: <richarddobson@...>; "Developer discussions" <csound-devel@...> Sent: Sunday, October 25, 2009 2:28 PM Subject: Re: [Cs-dev] Bugs/Errors with opcodes, strings,filenames and Windows > The file name in question is "105 Blanketed Lama.wav". The only thing > I see that might be a problem is the use of space characters. Are > spaces allowed in Windows? > > Best, > Jake > -- > The Csound Blog - http://csound.noisepages.com/ > >> Not a Windows problem (unless radically changed in Vista, W7 etc); >> Windows has file names with leading numbers all over the place, and file >> names comprised entirely of numbers (or entirely in hex) are far from >> uncommon. You can have a directory name of all digits too. Not >> necessarily a good idea, but you can do it. >> >> OS X does of course allow a whole tranche of characters in filenames >> (etc) that Windows (and NAS systems, most tiresome) does not accept; >> *?:\ among them. >> >> Richard Dobson >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@... >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Csound-devel mailing list > Csound-devel@... > https://lists.sourceforge.net/lists/listinfo/csound-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Csound-devel mailing list Csound-devel@... https://lists.sourceforge.net/lists/listinfo/csound-devel