Exporting to MP3 with Lame taking 14+ hours

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
kozikowski
Forum Staff
Posts: 69369
Joined: Thu Aug 02, 2007 5:57 pm
Operating System: macOS 10.13 High Sierra

Re: Exporting to MP3 with Lame taking 14+ hours

Post by kozikowski » Wed Nov 04, 2015 4:02 am

Please note Chrome is the biggest memory user. Restart the computer and close Chrome or don't let it start. Disconnect the network.

That help any?

I don't see any virus protection software in there.

Koz

themickster
Posts: 308
Joined: Wed Aug 12, 2015 10:50 pm
Operating System: Windows 10

Re: Exporting to MP3 with Lame taking 14+ hours

Post by themickster » Wed Nov 04, 2015 10:40 am

Google 'wav to mp3' and choose one. Better still, Google 'right click mp3'. Less than 500Kb and all you do is right click on the wav and press a key to start it. It's the only one I use. It says in BrotherSoft that it's Windows 98 and NT but my XP handles it.

steve
Site Admin
Posts: 81627
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Exporting to MP3 with Lame taking 14+ hours

Post by steve » Wed Nov 04, 2015 12:27 pm

In what way does your computer suck? 2GB of RAM and 500GB of hard drive does not sound too bad (my machine has 3GB RAM and 500GB hard drive, but my old machine was much lower spec than that).

What happens if you try to export the project as a WAV file?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

Gale Andrews
Quality Assurance
Posts: 41761
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Re: Exporting to MP3 with Lame taking 14+ hours

Post by Gale Andrews » Wed Nov 04, 2015 6:52 pm

themickster wrote:Google 'wav to mp3' and choose one. Better still, Google 'right click mp3'. Less than 500Kb and all you do is right click on the wav and press a key to start it. It's the only one I use. It says in BrotherSoft that it's Windows 98 and NT but my XP handles it.
As far as I can tell, "RightClickMP3" is only for Mac OS X. "RightClick-MP3" which was once available for Windows is no longer published.

I would steer clear of BrotherSoft - it has a poor reputation.

Doug often recommends https://sourceforge.net/projects/taudioconverter/.


Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual

Gale Andrews
Quality Assurance
Posts: 41761
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Re: Exporting to MP3 with Lame taking 14+ hours

Post by Gale Andrews » Wed Nov 04, 2015 7:09 pm

If RAM is the problem, which I am not convinced is the issue, then as Koz said, exiting Chrome will help a lot.

So you have a USB keyboard with a built-in hard drive? Are you sure you are exporting to that drive? Can you export somewhere else?

You can export as MP3 using FFmpeg, but I doubt it will help. Choose "Custom FFmpeg export" when you export then choose "MP3" from the "Formats" list and "libmp3lame" (the only choice) from the "Codecs" list. You can specify bit rate on the right of that dialogue.

Are you sure the project rate is still 44100 Hz? What sample rate is the track? Resampling from one rate to another will add greatly to the export time.

Have you tried reinstalling Audacity with "Reset Preferences" enabled? http://manual.audacityteam.org/o/man/fa ... html#reset .


Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual

cyrano
Posts: 2629
Joined: Fri Apr 17, 2015 11:54 pm
Operating System: macOS 10.13 High Sierra

Re: Exporting to MP3 with Lame taking 14+ hours

Post by cyrano » Wed Nov 04, 2015 9:20 pm

kambrielle wrote:I attached a screenshot of my task manager - looks like 20-30% of my CPU is being used with Chrome, Audacity, and the MP3 player open...I don't know if that's a lot, but it doesn't seem like it.
The only thing that consumes an abnormal amount of memory is Task manager itself. Audacity is at zero percent, Chrome uses 1,4%. That sounds about right.

Your computer should be able to cope, as you noticed in the past.

What I don't understand is that 500 GB harddisk in the keyboard. Do you mean it's an external USB harddisk, connected to the USB on the keyboard? If that's the case, most of the USB ports on keyboards are USB 1.1 only. Far too slow for a harddisk. Try connecting to another port.

I've never seen a keyboard with a harddisk. But I'm always willing to learn. :lol: Bet you it'll be Chinese...

Gale Andrews
Quality Assurance
Posts: 41761
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Re: Exporting to MP3 with Lame taking 14+ hours

Post by Gale Andrews » Wed Nov 04, 2015 9:30 pm

cyrano wrote:
kambrielle wrote:I attached a screenshot of my task manager - looks like 20-30% of my CPU is being used with Chrome, Audacity, and the MP3 player open...I don't know if that's a lot, but it doesn't seem like it.
The only thing that consumes an abnormal amount of memory is Task manager itself. Audacity is at zero percent, Chrome uses 1,4%. That sounds about right.
The zero and 1.4% were CPU use, just to make that clear.


Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual

cyrano
Posts: 2629
Joined: Fri Apr 17, 2015 11:54 pm
Operating System: macOS 10.13 High Sierra

Re: Exporting to MP3 with Lame taking 14+ hours

Post by cyrano » Thu Nov 05, 2015 10:05 am

Gale Andrews wrote:The zero and 1.4% were CPU use, just to make that clear.
Yes Gale, quite right. Sorry for the confusion. It's what I always look at when judging memory use, to see if a program hangs, or is still doing something.

Post Reply