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.

Issue moving project from iPad to Mac using TAL U-No-LX

cyberheatercyberheater
edited June 2023 in Logic Pro

I can start a project on the mac using a single instance of TAL UNO. Change some parameters on the synth and then share that to my iPad. When I load the project the changes are there.
If I change any of the parameters on the synth and share that back to the mac the parameters aren’t changed at all. Worse, it loads the TAL as init.

I hope that all makes sense.

Anyway to resolve this? Can anyone also confirm the behaviour.

EDIT: Have just tried it with Zeeon and that works okay. I think it’s a TAL issue.
EDIT2. I have requested to join the TAL facebook group and will ask the question there.

Comments

  • cyberheatercyberheater

    After doing some more investigation. It appears even if you select a preset within TAL on the iPad. That preset information doesn't get carried over to the Mac version. I am sad.

  • cyberheatercyberheater

    I’ve contacted TAL support. Will let you know what they say.

  • MisplacedDevelopmentMisplacedDevelopment

    I expect that the issue you are seeing is what I described below. Compatibility is going to be pot-luck, and unless Apple works some magic for mapping app state then some apps will stay incompatible unless developers do some amount of work to make it happen.

    @MisplacedDevelopment said:
    Using MTS as my reference point as it already supports bi-directional projects - you can move a project between platforms if the plugin developer chose the same plugin ID for the plugin on iOS and Mac. There are some pretty big devs that did not do this. This will get you past the “missing plugin” errors, saving you having to reload each missing plugin. If you get that far then there is the question as to whether the plugin state is restored correctly. That part seems to rely on whether there is a compatibility between the data state of the source and destination plugins. If the data format has changed because one plugin is newer or whatever then the state may not restore correctly on the other side.

    The developer of MTS added a workaround to his DAW to let you choose an alternative plugin to be used if a particular slot was “missing”. This means you can select plugin x on iOS and have the project load with plugin x on the destination, even if the plugin IDs are different. Hopefully Apple will come up with something as good or maybe even better, but really it is a job for the plugin developers to solve (like IKM did with MixBox).

    Moog is an example of a bigger developer that got all of this right. My projects containing their apps work both ways with all state saved without any intervention.

  • cyberheatercyberheater

    So Patrick (dev) has responded. He says it’s because the iPad is using AUv3 but Mac is using AUv2. He’s looking into it.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025