the command worked great, I was able to import my wav from DVD to audacity natively at 48khz (by first setting it as the project rate prior to import) and then I was able to export it to ALAC as a m4a, and play it in winamp, also at 48khz. so very smooth once I had your knowledge boost!
however, the wav files had some rudimentary tag info, that audacity seemingly recognizes, (as does windows explorer), but unfortunately this info was not populated / xfer’d into the m4a. had to do that part manually. is there a switch I can add to your ALAC command line to xfer tags?
hmm, I just did an experiment and I can’t reproduce. on wav import and export to flac, the whole thing went at 48khz automatically, even after I changed the default rate in prefs to 44.1
what I can’t explain then, is why my initial FLACs were 44.1? they were, but how that happened I have no idea, as I know I didn’t mess around with the prefs or project rate until AFTER making that initial FLAC.
but if I can’t figure out the steps to reproduce, I can’t prove the bug. I don’t use audio editing much, but i’ll try to keep an eye out from now on. (maybe it has something to do with how things were the last time I used Audacity, or the upgrade I did to 2.0.5 from 2.0.3 I believe)
No it’s not the latest version of FFmpeg. Audacity 2.0.5 for Windows can’t use later than FFmpeg 0.6.2 when importing or when exporting using one of the (FFmpeg) options.
But for exporting using (external program) you can download the latest 32-bit static build from Zeranoe and point the Audacity command to that ffmpeg.exe (using Browse… in the window where you type the alac command we gave you). Obviously I assume you are on Windows - you still have not confirmed that.
The next 2.0.6 release of Audacity is expected to support a much more recent version of FFmpeg for all importing and exporting.
As I said, if the file you import is the first file in that project window, then the project rate should change to the rate of the file if not already set at that file’s rate.
If after importing a 48000 Hz FLAC you changed the project rate to back to 44100 Hz and imported another 48000 Hz FLAC, the project rate would remain at 44100 Hz.
Perhaps you already had a track in the project when you imported the first FLAC file? If so the project rate would not change to 48000 Hz.
However you should understand that whatever the project rate changes to or doesn’t, the FLAC is imported at its native rate and is not resampled. Look above the Mute / Solo buttons of the track to confirm its rate is still 48000 Hz or whatever its native rate is.
Nonetheless if you have imported a 48000 Hz file and the project rate is at 44100 Hz then the export will at that point be resampled to 44100 Hz (or mixed to 44100 Hz in the project if you choose Tracks > Mix and Render).
that’s Kool and the Gang, i’ll just wait for that.
I am using win7 64.
if I could though, I’d like to suggest that Audacity support ALAC natively, as it does FLAC, which I think it should be able to now since apple made ALAC open source and royalty free. it would greatly simplify things for casual users like me, and allow tags to xfer like they do for FLAC.
I don’t think we could directly add ALAC support because although it is open source it’s licensed under Apache v2 which isn’t compatible with the Audacity GPL v2 licence.
However after some ferreting around I notice that the libsndfile library that we use for import/export of lossless formats has ALAC support listed in https://github.com/erikd/libsndfile/blob/master/src/sndfile.h.in in their development code. I see that ALAC support is included in their libsndfile 1.2.6 pre-release source code download.
So if ALAC support is added to the 1.2.6 libsndfile release, then when Audacity updates to libsndfile 1.2.6 ALAC export should appear as an encoding option when you export using “Other uncompressed files”. However you won’t be able to export ALAC with M4A extension because libsndfile does not support that. In the libsndfile pre-releases, ALAC encoding is marked as for Apple Core Audio Format CAF extension only.
The developers would not want explanatory text in the interface however I think the Manual is reasonably clear about the purpose of Default Sample Rate: Audacity Manual .
The Manual does lack an explanation of the sample rate and sample format at which files are imported, how Default Sample Format affects that and how empty projects affect the project rate when importing, so I have added that to the Importing Audio page in the Manual.
The changes will appear in the Manual for the next release of Audacity.
and so it would seem that ffmpeg is still needed to create ALAC’s in m4a, is that correct? (albeit using a much newer ver of ffmpeg, but whats the newest that can be used?)
however, in this thread you said it might be possible to natively export ALAC to the CAF format, does that now exist? if so, should it be added to that wiki link?
obviously, i would like to be able to natively export ALAC to m4a, but i understand if its not possible. still, native export to CAF would be helpful, b/c in winamp (using a plugin by Thinktink) i believe it is easy to convert ALAC CAF to ALAC m4a.
any feedback is welcome, and thanks again! Audacity is a truly wonderful project.
For exporting via (external program) you can point Audacity to any static build of FFmpeg from Zeranoe, even if very recent.
Audacity is still at libsndfile 1.0.24 at the moment. I will mention the possibility on our developers list of update to 1.0.26 after release of Audacity 2.1.2. There are some security fixes in 1.0.26. The ALAC support probably isn’t that useful given iTunes (at least on Windows) cannot play the saved CAF files. However the ALAC support does include 16-, 20-, 24- or 32-bit files.
that sounds great. i know the CAF container isn’t very useful; however if i am correct that i can easily convert ALAC CAF to ALAC m4a in winamp, it could be very useful to me (and others) b/c we could then easily & natively create (export) CAF ALAC files with a quick vanilla out of the box Audacity install. that probably sounds a lot more compelling to me than to you, but it would be a really nice improvement from my POV.
thanks for being open to it.
and thanks again for your prompt reply! i will patiently wait to see if its added in 2.1.3
(besides 16 to 32 bit files, afaik ALAC also supports multiple sample rates like 96 or 192khz, and multiple channels, like “5.1” …its like FLAC in that way, and i don’t think it matters which container it is in, insofar as what capabilities it has, but as always i could be mistaken)