I have been playing around a little but with Audacity on Mac OSX, after
looking for something to recommend for simple 2-track editing, and as best
as I can figure out, it seems to have some serious problems. I'm trying to
figure out if the issues are on my side or not.
If I rip a CD from within Audacity, it calls itunes to do the actual work,
and there is a substantial probability of there being loud bursts of digital
noise in the transfer. Uusually I can see them on the waveform display, and
usually if I rip two or three times I can get a clean transfer.
BUT, sometimes in the editing process, loud bursts of digital noise seem
to appear in the file. Sometimes what look like noise appears on the
waveform display, but if I zoom in and then zoom back out it disappears.
Sometimes I will have a clean file that appears to play properly. But then
I export it as a .wav file, and I get a file with loud bursts of noise in it.
I am running Audacity 1.2.3 from the Nov 13 build. Has anyone else seen
this sort of thing? It's enough that I would consider the thing basically
unusable. It's being run on a G5 with some insanely large amount of memory.
Considering that I have done reliable 2-track editing on a 68k mac and had
no problem, I can't imagine it's a lack of system resources....
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
I haven't ripped audio into Audacity yet, just imported files and none
of these isuues. I have the October build, V1.2.2 on a G4 PowerBook
with plenty of memory, etc.
I am using Spark XL from TC Electronics.It works pretty good and is quite
easy to use under OSX
Scott Dorsey <kludge@panix.com> wrote in message
news:cuigsd$64p$1@panix2.panix.com...
> I have been playing around a little but with Audacity on Mac OSX, after
> looking for something to recommend for simple 2-track editing, and as best
> as I can figure out, it seems to have some serious problems. I'm trying
to
> figure out if the issues are on my side or not.
>
> If I rip a CD from within Audacity, it calls itunes to do the actual work,
> and there is a substantial probability of there being loud bursts of
digital
> noise in the transfer. Uusually I can see them on the waveform display,
and
> usually if I rip two or three times I can get a clean transfer.
>
> BUT, sometimes in the editing process, loud bursts of digital noise seem
> to appear in the file. Sometimes what look like noise appears on the
> waveform display, but if I zoom in and then zoom back out it disappears.
>
> Sometimes I will have a clean file that appears to play properly. But
then
> I export it as a .wav file, and I get a file with loud bursts of noise in
it.
>
> I am running Audacity 1.2.3 from the Nov 13 build. Has anyone else seen
> this sort of thing? It's enough that I would consider the thing basically
> unusable. It's being run on a G5 with some insanely large amount of
memory.
> Considering that I have done reliable 2-track editing on a 68k mac and had
> no problem, I can't imagine it's a lack of system resources....
> --scott
> --
> "C'est un Nagra. C'est suisse, et tres, tres precis."
Scott Dorsey wrote:
> I have been playing around a little but with Audacity on Mac OSX, after
> looking for something to recommend for simple 2-track editing, and as best
> as I can figure out, it seems to have some serious problems. I'm trying to
> figure out if the issues are on my side or not.
>
> If I rip a CD from within Audacity, it calls itunes to do the actual work,
> and there is a substantial probability of there being loud bursts of digital
> noise in the transfer. Uusually I can see them on the waveform display, and
> usually if I rip two or three times I can get a clean transfer.
Have you tried importing an existing WAV file? I've never used Audacity for ripping, but it has worked for basic editing (and playing of polyphonic WAV files) on Win32, OS X, and Linux.
Come to think of it, I've never actually ripped anything on a Mac, and given iTunes' intense DRM-centricity, I don't think I'd choose that for the task.
Does the machine have cdparanoia on it? That will do a simple rip to wav from the command line.
> If I rip a CD from within Audacity, it calls itunes to do the actual work,
> and there is a substantial probability of there being loud bursts of digital
> noise in the transfer. Uusually I can see them on the waveform display, and
> usually if I rip two or three times I can get a clean transfer.
That's curious, because I recently set up a music teacher with an
AluBook, OSX, Edirol UA-25, and Audacity. She has now burned a few dozen
CD's for her students without any of the noise about which you're
talking, using the same approach: save the Audacity files, which are in
its own format, out to a format iTunes recognizes, drag 'n' drop, and
burn.
> Come to think of it, I've never actually ripped anything on a Mac, and
> given iTunes' intense DRM-centricity, I don't think I'd choose that for
> the task.
You really should try it first before making that kind of assumption.
iTunes is only DRM-centric in the music store, and rightfully so: that's
the part that made the labels comfortable enough to go with with the
concept in the first place. In fact, burning a CD from purchased music,
then ripping that, is how you get around its DRM features; you just
click "import" as soon as it's done.
On Sat, 12 Feb 2005 09:38:47 -0800, S O'Neill <nopsam@nospam.net>
wrote:
>dale wrote:
>> scott
>> dsp quatro is from the same people who started spark.
>> < http://www.i3net.it/Products/dspQu [...] anguage=EN >
>
>
>Wow. That looks like a good replacement for Peak and Audio Hijack Pro
>and maybe other stuff. Who here uses it, how is it?
play_on wrote:
> On Sat, 12 Feb 2005 09:38:47 -0800, S O'Neill <nopsam@nospam.net>
> wrote:
>
>
>>dale wrote:
>>
>>>scott
>>>dsp quatro is from the same people who started spark.
>>>< http://www.i3net.it/Products/dspQu [...] anguage=EN >>
>>
>>
>>Wow. That looks like a good replacement for Peak and Audio Hijack Pro
>>and maybe other stuff. Who here uses it, how is it?
>
>
> Looks like the Mac version of Samplitude...
> I checked out the demo. Peak is still 'way ahead.
If you check out the background of the main guy programming DSP Quattro
you might see that there is potential in the app that Peak isn't going
to get, ever. Then compare pricing, and note that the recent upgrade
price for DSP Quattro was something like twenty bucks. I think those i3
guys are onto something, and we're just seeing the early stages of their
efforts.
hank alrich wrote:
> S O'Neill <nopsam@nospam.net> wrote:
>
>
>>I checked out the demo. Peak is still 'way ahead.
>
>
> If you check out the background of the main guy programming DSP Quattro
> you might see that there is potential in the app that Peak isn't going
> to get, ever. Then compare pricing, and note that the recent upgrade
> price for DSP Quattro was something like twenty bucks. I think those i3
> guys are onto something, and we're just seeing the early stages of their
> efforts.
You're right about the potential; no question there. The cross grade
from Peak (not directly mentioned on the web site) is $109.
It's sad, though, they crippled the demo too much. And the plugin
screen has a strange layout.
The real killer for me is that it doesn't recognize anything but the
system I/O: only the system default two channels of my 2408mk3.
And although Peak does have some disappointing idiosyncrasies, its audio
is good and it's efficient to use.
In article <cuigsd$64p$1@panix2.panix.com>, kludge@panix.com (Scott Dorsey)
wrote:
> I have been playing around a little but with Audacity on Mac OSX, after
> looking for something to recommend for simple 2-track editing, and as best
> as I can figure out, it seems to have some serious problems. I'm trying to
> figure out if the issues are on my side or not.
>
> If I rip a CD from within Audacity, it calls itunes to do the actual work,
> and there is a substantial probability of there being loud bursts of digital
> noise in the transfer. Uusually I can see them on the waveform display, and
> usually if I rip two or three times I can get a clean transfer.
>
> BUT, sometimes in the editing process, loud bursts of digital noise seem
> to appear in the file. Sometimes what look like noise appears on the
> waveform display, but if I zoom in and then zoom back out it disappears.
>
> Sometimes I will have a clean file that appears to play properly. But then
> I export it as a .wav file, and I get a file with loud bursts of noise in it.
>
> I am running Audacity 1.2.3 from the Nov 13 build. Has anyone else seen
> this sort of thing? It's enough that I would consider the thing basically
> unusable. It's being run on a G5 with some insanely large amount of memory.
> Considering that I have done reliable 2-track editing on a 68k mac and had
> no problem, I can't imagine it's a lack of system resources....
> --scott
There's a setting in iTunes that will retry when errors are detected instead of
just going on. I have never seen a noise burst with iTunes itself, although I
don't rip stuff if I'm serious about it, I record it in S/PDIF instead.
-Jay
--
x------- Jay Kadis ------- x---- Jay's Attic Studio ------x
x Lecturer, Audio Engineer x Dexter Records x
x CCRMA, Stanford University x http://www.offbeats.com/ x
x---------- http://ccrma.stanford.edu/~jay/ ------------x
Kurt Albershardt <kurt@nv.net> wrote:
>
>Have you tried importing an existing WAV file? I've never used Audacity for ripping, but it has worked for basic editing (and playing of polyphonic WAV files) on Win32, OS X, and Linux.
Okay, it seems like perhaps 80% of my problem has to do with using
iTunes from within Audacity. If I do the ripping with iTunes and generate
files, then import the files, everything is fine.
I do still find some weird clicks and pops appearing now and then, and I
do still occasionally have problems where I zoom in and back out and the
image is different. But for the most part 80% of the issues seem to be
with iTunes/Audacity integration and aren't a problem with either one
individually.
>Does the machine have cdparanoia on it? That will do a simple rip to wav from the command line.
No, and because it has an ATAPI drive, the OS X build for the cdwrite kit
on the Fink site does not appear to work at all either.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
Jay Kadis <jay@ccrma.stanford.edu> wrote:
>
>There's a setting in iTunes that will retry when errors are detected instead of
>just going on. I have never seen a noise burst with iTunes itself, although I
>don't rip stuff if I'm serious about it, I record it in S/PDIF instead.
This also turned out to be a major issue. Why isn't this enabled by default?
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
"Scott Dorsey" wrote ...
> Jay Kadis wrote:
>>
>>There's a setting in iTunes that will retry when errors are detected
>>instead of
>>just going on. I have never seen a noise burst with iTunes itself,
>>although I
>>don't rip stuff if I'm serious about it, I record it in S/PDIF
>>instead.
>
> This also turned out to be a major issue. Why isn't this enabled by
> default?
Because "Macs are considered better for audio recording/editing"? :-)
In article <1108745513.438813.65000@z14g2000cwz.googlegroups.com>,
dale <dallen@frognet.net> wrote:
>does audacity create the disc image for the burn?
>
>try Applications - Utilities - Disk Utility - burn
>
>bypass itunes
No, the burning procedure seems to be fine, actually. The problems have
all been getting the data into Audacity, and getting it to stay there
uncorrupted.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
On Fri, 18 Feb 2005 12:05:19 -0500, Scott Dorsey wrote:
> In article <1108745513.438813.65000@z14g2000cwz.googlegroups.com>,
> dale <dallen@frognet.net> wrote:
>>does audacity create the disc image for the burn?
>>
>>try Applications - Utilities - Disk Utility - burn
>>
>>bypass itunes
>
> No, the burning procedure seems to be fine, actually. The problems have
> all been getting the data into Audacity, and getting it to stay there
> uncorrupted.
> --scott
IMHO, Rezound knocks spots off audacity as far as *reliable* free 2 track
editing goes. It also has meters that work.
http://rezound.sourceforge.net/
There is apparently an OSX version now, though I have no idea if that
means a simple package or that you must install X11, JackOSX and a heap of
other things.
Scott Dorsey wrote:
> Kurt Albershardt <kurt@nv.net> wrote:
>
>> Have you tried importing an existing WAV file? I've never used Audacity for ripping, but it has worked for basic editing (and playing of polyphonic WAV files) on Win32, OS X, and Linux.
>
>
> Okay, it seems like perhaps 80% of my problem has to do with using
> iTunes from within Audacity. If I do the ripping with iTunes and generate
> files, then import the files, everything is fine.
Good news (mostly.)
>> Does the machine have cdparanoia on it? That will do a simple rip to wav from the command line.
>
>
> No, and because it has an ATAPI drive, the OS X build for the cdwrite kit
> on the Fink site does not appear to work at all either.
Try installing portage for OS X, which will give you access to most of the open source world. Imagine Berkeley ports on steroids <http://www.gentoo.org/doc/en/macos-guide.xml> <http://gentoo-wiki.com/Gentoo_MacOS>
"Scott Dorsey" <kludge@panix.com> wrote in message
news:cv578f$7di$1@panix2.panix.com...
> In article <1108745513.438813.65000@z14g2000cwz.googlegroups.com>,
> dale <dallen@frognet.net> wrote:
>>does audacity create the disc image for the burn?
>>
>>try Applications - Utilities - Disk Utility - burn
>>
>>bypass itunes
>
> No, the burning procedure seems to be fine, actually. The problems have
> all been getting the data into Audacity, and getting it to stay there
> uncorrupted.
Suggest maybe using almost any other audio editor application then.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.