Ableton Forum

23 wrote:Live is great, but it still does leave some things to be desired.

For one, Live's MIDI implementation, though horrible by no means, still could use some help. I'm not expecting Ableton to push for making Live some sort of Logic or SX, but hopefully they can pump up the MIDI implementation some.

For one, anyone happen to have a synth that happens to throw out NRPN values? Try recording those into Live....try editing those in Live? I think you'll find you hit a brick wall in both cases.

In regard to editing continous MIDI controller data or even typical envelope information in samples, a line tool would be great!

Multi-timbral capable MIDI clips would be excellent!? Currently we get forced to have things streamlined to one MIDI channel (though we can take in from many), why can't a clip contain data being fed amongst varying MIDI channels? For those that may not see the use of this, say a drum line is composed utilizing different drum modules....rather than having to spread them out amongst tracks, one track could be used to for all the modules; further a clip could be used to send information for any number of the modules pertaining to that track.

Have some sort of display allowing the user to see how much RAM Live currently needs and is using to work effectively (allowing users to gain warning as to when they are about to enter into memory swapping territory).

Now maybe there is a way to do this that I just haven't caught, but Live can export audio, why can't it export MIDI (in regard to arrangement view or clips in session view). Further, rather than having to deal with resampling, how bout a means of having Live develop a new entirely new sample in Session view that is based upon how the envelopes, time stretches, etc. within a clip are set, this new sample can then replace the originala sample. Essientially giving the user the option of if they want to take up more drive/disk space or if they want to simply take up more CPU for the automation being conducted. As is, from what I understand, this is practically what's being done during track freezes......why not give us the ability to not freeze, and just simply create entirely new replacement samples for what we have in the clip without going through a formal resampling process.

MIDI program changes......lets get it so that they can occur at any given time within a clip.

Keystroke/MIDI assignments.....you get to dealing with large Live sets, and well, you can eventually start running out of keys or various MIDI actions to use to trigger scenes or clips. How bout providing a means by which large amounts of key/MIDI assignments can be reassigned quickly, on the go, while things are playing. For example, say someone has a full octave on a keyboard with each key pertaining to a given scene. The full amount of scenes go beyond this designated octave though. Perhaps a means could be implemented where the range group of keys that do pertain to scenes can be considered part of a group, and a command could be implemented where by that entire group could be kept in order but moved down to the next until the first key of the group is now located at what would have been the first unassigned scene (if this causes some keys to no longer be active within the set, so be it). Like wise the group could be moved back up in the same manner.

The ability to tell live to clear it's undo history quickly and efficiently. Again, just as a means of being able to help manage RAM allocation. Have a super large Live set, you know memory swapping is going to eventually become a problem, well then before it becomes a problem, wipe out a bunch of samples you know you will know longer be using, clear the undo history, and Live now has access to that much more RAM.

In any regard, just my two cents on some of the things that I think could be implemented in a future version(s) of Live.

-Al

knotkranky wrote:

leisuremuffin wrote: I thnk the guys running the ship think of live as their baby first and as a product second. .lm.

Thank you.



Ok, so what we have are a bunch of peoples faces and names without titles or positions, even some grapes.

Who is the CEO, CFO and COO of Ableton? Do you know? Do tell.

23 wrote:

In any regard, I meant to address both, but more definately more keenly on feature issues. The problem with software development is that you can't count on eveyrone to be using exactly the same system. You can attempt to emulate a good number of different systems on which your software may be used, but in the end in all probability there will be systems your software is used on that you didn't test for/weren't expecting.

Along side this, you can bang and bang and bang to test things out, but the chances of you trying everything in every possible combination is also unlikely (beta testing is great for this). In any regard, in this way it becomes likely that there will be some sort of bug or other that gets left in despite your best attempts to not allow such.

All in all, it's great, all be it extremely rare that a piece of software with any kind of depth to it gets released and is able to work 100% In this way, what I would look for is for Ableton to address uprising problems in a time efficient manner; but not expect them to not run into them. In this regard I feel Ableton have shown that they in deed care about the quality of their product and their clientel base.

With that aside, that leaves the next important issue of a future major version of Live to reside in it's feature set. And if Live 6 is in deed to be a "Rock" I feel that we should not only be looking towards good product support (which I feel Ableton has shown), but also a hosting of usefull features that were missed during previous incarnations (for whatever reason).

If anything, I think the single largest stablity issue we should look towards Ableton resolving is the memory swap issue. They already give us a means of monitoring a CPU load, but Live is so RAM dependent, that I feel that they need to give us a means of monitoring this as well.

RopeyPunter wrote:hey 23...if you are supster will you PM me and let me know my powers of deduction are second to none ?

23 wrote:Live is great, but it still does leave some things to be desired.

For one, Live's MIDI implementation, though horrible by no means, still could use some help. I'm not expecting Ableton to push for making Live some sort of Logic or SX, but hopefully they can pump up the MIDI implementation some.

For one, anyone happen to have a synth that happens to throw out NRPN values? Try recording those into Live....try editing those in Live? I think you'll find you hit a brick wall in both cases.

In regard to editing continous MIDI controller data or even typical envelope information in samples, a line tool would be great!

Multi-timbral capable MIDI clips would be excellent!? Currently we get forced to have things streamlined to one MIDI channel (though we can take in from many), why can't a clip contain data being fed amongst varying MIDI channels? For those that may not see the use of this, say a drum line is composed utilizing different drum modules....rather than having to spread them out amongst tracks, one track could be used to for all the modules; further a clip could be used to send information for any number of the modules pertaining to that track.

Have some sort of display allowing the user to see how much RAM Live currently needs and is using to work effectively (allowing users to gain warning as to when they are about to enter into memory swapping territory).

Now maybe there is a way to do this that I just haven't caught, but Live can export audio, why can't it export MIDI (in regard to arrangement view or clips in session view). Further, rather than having to deal with resampling, how bout a means of having Live develop a new entirely new sample in Session view that is based upon how the envelopes, time stretches, etc. within a clip are set, this new sample can then replace the originala sample. Essientially giving the user the option of if they want to take up more drive/disk space or if they want to simply take up more CPU for the automation being conducted. As is, from what I understand, this is practically what's being done during track freezes......why not give us the ability to not freeze, and just simply create entirely new replacement samples for what we have in the clip without going through a formal resampling process.

MIDI program changes......lets get it so that they can occur at any given time within a clip.

Keystroke/MIDI assignments.....you get to dealing with large Live sets, and well, you can eventually start running out of keys or various MIDI actions to use to trigger scenes or clips. How bout providing a means by which large amounts of key/MIDI assignments can be reassigned quickly, on the go, while things are playing. For example, say someone has a full octave on a keyboard with each key pertaining to a given scene. The full amount of scenes go beyond this designated octave though. Perhaps a means could be implemented where the range group of keys that do pertain to scenes can be considered part of a group, and a command could be implemented where by that entire group could be kept in order but moved down to the next until the first key of the group is now located at what would have been the first unassigned scene (if this causes some keys to no longer be active within the set, so be it). Like wise the group could be moved back up in the same manner.

The ability to tell live to clear it's undo history quickly and efficiently. Again, just as a means of being able to help manage RAM allocation. Have a super large Live set, you know memory swapping is going to eventually become a problem, well then before it becomes a problem, wipe out a bunch of samples you know you will know longer be using, clear the undo history, and Live now has access to that much more RAM.

In any regard, just my two cents on some of the things that I think could be implemented in a future version(s) of Live.

-Al

leisuremuffin wrote:

talking is about the exchange of ideas, not just having people pat you on the back and agree with you...

njh wrote:the both of you need to kiss and make up