Ableton Forum

Hi folks,

another beta for the upcoming 7.0.2 bug fix is available.
The current beta, Live 7.02b3, is free for every Live 7 customer and will expire on the 24th January.

http://www.ableton.com/_common/download ... 2b3_en.zip
http://www.ableton.com/_common/download ... 2b3_en.dmg

Please send your beta related feedback to [email protected] or use the Bugs and Problems section of the forum.
Please keep in mind that it is helpful to know if a certain bug or problem you run into already exists in Live 7.0,1.


Kind Regards
/Alex



Changes from Live 7.0.2b2 to Live 7.0.2b3


Improvements

Several updated or corrected info texts.

Windows only: If the DebugOption “-_EnsureKeyMessagesForPlugins” is set in the Options.txt, we make sure that all key messages reach a plugin’s window in front. That way, edit fields are again editable in the NI VST plug-ins. On the downside, key messages do not reach Live anymore as soon as some objects in the window of the VST plug-in are selected. Thus, for example, once an edit field has been edited, Live’s playback cannot be started via Space until Live’s main window regains focus.



Bug fixes

Editing an info text would not create an undo history entry and would not make a fresh document dirty.

Routing choosers would show the wrong chain name after renaming the device inside a chain.

Switching the upper chooser of a MIDI routing from one external device to another would set the MIDI channel back to the first one.

Moving corrupted or ‘more recent’ Live documents within the Browser could result in these documents being deleted.

The Quantize parameter of the Auto Filter effect would not work properly.

The frequency response view in Sampler would only work properly with a sample rate of 44100 Hz.

On Windows, it would not possible to save a preset with the char ‘:’ in its name. Now, ‘:’ is replaced by a ‘_’ when saving it as preset.

Drum Rack pads were not renamed when a slice was replaced.

Routing choosers would not always show the correct device name.

Turning on ‘Don’t show again’ in a message box with multiple choices would not respect the choice that was made, but would instead always press the default button in future invocations. With this fix, all warnings will be reset, as if the “Reset all warnings” button in the Preferences had been pressed.

Dragging MIDI files from Addictive Drums in the Arrangement could crash Live.



Announcement for Live 7.0.2b2
http://www.ableton.com/forum/viewtopic.php?t=82360

Yay for keyboard input!

Any news on the Remote SL fix?

LiquidFix wrote:Any news on the Remote SL fix?

this was already here:
http://www.ableton.com/forum/viewtopic.php?t=82360

best,
nico

I would call this a workaround and not a fix. But i guess a fix would involve some actions by Novation.

[nis] wrote:

LiquidFix wrote:Any news on the Remote SL fix?

this was already here:
http://www.ableton.com/forum/viewtopic.php?t=82360

best,
nico

Acidfever wrote:I would call this a workaround and not a fix. But i guess a fix would involve some actions by Novation.

[nis] wrote:

LiquidFix wrote:Any news on the Remote SL fix?

this was already here:
http://www.ableton.com/forum/viewtopic.php?t=82360

best,
nico

well, my remoteSL works very well in Live6.
so i'd say the problem is on ableton's side.

Hi folks,

it is quite hard to understand bug reports containing of one short sentence.
Please try to describe your issues a bit more detailed.

When you use Live 7.0 & 7.0.1 on Windows together with certain MIDI Controllers you might experiences audio and graphical drop outs.
If that is the case for you, try the latest Beta and get sure to set the Port Type of your MIDI ports to 'MME'.

If you still experience a problem in the latest beta (Live 7.0.2b3), please report. (Create a new thread or send an email to [email protected])

Kind Regards,
/Alex

Hi, quick question: where is options.txt? Just did a full search of c: but couldn't find it, XP's search is shite though
BTW great news about keyboard input!!! fingers crossed, will try it as soon as I can edit the .txt

Hi rozling,

Check out
http://www.ableton.com/pages/faq/options_text

cheers,
Jan

Nice one

Alex wrote: Windows only: If the DebugOption “-_EnsureKeyMessagesForPlugins” is set in the Options.txt, we make sure that all key messages reach a plugin’s window in front. That way, edit fields are again editable in the NI VST plug-ins. On the downside, key messages do not reach Live anymore as soon as some objects in the window of the VST plug-in are selected. Thus, for example, once an edit field has been edited, Live’s playback cannot be started via Space until Live’s main window regains focus.

Editing in Reaktor works fine with this fix.

and what this?

http://www.ableton.com/forum/viewtopic.php?t=76475


still not fixed in Live 7.0.1

arachnaut wrote:

Alex wrote: Windows only: If the DebugOption “-_EnsureKeyMessagesForPlugins” is set in the Options.txt, we make sure that all key messages reach a plugin’s window in front. That way, edit fields are again editable in the NI VST plug-ins. On the downside, key messages do not reach Live anymore as soon as some objects in the window of the VST plug-in are selected. Thus, for example, once an edit field has been edited, Live’s playback cannot be started via Space until Live’s main window regains focus.

Editing in Reaktor works fine with this fix.

Can confirm Kore 2 is working with this too - haven't checked the other NI plugs. I am really happy with this, hopefully I can start working with Kore 2 in some kind of practical way now

I am still having an issue where rack macros mapped to most of my Native Instruments VSTs' parameters get forgotten when I re-load the rack though

and what this?

http://www.ableton.com/forum/viewtopic.php?t=76475


still not fixed in Live 7.0.1 Evil or Very Mad

Not sure what do you mean with not fixed in Live 7.0.1, because Live 7.0.1 was released at the end of November.
But that specific bug with the Impulse should be fixed in the current Beta as Torsten posted two days ago.

Regards,
/Alex

arachnaut wrote:

Alex wrote: Windows only: If the DebugOption “-_EnsureKeyMessagesForPlugins” is set in the Options.txt, we make sure that all key messages reach a plugin’s window in front. That way, edit fields are again editable in the NI VST plug-ins. On the downside, key messages do not reach Live anymore as soon as some objects in the window of the VST plug-in are selected. Thus, for example, once an edit field has been edited, Live’s playback cannot be started via Space until Live’s main window regains focus.

Editing in Reaktor works fine with this fix.

not so much a fix as a workaround - might be better in the long run though...