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.

Ableton 9/Windows 10/Intel/ASIO4ALL/Focusrite/iConnectivity CRASH

aciddogaciddog
in Other

I have extremely frustrating problem. While setting up configuration on new laptop, Ableton crashes (goes off) anytime i'm choosing ASIO4ALL. Sometimes, when i connect one of 2 interfaces and then the second one, anything is fine beside the high CPU usage/latency. Is there any alternative for connecting both interfaces on Windows 10? I have never experienced similiar issues on my older laptop with Windows 7, with the same gear FOcusrite + iConnectivity. The use of second interface (iConnectivity) it's a must for processing signal in iPad. If there's anyone who have struggled with the same issue, or someone who have any idea how to set it up, let me know please.

Specs:

Ableton 9 the latest version on Windows 10
Intel Core i7-8750H (Intel HM370)
Sound Blaster™ Cinema 3
Focusrite 6i6 (1 generation)
iConnectivity MIDI2+
ASIO4ALL (the latest ver.)

DOn't tell me MAC is the only solution hhm

Thank You for taking the time to help me out!

MERRY CHRISTMAS / HAPPY HOLIDAYS nd HAPPY NEW YEAR!

k.

Comments

  • [Deleted User][Deleted User]

    @aciddog said:
    I have extremely frustrating problem. While setting up configuration on new laptop, Ableton crashes (goes off) anytime i'm choosing ASIO4ALL. Sometimes, when i connect one of 2 interfaces and then the second one, anything is fine beside the high CPU usage/latency. Is there any alternative for connecting both interfaces on Windows 10? I have never experienced similiar issues on my older laptop with Windows 7, with the same gear FOcusrite + iConnectivity. The use of second interface (iConnectivity) it's a must for processing signal in iPad. If there's anyone who have struggled with the same issue, or someone who have any idea how to set it up, let me know please.

    Specs:

    Ableton 9 the latest version on Windows 10
    Intel Core i7-8750H (Intel HM370)
    Sound Blaster™ Cinema 3
    Focusrite 6i6 (1 generation)
    iConnectivity MIDI2+
    ASIO4ALL (the latest ver.)

    DOn't tell me MAC is the only solution hhm

    Thank You for taking the time to help me out!

    MERRY CHRISTMAS / HAPPY HOLIDAYS nd HAPPY NEW YEAR!

    k.

    • Do not plug/unplug any interface while ASIO4ALL is active/Live is running. First connect everything then launch Live, select ASIO4ALL, set your preferred routing in ASIO4ALL.
    • It can also be sample rate mismatch. Make sure everything (Windows system audio, Focusrite, iCM, ASIO4ALL, Live) is set to 48kHz. As far as I remember both of those interfaces allow you to store 'default/init' state for standalone operation, as well the applications (Live, ASIO4ALL) can be launched into set sample rate. I'm suggesting 48kHz because I think Win10 defaults to that, so in theory there won't be any sample rate switching when you launch Live.

    Let me know if that helps.

  • jigglypuffjigglypuff

    I had similar problems too. Music making on Windows can be a frustrating experience. I'm not going to tell you that Mac is the only solution, because it isn't. The other option is the Hackintosh. If you spend most of your time making music on a PC then you owe it to yourself to convert to Hackintosh. It is SO much better in so many different ways. Now I don't spend any time fighting the operating system or ASIO4ALL. It just works.

    Cost me exactly $0, although I did donate to tonymacx86.com.

  • [Deleted User][Deleted User]

    @jigglypuff said:
    I had similar problems too. Music making on Windows can be a frustrating experience. I'm not going to tell you that Mac is the only solution, because it isn't. The other option is the Hackintosh. If you spend most of your time making music on a PC then you owe it to yourself to convert to Hackintosh. It is SO much better in so many different ways. Now I don't spend any time fighting the operating system or ASIO4ALL. It just works.

    Cost me exactly $0, although I did donate to tonymacx86.com.

    Hackintosh as a pain free solution?
    Tried it in the past and it was never pain free, or stable.

  • aciddogaciddog

    hi fellas, RECCCP man thank You for Your advice! after re-installing all drivers, setting up the sample rate like You suggested, the CPU usage dropped diametrically to 35%+. There's still some confusion, Ableton turnes of once after i gave this configuration few tests on different projects, but looks like different sample rate was the problem!

  • [Deleted User][Deleted User]

    @aciddog said:
    hi fellas, RECCCP man thank You for Your advice! after re-installing all drivers, setting up the sample rate like You suggested, the CPU usage dropped diametrically to 35%+. There's still some confusion, Ableton turnes of once after i gave this configuration few tests on different projects, but looks like different sample rate was the problem!

    Probably older projects were recalling their saved states at different sample rates. It's always good to keep everything at same sample rate/bit depth to avoid trouble and take off some load from DAW (converting internally).

Sign In or Register to comment.