Ableton Forum

Hi folks,

We just released the eighth beta version of an upcoming 8.0.5 bugfix update.
Every Live 8 owner can use this beta version.

As it is a beta, please remember to backup critical data before you use it.


Version info:

Current version: Live 8.0.5b8
Expiration date: 2009/08/16
Required serial: Live 8 full version


Download info:

http://downloads.ableton.com/extra/5839 ... ent_en.dmg
http://downloads.ableton.com/extra/5839 ... ent_en.zip



Kind Regards
/Alex




Changes from Live 8.0.5b7 to 8.0.5b8:



Bugfixes:

A deactivated clip would still appear in the Arranger overview [5746]

Duplicate time or duplicate envelopes command would erase Live's global clipboard [5745]

Flatten a frozen MIDI track could crash Live depending on the currently selected envelope [5773]

Converting Simpler to Sampler while receiving parameter changes via MIDI controller would crash Live [5303]

If activated, a second running instance of Live would always show the Bug Reporting dialog on startup [4588]




Announcement of Live 8.0.5b7:
http://forum.ableton.com/viewtopic.php?f=1&t=120954

Announcement of Live 8.0.5b6:
http://forum.ableton.com/viewtopic.php?f=1&t=120321

Announcement of Live 8.0.5b5:
http://forum.ableton.com/viewtopic.php?f=1&t=119693

Announcement of Live 8.0.5b4:
http://forum.ableton.com/viewtopic.php?f=1&t=119282

Announcement of Live 8.0.5b3:
http://forum.ableton.com/viewtopic.php?f=1&t=118730

Announcement of Live 8.0.5b2:
http://forum.ableton.com/viewtopic.php?f=1&t=118317

Announcement of Live 8.0.5b1:
http://forum.ableton.com/viewtopic.php?f=1&t=117815

Hi Alex,

I would like to respectfully bring your attention to a serious problem that was introduced in 8.0.5b4. You had shown an interest in this on a previous thread, but I don't think that you ever got an answer to your question about how locking down the APC40 MIDI ports is a problem for some users. The previous thread was at http://forum.ableton.com/viewtopic.php?f=1&t=119282 and the workaround referenced here is detailed at http://forum.ableton.com/viewtopic.php? ... 78#p956278

In short, we colorblind users are left with a virtually useless APC40 because of the following change:

"When using the APC40 Controller surface script, we check if the selection MIDI ports are the one from the APC40"

To recap my other post, this means that we can no longer use a virtual port to change the colors sent out to the APC40. While I'm sure that this change is well intentioned, I really don't see that it's beneficial since once can still select the "wrong" port. The only difference is that now instead of MIDI being sent to the "wrong" device (which is harmless), it's apparently not sent at all. The irony with this is that I am experiencing this on Mac OS X which does not have the issue of ambiguous port naming that is described in the update notes.

Thanks for hearing us out, your support is always appreciated!

dstroud wrote:Hi Alex,

I would like to respectfully bring your attention to a serious problem that was introduced in 8.0.5b4. You had shown an interest in this on a previous thread, but I don't think that you ever got an answer to your question about how locking down the APC40 MIDI ports is a problem for some users. The previous thread was at http://forum.ableton.com/viewtopic.php?f=1&t=119282 and the workaround referenced here is detailed at http://forum.ableton.com/viewtopic.php? ... 78#p956278

In short, we colorblind users are left with a virtually useless APC40 because of the following change:

"When using the APC40 Controller surface script, we check if the selection MIDI ports are the one from the APC40"

To recap my other post, this means that we can no longer use a virtual port to change the colors sent out to the APC40. While I'm sure that this change is well intentioned, I really don't see that it's beneficial since once can still select the "wrong" port. The only difference is that now instead of MIDI being sent to the "wrong" device (which is harmless), it's apparently not sent at all. The irony with this is that I am experiencing this on Mac OS X which does not have the issue of ambiguous port naming that is described in the update notes.

Thanks for hearing us out, your support is always appreciated!

+1.

I can't see a damn thing that's going on with the current APC LEDs.

Dstroud has come up with a 3rd party workaround using MIDI Pipe for OSX that changes the clip LED output, but an internal solution from Ableton would be preferable. Please factor this in and amend accordingly. I'm sure there's more than just a handful of colorblind APC-40 users out there...

After all the APC-40 marketing hype which I bought into, the APC is currently rendered useless because I cannot differentiate between the different clip LED statuses.

dstroud wrote:Hi Alex,

I would like to respectfully bring your attention to a serious problem that was introduced in 8.0.5b4. You had shown an interest in this on a previous thread, but I don't think that you ever got an answer to your question about how locking down the APC40 MIDI ports is a problem for some users. The previous thread was at http://forum.ableton.com/viewtopic.php?f=1&t=119282 and the workaround referenced here is detailed at http://forum.ableton.com/viewtopic.php? ... 78#p956278

In short, we colorblind users are left with a virtually useless APC40 because of the following change:

"When using the APC40 Controller surface script, we check if the selection MIDI ports are the one from the APC40"

To recap my other post, this means that we can no longer use a virtual port to change the colors sent out to the APC40. While I'm sure that this change is well intentioned, I really don't see that it's beneficial since once can still select the "wrong" port. The only difference is that now instead of MIDI being sent to the "wrong" device (which is harmless), it's apparently not sent at all. The irony with this is that I am experiencing this on Mac OS X which does not have the issue of ambiguous port naming that is described in the update notes.

Thanks for hearing us out, your support is always appreciated!

Hi ya,

Thanks for popping over to my blog, just tried this beta and no problems with bomes to report...

Cheers
D

"When using the APC40 Controller surface script, we check if the selection MIDI ports are the one from the APC40"

This is a serious problem for me. I use the NativeKontol templates and some custom Max/MSP stuff to enhance my APC. If Ableton will not speak to my APC through another application then all this functionality will be lost, making my APC essentially useless.

It works well now. Why cripple it?

+1
damn don't make the things worst

8 betas for a point release?

haha

so if ya red green colourblind like i am - the apc 40 is gonna be pretty pointless to use?

i did kinda sign when saw the red green yellow leds but hoped i would be able to see em better than the green and orange lcd backlights on ma microkontrol - i cant see them change at all urgh

OK guys, good news. While I've been busy stirring up the hornet's nest, it turns out that this might not be a problem after all. I don't know why this was not working for me before, but I just tested again and it looks like we're not getting blocked- at least in version 8.0.5b8.

Sorry for wasting everyone's time.

As a peace-offering, I've made a little Mac app in Max that some of you colorblind folks may find useful. This is just a quick and dirty implementation of the aforementioned MidiPipe, but perhaps it will work better. The app and the patch are available for download at:

idisk.mac.com/dstroud-Public/LiveAPC40

I think that PC Max users can probably take the patch and modify as needed. Note that this is only my personal implementation and it may not work if all the 3 colors look the same to you. I have some ideas to work around this down the road, but this will have to wait until I return from vacation in a week.

If anyone tries this out, let me know if it works for you or not.

dstroud

Guys,

So that we don't hijack this thread any further, I'll put future updates about the APC Buddy color remapper on the previous thread at: http://forum.ableton.com/viewtopic.php? ... 92#p957592

The new version may work for some of you guys who can't distinguish any of the colors.

Quick question:
Is the library complete for Live 8?

I've avoided doing customizations to the library because I've been doing FULL suite downloads and performing 'fresh' installs each time. I've screwed up the library a time or two in the past, and not really looking to reinstall the library each time (unless there is new stuff in it).

Willyum wrote:Quick question:
Is the library complete for Live 8?

Is this question another way of asking: "Can Ableton promise that there will be no more updates to the library in any future version of Live 8?"

If so, I would guess that the answer has to be no, unless you really think there will be no changes to the library when Max for Live comes out.

Willyum wrote:I've avoided doing customizations to the library because I've been doing FULL suite downloads and performing 'fresh' installs each time. I've screwed up the library a time or two in the past, and not really looking to reinstall the library each time (unless there is new stuff in it).

As disk space is cheap nowadays I prefer to store the whole library on a USB-Harddisk before I carry out a bugfix update. I also perform a 'fresh' installation each time... Maybe there could have been made an improvement to the library which is not mentioned in the change log I also make a disk image from my system drive using drive snapshot before I install a bugfix update... A long experience in business told me to do so

ark wrote:

Willyum wrote:Quick question:
Is the library complete for Live 8?

Is this question another way of asking: "Can Ableton promise that there will be no more updates to the library in any future version of Live 8?"

If so, I would guess that the answer has to be no, unless you really think there will be no changes to the library when Max for Live comes out.

No, I have 4 or 5 versions of Live and after several updates of each version, the library doesn't get touched any more, just 'bug fix' and 'improvement' updates (or extra Live packs) I am trying to find out have we reached that point yet.

And from what I hear (rumor), Max won't be out til next year (and is not included in my suite version) so I may not spend the extra $200 bucks. All I need is 'intelligent time-stretch' in my Simpler/Sampler to make my setup complete.

can't wait for the new beta 9.