Jump to content

Recommended Posts

Posted
probably easiest way to do it as an msi would be using winstall le on a referance pc and captureing the before/after state. Problem with audacity is iirc that the pointer to the lame codec is stored in hkey current ujser so needs adding to every user that logs in
  • 4 weeks later...
Posted

There's a nice gotcha - be aware that if you remote desktop into a machine to check it's installed ok, Audacity can (will?) crash ungracefully. You can then spend a while chasing your tail when it's actually installed fine.

 

I used an msi fwiw.

Posted
Hi We need a way to deploy audacity wit the lame encoder ideally an msi

 

I didn't install it to the desktops, I installed it to a share and put the lame encoder there to. To make sure the lame encoder is discovered you just need to copy audacity.cfg to application data, I did this in the logon script. It's also worth changing the default quality to 16bit from 32bit to reduce disk usage, unless you have a reason to leave it.

 

The .cfg is created on first run so run Audacity set your options and then just hunt it down in Application Data.

Posted

I use audacity portable.

Deploy it to a machine in a folder (I use c:\apps\aud)

 

Add in Lame encoder

 

Do a test and make sure everything works.

Export c:\apps\aud back out to a network share and then build a script to deploy it clients.

 

regards

 

Simon

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...