Error in saving message

Audacity Forum

For questions, answers and opinions

Error saving message

Forum rules
This forum is now closed.

For help with current Audacity, please post to the 2.x. board for your operating system.

Please post feedback about the current 2.x version on the 2.x.feedback board.

Error saving message

Post by VHF » Tue Feb 16, 2010 9:42 pm

After a lot of searching, I now learn that Audacity is unduly sensitive to the characters one uses to name one’s project. Meanwhile I had been told that there was an error saving my projects, and as a result a lot of work went down the drain.

The message basically says . Perhaps your disk is full. What nonsense in 2010! Before 2.0 is released can someone update this error message? New users need to be told two things: one, they should try renaming the project using the plainest characters; second, they should be advised that exporting to a lossless format (AIFF or WAV) will effectively preserve their work too.

Re: Error saving message

Post by kozikowski » Tue Feb 16, 2010 10:15 pm

I know it doesn’t seem like it, but the elves on the forum have been trying to get the developers to improve things like that forever. My favorite change would be in the Save Project dialog. [You are not saving a sound File!]

Your above comment is a little harder. That does not work if the user has more than one stereo track. Then each stereo track must be exported separately and suddenly the instructions don’t fit on an automobile bumper sticker or Post-It Note any more.

Someone will correct me, but the only uncompressed multi-channel sound format is Broadcast WAV which very few people support.

I’m going to post a link to this on the Improve Audacity forum.

By the way, I don’t think odd filename characters are an Audacity problem. All Audacity does is go out and tries to save MyMusic12/3/98.wav sound file and it’s the operating system that throws up. You can’t do that in Photoshop or Excel, either.

Re: Error saving message

Post by VHF » Wed Feb 17, 2010 3:12 am

Diligently, I found one reference to forbidden characters nested somewhere in the forum. If I hadn’t found that I would have trashed the program and never looked back. I’m sure countless users have done that already and we just never hear from them.

I assumed this problem was universal, which is why I didn’t post specifically to the OSX sub-forum, the environment in which I work. The characters in question work fine for me in all other programs, so I still assume the problem is with Audacity, or at best with the way Audacity interacts with a Mac system.

My suggestion about including the suggestion to export just has to do with offering a possibly useful workaround to someone who might be at wit’s end, facing the potential loss of hours of work.

There was also supposed to have been an auto-save function, which does not seem ever to have kicked in. I’m assuming now, for the same reason. (How about a meaningful error message then, to the effect, we’re scheduled to be doing an auto-save now, but can’t because of your file name. Change it, human, or else.)

Re: Error saving message

Post by billw58 » Wed Feb 17, 2010 4:11 am

Which characters specifically were the problem?

This needs further testing. I’m on a Mac, 10.5.8 PPC, Audacity 1.3.12-Feb 14. I’ve just successfully saved projects named:
test/this/name (saves unchanged)
test:this:name (the save dialog changes the «:» characters to «-» — a legacy issue from the days when the Mac OS used «:» instead of «/» for path names)
test-this-name? (saves unchanged)
test-this*name? (saves unchanged)
But I got the «disk full?» message with
testthis*name?

The error with autosave may have to do with not going through the Mac save dialog, which apparently filters the «/» character. Without that filtering, a file name with a slash in it may be interpreted as a partial path name.

A similar issue appears with Export Multiple, which does not go through the Mac save dialog. Using «/» characters in labels (which are used for the file names) results in a «directory not found» error. Strangely, AFAIK, the export multiple function does not trap the «/» character as illegal, but it does trap «*» and «?».

This may also have to do with the cross-platform basis of Audacity — certain characters are illegal in file names on different OS’s.

Further to that, filtering/replacement of all illegal characters whenever anything is saved (a project or an exported file) would be nice. That way you could send your project to someone working on a different OS and it would work.

Re: Error saving message

Post by kozikowski » Wed Feb 17, 2010 4:24 am

Such as? In detail, plz. The whole list.

Such as? Program names and versions and operating system version?

It’s possible, but we can’t approach the developers with no data. They don’t just frown on that. They’ve been know to smite us with lighting bolts.

[WHY HAVE YOU COME TO US, ELF?]

Not good being smitten, trust me on that.

Re: Error saving message

Post by waxcylinder » Wed Feb 17, 2010 12:12 pm

kozikowski wrote: . but we can’t approach the developers with no data. They don’t just frown on that. They’ve been know to smite us with lighting bolts.

[WHY HAVE YOU COME TO US, ELF?]

Not good being smitten, trust me on that.

Re: Error saving message

Post by VHF » Wed Feb 17, 2010 1:05 pm

This is really silly. The leading lights wrote the code, or at least have access to it, and don’t need us to tell them which characters are rejected when in Save mode. Billw58 has the same system I do, and since he seems to be more scientifically inclined, I’ll let him do the experimentation if he’s so inclined. For me, to mention that there is at least one other application that does not have this issue (probably because their code is more up to date. ) speaks to an Audacity issue.

All I care about is that benighted error message, which seems to be leftover from 1922.

I have established the scenario. A new user reviews the Preferences and sees an auto-save function active by default. She imports a sound file, and its name appears without alteration as that of the project, with the suffix .aup, and feels safe. As a newbie, she does not realize that this thing that plays back is not a sound file (as koz says), and that simply exporting the file as such could save a lot or even all of her work. All she knows is, she’s in a Catch-22, where the system is telling her her multi-terabyte disk must be full, so the file is not being saved!

Oh, well. So, I guess I have to live with my work from two minutes ago (the default time in the auto-save preference) in the auto-save file, wherever that is, and she quits. Looks for any trace of her hours of work. None to be found.

Not a pretty picture. And, as I said, has probably turned any number of new users fast into former users!

Re: Error saving message

Post by billw58 » Wed Feb 17, 2010 5:20 pm

But did you determine which characters specifically were the problem? That would really help.

Re: Error saving message

Post by steve » Wed Feb 17, 2010 5:28 pm

That was certainly true before full Unicode support, but for the current 1.3.x version the main limitation in file naming is the operating system.
On Linux, of the characters available on my keyboard, the only one that I cannot use in a file name is the slash (/). The forward slash is used for path names, so if I tried to write: «new-file-17/2/2010» as a file name, the operating system would be looking for a (non-existent) folder called «new-file-17» with a subdirectory called «2».

On Windows the conventions for file naming are far more restrictive and are described here: http://msdn.microsoft.com/en-us/library . S.85).aspx
In short, you cant use any of the characters: * : » / | ? Integer value zero, ASCII NUL character, characters whose integer representations are in the range from 1 through 31, two consecutive dots, and any others that I’ve missed. In addition, there are rules according to the file system, for example the MS-DOS FAT file system supports a maximum of 8 characters for the base file name and 3 characters for the extension. On more recent file systems this 8.3 limit is removed but there is still a limit on the maximum path length (256 characters?). In addition, you cannot use the following names: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9 and you cannot start a file name with a space. File names on Windows are not case sensitive so Desktop.wav is identical to desktop.WAV

Although Audacity itself now supports Unicode, that does not mean that all of the components and libraries that Audacity uses will also support Unicode. For example, the names of Nyquist plug-ins must be alpha-numeric. Nyquist is a separate program from Audacity, developed by other people (as is Lame, FFMpeg and others). It is included in Audacity as it provides additional functionality (support for Nyquist plug-ins). Just as we would not expect the Audacity developers to rewrite the operating system on which Audacity is running, we cannot expect them to rewrite all of the shared libraries that Audacity uses (though they have been known to fix the occasional bug in other libraries).

There are additional naming problems that occur as a result of the internet. You’ve probably noticed that some file names have the characters «%20» in the name. This is a result of ASCII encoding (of a space) that occurs somewhere between a person typing the name and it being downloaded. Other substitutions can also occur, and while it is usually harmless, in some cases it can break things.

The upshot is that it is always safest to use «standard» characters when naming anything on computers. («standard» characters are a-z, 0-9, hyphen and underscore). This should be a matter of common practice for people familiar with computers.

As a matter of interest, how does your web browser display this word: の検索結果
It should look something like this:

Now that is a much better error message, I like it
However, the choice of file name should have no effect on whether or not Audacity performs an «Auto Save».
On Linux, the autosave file is (by default) in /home/ /.audacity_data/AutoSave/
(I’m not sure where it is on other platforms — anyone?)

The file name will be something like: «New Project — 2010-02-17 17-03-55 N-1.autosave» until the project is successfully saved.
On attempting to save the project with an invalid name (with a forward slash) I get the error message:

The Autosave file is not affected and still exists.

If I then purposefully crash out of Audacity (kill the process), the AutoSave file still exists, the temporary data is still in the temporary data folder, and restarting Audacity can automatically recover the project.
Anyone want to try on another platform?

kozikowski wrote: It’s possible, but we can’t approach the developers with no data. They don’t just frown on that. They’ve been know to smite us with lighting bolts.

[WHY HAVE YOU COME TO US, ELF?]

Not good being smitten, trust me on that.

Re: Error saving message

Post by billw58 » Wed Feb 17, 2010 6:00 pm

stevethefiddle wrote: Not sure about that Bill. What if I want to be a bad boy on my Linux box and name a project

He said «HELP?».AUP

That is perfectly valid on my machine, so why mess me around?

Try saving a project with the name:

That should be valid on your machine but I’ll bet Audacity will choke. Is Audacity treating the backslash as a path delimiter or an escape character?

Try doing an export multiple with label names containing «?» or «*» — Audacity won’t let you, and offers to change those characters to underscores.

No time right now, but later I’ll test what happens with autosave on Mac when the project name contains a slash character.

Источник

Deluge

The fastest programming language for developers

Choose where youвЂ™d like to start

Deluge Error Messages

Save Errors

Save error is a type of error that prevents the user from saving their script. This type of errors mostly occurs due to incorrect syntax and variable declaration. The following table lists the save errors in Deluge.

(Line no: 3) In Criteria left expression is of type and right expression is of type and the operator is not valid

Type mismatch:
This error message is displayed if the user tries to perform an operation with two operands of incompatible data types.

Example:
Solution:
In the above example, both the operands of the multiplication operation are supplied with number values.

(Line no: 2) Variable ‘ ‘ is not defined

This error message is displayed if a variable is used before it is defined. One common way to define a variable is to use set variable task.

Example:
Solution:
The variable b is defined with a number value.

(Line no: 5) Expecting ‘>’ but found ‘ ‘

This error message is displayed if an opening parenthesis is not perfectly matched with a closing parenthesis. The closing parenthesis marks the end of a block of statements.

Example:
Solution:
The opening parenthesis is correctly matched with a closing parenthesis.

(Line no: 5) Comment Task is not closed properly

This error message is displayed if an opening comment symbol (/*) is not correctly paired with a closing comment symbol (*/). Anything between these two comment symbols is skipped from execution.

Example:
Solution:
The opening comment symbol is perfectly paired with a closing comment symbol.

(Line no: 1) Improper Statement Error might be due to missing ‘;’ at end of the line or incomplete expression

In Deluge, every line must be terminated by a semicolon to call it a statement. The mentioned error message is displayed if a statement is not properly terminated with a semicolon.

Example:

Solution:
The variable definition statement is terminated with a semicolon.

A text must always be enclosed in double quotes. If it is not properly enclosed, the improper statement error is thrown.

Example:

Solution:
The text value, Harry is correctly enclosed in double quotes.

Misinterpreted as an escape sequence:
Consider a text value that ends with a backslash (Example: a = «test\»;). In this case, the closing double quote is misinterpreted as the character to be escaped from the usual execution. Thus resulting in improper statement error assuming that the text value is not properly enclosed in double quotes.

Example:

Solution:
Another closing double quote is appended to the text value to make sure that the text is properly enclosed in double quotes.

(Line no: 2) Number of Arguments mismatches

This error message is displayed if the number of arguments that the user specified in a task does not match the number of arguments that are meant to be present.

Example:

Solution:
The IF() task is provided with three arguments.

(Line no: 4) In cases where From: address is not a zoho.adminuserid or zoho.loginuserid, the To: address can only be zoho.adminuserid and the sendmail task cannot have any CC: or BCC: address.

In a sendmail task, either the From or the To address must be zoho.adminuserid or zoho.loginuserid. This constraint is to avoid communication between two unknown accounts for security purposes.

Example:

Solution:
The From address in the sendmail task is replaced with zoho.adminuserid.

(Line no: 7) Invalid BCC: From address is not zoho.adminuserid or zoho.loginuserid so BCC address is not allowed

To avoid spam messages, if the From address is not zoho.adminuserid or zoho.loginuserid, the bcc and cc fields are restricted to use. The mentioned error message is displayed if the user tries to include a bcc field when the From address is neither zoho.adminuserid nor zoho.loginuserid.

Example:

Solution:
The From address is replaced with zoho.loginuserid.

(Line no: 7) Invalid CC: From address is not zoho.adminuserid or zoho.loginuserid so CC address is not allowed

This error message is displayed if the user tries to include a cc field when the From address is neither zoho.adminuserid nor zoho.loginuserid.

Example:

Solution:
The From address is replaced with zoho.loginuserid.

(Line no: 3) Invalid email address found

This error message is displayed if the From or To field in sendmail task is assigned with a value that is not of Text data type.

Example:

Solution:
The From address is replaced with a valid email address.

(Line no: 3) ‘FROM’ message is missing for sendmail task

This error message is displayed if the from field is not included by the user in a sendmail task.
Example:

Solution:
The mandatory field — from is included in the sendmail task

(Line no: 4) ‘TO’ message is missing for sendmail task

This error message is displayed if the to field is not included by the user in a sendmail task.
Example:

Solution:
The mandatory field — to is included in the sendmail task

(Line no: 6) ‘SUBJECT’ message is missing for sendmail task

This error message is displayed if the subject field is not included by the user in a sendmail task.
Example:

Solution:
The mandatory field — subject is included in the sendmail task

(Line no: 7) Error at ‘SUBJECT’ or ‘MESSAGE’ field

This error message is displayed if the message field is not included by the user in a sendmail task.
Example:

Solution:
The mandatory field — message is included in the sendmail task

(Line no: 4) ‘MESSAGE’ is missing for sendsms task

In a sendsms task, the Message and To fields are mandatory. The mentioned error message is displayed if the Message field is not included by the user.

Example:

Solution:
The MESSAGE field is included in the sendsms task.

(Line no: 3) ‘TO’ message is missing for sendsms task

This error message is displayed if the To field is not included by the user in a sendsms task.

Example:

Solution:
The TO field is included in the sendsms task.

(Line no: 1) Missing return statement: Provide MAP expression to return

This error message is displayed if a return statement is defined but no value is returned.

(Line no: 1) Not able to find ‘ ‘ function

This error message is displayed if a function is called but it is not originally defined. Also, it is displayed if the user did not assign a variable to store the returned value from a function.

Save errors for functions

Error Message	Description

(Line no: 2) function needs to be assigned to a variable

This error message will be displayed if the value returned by a function is not assigned to a variable, or used as a part of an expression.

Example:

Solution:
The value returned by the function — subtext is assigned to the variable — result.

(Line no: 2) function cant be assigned to variable or used in expression

This error message will be displayed if a function that does not return any value is assigned to a variable, or used as a part of an expression.

Example:

Solution:
The function — insert is not assigned to a variable.

(Line no: 2) No. of arguments mismatches for the function

This error message will be displayed if the number of arguments supplied to a function is different from the number of arguments that the function expects.

Example:

Solution:
The function — contains is supplied with one argument.

(Line no: 2) Argument type mismatches for the function at index

This error message will be displayed if the data type of the argument supplied to a function is different from the data type that the function expects.

Example:

Solution:
The function — subtext is provided with an argument of NUMBER data type.

Save errors for integration tasks

Error Message	Description

(Line no: 1) Invalid module name for the function at index

This error message will be displayed if an unsupported or incorrect module name is supplied as the parameter to a Zoho integration task.

Example:

Solution:
A valid module name — Contacts is supplied to the Zoho Inventory integration task — Create Record.

(Line no: 1) is not supported for this function

This error message will be displayed:

If an integration task that is meant to be executed only from the Deluge editor of a specific Zoho service is tried to save elsewhere.
For example, the integration tasks — zoho.salesiq.visitorsession.get and zoho.salesiq.visitorsession.put are allowed to be executed on the Deluge editor of Zoho Sales IQ only. The mentioned error message will be displayed, if either of these tasks is tried on any Zoho Service other than Zoho Sales IQ.
If the connections parameter is not specified for an integration task while saving it on Zoho Cliq.
Note: The connection param is mandatory while executing any integration task on the Deluge editor of Zoho Cliq.

Error Message	Description

Runtime Errors

Runtime error occurs during script execution. This type of error mostly occurs due to the inappropriate action, done by the user. The following table lists the runtime errors in Deluge.

(Line no: 2) Invalid JSON Format String

This error message is displayed if the user tries to convert a text value that is not in a proper JSON format to a key-value collection.

Example:

Error message:

Solution:
The variable a is assigned with a proper JSON format text.

(Line no: 3) Error in performing the Operation / : Divide by zero error

This error occurs if the user tries to divide a number by zero. The program execution is terminated as it is mathematically impossible to divide a number by zero.

Example:

Error message:

Solution:
The variable b is assigned with a number value that is not zero.

(Line no: 2) Given string is lesser than the applied boundary, so index out of bounds exception arisen.

This error occurs when the script involves manipulations with Text values. The mentioned error message is displayed if the length of the text is lesser than the index value invoked by the user.

Example:

Error message:

Solution:
The arguments of the subText() function are provided with index numbers such that they do not exceed the length of the text value.

(Line no: 2) Given index is greater than the list size

This error message is displayed if the size of the collection is lesser than the index value invoked by the user.

Example:

Error message:

Solution:
The argument of the get() function is supplied with an index value that is lesser than the size of the Collection.

(Line no: 3) Null value occurred while performing operation

This type of error message is displayed if the user tries to perform operations with a null value.

Example:

Error message:

Solution:
The variable a is assigned with a number value.

(Line no: 3) On performing mod operation mismatch of data type expressions found

This type of error message is displayed if the user tries to perform modulo operation with a null value.

Example:

Error message:

Solution:
The variable a is assigned with a number value.

(Line no: 1) An error occurred while performing this action

This error message is displayed if the user tries to compare two non-numeric operands using a relational operator.

(Line no: 1) ‘ ‘ can not be cast to ‘MAP’.

This error message is displayed if the user tries to substitute a number value in the place of a key-value collection.

Runtime Errors: Built-In Functions

The following tables list the different runtime errors you might face while executing Deluge built-in functions.

Error messages while executing TEXT Functions

Error Message	Description

(Line no: 2) Given string is lesser than the applied boundary, so index out of bounds exception arisen

It is displayed when the value supplied to the index parameter is not within the allowed range.

Example:

Error message:

Solution:
The parameters are supplied with values that lie within the index range of the source text.

(Line no: 2) ‘TEXT’ can not be cast to ‘[BIGINT]’ for the function

It is displayed when a parameter that needs to be a number value is incorrectly provided with text value.

Example:

Error message:

Solution:
The parameters are provided with number values.

Error messages while executing NUMBER Functions

Error Message

Description

It is displayed when a parameter that needs to be a number value is incorrectly provided with text value.

Example:

Error message:

Solution:
A number value is assigned to the variable — number, which in turn is supplied as the parameter.

Error messages while executing XML Functions

Error Message

Description

(Line no: 2) Invalid XML or Invalid XPath

It is displayed if the provided XML or XPath is incorrect.

Example:

Error message:

Solution:
A valid XPath is provided as the parameter.

Error messages while executing Common Functions

Error Message

Description

(Line no: 2) ‘TEXT’ can not be cast to ‘[DECIMAL, NUMBER, DATE, DATE-TIME]’ for the function ‘text’

It is displayed when a parameter that needs to be a number value is incorrectly provided with text value.
Example:

Error message:

Solution:
A number value is assigned to the variable — fieldValue.