what are some new features I should be looking for in this one...or is it FULLY an integration/remodelled build.

It is the stable release at the end of the 0.3 development stream, so it includes all of the improvements from 0.3:

0.3.0:
http://www.audioman.org/news/archives/001316.html

0.3.1:
http://www.audioman.org/news/archives/001365.html

and the last stretch was up to 0.4.0, which included bugfixes and minor tweaks. If you want to see which bugs were fixed for between 0.3.1 and 0.4.0, go to the Bugzilla repository and search for bugs with Target Milestone 0.4.0.

http://www.ryanlowe.ca/bugzilla/

I'm going to make a release notice for 0.4.0 once I know this build is OK. :)

What kind of time would I have to put in to get up to date on this project. I'd like to contribute, maybe to get it working in Linux. How much work is left in this area. I've written a few Java Apps that worked on both windows and Linux environments. Do you think you could use my help?

I was actually going to start making the Windows, Linux and Mac OS X builds available all at the same time, which isn't that hard to do. I just have to organize the Ant build.xml file properly to handle it.

Because it's Java, the "ports" would be fairly straightforward -- EXCEPT for SWT, which is implemented slightly differently on the 3 platforms and has idiosyncracies that need to be managed. The Linux and Mac OS X ports of SWT are frequently behind the Windows version. If you want ownership of the Linux port, by all means it's yours. I'm not on Linux enough to be able to do that job properly.

The main job of this ownership would then be to properly triage (sort) bugs as Linux specific or not, and track how they are being fixed (most would be problems with SWT, which could point to Eclipse/SWT's Bugzilla) and also managing *nix type problems, mostly dealing with files, file associations, icons, etc.

For the time being I'm going to be the only committer to CVS, so your stuff will have to come to me in patches (which Eclipse can generate for you) attached to specific bugs. I'll apply the patch and the change will be in the next nightly build.

This are just my ideas for how I see it working. If you have other ideas just let me know. I'll get the instructions for setting up the developer tools (Eclipse, CVS, etc) back up on the web site so you can build AudioMan yourself.

If you've never used Eclipse, this will also be a good opportunity to give it a go!

Kibbee: I've updated the AudioMan web site to include setup instructions for Eclipse and CVS. The Eclipse page also goes into how to build AudioMan on platforms other than Windows.

http://www.audioman.org/pages/developers.php

I'll be adding more of these pages to the web site to set up other tools, they just have to formatted properly. If you have any problems let me know.

Is it entirely necessary to use Eclipse, or can I use an IDE that i'm mroe familiar with such as Netbeans?

You can try Netbeans, but since I've never used it I won't be able to help you if you have problems. :) All of my setup documentation is geared towards Eclipse.

There's nothing Eclipse-specific about AudioMan except the .project file. I'm assuming Netbeans will have it's own project file type, which you will have to set up yourself and maintain.