Dubstepforum.com

This is a simple question that I just cat figure out or find the solution to.



In Ableton Live 7: How do I select all volume faders and control them at once?

ie. I want to turn everything down -6db and dont feel like individually go through each track.

If Its the same as live 8 then you hold shift whilst highlighting the first track in the row and keep it held down and click on the last track. It will highlight everything in between.

billy crystal meth wrote:This is a simple question that I just cat figure out or find the solution to.



In Ableton Live 7: How do I select all volume faders and control them at once?

ie. I want to turn everything down -6db and dont feel like individually go through each track.

Sadly (and stupidly) you can't. They didn't introduce that "feature" until Live 8.

Just go to every channel meter and subtract -6 from the number.

contakt321 wrote:

billy crystal meth wrote:This is a simple question that I just cat figure out or find the solution to.



In Ableton Live 7: How do I select all volume faders and control them at once?

ie. I want to turn everything down -6db and dont feel like individually go through each track.

Sadly (and stupidly) you can't. They didn't introduce that "feature" until Live 8.

Just go to every channel meter and subtract -6 from the number.

Thanks. I have been doing this. Strange that this would be left out.

Ok, so I am working on some tunes with a friend, and hes got Ableton 7, and I got Ableton 8, I just know when he sends me all the files, they wont open, any way to make doing this, and it not be time consuming (rendering every individual track) and pain in the ass...???

have you done "collect all and save" with the project and then ask him to send the project folder. my memory of switching from 7 to 8 is vague but i don't remember any issues opening my 7 projects in 8. otherway round won't work though.

rendering individual tracks doesn't need to be that time-consuming though, the options box that pops up when you select render has an option to render the individual tracks.

ShadowMachine wrote:Ok, so I am working on some tunes with a friend, and hes got Ableton 7, and I got Ableton 8, I just know when he sends me all the files, they wont open, any way to make doing this, and it not be time consuming (rendering every individual track) and pain in the ass...???

I've had the same exact problem. About 3 months ago my boy sent me an old project and when i oppened it an error message popped up saying something like 'older version of live used for this project...not compatible with current version'. None of the samples could be found either. Only thing that showed up was the Midi track for a drum rack he had up. Whichhhhh, didn't contain any drums once i looked inside. All audio clips were blank and said 'samples offline'.

Just make him export all the tracks from the render window (Rendered track: All tracks). Watch out for those sends though! They get exported as one stem and if you have 5 tracks routed to Send A things can get messy later. For further ease, collect midi, patches and anything else you can.

Redderious wrote:None of the samples could be found either. Only thing that showed up was the Midi track for a drum rack he had up. Whichhhhh, didn't contain any drums once i looked inside. All audio clips were blank and said 'samples offline'.

Maybe he didn't self-contain the set?

Hi all, I have a very unusual problem and any help to solve this problem would be deeply appreciated. I have searched around the net beforehand and found nothing so here we go...

When I am am manually automating clips by drawing them in on my arrange view the automation isnt happening as it should. For instance, lets say I am using massive and want to automate the LFO rate of my bass half way though a note. So i draw in my automation for it to change half way through the note but it doesn't change straight away. It changes a split second later which makes the note it changed on modulate too when this may not be what i want.

To me it seems like some sort of latency issue where the automation isnt starting where it is supposed to but I have no idea how to fix this. If anyone has any advice or has had a similar problem the help would be great.

Thanks.

What audio driver are you using? If you're on Windows you need to be using ASIO.
Changing it should fix your problem

Does not sound like that to me, to be honest.

Is it happening with all your automation parameters or does it happen only in Massive or only in this project?

If it's Massive related, have you tried seeing whether there is an ADSR envelope with a slow attack and no retrigger on the parameter?

Unfortunately not of that worked ... The problem isn't massive only related because I just tried it with a 'Simpler' and the same problem occured

Heres what the problem looks like...

http://postimage.org/image/1t7vnxtw

As you can see by the automation i am trying to make it stop before the next notes starts....

http://postimage.org/image/1t2x1wck

In this picture the automation is working how i would like it too but as you can see the automation line is a third the way through the next note which is what makes me think there might be some latency issues. This is a bit annoying considering everytime i want to do a simple automation i have to spend ages trying to figure out how the automation line should be drawn out.

Any further advice would be greatful!

preferences ---> CPU ---> plug-in buffer size ---> 128

that would be the first thing i'd check. by default it's set to the same as your ASIO buffer size, so at high soundcard latencies you get latency on the automation as well. it's strange, though, that in your case the automation is *late* -- i've always found it to be a few milliseconds *early* when the buffer size was too large.

EDIT: looking at the screenshots it seems your automation does come in early, not late

static_cast wrote:preferences ---> CPU ---> plug-in buffer size ---> 128

that would be the first thing i'd check. by default it's set to the same as your ASIO buffer size, so at high soundcard latencies you get latency on the automation as well. it's strange, though, that in your case the automation is *late* -- i've always found it to be a few milliseconds *early* when the buffer size was too large.

EDIT: looking at the screenshots it seems your automation does come in early, not late

yeah sorry pal your right, it is coming in too early... I tried what you said and it made a slight difference but still a tad to early, i also tried the other buffer sizes but still didn't work

matb123 wrote:

static_cast wrote:preferences ---> CPU ---> plug-in buffer size ---> 128

that would be the first thing i'd check. by default it's set to the same as your ASIO buffer size, so at high soundcard latencies you get latency on the automation as well. it's strange, though, that in your case the automation is *late* -- i've always found it to be a few milliseconds *early* when the buffer size was too large.

EDIT: looking at the screenshots it seems your automation does come in early, not late

yeah sorry pal your right, it is coming in too early... I tried what you said and it made a slight difference but still a tad to early, i also tried the other buffer sizes but still didn't work

set the plug-in buffer size to 64, then try automating a Utility or something and see if it lines up with, say, a kick drum sequenced on the beat, and report back... 64 samples should be almost unnoticeable, given latency compensation.

static_cast wrote:

matb123 wrote:

static_cast wrote:preferences ---> CPU ---> plug-in buffer size ---> 128

that would be the first thing i'd check. by default it's set to the same as your ASIO buffer size, so at high soundcard latencies you get latency on the automation as well. it's strange, though, that in your case the automation is *late* -- i've always found it to be a few milliseconds *early* when the buffer size was too large.

EDIT: looking at the screenshots it seems your automation does come in early, not late

yeah sorry pal your right, it is coming in too early... I tried what you said and it made a slight difference but still a tad to early, i also tried the other buffer sizes but still didn't work

set the plug-in buffer size to 64, then try automating a Utility or something and see if it lines up with, say, a kick drum sequenced on the beat, and report back... 64 samples should be almost unnoticeable, given latency compensation.

Hmm... seems to be working fine with the kick drum but the problem still continues with the massive automation. Maybe the problem lies with massive itself?

okay thats strange... even though i tried it a minite ago it now seems to be working with massive aha....

Thank you static_cast, owe you one!

okay maybe not worked for about 2 minitues and went off, if there is anyone that knows how to fix this please could you give me some advice on what to do.

thanks!

Can you resample the result on another track so we can look at them side by side? Maybe automate gain, so that the delay is more obvious when looked at. Make the modulation and the resampled material visible.

Out of curiosity

What does your new live set template look like?

I have

Track 1 - Kik - Instrument rack with 2 Simplers
Track 2 - Snare - Instrument rack with 3 Simplers
Track 3 - Percussion - Drum Rack

I find that these are the barebone essential when Im starting almost any track of any genre