Importing 16-bit WAV or AIF into 24-bit project fails
|
|
Bill Wharrie
|
Confirmed on 1.3.10-alpha-Nov 1 2009 Mac
Also see this thread on the forum: http://forum.audacityteam.org/viewtopic.php?f=16&t=15302 New project Go to Quality Prefs and set the default sample rate to 44100 and format to 24-bit Import any 16-bit WAV or AIF file - imported audio is garbage -- Bill ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Michael Chinen
|
Hi Bill,
On Sun, Nov 1, 2009 at 7:01 PM, Bill Wharrie <[hidden email]> wrote: > Confirmed on 1.3.10-alpha-Nov 1 2009 Mac > Also see this thread on the forum: > http://forum.audacityteam.org/viewtopic.php?f=16&t=15302 Nice detective work. These settings based bugs are hard to find. > > New project > Go to Quality Prefs and set the default sample rate to 44100 and > format to 24-bit > Import any 16-bit WAV or AIF file > - imported audio is garbage I've tried this out with my own wavs and with the 10 sec tone you suggested on the forum, and I can't reproduce it. Are there other settings that might be different? I'm on PPC mac, which might matter. I don't think this is on-demand related, because a 10 second wav is not imported with on-demand, but there always is the possibility. If you want to be sure, turn on the "make a copy of uncompressed audio" before importing. Michael > > -- Bill > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
On 1-Nov-09, at 3:33 PM, Michael Chinen wrote: > Hi Bill, > > On Sun, Nov 1, 2009 at 7:01 PM, Bill Wharrie <[hidden email]> > wrote: >> Confirmed on 1.3.10-alpha-Nov 1 2009 Mac >> Also see this thread on the forum: >> http://forum.audacityteam.org/viewtopic.php?f=16&t=15302 > Nice detective work. These settings based bugs are hard to find. >> >> New project >> Go to Quality Prefs and set the default sample rate to 44100 and >> format to 24-bit >> Import any 16-bit WAV or AIF file >> - imported audio is garbage > I've tried this out with my own wavs and with the 10 sec tone you > suggested on the forum, and I can't reproduce it. Are there other > settings that might be different? I'm on PPC mac, which might matter. > > I don't think this is on-demand related, because a 10 second wav is > not imported with on-demand, but there always is the possibility. If > you want to be sure, turn on the "make a copy of uncompressed audio" > before importing. I'm running a G5 dual 2 GHz, 10.5.8. I have the "make a copy" option selected. Damn! I just tried this with "read files from original" and the imported audio is fine! This was with a 2m15s file that also triggered on-demand loading. I set Projects Prefs for "when saving ..." to "Ask user" then saved the project. The dependencies dialog came up and I chose to copy the audio into the project. After that the imported audio was still fine. Quit Audacity and re-opened the saved project and all is still fine. -- Bill ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Gale (Audacity Team)
|
| From Bill Wharrie <[hidden email]> | Sun, 1 Nov 2009 15:57:02 -0500 | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails > > On 1-Nov-09, at 3:33 PM, Michael Chinen wrote: > > > Hi Bill, > > > > On Sun, Nov 1, 2009 at 7:01 PM, Bill Wharrie <[hidden email]> > > wrote: > >> Confirmed on 1.3.10-alpha-Nov 1 2009 Mac > >> Also see this thread on the forum: > >> http://forum.audacityteam.org/viewtopic.php?f=16&t=15302 > > Nice detective work. These settings based bugs are hard to find. > >> > >> New project > >> Go to Quality Prefs and set the default sample rate to 44100 and > >> format to 24-bit > >> Import any 16-bit WAV or AIF file > >> - imported audio is garbage > > I've tried this out with my own wavs and with the 10 sec tone you > > suggested on the forum, and I can't reproduce it. Are there other > > settings that might be different? I'm on PPC mac, which might matter. > > > > I don't think this is on-demand related, because a 10 second wav is > > not imported with on-demand, but there always is the possibility. If > > you want to be sure, turn on the "make a copy of uncompressed audio" > > before importing. > > I'm running a G5 dual 2 GHz, 10.5.8. I have the "make a copy" option > selected. > > Damn! I just tried this with "read files from original" and the > imported audio is fine! This was with a 2m15s file that also > triggered on-demand loading. I set Projects Prefs for "when > saving ..." to "Ask user" then saved the project. The dependencies > dialog came up and I chose to copy the audio into the project. After > that the imported audio was still fine. Quit Audacity and re-opened > the saved project and all is still fine. As I posited in the "Hello All" thread I think this is not mechanistic and is actually this: "P3 R AIFF files created by Audacity from recorded or generated data import intermittently (but at times very frequently) as noise - files play fine in other software." except that as has been demonstrated it can be an issue with WAV as well. Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute WAVs (a mix of those created by Audacity and otherwise) using On-Demand and all were fine. I did this by a clearing to a fresh project window after each import. Then I changed prefs. to "read directly" and the WAVs all imported fine, except two which were noise (both had been exported by some Beta version of Audacity or other). I quit Audacity and re-imported the first of the two troublesome files i.e. reading directly and got noise. Quit and restart, import the same file and it's fine. Quit and restart and import the second troublesome file and that's now fine also. Gale ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
Some javascript/style in this post has been disabled (why?)
On 1-Nov-09, at 5:08 PM, Gale Andrews wrote:
Well, I can reproduce this to order. I created three WAV files from within iTunes and tried importing them. Reset prefs (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" and every attempt on all three files produced noise, following your "new project window between attempts" method, and also with quitting between attempts. Same for AIF files created by Audacity but that have burned to CD without problem. Steve reports this on Windows (though I don't know if he was as thorough as you were), but reports no problem on Linux. The forum poster who reported this problem has had it constantly for years! Clearing his config file worked, but probably only because that reset him to 32-bit float. -- Bill ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Michael Chinen
|
On Mon, Nov 2, 2009 at 12:00 AM, Bill Wharrie <[hidden email]> wrote:
> > On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: > > [snip] > > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute WAVs > (a mix of those created by Audacity and otherwise) using On-Demand > and all were fine. I did this by a clearing to a fresh project window after > each import. Then I changed prefs. to "read directly" and the WAVs all > imported fine, except two which were noise (both had been exported by > some Beta version of Audacity or other). > > I quit Audacity and re-imported the first of the two troublesome files > i.e. reading directly and got noise. Quit and restart, import the same > file and it's fine. Quit and restart and import the second troublesome > file and that's now fine also. > > > Well, I can reproduce this to order. I created three WAV files from within > iTunes and tried importing them. Reset prefs (NewPrefsInitialized=1). > On-demand was fine. Change to "read directly" and every attempt on all three > files produced noise, following your "new project window between attempts" > method, and also with quitting between attempts. > Same for AIF files created by Audacity but that have burned to CD without > problem. > Steve reports this on Windows (though I don't know if he was as thorough as > you were), but reports no problem on Linux. > The forum poster who reported this problem has had it constantly for years! > Clearing his config file worked, but probably only because that reset him to > 32-bit float. reproduce it 100%. This will help with debugging it. Unless someone else really wants to, I'd like to take this bug as I have been working on importing and blockfiles lately. Michael > -- Bill > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Stevethefiddle
|
In reply to this post
by Bill Wharrie
Bill Wharrie wrote:
> > On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: > >> [snip] > >> Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute WAVs >> (a mix of those created by Audacity and otherwise) using On-Demand >> and all were fine. I did this by a clearing to a fresh project >> window after >> each import. Then I changed prefs. to "read directly" and the WAVs all >> imported fine, except two which were noise (both had been exported by >> some Beta version of Audacity or other). >> >> I quit Audacity and re-imported the first of the two troublesome files >> i.e. reading directly and got noise. Quit and restart, import the same >> file and it's fine. Quit and restart and import the second troublesome >> file and that's now fine also. >> > > Well, I can reproduce this to order. I created three WAV files from > within iTunes and tried importing them. Reset prefs > (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" > and every attempt on all three files produced noise, following your > "new project window between attempts" method, and also with quitting > between attempts. > > Same for AIF files created by Audacity but that have burned to CD > without problem. > > Steve reports this on Windows (though I don't know if he was as > thorough as you were), but reports no problem on Linux. Actually the problem is also on Linux - when I initially tested I had "make a copy before editing" switched off. Switching this option on creates the problem on both Windows and Linux. Even with resetting preferences the problem is 100% reproducible. 1) Generate a tone and Export as 16 bit WAV 2) Set Preferences for: Quality=24 bit. "When importing audio.. > Make a copy (safer)" 3) Import the tone > noise > > The forum poster who reported this problem has had it constantly for > years! Clearing his config file worked, but probably only because that > reset him to 32-bit float. > > -- Bill > I think the default is also for "on demand" (make a copy before editing = off) Steve D ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Martyn Shaw-2
|
In reply to this post
by Michael Chinen
Michael Chinen wrote: > On Mon, Nov 2, 2009 at 12:00 AM, Bill Wharrie <[hidden email]> wrote: >> On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: >> >> [snip] >> >> Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute WAVs >> (a mix of those created by Audacity and otherwise) using On-Demand >> and all were fine. I did this by a clearing to a fresh project window after >> each import. Then I changed prefs. to "read directly" and the WAVs all >> imported fine, except two which were noise (both had been exported by >> some Beta version of Audacity or other). >> >> I quit Audacity and re-imported the first of the two troublesome files >> i.e. reading directly and got noise. Quit and restart, import the same >> file and it's fine. Quit and restart and import the second troublesome >> file and that's now fine also. >> >> >> Well, I can reproduce this to order. I created three WAV files from within >> iTunes and tried importing them. Reset prefs (NewPrefsInitialized=1). >> On-demand was fine. Change to "read directly" and every attempt on all three >> files produced noise, following your "new project window between attempts" >> method, and also with quitting between attempts. >> Same for AIF files created by Audacity but that have burned to CD without >> problem. >> Steve reports this on Windows (though I don't know if he was as thorough as >> you were), but reports no problem on Linux. >> The forum poster who reported this problem has had it constantly for years! >> Clearing his config file worked, but probably only because that reset him to >> 32-bit float. > Ah, I see! Thanks. After putting the copy mode (non-OD) on, I can > reproduce it 100%. This will help with debugging it. Unless someone > else really wants to, I'd like to take this bug as I have been working > on importing and blockfiles lately. Go for it Michael! > Michael > > >> -- Bill >> ------------------------------------------------------------------------------ >> 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 >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
In reply to this post
by Bill Wharrie
| From Bill Wharrie <[hidden email]> | Sun, 1 Nov 2009 18:00:20 -0500 | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails > > On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: > > > [snip] > > > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute > > WAVs > > (a mix of those created by Audacity and otherwise) using On-Demand > > and all were fine. I did this by a clearing to a fresh project > > window after > > each import. Then I changed prefs. to "read directly" and the WAVs all > > imported fine, except two which were noise (both had been exported by > > some Beta version of Audacity or other). > > > > I quit Audacity and re-imported the first of the two troublesome files > > i.e. reading directly and got noise. Quit and restart, import the same > > file and it's fine. Quit and restart and import the second troublesome > > file and that's now fine also. Firstly, apologies for the confusion of terms above. To clarify, I changed from on-demand (*read... directly*, where there was no problem importing a variety of WAV files into a 24-bit project) to *make a copy* (not aliased). Then two of the files I was testing failed with noise, but only for a time. > Well, I can reproduce this to order. I created three WAV files from > within iTunes and tried importing them. Reset prefs > (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" > and every attempt on all three files produced noise, following your > "new project window between attempts" method, and also with quitting > between attempts. > > Same for AIF files created by Audacity but that have burned to CD > without problem. > > Steve reports this on Windows (though I don't know if he was as > thorough as you were), but reports no problem on Linux. > > The forum poster who reported this problem has had it constantly for > years! Clearing his config file worked, but probably only because that > reset him to 32-bit float. Steve was importing files created by Audacity. I know you weren't but the reports I've seen are mostly of Audacity-created files. They are the ones that are much more likely to create problems for me, as per the P3. When I was trying to figure out the P3 problem, I always saw the same "noise sometimes" behaviour importing non-aliased WAV/AIFF into 24-bit projects. And sometimes there was a crash instead. But Leland (also on Mac) could not reproduce this at all when he tried. Also I have seen noise with on-demand too, but that was a while ago. I've seen old (1.2-influenced) .cfg files from four users (one on Mac, three on Windows) where AIFFs/WAVs were "importing as noise". Only two of these were on 24-bit "make a copy". In all four cases, initialising .cfg removed the problem, and I know specifically that one user (Windows) had gone back to 24-bit "make a copy" and had no problem importing AIFFs or WAVs. He then told me later the problem had come back (he had supposedly uninstalled Audacity 1.2.6 and removed the Audacity registry key). I've little idea what to make of all the above, or why the problem is not mechanistically replicable here. It would be great if we can find a replicable problem we can fix. As you know there are occasional cases where .cfg just seems to interpret things wrong and the only answer is to reset it, but these usually tend to be "hybrid" .cfgs where some settings are being taken from 1.2. I think we're still planning to leave old 1.2 settings in situ for 2.0. Gale ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Ed Musgrove-2
|
> -----Original Message-----
> From: Gale Andrews [mailto:[hidden email]] > Sent: Sunday, November 01, 2009 10:13 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project > fails > > > | From Bill Wharrie <[hidden email]> Sun, 1 Nov 2009 18:00:20 -0500 > | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit > | project fails > > > > On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: > > > > > [snip] > > > > > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute > > > WAVs (a mix of those created by Audacity and otherwise) using > > > On-Demand and all were fine. I did this by a clearing to a fresh > > > project window after each import. Then I changed prefs. to "read > > > directly" and the WAVs all imported fine, except two which were > > > noise (both had been exported by some Beta version of Audacity or > > > other). > > > > > > I quit Audacity and re-imported the first of the two troublesome > > > files i.e. reading directly and got noise. Quit and restart, import > > > the same file and it's fine. Quit and restart and import the second > > > troublesome file and that's now fine also. > > Firstly, apologies for the confusion of terms above. To clarify, I changed > on-demand (*read... directly*, where there was no problem importing a > variety of WAV files into a 24-bit project) to *make a copy* (not aliased). > Then two of the files I was testing failed with noise, but only for a time. > > > > Well, I can reproduce this to order. I created three WAV files from > > within iTunes and tried importing them. Reset prefs > > (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" > > and every attempt on all three files produced noise, following your > > "new project window between attempts" method, and also with quitting > > between attempts. > > > > Same for AIF files created by Audacity but that have burned to CD > > without problem. > > > > Steve reports this on Windows (though I don't know if he was as > > thorough as you were), but reports no problem on Linux. > > > > The forum poster who reported this problem has had it constantly for > > years! Clearing his config file worked, but probably only because that > > reset him to 32-bit float. > > Steve was importing files created by Audacity. I know you weren't but the > reports I've seen are mostly of Audacity-created files. They are the ones > are much more likely to create problems for me, as per the P3. > > When I was trying to figure out the P3 problem, I always saw the same "noise > sometimes" behaviour importing non-aliased WAV/AIFF into 24-bit projects. > And sometimes there was a crash instead. But Leland (also on Mac) could not > reproduce this at all when he tried. Also I have > seen noise with on-demand too, but that was a while ago. > > I've seen old (1.2-influenced) .cfg files from four users (one on Mac, three on > Windows) where AIFFs/WAVs were "importing as noise". > Only two of these were on 24-bit "make a copy". In all four cases, initialising > .cfg removed the problem, and I know specifically that one user (Windows) > had gone back to 24-bit "make a copy" and had no problem importing AIFFs > or WAVs. He then told me later the problem had come back (he had > supposedly uninstalled Audacity > 1.2.6 and removed the Audacity registry key). > > I've little idea what to make of all the above, or why the problem is not > mechanistically replicable here. It would be great if we can find a replicable > problem we can fix. > > As you know there are occasional cases where .cfg just seems to interpret > things wrong and the only answer is to reset it, but these usually tend to be > "hybrid" .cfgs where some settings are being taken from 1.2. I think we're > still planning to leave old 1.2 settings in situ for 2.0. > [ Ed-- ] How about, if there is no .cfg file (or if it only has the first line??), and there are existing registry entries (where did 1.2 on the Mac and Linux store this info??) asking the user to verify (either one-by-one or all-or-nothing) the importation of these settings into 2.x's .cfg? Maybe post-release? --Ed > > > > Gale > > > > ---------------------------------------------------------------------------- -- > 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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Richard Ash (audacity-help)
|
On Sun, 2009-11-01 at 22:57 -0800, Ed Musgrove wrote:
> [ Ed-- ] > How about, if there is no .cfg file (or if it only has the first line??), > and there are existing registry entries (where did 1.2 on the Mac and Linux > store this info??) In a configuration file, but one with a different name IIRC. The change to windows was to bring it in line with other platforms, and we made all platforms keep the file and other associated files in a folder called audacity-data - ~/.audacity-data/ on *nix systems including Mac, and audacity-data in the application settings folder on Windows. The reason for not calling the directory ~/.audacity/ was that 1.2.x on *nix used to keep it's settings in a file called ~/.audacity so we would get a naming conflict. Richard ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
On 2-Nov-09, at 3:21 PM, Richard Ash wrote: > On Sun, 2009-11-01 at 22:57 -0800, Ed Musgrove wrote: >> [ Ed-- ] >> How about, if there is no .cfg file (or if it only has the first >> line??), >> and there are existing registry entries (where did 1.2 on the Mac >> and Linux >> store this info??) > > In a configuration file, but one with a different name IIRC. The > change > to windows was to bring it in line with other platforms, and we made > all > platforms keep the file and other associated files in a folder called > audacity-data - ~/.audacity-data/ on *nix systems including Mac, and > audacity-data in the application settings folder on Windows. > > The reason for not calling the directory ~/.audacity/ was that 1.2.x > on > *nix used to keep it's settings in a file called ~/.audacity so we > would > get a naming conflict. > On Mac the 1.2 preferences file is called "audacity Preferences" and is in ~/Library/Preferences For 1.3 it's called "audacity.cfg" and is in ~/Library/Application Support/audacity My understanding is that editing the 1.3 audacity.cfg file down to the one magic line "NewPrefsInitilized=1" will prevent 1.3 from looking for the old 1.2 preferences file. -- Bill ------------------------------------------------------------------------------ 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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Ed Musgrove-2
|
Richard & Bill;
Thanks for the info. Makes figuring out what is happening easier (not that it will be easy <grin>). --Ed > -----Original Message----- > From: Bill Wharrie [mailto:[hidden email]] > Sent: Monday, November 02, 2009 1:27 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Conbfiguration files (was: Importing 16-bit > WAV or AIF into 24-bit project fails) > > > On 2-Nov-09, at 3:21 PM, Richard Ash wrote: > > > On Sun, 2009-11-01 at 22:57 -0800, Ed Musgrove wrote: > >> [ Ed-- ] > >> How about, if there is no .cfg file (or if it only has the first > >> line??), and there are existing registry entries (where did 1.2 on > >> the Mac and Linux store this info??) > > > > In a configuration file, but one with a different name IIRC. The > > change to windows was to bring it in line with other platforms, and we > > made all platforms keep the file and other associated files in a > > folder called audacity-data - ~/.audacity-data/ on *nix systems > > including Mac, and audacity-data in the application settings folder on > > Windows. > > > > The reason for not calling the directory ~/.audacity/ was that 1.2.x > > on *nix used to keep it's settings in a file called ~/.audacity so we > > would get a naming conflict. > > > > On Mac the 1.2 preferences file is called "audacity Preferences" and is in > ~/Library/Preferences > > For 1.3 it's called "audacity.cfg" and is in ~/Library/Application > Support/audacity > > My understanding is that editing the 1.3 audacity.cfg file down to the one > magic line "NewPrefsInitilized=1" will prevent 1.3 from looking for the > preferences file. > > -- Bill > > ---------------------------------------------------------------------------- -- > 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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-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 _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Michael Chinen
|
In reply to this post
by Gale (Audacity Team)
On Mon, Nov 2, 2009 at 7:13 AM, Gale Andrews <[hidden email]> wrote:
> > | From Bill Wharrie <[hidden email]> > | Sun, 1 Nov 2009 18:00:20 -0500 > | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails >> >> On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: >> >> > [snip] >> >> > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute >> > WAVs >> > (a mix of those created by Audacity and otherwise) using On-Demand >> > and all were fine. I did this by a clearing to a fresh project >> > window after >> > each import. Then I changed prefs. to "read directly" and the WAVs all >> > imported fine, except two which were noise (both had been exported by >> > some Beta version of Audacity or other). >> > >> > I quit Audacity and re-imported the first of the two troublesome files >> > i.e. reading directly and got noise. Quit and restart, import the same >> > file and it's fine. Quit and restart and import the second troublesome >> > file and that's now fine also. > > Firstly, apologies for the confusion of terms above. To clarify, I changed > from on-demand (*read... directly*, where there was no problem > importing a variety of WAV files into a 24-bit project) to *make a copy* > (not aliased). Then two of the files I was testing failed with noise, but > only for a time. > > >> Well, I can reproduce this to order. I created three WAV files from >> within iTunes and tried importing them. Reset prefs >> (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" >> and every attempt on all three files produced noise, following your >> "new project window between attempts" method, and also with quitting >> between attempts. >> >> Same for AIF files created by Audacity but that have burned to CD >> without problem. >> >> Steve reports this on Windows (though I don't know if he was as >> thorough as you were), but reports no problem on Linux. >> >> The forum poster who reported this problem has had it constantly for >> years! Clearing his config file worked, but probably only because that >> reset him to 32-bit float. > > Steve was importing files created by Audacity. I know you weren't but > the reports I've seen are mostly of Audacity-created files. They are > the ones that are much more likely to create problems for me, as per > the P3. > > When I was trying to figure out the P3 problem, I always saw the same > "noise sometimes" behaviour importing non-aliased WAV/AIFF into > 24-bit projects. And sometimes there was a crash instead. But Leland > (also on Mac) could not reproduce this at all when he tried. Also I have > seen noise with on-demand too, but that was a while ago. > > I've seen old (1.2-influenced) .cfg files from four users (one on Mac, > three on Windows) where AIFFs/WAVs were "importing as noise". > Only two of these were on 24-bit "make a copy". In all four cases, > initialising .cfg removed the problem, and I know specifically that > one user (Windows) had gone back to 24-bit "make a copy" and had > no problem importing AIFFs or WAVs. He then told me later the > problem had come back (he had supposedly uninstalled Audacity > 1.2.6 and removed the Audacity registry key). > > I've little idea what to make of all the above, or why the problem is > not mechanistically replicable here. It would be great if we can find a > replicable problem we can fix. same as OD. I don't know why you couldn't reproduce the bug. But for those curious the problem was that audacity was claiming an array of floats was an array of int in the non-OD 24 bit case. Michael > > As you know there are occasional cases where .cfg just seems to > interpret things wrong and the only answer is to reset it, but these > usually tend to be "hybrid" .cfgs where some settings are being taken > from 1.2. I think we're still planning to leave old 1.2 settings in situ > for 2.0. > > > > > Gale > > > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Michael Chinen <[hidden email]> | Wed, 4 Nov 2009 17:49:22 +0100 | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails > On Mon, Nov 2, 2009 at 7:13 AM, Gale Andrews <[hidden email]> wrote: > > > > | From Bill Wharrie <[hidden email]> > > | Sun, 1 Nov 2009 18:00:20 -0500 > > | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails > >> > >> On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: > >> > >> > [snip] > >> > >> > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute > >> > WAVs > >> > (a mix of those created by Audacity and otherwise) using On-Demand > >> > and all were fine. I did this by a clearing to a fresh project > >> > window after > >> > each import. Then I changed prefs. to "read directly" and the WAVs all > >> > imported fine, except two which were noise (both had been exported by > >> > some Beta version of Audacity or other). > >> > > >> > I quit Audacity and re-imported the first of the two troublesome files > >> > i.e. reading directly and got noise. Quit and restart, import the same > >> > file and it's fine. Quit and restart and import the second troublesome > >> > file and that's now fine also. > > > > Firstly, apologies for the confusion of terms above. To clarify, I changed > > from on-demand (*read... directly*, where there was no problem > > importing a variety of WAV files into a 24-bit project) to *make a copy* > > (not aliased). Then two of the files I was testing failed with noise, but > > only for a time. > > > > > >> Well, I can reproduce this to order. I created three WAV files from > >> within iTunes and tried importing them. Reset prefs > >> (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" > >> and every attempt on all three files produced noise, following your > >> "new project window between attempts" method, and also with quitting > >> between attempts. > >> > >> Same for AIF files created by Audacity but that have burned to CD > >> without problem. > >> > >> Steve reports this on Windows (though I don't know if he was as > >> thorough as you were), but reports no problem on Linux. > >> > >> The forum poster who reported this problem has had it constantly for > >> years! Clearing his config file worked, but probably only because that > >> reset him to 32-bit float. > > > > Steve was importing files created by Audacity. I know you weren't but > > the reports I've seen are mostly of Audacity-created files. They are > > the ones that are much more likely to create problems for me, as per > > the P3. > > > > When I was trying to figure out the P3 problem, I always saw the same > > "noise sometimes" behaviour importing non-aliased WAV/AIFF into > > 24-bit projects. And sometimes there was a crash instead. But Leland > > (also on Mac) could not reproduce this at all when he tried. Also I have > > seen noise with on-demand too, but that was a while ago. > > > > I've seen old (1.2-influenced) .cfg files from four users (one on Mac, > > three on Windows) where AIFFs/WAVs were "importing as noise". > > Only two of these were on 24-bit "make a copy". In all four cases, > > initialising .cfg removed the problem, and I know specifically that > > one user (Windows) had gone back to 24-bit "make a copy" and had > > no problem importing AIFFs or WAVs. He then told me later the > > problem had come back (he had supposedly uninstalled Audacity > > 1.2.6 and removed the Audacity registry key). > > > > I've little idea what to make of all the above, or why the problem is > > not mechanistically replicable here. It would be great if we can find a > > replicable problem we can fix. > > I just checked in a fix. The treatment of non-OD importing is now the > same as OD. > > I don't know why you couldn't reproduce the bug. But for those > curious the problem was that audacity was claiming an array of floats > was an array of int in the non-OD 24 bit case. Thanks, Michael. Have tried to give it a good going over on XP by doing things that (sometimes) caused me trouble, like generating 24-bit tones then exporting as 24-bit AIFF and re-importing into a 24-bit copy-in project. No problem here. Also did a check on Linux, which was fine with WAV, but I noticed that AIFFs import at 32-bit float when the Quality is set to 24-bit, both for OD and copy-in (WAV comes in at 24-bit). Should we fix that and re-check AIFF import is OK on Linux? I also found a note from someone on Mac that they were having "no problems" importing AIFF into 24-bit "copy-in" projects 6 weeks ago, despite ImportPCM.cpp hadn't changed for a couple of months prior to your fix. And WAVs (I think) from some CD ripper still won't give noise for me in a pre-fix build if I do 24-bit copy in... Anyway if confused "hybrid" .cfgs are part of the problem, they have one reason less to be confused now. Thanks Gale > > As you know there are occasional cases where .cfg just seems to > > interpret things wrong and the only answer is to reset it, but these > > usually tend to be "hybrid" .cfgs where some settings are being taken > > from 1.2. I think we're still planning to leave old 1.2 settings in situ > > for 2.0. > > > > > > > > > > Gale ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Michael Chinen
|
On Thu, Nov 5, 2009 at 11:22 AM, Gale Andrews <[hidden email]> wrote:
> > | From Michael Chinen <[hidden email]> > | Wed, 4 Nov 2009 17:49:22 +0100 > | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails >> On Mon, Nov 2, 2009 at 7:13 AM, Gale Andrews <[hidden email]> wrote: >> > >> > | From Bill Wharrie <[hidden email]> >> > | Sun, 1 Nov 2009 18:00:20 -0500 >> > | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails >> >> >> >> On 1-Nov-09, at 5:08 PM, Gale Andrews wrote: >> >> >> >> > [snip] >> >> >> >> > Setting Quality Prefs. to 24-bit, I imported a lot of 3 or 4 minute >> >> > WAVs >> >> > (a mix of those created by Audacity and otherwise) using On-Demand >> >> > and all were fine. I did this by a clearing to a fresh project >> >> > window after >> >> > each import. Then I changed prefs. to "read directly" and the WAVs all >> >> > imported fine, except two which were noise (both had been exported by >> >> > some Beta version of Audacity or other). >> >> > >> >> > I quit Audacity and re-imported the first of the two troublesome files >> >> > i.e. reading directly and got noise. Quit and restart, import the same >> >> > file and it's fine. Quit and restart and import the second troublesome >> >> > file and that's now fine also. >> > >> > Firstly, apologies for the confusion of terms above. To clarify, I changed >> > from on-demand (*read... directly*, where there was no problem >> > importing a variety of WAV files into a 24-bit project) to *make a copy* >> > (not aliased). Then two of the files I was testing failed with noise, but >> > only for a time. >> > >> > >> >> Well, I can reproduce this to order. I created three WAV files from >> >> within iTunes and tried importing them. Reset prefs >> >> (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" >> >> and every attempt on all three files produced noise, following your >> >> "new project window between attempts" method, and also with quitting >> >> between attempts. >> >> >> >> Same for AIF files created by Audacity but that have burned to CD >> >> without problem. >> >> >> >> Steve reports this on Windows (though I don't know if he was as >> >> thorough as you were), but reports no problem on Linux. >> >> >> >> The forum poster who reported this problem has had it constantly for >> >> years! Clearing his config file worked, but probably only because that >> >> reset him to 32-bit float. >> > >> > Steve was importing files created by Audacity. I know you weren't but >> > the reports I've seen are mostly of Audacity-created files. They are >> > the ones that are much more likely to create problems for me, as per >> > the P3. >> > >> > When I was trying to figure out the P3 problem, I always saw the same >> > "noise sometimes" behaviour importing non-aliased WAV/AIFF into >> > 24-bit projects. And sometimes there was a crash instead. But Leland >> > (also on Mac) could not reproduce this at all when he tried. Also I have >> > seen noise with on-demand too, but that was a while ago. >> > >> > I've seen old (1.2-influenced) .cfg files from four users (one on Mac, >> > three on Windows) where AIFFs/WAVs were "importing as noise". >> > Only two of these were on 24-bit "make a copy". In all four cases, >> > initialising .cfg removed the problem, and I know specifically that >> > one user (Windows) had gone back to 24-bit "make a copy" and had >> > no problem importing AIFFs or WAVs. He then told me later the >> > problem had come back (he had supposedly uninstalled Audacity >> > 1.2.6 and removed the Audacity registry key). >> > >> > I've little idea what to make of all the above, or why the problem is >> > not mechanistically replicable here. It would be great if we can find a >> > replicable problem we can fix. >> >> I just checked in a fix. The treatment of non-OD importing is now the >> same as OD. >> >> I don't know why you couldn't reproduce the bug. But for those >> curious the problem was that audacity was claiming an array of floats >> was an array of int in the non-OD 24 bit case. > > Thanks, Michael. Have tried to give it a good going over on XP by doing > things that (sometimes) caused me trouble, like generating 24-bit tones > then exporting as 24-bit AIFF and re-importing into a 24-bit copy-in > project. No problem here. > > Also did a check on Linux, which was fine with WAV, but I noticed that > AIFFs import at 32-bit float when the Quality is set to 24-bit, both for > OD and copy-in (WAV comes in at 24-bit). Should we fix that and > re-check AIFF import is OK on Linux? > > I also found a note from someone on Mac that they were having "no > problems" importing AIFF into 24-bit "copy-in" projects 6 weeks > ago, despite ImportPCM.cpp hadn't changed for a couple of months > prior to your fix. And WAVs (I think) from some CD ripper still won't > give noise for me in a pre-fix build if I do 24-bit copy in... Whether the bug would be hit also depends on the wav/aiff file. If the wav/aiff file is something better than 16 bit, the import method defaults to float. The case that should be tested is audacity prefs in "copy-in" and quality at "24-bit int," and the wav/aiff file in question should be 16 bits. From line 171 of ImportPCM.cpp if (mFormat != floatSample && sf_subtype_more_than_16_bits(mInfo.format)) mFormat = floatSample; Michael > > Anyway if confused "hybrid" .cfgs are part of the problem, they have > one reason less to be confused now. > > > Thanks > > > Gale > > > > >> > As you know there are occasional cases where .cfg just seems to >> > interpret things wrong and the only answer is to reset it, but these >> > usually tend to be "hybrid" .cfgs where some settings are being taken >> > from 1.2. I think we're still planning to leave old 1.2 settings in situ >> > for 2.0. >> > >> > >> > >> > >> > Gale > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
On Thu, Nov 5, 2009 at 11:22 AM, Gale Andrews <[hidden email]> wrote: | From Michael Chinen <[hidden email]> | Thu, 5 Nov 2009 23:05:43 +0100 | Subject: [Audacity-devel] Importing 16-bit WAV or AIF into 24-bit project fails > >> > > From Bill Wharrie <[hidden email]> > >> >> Well, I can reproduce this to order. I created three WAV files from > >> >> within iTunes and tried importing them. Reset prefs > >> >> (NewPrefsInitialized=1). On-demand was fine. Change to "read directly" > >> >> and every attempt on all three files produced noise, following your > >> >> "new project window between attempts" method, and also with quitting > >> >> between attempts. > >> >> > >> >> Same for AIF files created by Audacity but that have burned to CD > >> >> without problem. > > > Thanks, Michael. Have tried to give it a good going over on XP by doing > > things that (sometimes) caused me trouble, like generating 24-bit tones > > then exporting as 24-bit AIFF and re-importing into a 24-bit copy-in > > project. No problem here. > > > > Also did a check on Linux, which was fine with WAV, but I noticed that > > AIFFs import at 32-bit float when the Quality is set to 24-bit, both for > > OD and copy-in (WAV comes in at 24-bit). Should we fix that and > > re-check AIFF import is OK on Linux?... > > Hi Gale, > > Whether the bug would be hit also depends on the wav/aiff file. If > the wav/aiff file is something better than 16 bit, the import method > defaults to float. The case that should be tested is audacity prefs > in "copy-in" and quality at "24-bit int," and the wav/aiff file in > question should be 16 bits. > > > From line 171 of ImportPCM.cpp > if (mFormat != floatSample && > sf_subtype_more_than_16_bits(mInfo.format)) > mFormat = floatSample; > > Michael Thanks, Michael yes I had not taken into account the AIFFs I was importing on Linux were 24-bit. Just double checked: 16-bit WAV and 16-bit AIFF on Linux come in fine at 24-bit with "24-bit copy-in" settings. The CD rips that gave me no trouble pre-fix at "24-bit copy-in" are definitely 16-bit, thus importing at 24-bit, so I still don't understand that. Yes 24-bit WAV coming into a 24-bit project as alluded to above was definitely coming in as 32-bit as expected, but giving noise at times. I did that more times than I care to recall. History, I hope. Gale ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Stevethefiddle
|
In reply to this post
by Michael Chinen
Working OK here on Linux (Ubuntu 9.04 - Audacity cvs Nov. 6th Unicode). (Issue was previously 100% repeatable on this machine). Steve |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
