Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Massive clicking with iConnectMIDI4+ in live rig

Hi there,

I've searched this forum and what feels like everywhere else, but I can't find a solution. I've also opened a ticket at iConnectivity but I'd like to ask you guys, because maybe someone has already experienced the same problem and fixed it. So thanks for reading this, I hope someone can help.

I'm experiencing massive clicking issues with the iConnectMIDI4+ in my live rig. Dave Smith Mopho x4 stereo out to Focusrite Scarlett 18i8 inputs 5 and 6 (switching inputs didn't help), DAW is Ableton Live 9.1.7 which is routing above mentioned inputs to the iConnect ports of my aggregated device sending to the iPad Air 2 and receiving audio passthrough in ports 19 and 20. These are then routed to the main outputs aka the speakers. Sound is coming and interaction with the apps (Audiobus, FLUX:FX, AUFX:Space, AUFX:PeakQ, Holderness Stereo Designer, ...) is working fine BUT i get this clicking sound: http://www6.zippyshare.com/v/qmH5RIVl/file.html. Raising latency, buffers, etc... doesn't help anything. I think it has to do something with the resampling in the aggregated device. But no matter which device i resample or if i switch it completely off, the problem is still there. Only if i raise the Hz on the Focusrite Scarlett, it gets worse. I have attached a PDF with all relevant settings.

If you have any idea what I could do to fix this, please let me know.

Thanks again and all the best

B

Comments

  • What do you have the clock source set to?

  • No matter if I set the clock to the ICM4+ or the 18i8, it's always the same :-(

  • Have you tried changing the order of the 4 + in the chain ? Try putting it first. Clock the 4+ from the 18i8 and set the 4 + to resample. This is how I have an ICM 2 + working with a motu ultralite. Any other way results in low level clicks. I'm on 10.6.8 though. Failing that.....could be bye bye aggregate device.

  • Typically, you should set the iCM device to take its clock from the Mac (port 3), and then set your Mac to be the clock source (include built-in input in the aggregate for example). Also then resample all the devices in the aggregate.

  • I made a mistake above. Actually I have the ICM 2 + set as clock master(as per iconnect's advice) and ultralite resampled. Click free.

    @ musicinclusive - intrigued as to your recommendation to clock from the mac. Not seen it suggested before. I tried on my system and get low level clicks every time.

  • edited January 2015

    Hmmm. I have both the iCM2+ and 4+ hooked up that way @zeropoint and there are no clicks. What are your "Number of buffered audio frames" and "Sync factor values" set to in the Audio info. pane?

    Also - have you seen this:

    http://iconnectivity.com/blog/controlling-latency

  • edited January 2015

    I was just about to drop that link Derek - so thanks!

    If you are not having a clocking issues as other members have suggested, then you may have a really low latency buffer that is causing it. With the lowest values, like 64 and 128, you may get click and pops due to dropouts in USB buffering. This interference will not record and should go away when raising the buffer value - which allows the computer to look ahead for a jump start on audio processing. You can use low values when recording and higher values when mixing and bouncing down.

    If you need deeper troubleshooting, feel free to create a support ticket here:
    www.iconnectivity.com/support
    That way the support team has all your details documented in order to get you up and running with optimal performance.

  • Hi Josh, guys are there any videos, tutorials, info for connecting PC, Mac and iPad via iCM4 all at the same time.

  • edited January 2015

    @MusicInclusive said:

    Typically, you should set the iCM device to take its clock from the Mac (port 3), and then set your Mac to be the clock source (include built-in input in the aggregate for example). Also then resample all the devices in the aggregate.

    iCM was (and is) set to port 3 and iCM was the clock source. As soon as I set the resample flags, I got the clicks. All devices are set to 44.1 kHz and 24 bit so is there any need of setting the resample flags at all? I didn't know about including the built-in input into the aggregate device, so I included it and set it as clock source. Usually when I don't set the resample flag, the audio goes to shit with all crackles after a few minutes. Let's see how long this lasts now. Right now it's built in input as clock source, the 18i8 and the iCM without resampling all at 44.1 kHz. No clicks since 10 mins. Please help me understand the resampling option: Let's say one of three devices in the aggregated device is 48kHz while the other two are 44.1kHz, which one needs the resampling flag? Does it depend on which one is the clock source?

    BTW: Thanks for your replies everyone, looks like we might be able to solve this. If it isn't solved already.

  • edited January 2015

    @bedhead You have to actually set the input as the clock source in the aggregate on the Mac. Not automatic. You can also only have all aggregate components at 44.1 or 48 or 96. So, that may be a source of your issues as well. You have to choose one. If you are recording from Audiobus, you can only reliably use 44.1 - whatever the interface, iCM or not - otherwise you'll get resampling issues and clicks. You may do fine with 24 bit however.

    If you are using apps standalone, outside of Audiobus, you can usually use 48/24 without issues.

  • @knewspeak - I have it in mind to try and put something together along those lines at some point.

  • @MusicInclusive said:

    @bedhead You have to actually set the input as the clock source in the aggregate on the Mac. Not automatic. You can also only have all aggregate components at 44.1 or 48 or 96. So, that may be a source of your issues as well. You have to choose one. If you are recording from Audiobus, you can only reliably use 44.1 - whatever the interface, iCM or not - otherwise you'll get resampling issues and clicks. You may do fine with 24 bit however.

    If you are using apps standalone, outside of Audiobus, you can usually use 48/24 without issues.

    Including the built in input into the aggregate device and setting it as clock source was new to me. All the tutorials I've read and watched advised to combine the audio interface and the iCM into an aggregated device and set the audio interface as clock source. About the resample option: If all devices in the aggregate have the same sample rate, why check the resample option for any of them?

  • this is strange....@ musicinclusive - the second link you have provided clearly shows the saffire interface being used for clock. the first link simply states that by default the mac is set master clock.....which isn't a stipulation. am i missing something?

    hey josh - i've also seen Al (?) from iconnect recommend elsewhere that the ICM2 + should be clock master....

    well i guess if it works for you and bedhead and others it works. but like i say i am click free with the way i have it set up but get clicks when i try to have the mac as master (could be down to my use of a legacy OS ?). thanks for the link about sync factor etc. i have both settings at 2.

  • In regards to my ticket at Focusrite I got the information that they do not support aggregate devices with their interfaces. This might be part of the problem. Or the problem itself. Disappointing.

  • edited March 2015

    If the developer's driver does not support aggregating, unfortunately you will not be able to pair it with other hardware - unless a driver update changes that.

    If you needs further troubleshooting assistance, feel free to create forum or support ticket:

    Support: http://www.iconnectivity.com/support

    Forum: http://www.iconnectivity.com/forum

    We can assist better there because we will get notifications easier.
    You can post this link as well, so you don't have to start from scratch.

    Cheers,

    -JS

Sign In or Register to comment.