New post
Avatar
0

Selecting File - Export - Audio file, then choosing a location for the .aiff file to be saved. The file seems to be exporting. But there is no exported file in my chosen location—unless I select to save it on the Desktop.

Mac OSX 10.11.6 (El Capitan)

Finale 2014.5

6 comments

Date Votes
Avatar
0

Hi

Someone else found a solution to a problem which might be similar to what you are experiencing.

 

This is what she sid in her post https://makemusic.zendesk.com/hc/en-us/community/posts/218703347-Can-t-export-my-project-?page=1#community_comment_219062048 

"
Look what i found:

There is a known issue exporting audio on Finale 2014 for Mac. When playing Finale through Audio Units, you cannot export an audio file if the file name contains special characters such as accented letters (such as É and ü). These characters commonly appear in pieces with titles that are in a language other than English.

 

And it worked! We hoo!

 "

 

I wonder if that might help you?

 

Cheers...

 

Daz :o)

Comment actions Permalink
Avatar
0

Thanks—I had seen that comment about special characters in file names, and made sure mine contained no such characters. So that was not the issue. (By the way, I haven't checked lately, but there was a time Finale had trouble exporting to the same folder that contained the file from which you were trying to export.)

Finale's tech suggested that I might be having difficulty because the hard drives themselves contain "special characters" (an asterisk). I have not tried renaming my hard drives to confirm this guess, but what an odd restriction! I cannot think of another application that suffers from such prejudice.

Comment actions Permalink
Avatar
0

Hi

I'm not that certain about the Mac, but certainly for Windows, linux, unix and DOS systems, naming anything to do with the disk (disk name, partition name, file name directory name etc) should not use special characters. Windows will not allow it, neither will DOS, unix or Linux. (In fact I'm surprised the MacOS allows it, as it is based on version of unix at its core). The asterix is used as a 'wildcard' when naming/searching on the command line (in all OS's) and also used as a wildcard in programming languages. It is so ingrained into a programmers mindset, they they will not even consider the possibility that someone can name anything with an asterisk.

There is good guide for naming conventions (and the reasons to avoid certain names, characters etc) https://support.apple.com/en-au/HT202808 

While it specifically says for cross platform compatibility, a lot of the conventions are good for normal use as well.

I would be interested to find out what your hard disks are called, and how you managed to get an aterisk into the disks' name.

 

Cheers...

 

Daz :o)

Comment actions Permalink
Avatar
0

It's a Mac and many wonderful things are possible. We can even put spaces in our file names!

I actually use a degree symbol (°) as a leading character for my internal drive (°DISKNAME), and an asterisk as a leading symbol for a folder on that drive (*FOLDERNAME). Such leading special characters (*, •, °, ~) can often result in automatic sorting. I used to use 1., 2., 3., etc. but went for a different aesthetic.

Macs do have an issue with using a colon or a slash in some naming conventions And for cross-platform files I am more careful about PCs' conservative ways. 

Comment actions Permalink
Avatar
0

Hi

Having the asterisk there might be a factor. As I mentioned, the asterisk is used as a wildcard in command line utilities and also in programming. (ditto the question mark)

Are you able to use a different character in the name, keeping your aesthetics and sorting?

It might be worth a try.

 

Cheers...

 

Daz :o)

 

Comment actions Permalink
Avatar
0

Hi all —

Just wanted to make it known that I have the same problem as Kristian. The deciding factor here, in my case, seems to be the chosen location (Desktop works, same folder as .musx file does not), rather than special characters.

Maybe it's also worth noting that the .musx file is enclosed in a folder with the following characters in it:

(–,)

Which in turn is enclosed in a folder with this character: /

That might be an issue?

Mac OS X Yosemite 10.10.5

Finale 2014.5.7098

Comment actions Permalink

Please sign in to leave a comment.