Beta of upcoming bug fix update available: Live 5.0.3b4!
Beta of upcoming bug fix update available: Live 5.0.3b4!
Hi folks,
we just uploaded a beta version of the upcoming bug fix update Live 5.0.3.
This beta is free for every Live 5 user.
Use the following links to download the beta:
Mac: http://www.ableton.com/_common/download ... e503b4.dmg
Win: http://www.ableton.com/_common/download ... e503b4.zip
Please send all beta related feedback to beta@ableton.com.
Current version: Live 5.0.3b4
Expire date: 2005-12-14
This beta has the following some limitations:
- No manual is included
- No content is included
This beta also has enabled our bug reporter.
You will notice it when restarting Live after experiencing a crash.
Furthermore the Windows version has additional debug code to dump
information into the log file. Therefore the Windows version is a bit
slower as the final version (something between 5% to 15%).
When starting live 5.0.3b4 for the first time it should open the Beta lesson
which also contains the change log.
Kind Regards,
Alex
Change log Live Live 5.0.3b3 - 5.0.3b4
-----------------------------------------------------------------
[01] Bug: Pre-Listening status view
-----------------------------------------------------------------
Platform: All
When loading a new Live set while Pre-Listening an audio file within Live's file browser the Pre-Listen status view would not be removed.
Status: Fixed
Change log Live Live 5.0.3b2 - 5.0.3b3
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
Better support for hot (un)plugging of audio interfaces. (OS X only)
Added a preference to enable the System file cache for reading files from hard disk. (Win only)
-----------------------------------------------------------------
[01] Bug: Browser: Delete entry
-----------------------------------------------------------------
Platform: All
Live could crash when when deleting the last item in the Live browser after the browser gained focus by a mouse click below the last row.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Arranger recording
-----------------------------------------------------------------
Platform: All
Arranger recording would not work for recorded Session clips on armed tracks.
Status: Fixed
-----------------------------------------------------------------
[03] Bug: Mappable "?" Key
-----------------------------------------------------------------
Platform: All
The "?" key would be remote-mappable by mistake but would not have any effect as it exclusively do open or do close the info view. Now the "?" is not longer mappable.
Status: Fixed
-----------------------------------------------------------------
[04] Bug: Legato played clips
-----------------------------------------------------------------
Platform: All
Clips played Legato would be "sluggish" if the quantization is set of "None".
Status: Fixed
-----------------------------------------------------------------
[05] Bug: Controller data of MIDI clips
-----------------------------------------------------------------
Platform: All
Assumed there is a playing MIDI clip with some MIDI controller data playing in a an armed MIDI track with Monitoring set to "In", so the clip is not audible.
But although the clip is not audible the MIDI controller data are used as start value for the next recording MIDI clip.
Status: Fixed
Change log Live Live 5.0.3b1 - 5.0.3b2
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
- Stop clips and clips with quantization set to 'global' are fired unquantized in follow actions.
- A clip stop action based on follow action is always unquantized.
- Improved GUI performance when any a Mackie Control device is selected in Live's MIDI preferences.
- Improved GUI performance when select a scene or a track in the Session view.
-----------------------------------------------------------------
[01] Bug: Recording MIDI clip
-----------------------------------------------------------------
Platform: All
When recording a non-overdubbing MIDI session clip with global record enabled at the same time, monitoring would not be possible.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Render To Disk
-----------------------------------------------------------------
Platform: All
Under certain circumstances Live could crash after or during a 'Render To Disk' operation because of overwritten memory.
Status: Fixed
Change log Live Live 5.0.2 - 5.0.3b1
-----------------------------------------------------------------
Improvements: Memory usage
-----------------------------------------------------------------
We were able to reduce the memory usage of Live. Depending on how many clips and how many different physical audio files are used within a set Live could need up to 25% less memory.
-----------------------------------------------------------------
Improvements: Mackie Control Support
-----------------------------------------------------------------
-> Holding down shift while pressing play will do Pause or Continue now.
-> Bank switches will now never align the tracks to the last strip, but always wrap by the number of available strips (8, when using only the main Mackie without any extensions).
-> Support for the "ProjectMix IO" hardware from M-Audio.
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
-> Improved MIDI input timing accuracy.
-> When pressing a keyboard key, which is assigned to the Computer MIDI Keyboard and the RemoteMapper, the keyboard and key-learn mode buttons will flash for a short time in key-learn color to indicate the conflict.
-> Better GUI performance when firing a scene via KEY remote and "Select on Launch" is enabled.
-> Shift + Space also does a Song stop.
-> Improved warper performance when no interpolation is required.
-----------------------------------------------------------------
[01] Bug: Startup scanning of VST Shell plug ins
-----------------------------------------------------------------
Platform: All
Live could crash when scanning a VST Shell-plug in during startup.
This fixes the startup scanning crash with the Waves Shell VST.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Plug-ins in master track
-----------------------------------------------------------------
Platform: All
Routings to or from plug ins in the master track would become gray after saving and opening a song.
Status: Fixed
-----------------------------------------------------------------
[03] Bug: Arpeggiator
-----------------------------------------------------------------
Platform: All
-> Retrigger does not work properly
-> Hold does not work properly
Status: Fixed
-----------------------------------------------------------------
[04] Bug: Summer time on NTFS partition
-----------------------------------------------------------------
Platform: Win only
On Windows computers with summer time change switch active, the modification time of files created on a NTFS partition during the summer time period would be read incorrectly.
Note: This fix will lead Live to scan again the plug-in folder on startup.
Status: Fixed
-----------------------------------------------------------------
[05] Bug: MIDI timing on Multi-core CPUs
-----------------------------------------------------------------
Platform: Win only
When using Windows XP with SP 2 on a multi core CPU, the midi timing could be sometimes wrong because a bug with the power management.
Status: Fixed
-----------------------------------------------------------------
[06] Bug: Mackie Control
-----------------------------------------------------------------
Platform: All
-> When enabling the return track mode via the "edit" button the return channel offset could be wrong.
-> While touching at least one fader, and then pressing the V-Pot to reset its parameter to the default value, the Faders value itself would be set to the default value instead.
Status: Fixed
-----------------------------------------------------------------
[07] Bug: Crossfade on moved tracks
-----------------------------------------------------------------
Platform: All
A track's crossfade assignment would be lost when moving the track.
Status: Fixed
-----------------------------------------------------------------
[08] Bug: Selecting menu with opened plug ins
-----------------------------------------------------------------
Platform: Mac only
Under certain conditions Live could crash when selecting menu items while the editor windows of certain plug ins are open (e.g. Reaktor 5).
Status: Fixed
-----------------------------------------------------------------
[09] Bug: Play selection command
-----------------------------------------------------------------
Platform: All
When the song was running the play selection command on an empty arranger selection Live would stop the song instead of jumping to the insert marker.
Status: Fixed
-----------------------------------------------------------------
[10] Bug: Open or save documents
-----------------------------------------------------------------
Platform: All
Under certain conditions Live could crash when open or save approximately 60 different documents during one run.
Status: Fixed
-----------------------------------------------------------------
[11] Bug: Audio device bit depth resolution
-----------------------------------------------------------------
Platform: Mac only
Audio devices providing several bit depth resolution would be reset to the lower resolution when opening them in Live.
Now the bit depth resolution is used as showed in the "Audio and MIDI Setup" utility from OS X.
Status: Fixed
-----------------------------------------------------------------
[12] Bug: Switching Clip loop during record
-----------------------------------------------------------------
Platform: All
When switching off clip loop during an arranger recording Live would stop the recording of that clip.
Status: Fixed
-----------------------------------------------------------------
[13] Bug: Redo of Impulse slot filling
-----------------------------------------------------------------
Platform: All
The Redo step of filling any impulse slot with a sample would not work properly and could result in bad sounding and a flashing red "D".
Status: Fixed
-----------------------------------------------------------------
[14] Bug: Track out fading
-----------------------------------------------------------------
Platform: All
Under certain circumstances the track in or out fading would not work properly.
This fixes also the bug that switching off a tracks 'solo' button could result in a click.
Status: Fixed
-----------------------------------------------------------------
[15] Bug: Complex warper
-----------------------------------------------------------------
Platform: All
Under certain conditions there are CPU usage peak when using the complex warper because a division by zero.
Status: Fixed
-----------------------------------------------------------------
[16] Bug: Dragging files from outside
-----------------------------------------------------------------
Platform: All
Live could crash when dragging different types of files from outside into the arranger.
Status: Fixed
-----------------------------------------------------------------
[17] Bug: Deactivated MIDI notes
-----------------------------------------------------------------
Platform: All
Deactived MIDI notes would be shown in arranger and envelope view.
Status: Fixed
we just uploaded a beta version of the upcoming bug fix update Live 5.0.3.
This beta is free for every Live 5 user.
Use the following links to download the beta:
Mac: http://www.ableton.com/_common/download ... e503b4.dmg
Win: http://www.ableton.com/_common/download ... e503b4.zip
Please send all beta related feedback to beta@ableton.com.
Current version: Live 5.0.3b4
Expire date: 2005-12-14
This beta has the following some limitations:
- No manual is included
- No content is included
This beta also has enabled our bug reporter.
You will notice it when restarting Live after experiencing a crash.
Furthermore the Windows version has additional debug code to dump
information into the log file. Therefore the Windows version is a bit
slower as the final version (something between 5% to 15%).
When starting live 5.0.3b4 for the first time it should open the Beta lesson
which also contains the change log.
Kind Regards,
Alex
Change log Live Live 5.0.3b3 - 5.0.3b4
-----------------------------------------------------------------
[01] Bug: Pre-Listening status view
-----------------------------------------------------------------
Platform: All
When loading a new Live set while Pre-Listening an audio file within Live's file browser the Pre-Listen status view would not be removed.
Status: Fixed
Change log Live Live 5.0.3b2 - 5.0.3b3
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
Better support for hot (un)plugging of audio interfaces. (OS X only)
Added a preference to enable the System file cache for reading files from hard disk. (Win only)
-----------------------------------------------------------------
[01] Bug: Browser: Delete entry
-----------------------------------------------------------------
Platform: All
Live could crash when when deleting the last item in the Live browser after the browser gained focus by a mouse click below the last row.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Arranger recording
-----------------------------------------------------------------
Platform: All
Arranger recording would not work for recorded Session clips on armed tracks.
Status: Fixed
-----------------------------------------------------------------
[03] Bug: Mappable "?" Key
-----------------------------------------------------------------
Platform: All
The "?" key would be remote-mappable by mistake but would not have any effect as it exclusively do open or do close the info view. Now the "?" is not longer mappable.
Status: Fixed
-----------------------------------------------------------------
[04] Bug: Legato played clips
-----------------------------------------------------------------
Platform: All
Clips played Legato would be "sluggish" if the quantization is set of "None".
Status: Fixed
-----------------------------------------------------------------
[05] Bug: Controller data of MIDI clips
-----------------------------------------------------------------
Platform: All
Assumed there is a playing MIDI clip with some MIDI controller data playing in a an armed MIDI track with Monitoring set to "In", so the clip is not audible.
But although the clip is not audible the MIDI controller data are used as start value for the next recording MIDI clip.
Status: Fixed
Change log Live Live 5.0.3b1 - 5.0.3b2
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
- Stop clips and clips with quantization set to 'global' are fired unquantized in follow actions.
- A clip stop action based on follow action is always unquantized.
- Improved GUI performance when any a Mackie Control device is selected in Live's MIDI preferences.
- Improved GUI performance when select a scene or a track in the Session view.
-----------------------------------------------------------------
[01] Bug: Recording MIDI clip
-----------------------------------------------------------------
Platform: All
When recording a non-overdubbing MIDI session clip with global record enabled at the same time, monitoring would not be possible.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Render To Disk
-----------------------------------------------------------------
Platform: All
Under certain circumstances Live could crash after or during a 'Render To Disk' operation because of overwritten memory.
Status: Fixed
Change log Live Live 5.0.2 - 5.0.3b1
-----------------------------------------------------------------
Improvements: Memory usage
-----------------------------------------------------------------
We were able to reduce the memory usage of Live. Depending on how many clips and how many different physical audio files are used within a set Live could need up to 25% less memory.
-----------------------------------------------------------------
Improvements: Mackie Control Support
-----------------------------------------------------------------
-> Holding down shift while pressing play will do Pause or Continue now.
-> Bank switches will now never align the tracks to the last strip, but always wrap by the number of available strips (8, when using only the main Mackie without any extensions).
-> Support for the "ProjectMix IO" hardware from M-Audio.
-----------------------------------------------------------------
Improvements: General
-----------------------------------------------------------------
-> Improved MIDI input timing accuracy.
-> When pressing a keyboard key, which is assigned to the Computer MIDI Keyboard and the RemoteMapper, the keyboard and key-learn mode buttons will flash for a short time in key-learn color to indicate the conflict.
-> Better GUI performance when firing a scene via KEY remote and "Select on Launch" is enabled.
-> Shift + Space also does a Song stop.
-> Improved warper performance when no interpolation is required.
-----------------------------------------------------------------
[01] Bug: Startup scanning of VST Shell plug ins
-----------------------------------------------------------------
Platform: All
Live could crash when scanning a VST Shell-plug in during startup.
This fixes the startup scanning crash with the Waves Shell VST.
Status: Fixed
-----------------------------------------------------------------
[02] Bug: Plug-ins in master track
-----------------------------------------------------------------
Platform: All
Routings to or from plug ins in the master track would become gray after saving and opening a song.
Status: Fixed
-----------------------------------------------------------------
[03] Bug: Arpeggiator
-----------------------------------------------------------------
Platform: All
-> Retrigger does not work properly
-> Hold does not work properly
Status: Fixed
-----------------------------------------------------------------
[04] Bug: Summer time on NTFS partition
-----------------------------------------------------------------
Platform: Win only
On Windows computers with summer time change switch active, the modification time of files created on a NTFS partition during the summer time period would be read incorrectly.
Note: This fix will lead Live to scan again the plug-in folder on startup.
Status: Fixed
-----------------------------------------------------------------
[05] Bug: MIDI timing on Multi-core CPUs
-----------------------------------------------------------------
Platform: Win only
When using Windows XP with SP 2 on a multi core CPU, the midi timing could be sometimes wrong because a bug with the power management.
Status: Fixed
-----------------------------------------------------------------
[06] Bug: Mackie Control
-----------------------------------------------------------------
Platform: All
-> When enabling the return track mode via the "edit" button the return channel offset could be wrong.
-> While touching at least one fader, and then pressing the V-Pot to reset its parameter to the default value, the Faders value itself would be set to the default value instead.
Status: Fixed
-----------------------------------------------------------------
[07] Bug: Crossfade on moved tracks
-----------------------------------------------------------------
Platform: All
A track's crossfade assignment would be lost when moving the track.
Status: Fixed
-----------------------------------------------------------------
[08] Bug: Selecting menu with opened plug ins
-----------------------------------------------------------------
Platform: Mac only
Under certain conditions Live could crash when selecting menu items while the editor windows of certain plug ins are open (e.g. Reaktor 5).
Status: Fixed
-----------------------------------------------------------------
[09] Bug: Play selection command
-----------------------------------------------------------------
Platform: All
When the song was running the play selection command on an empty arranger selection Live would stop the song instead of jumping to the insert marker.
Status: Fixed
-----------------------------------------------------------------
[10] Bug: Open or save documents
-----------------------------------------------------------------
Platform: All
Under certain conditions Live could crash when open or save approximately 60 different documents during one run.
Status: Fixed
-----------------------------------------------------------------
[11] Bug: Audio device bit depth resolution
-----------------------------------------------------------------
Platform: Mac only
Audio devices providing several bit depth resolution would be reset to the lower resolution when opening them in Live.
Now the bit depth resolution is used as showed in the "Audio and MIDI Setup" utility from OS X.
Status: Fixed
-----------------------------------------------------------------
[12] Bug: Switching Clip loop during record
-----------------------------------------------------------------
Platform: All
When switching off clip loop during an arranger recording Live would stop the recording of that clip.
Status: Fixed
-----------------------------------------------------------------
[13] Bug: Redo of Impulse slot filling
-----------------------------------------------------------------
Platform: All
The Redo step of filling any impulse slot with a sample would not work properly and could result in bad sounding and a flashing red "D".
Status: Fixed
-----------------------------------------------------------------
[14] Bug: Track out fading
-----------------------------------------------------------------
Platform: All
Under certain circumstances the track in or out fading would not work properly.
This fixes also the bug that switching off a tracks 'solo' button could result in a click.
Status: Fixed
-----------------------------------------------------------------
[15] Bug: Complex warper
-----------------------------------------------------------------
Platform: All
Under certain conditions there are CPU usage peak when using the complex warper because a division by zero.
Status: Fixed
-----------------------------------------------------------------
[16] Bug: Dragging files from outside
-----------------------------------------------------------------
Platform: All
Live could crash when dragging different types of files from outside into the arranger.
Status: Fixed
-----------------------------------------------------------------
[17] Bug: Deactivated MIDI notes
-----------------------------------------------------------------
Platform: All
Deactived MIDI notes would be shown in arranger and envelope view.
Status: Fixed
Last edited by Alex on Fri Dec 09, 2005 6:31 pm, edited 1 time in total.
Thanks.
I hope you guys can fix this bug soon:
I hope you guys can fix this bug soon:
Q&A wrote:Problem:
When Rendering to disk Live is not prompting the name of the song that I am rendering, instead it is prompting the name of the last rendered file.
example:
I launch Live, open a set called "A". I select render to disk and am prompted with
"A Rendered"
Fine.
Then I open set named "B". I select the 'render to disk' command, and I am prompted with
"A Rendered"
When "B Rendered" is what should be there.
If I relaunch Live and open Set named "B", now it will prompt me with
"B Rendered" but obviously the obove problem continues.
I hope this is enough info for the fix to be implimented....if this is a crosspost??....GOOD, fix it.
thanks.
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
appears to be very smooth and using less cpu though I haven't done a direct comparison to see how much less cpu
but I'm having a problem with a song I made that has alot of quick follow actions. in 5.0.2 it sounds very rhythmic but in 5.0.3 it just sounds jumbled. the follow actions are set on random selecting from about 10 different midi clips, each action happens between a 16th note and a quarter note appart which isn't too fast but it just doesn't sound the same in the least. any idea as to why? they are set to legato and global.
but I'm having a problem with a song I made that has alot of quick follow actions. in 5.0.2 it sounds very rhythmic but in 5.0.3 it just sounds jumbled. the follow actions are set on random selecting from about 10 different midi clips, each action happens between a 16th note and a quarter note appart which isn't too fast but it just doesn't sound the same in the least. any idea as to why? they are set to legato and global.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
figured out why but it raises a question for the abes.
(and apparently it wasn't that fast of a follow action, only 1 bar per action)
in 5.0.2 I had follow actions happening set to global but the little number box in the follow action settings was set to 0 0 1 and 0 1 0 and such, but being that they were set to global and global was set to 1 bar then each event happened at each bar (and ignored the numbers if I'm not mistaken). but in 5.0.3 beta the same song with the same settings would have follow actions not happening at the global 1 bar but it would have the action happen at 0 0 1 and 0 1 0 and so on even though the follow action is specifically set to global. so I'm just trying to understand if this is a bug or just a difference in the implimentation of the feature or what. please explain to me if I'm missing something here.
(and apparently it wasn't that fast of a follow action, only 1 bar per action)
in 5.0.2 I had follow actions happening set to global but the little number box in the follow action settings was set to 0 0 1 and 0 1 0 and such, but being that they were set to global and global was set to 1 bar then each event happened at each bar (and ignored the numbers if I'm not mistaken). but in 5.0.3 beta the same song with the same settings would have follow actions not happening at the global 1 bar but it would have the action happen at 0 0 1 and 0 1 0 and so on even though the follow action is specifically set to global. so I'm just trying to understand if this is a bug or just a difference in the implimentation of the feature or what. please explain to me if I'm missing something here.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
Hi,Johnisfaster wrote:figured out why but it raises a question for the abes.
(and apparently it wasn't that fast of a follow action, only 1 bar per action)
in 5.0.2 I had follow actions happening set to global but the little number box in the follow action settings was set to 0 0 1 and 0 1 0 and such, but being that they were set to global and global was set to 1 bar then each event happened at each bar (and ignored the numbers if I'm not mistaken). but in 5.0.3 beta the same song with the same settings would have follow actions not happening at the global 1 bar but it would have the action happen at 0 0 1 and 0 1 0 and so on even though the follow action is specifically set to global. so I'm just trying to understand if this is a bug or just a difference in the implimentation of the feature or what. please explain to me if I'm missing something here.
I can't quote it on that computer, but yes, the design of the stop of a follow action has changed. Enable the Lessons in 5.0.3 and see the change log, I blelive from 5.0.2 to 5.0.3b1, but it could be 5.0.3b1 to 5.0.3b2.
Best,
amo
Live 5.0.3 - IBM Thinkpad R51 1.5ghz Centrino - 1,5 Go RAM - 7200 RPM 2nd HDD intern - RME Multiface - Windows XP Pro SP2
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
it's really very frustrating that as they improve this program apparently my old songs aren't always going to sound the same? thats basically what you're telling me if you say the design of the follow action has changed.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
Well, I'm just recalling that thing from memory and thought it would help you understand you're problem. What changed is the behaviour of the stopping of clips playing in follow action.Johnisfaster wrote:it's really very frustrating that as they improve this program apparently my old songs aren't always going to sound the same? thats basically what you're telling me if you say the design of the follow action has changed.
True that tracks using follow action will need some adjustment. I guess, but could be wrong, that the quickest way in your case would be to select all the concerned clips at once, and change their launch mode from global to "1 bar". Does that work for you ?
Cheers,
amo
Live 5.0.3 - IBM Thinkpad R51 1.5ghz Centrino - 1,5 Go RAM - 7200 RPM 2nd HDD intern - RME Multiface - Windows XP Pro SP2
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
yeah I did that right after I figured out what the difference was. and that seems to do the trick but (I may or may not be wrong about this) it seems to repeatedly go back to different clips more often than in 5.0.2. it seemed more naturally random in 5.0.2 now it seems like it keeps going back to the same few over and over.
maybe I'm crazy, but maybe they changed the "randomness"
although!!!!!!!!! I just tried opening a few songs that I had previously not been ableton play in 5.0.2 without crazy amounts of glitches and they run so smooth now. I used to have to freeze everything. but now they work great. SO FAR I'M VERY HAPPY WITH THE CPU USAGE. just a little unsure of the follow action differences.
maybe I'm crazy, but maybe they changed the "randomness"
although!!!!!!!!! I just tried opening a few songs that I had previously not been ableton play in 5.0.2 without crazy amounts of glitches and they run so smooth now. I used to have to freeze everything. but now they work great. SO FAR I'M VERY HAPPY WITH THE CPU USAGE. just a little unsure of the follow action differences.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
Johnisfaster---fwiw, it doesn't seem to cause any trouble to leave a previous version of Live 5 on your computer, so at least a workaround for now would be to leave 5.0.2 on there so that the songs that are working the way you want in 5.0.2 will continue to do so. Guess it might be safest to save a copy of them to open in any subsequent version. hope it all works out.
Dell Studio XPS 8100 Windows 7 64-bit, 10 GB RAM. RME Multiface, Avalon U5 & M5, Distressor, Filter Factory, UC33e, BCR-2000, FCB1010, K-Station, Hr 824 & H120 sub, EZ Bus, V-Drums, DrumKat EZ, basses, guitars, pedals... http://www.ryan-hughes.net
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
oh totally I plan on leaving 5.0.2 on here. with 100 gigs on this laptop available to me I never remove any programs unless I either hate it or it becomes a problem. I've seen in the past with fruityloops that alot of times when you get updates your old songs just don't work properlly so I got in the habit of keeping all versions.
I hope I'm not coming accross like a jerk here but what is fwiw?
I hope I'm not coming accross like a jerk here but what is fwiw?
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
-
- Posts: 76
- Joined: Wed May 08, 2002 9:44 am
- Location: Italy
Hi Eraldo,
in Live 5.0.3 follow actions should behave like Robert stated in his second! statement of this thread: http://www.ableton.com/forum/viewtopic.php?t=27876
regards,
/Alex
in Live 5.0.3 follow actions should behave like Robert stated in his second! statement of this thread: http://www.ableton.com/forum/viewtopic.php?t=27876
regards,
/Alex