Ableton Forum

lola wrote:

Sibanger wrote:
Its crapping me off about the SL though. I don't want to turn it off,
or go back to Live 6.

Have patience , they are working on it, think its fixed in 7.02 ( as the mail sayed that i received from them)


Funny tho, you talked about the bcr that it is working flawless..
I got F****** blue screens from its driver when just hit one control on it.
Thats why i switched to a remote sl hehe

How long ago did you have the BCR problems?
Have you still got it? If so, you might have to drag it out again.

same problemo with the crackles

Sibanger wrote:

lola wrote:

Sibanger wrote:
Its crapping me off about the SL though. I don't want to turn it off,
or go back to Live 6.

Have patience , they are working on it, think its fixed in 7.02 ( as the mail sayed that i received from them)


Funny tho, you talked about the bcr that it is working flawless..
I got F****** blue screens from its driver when just hit one control on it.
Thats why i switched to a remote sl hehe

How long ago did you have the BCR problems?
Have you still got it? If so, you might have to drag it out again.

Think it was a couple of months ago... maybe in august..
The strangest thing was the driver behringer provided on their site which would fix the blue screen error (caused by midi) caused even more blue screens.
I mailed Behringer, and they provided a working driver....
I thought " what a strange policy, put it for all users on the site so everybody can benefit from it" hehe

But to cut it short, the behringer is collecting dust now, and i like the remote sl much better.

I'm also having the same crackle problem. I see though that crackle happens when a live sends out a midi sync message to my remote sl, a CPU spike happens, and then the audible glitch. When I don't have the sl hooked up then no issue. Its the same deal with no issue with the PCR-300, with is only sending midi messages not receiving them like the SL does. So in a nutshell I'm convinced the bug is in Lives "new" midi engine since this is happening with other devices that also recieve midi messages as a part of its functions.

Are you all running Windows ?

If so, then I've seen this before and this problem has nothing to do with your controllers, mouse or Live, it's all down to IRQ sharing in Windows XP.

Video cards, hard drives, ect usually get their own IRQ in XP but audio cards (PCI, usb and firewire) for some reason are lumped into the 'Other devices' category and often onto the same IRQ as other devices like mice, even QWERTY keyboards and controllers, so when you move a control/mouse the data flow from your card is interrupted and you hear a crackle.

It's pretty common, used to have this problem on my old PC with a PCI Emu 1212m

You can find out what is sharing IRQ's by going to

System Information > Hardware Resources> IRQ

Solving it is sometimes tough, on a desktop pc you can keep changing the PCI slot your card is in, and keep booting in different configurations till you find one where you audio card is sharing with nothing (if your lucky) or something which you can easily do without or disable. Switching USB ports on a lappy may have the same effect but I'd say only if they are in a different physical location (i.e. left and right on a lappy), I've never tried this though but worth a look.

On a laptop you need to disable anything you don't need, card readers, wireless networking, wired networking, integrated webcams ect reboot and hope your card is sitting on its own IRQ, if you've exhausted every option you can edit the IRQ configuration manually but this is NOT recommended and you may have problems down the road as XP likes to manage IRQs itself and can throw a wobbly. If you do go down this road be sure to read up before you try it.

XP can see different controllers differently and put them on different IRQ's, that's why people changed controllers and the problem went away, there was probably nothing wrong with your controller.

Any questions let me know.

Hope this helps.



edit: I'm thinking the Live 7 CPU spike issue, linked to in this thread, is a different issue to the one I and johnisfaster have described. This issue relates only to crackles when moving controllers/mouse, not cpu spikes.

Thanks for sharing knowledge Beatpoet,

I'm not too familiar with these kind of settings so I'll just have a look and see if it is easily solved.
From the beta forum I did read several replies stating this is a known issue in v7.01 and should be fixed in the next release.
Let's hope they will!

Also from the beta user forum I did find a workaround which is helpfull for me for the time being.
Turning off MIDI output 2 of my remote in Live's preferences did work, but I don't exactly understand what this setting is ment for, so which functionality is missing right now.
I still can edit and arrange a sequence or plugin parameters with my remote.

cherio

beatpoet wrote:Are you all running Windows ?

If so, then I've seen this before and this problem has nothing to do with your controllers, mouse or Live, it's all down to IRQ sharing in Windows XP.

Video cards, hard drives, ect usually get their own IRQ in XP but audio cards (PCI, usb and firewire) for some reason are lumped into the 'Other devices' category and often onto the same IRQ as other devices like mice, even QWERTY keyboards and controllers, so when you move a control/mouse the data flow from your card is interrupted and you hear a crackle.

It's pretty common, used to have this problem on my old PC with a PCI Emu 1212m

You can find out what is sharing IRQ's by going to

System Information > Hardware Resources> IRQ

Solving it is sometimes tough, on a desktop pc you can keep changing the PCI slot your card is in, and keep booting in different configurations till you find one where you audio card is sharing with nothing (if your lucky) or something which you can easily do without or disable. Switching USB ports on a lappy may have the same effect but I'd say only if they are in a different physical location (i.e. left and right on a lappy), I've never tried this though but worth a look.

On a laptop you need to disable anything you don't need, card readers, wireless networking, wired networking, integrated webcams ect reboot and hope your card is sitting on its own IRQ, if you've exhausted every option you can edit the IRQ configuration manually but this is NOT recommended and you may have problems down the road as XP likes to manage IRQs itself and can throw a wobbly. If you do go down this road be sure to read up before you try it.

XP can see different controllers differently and put them on different IRQ's, that's why people changed controllers and the problem went away, there was probably nothing wrong with your controller.

Any questions let me know.

Hope this helps.



edit: I'm thinking the Live 7 CPU spike issue, linked to in this thread, is a different issue to the one I and johnisfaster have described. This issue relates only to crackles when moving controllers/mouse, not cpu spikes.

Yep, on PC here.
Thanks for your advice beatpoet.
I'm still hoping it will be fixed in 7.02. If not I'll be pissed and then I'll
go through your process described above.

beatpoet wrote:Are you all running Windows ?

why would this problem only materialise in live 7 and not live 6 ?

If what you're suggesting is actually the problem, wouldn't it manifest in other audio programs too ?

If this is the problem then it would happen in Live 6 also and other software. The original post was not Live 7 specific.

Anytime I've ever seen mouse/keyboard movements affect audio, it was because of IRQ sharing problems.

A quick check would be to see if your audio card is sharing an IRQ by going into system information, if it isn't then it's something else causing the problem.

b0unce wrote:

beatpoet wrote:Are you all running Windows ?

why would this problem only materialise in live 7 and not live 6 ?

If what you're suggesting is actually the problem, wouldn't it manifest in other audio programs too ?

Good point. It's Live 7 specific.

So it is 7, oh well.

Still windows specific, so might be worth a look.