2.0rc2 released

A week or two on from 2.0rc1, and its time to offer up 2.0rc2 and the Mac OS X DMG, which we hope will be the final release before 2.0. At this point, we don't anticipate any code changes at all before 2.0. Read more below for the changes since rc1 ...

Changes since 2.0 rc1

  • change track input connection order to be 1,2 on every track instead of odd tracks using 1,2 and even using 2,1 (Sampo)
  • fix autoplay (Jesse)
  • fix cleanup issue with realpath() (Sampo)
  • make region opacity work again
  • fix several region context menu items that altered region state in various unforeseen ways
  • fix "Remove Last Capture" (Sampo)
  • fix crashing bug when removing regionviews from the selection
  • fixes for #1158 and 1554 (Carl)
  • correct boundary determination when building region boundary cache
  • stop button release from adding an extra automation control point
  • prevent click in automation tracks from selecting regions
  • prevent copy & paste of sends and inserts. Add "delete" command to the redirect box (Sampo)
  • stop transport when MTC stops
  • improve behaviour when dragging in rulers
  • added the session resampler which now should work for 2.0 sessions and almost work for 0.99 originated session (automation is not handled yet) (Sampo)
  • stopped the creation on the automation/ directory in new sessions as it's not used anymore (Sampo)
  • fix for crash in diskstream due to removed port access
  • fix dangling jack_client_t* in JACK_Slave when disconnecting+reconnecting to JACK
  • make rubber band select act across all tracks, not the current selection
  • fix positioning of certain kinds of xfades
  • resurrected the periodic safety backup. defaults to 120 second interval between saves. never lose your work again. (Jesse)
  • Fix mantis bug #1619; de-selecting Options->Crossfades->Show now hides all crossfades, and likewise selecting it shows all crossfades. (Carl)
  • Update height after changing order to fix mantis bug #1618 (Carl)
  • Fix update of follow-playhead state to fix mantis bug 1599 (Carl)
  • Fix for gnome themes that squash the zoom controls (Doug)
  • ardour_system.rc now has the same content as ardour.rc, to allow us to more easily add new variable/parameters when updating a user's configuration
  • different name for old-session-format copied file, so that 0.99 can always load it
  • fix crash bug caused by removing a region while it was involved in a crossfade
  • fix crash bug when loading/creating a new session if control protocols had been used in a previous one.

Fixes this release from Paul, Sampo, Jesse, Carl and Doug. Thanks to them and all our beta testers.

There’s nothing new in RC2 that should’ve caused compile times to become noticeably slower. Ardour does take quite a while to compile.

Were you perhaps running something cpu and/or disk intensive while compiling?

Do you have a frequency scaling processor? Some boxes (for examply my laptop) sometimes go in a state where the processor speed gets locked down. For me this happens when my PSU connector is not plugged in completely.

Nice, I’m gonna try this once I install fiesty fawn, I’m running suse 10.0 right now and I wasn’t able to compile ardour then for some reason. Anyways, I have a question: What’s different from the regular kernel and the RT kernel? and do I have to use the RT kernel to run ardour?

Linux :slight_smile:

The new 2.6.x series kernels (from around 2.6.15 onwards) are very good for most audio work. The RT kernels are patched to provide better scheduling but they are not as stable as the mainline kernels.

If you do tracking, mixing and mastering on Ardour and do not require low-latency for software monitoring or play live software synthesizers, a standard kernel will be good for you. If you want to play your electric guitar “through” your computer and run realtime effects on it, you might want a RT patched kernel to do that.

Ubuntustudio is something you need to keep an eye out for if you decide to go for feisty.

Hmm I see, But I will be able to record audio with mics and maybe the guitar going right into the comp through and external audio card and then apply effects afterwards?

What about external audio cards, which works with linux and which doesn’t? I’d also like to hear some general suggestions about what card to get.

Yes of course, recording and mixing is what Ardour was created for. See http://ardour.org/system_requirements/audio_compatibility for information about sound cards.

This is hardly the right topic to continue this conversation though.

Again, excellent news guys :slight_smile:
Keep up the good work

Brilliant. Just compiled (on Ubuntu 7.04 AMD64). BTW this took absolute ages to compile, I think considerably longer than earlier beta snapshots. Is this to do with
a) my perception?
b) my new realtime kernel not being optimised for throughput?
c) lots of stuff to compile in this big program?
It’s worth the wait though.

Excellent work - i’m really impressed

Fringe Serie

changes are quite impressive. you did a godo work.keep it up. cash advance

Excellent work guys You launched newer version very fast. Really very good.
collar bones

Excellent work. But till I not able to buy your old version and you launched new one. You guys are really very speedy.joint life insurance
work from home