This section is now closed
Forum rules
Audacity 1.2.x is now obsolete. Please use the
current Audacity 2.1.x version.
Mac 0S X 10.3 and earlier are no longer supported but you can download legacy versions of Audacity for those systems
HERE.
-
billw58
- Forum Staff
- Posts: 5566
- Joined: Wed Aug 12, 2009 2:10 am
- Operating System: macOS 10.15 Catalina or later
Post
by billw58 » Tue Nov 03, 2009 1:03 am
coordinatezero wrote:We figured "aha, maybe they know something we don't". There's little to no information on this anywhere on the net. (Perhaps someone out there can formulate a better Google search.) Our current theory is that there's something in Carbon that freaks out on certain long filenames (but not all), but we can't pin it down.
You might try posting this to the Programming and Development section. I think more developers might hang out there. We're just the user support elves and are more focused on helping users with their problems and getting them working again.
It
is an interesting issue, I think. Especially since Final Cut Pro (of all programs!) exhibits this behaviour too.
-- Bill
-
steve
- Site Admin
- Posts: 80752
- Joined: Sat Dec 01, 2007 11:43 am
- Operating System: Linux *buntu
Post
by steve » Tue Nov 03, 2009 2:55 am
It's late now and I've only skim-read this topic (so apologies if this is irrelevant), but I remembered seeing something that may be relevant:
No Unicode or long file name support
Applies to: Audacity 1.2.x versions only
There are bugs in the Mac version of wxWidgets, called wxMac, that can affect Audacity. One bug involves Unicode support: because of this bug, Audacity stable 1.2.x versions cannot work with files or folders located inside a directory named with non-ASCII characters (usually international or accented characters). There is an additional artificial restriction of file name length, limiting your file names to 32 characters despite support in OS X for much longer names.
http://wiki.audacityteam.org/index.php?title=Mac_Bugs