Beta of upcoming 7.0.2 bug fix update
-
dave dominey
- Posts: 514
- Joined: Thu Apr 29, 2004 4:11 pm
Yes and no: a bug always has two sides: One is the bug the user experiences, and one is the mistake in the code of the software. And it can happen (actually often happens), that one mistake in the code causes several bugs for the user, where the user will not be aware that they have a common cause. That means, if Ableton is aware of a bug, finds the mistake in the software and fixes it, it can happen that through this another bug has been fixed without the programmer being aware of it, and then Ableton cannot announce this bugfix because it was kind of done "by accident" (a good accident in this case).Timur wrote: Ah, good to know. I just needed to make sure that I don't have to test all and everything I ever reported. So unless I don't find a fix in the list I can assume it still to be broken. And sure you cannot announce fixes for symptoms you do not know about, no one with a sane mind would expect you to.
Know what I mean?
I understand, but hopefully you put a "fixed" entry into the release notes for every bug that was reported and has been fixed knowingly by your fine coders. Unfortunately the fix-list of this release includes none of my mayor problems, so my copy of Live 7 will stay unpaid at the post office for some more days until I had a chance to test this update some.
Just did a little test. Playback starts better than 7.0.1. No performance problems even if all 5 tracks are unfrozen (7.0.1 wasn't able to do so). BUT after about 5 minutes of playback glitching starts again... 
Live Suite 8.2.2 | Novation Remote SL25 & Launchpad | MacBook 2.4GHz | NI Audio Kontrol 1 | Yamaha HS80M & HS10W | Dozens of plugins...
-
evilxsystems
- Posts: 114
- Joined: Sat Jul 15, 2006 12:32 am
- Location: West Seattle
Re: Beta of upcoming 7.0.2 bug fix update
I think my question might have been overlooked in the Timur / Alex bug debate.rishi wrote:I am running Live7.0.1 with 3 faderfoxes. Can someone please explain what with update actually means? Thanks.Alex wrote:
Changes from Live 7.0.1 to Live 7.02b2
MIDI Surface Controller support for Faderfox LV1, LX1, LV2, LX2, LC2 & LD2.
So to bump...... (and please pardon my ignorance) What does MIDI Surface Controller support for Faderfox actually mean?
Faderfox controllers have been used with Live since version 4 at least.
-
bensuthers
- Posts: 760
- Joined: Wed Oct 01, 2003 4:51 am
-
RhinoInRio
- Posts: 118
- Joined: Wed Nov 14, 2007 1:48 am
- Location: DeutschLand
- Contact:
-
snakedogman
- Posts: 852
- Joined: Mon Jan 29, 2007 11:04 pm
- Location: the Netherlands
Re: Beta of upcoming 7.0.2 bug fix update
yes but they were never supported out of the box for instant/auto mapping.rishi wrote: So to bump...... (and please pardon my ignorance) What does MIDI Surface Controller support for Faderfox actually mean?
Faderfox controllers have been used with Live since version 4 at least.
Hi epytryga,
in Live's preferences? The easiest way to do this is to
delete your preferences file; Live will set all ports to MME
by default the next time you launch it.
cheers,
Jan
Have you tried setting the Remote's MIDI ports to MMEepytryga wrote:with this beta live still freaks out with track volume automation with the Remote Sl...ugh
in Live's preferences? The easiest way to do this is to
delete your preferences file; Live will set all ports to MME
by default the next time you launch it.
cheers,
Jan
After some in-depth investigation with all of my Midi interfaces and a hardware synth I have found the connections between probably all Live 7.01/Midi related problems. Most likely the source of all timing/spikes/glitches problem is the very same that affects the Remote SL: Live's Midi Output is extremly bandwidth limited, for those interfaces/drivers affected it often even worse with MME than with emulated/native DirectMusic. These bugs do not affect Live 6.10 when using the very same interfaces/drivers.
Since I cannot use 7.02 (only useable by registered users) I do not know how much of these issues have been fixed yet. I don't want to waste my time with writing a lenghty report if these things have been handled already anyway, so let me know if you need exact number of notes/midi events necessary to make these issues appear. Different interface/drivers behave differently, all show a specific limit of bandwidth from which on the issues appear. Some start increasing Live CPU meter step by step with increasing bandwidth (more notes being send), some stay down at 1% but start showing short spikes of 100-600% on Live's CPU meter, others start showing regular spikes around 50-60%, some are very much affected by turning on Sync, some are not. All get worse the more midi events/notes are send, which is can also be a problem when stoping a Midi clip during playback, because the Note Off commands increase bandwidth for a short time. All work fine upto a certain point/bandwidth which is different for all interfaces/drivers. It does not matter wether an external hardware synth is connected to an interface or not!
This is an all internal problem of Live 7's engine, Live's CPU load hardly increases when checked with Windows' Task-Manager. And Live 6.10 does even increase its own CPU meter above 1% when sending double or tripple as many notes to the very same devices.
But for those poor souls who keep fighting their Remote SL problems and have "Sync" output enabled I advice to disable it to lower the outgoing bandwidth to the Remote SL. Unfortunately the SL is among those devices that are heavily affected, even more with MME than DirectMusic.
Since I cannot use 7.02 (only useable by registered users) I do not know how much of these issues have been fixed yet. I don't want to waste my time with writing a lenghty report if these things have been handled already anyway, so let me know if you need exact number of notes/midi events necessary to make these issues appear. Different interface/drivers behave differently, all show a specific limit of bandwidth from which on the issues appear. Some start increasing Live CPU meter step by step with increasing bandwidth (more notes being send), some stay down at 1% but start showing short spikes of 100-600% on Live's CPU meter, others start showing regular spikes around 50-60%, some are very much affected by turning on Sync, some are not. All get worse the more midi events/notes are send, which is can also be a problem when stoping a Midi clip during playback, because the Note Off commands increase bandwidth for a short time. All work fine upto a certain point/bandwidth which is different for all interfaces/drivers. It does not matter wether an external hardware synth is connected to an interface or not!
This is an all internal problem of Live 7's engine, Live's CPU load hardly increases when checked with Windows' Task-Manager. And Live 6.10 does even increase its own CPU meter above 1% when sending double or tripple as many notes to the very same devices.
But for those poor souls who keep fighting their Remote SL problems and have "Sync" output enabled I advice to disable it to lower the outgoing bandwidth to the Remote SL. Unfortunately the SL is among those devices that are heavily affected, even more with MME than DirectMusic.
Last edited by Timur on Tue Jan 15, 2008 12:43 pm, edited 2 times in total.