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.

Tera Pro newbie

I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

«1

Comments

  • It doesn’t really work like that. I wish it did.

  • @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

  • @Gavinski said:

    @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

    What is this ‘reading’ you speak of? ;)

  • @Gavinski said:

    @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

    Subtractive Subtractive Synthesis? 😂

  • @Stuntman_mike said:

    @Gavinski said:

    @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

    Subtractive Subtractive Synthesis? 😂

    Ah hah! A double negative. Must mean a positive!

    Adding things by the process of elimination amiright

  • @Edward_Alexander said:

    @Stuntman_mike said:

    @Gavinski said:

    @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

    Subtractive Subtractive Synthesis? 😂

    Ah hah! A double negative. Must mean a positive!

    Adding things by the process of elimination amiright

    Yes!!!

  • It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

  • @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

  • wimwim
    edited March 2023

    @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Yeh, a very quick intro tutorial on first opening would go a long way toward helping people over that hump. It gets asked over and over.

    That part doesn't surprise me. What I don't get is why, once it's understood, it continues to bother some people so much. 🤷🏼‍♂️

  • @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Maybe a video from you explaining this would be in order?

  • ALBALB
    edited March 2023

    @wim said:

    @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Yeh, a very quick intro tutorial on first opening would go a long way toward helping people over that hump. It gets asked over and over.

    That part doesn't surprise me. What I don't get is why, once it's understood, it continues to bother some people so much. 🤷🏼‍♂️

    Answer: It simply isn't set up like other synths or even modular synths. And if you don't use it for awhile, you have to reacquaint yourself. It doesn't make it wrong, it's just different and takes ongoing familiarity.

  • @NeuM said:

    @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Maybe a video from you explaining this would be in order?

    Maybe yes... Or maybe you could make one? 🤔

  • @NeuM said:

    Maybe a video from you explaining this would be in order?

    I guess there are many views to be had from ppl who can't be bothered to read. Sarcasm aside, the manual is well written.

  • edited March 2023

    @Gavinski said:

    @NeuM said:

    @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Maybe a video from you explaining this would be in order?

    Maybe yes... Or maybe you could make one? 🤔

    It was a friendly suggestion, not marching orders. You're far better suited than me to create an instructional video and I made the suggestion because of the way you phrased your response. Obviously, if you have no interest in doing so it makes no difference to me.

  • @NeuM said:

    @Gavinski said:

    @NeuM said:

    @Gavinski said:

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    Why that's such a mind f*ck beyond the first head scratch is beyond me. Sure it's "backward" from how people are used to approaching things, but it isn't a momentous thing to understand and incorporate into a workflow once you do.

    Yep, but unless ppl read the manual they're unlikely to understand that. I don't think there's a detailed tutorial vid is there? Maybe I'm wrong though. But most people just opening the app and not looking at the help / manual will be a little lost.

    Maybe a video from you explaining this would be in order?

    Maybe yes... Or maybe you could make one? 🤔

    It was a friendly suggestion, not marching orders. You're far better suited than me to create an instructional video and I made the suggestion because of the way you phrased your response. Obviously, if you have no interest in doing so it makes no difference to me.

    Sorry Neu if I came across as sarky, didn't mean that really.

    But there was a little bit of frustration coming out there about the fact that there are just so many deep apps, and that making vids on deep apps takes a lot of time.

    Your comment was terse but well meant.

    I'd love to get around to making a detailed Tera Pro vid but given the huge flow of recent apps, and the way that ios music YouTube viewers generally only have big interest in new apps, it's a really hard decision to put the time into older apps. And unfortunately, in this space, it seems that for viewers, older apps are pretty much anything more than a few days old 😂.

    One of my best videos, and yet one that has the lowest views, is one of the first ones that I made, on Stria. An absolute masterpiece app. It took me about a week of full time work to understand that app and make that vid. Admittedly, I knew a lot less then than I do now.

    Same goes for my Aparillo vid.

    If devs want detailed vids on very complex apps, they can hit me up for a sponsored video. Or they can donate to my PayPal. Until now, after making hundreds of vids, I think only three devs have ever done that.

    If viewers want detailed vids on complex apps they can support me on PayPal. Very very few do. My PayPal donations over the past year amount to a few hundred bucks max.

    The amount of time I put into my channel is madness in comparison to the amount earned, or even considering future earnings.

    In my early days of YouTubing I saw a niche for vids on apps that were so complicated that most youtubers would not take the time to make vids on them. I thought that by filling that niche I might have a chance at making a living from youtube.

    But I found after a while that the amount of time I needed to invest in making vids on these was just too much. It affected my personal life, my finances, my happiness, even my eyes. And YouTube wasn't paying shit, and still isn't paying shit after almost 3 years of doing this pretty hardcore.

    Initially I thought that people would appreciate these detailed vids so much they would support me on PayPal etc, knowing that YouTube pays so little. That's not the way it panned out, apart from a few generous people who did appreciate enough that they supported. But it still didn't make up for the time invested, not remotely.

    So now I find I have to strike a better balance between my life and my video making. Frankly, that mostly involves not making walkthroughs on complex apps. It's a pity, but that's the reality of the situation. I also find that, given that situation, I prefer to spend my time on demos, as these are a result of play, and I enjoy making them more than tutorials.

    I'll probably start something like a patreon at some point, but that also comes with its own baggage. Let's see. This is probably a much longer answer than you expected or wanted - sorry brother - but once I started, it just flowed. If this seems like too much, forgive me. It's the frustration of several years of hard work that just aren't paying off, even though I love the 'job' 🤷‍♂️

  • I feel like the confusion comes with INIT or lack of a true INIT. Press + to create a basic patch which has to have a name. Most users are used to building synths ground up in modular environments, one module at a time. This app acts like a semi modular synth as far as requiring users to start with a patch instead of blank workspace, perhaps that is where the confusion starts for some. My observation may be wrong.

  • edited March 2023

    Deleted

  • This one always refreshes my memory at around the 4:30 mark.

  • edited March 2023

    This statement in the manual confused me: “Tap on a free space in the modules pane and drag left/right to reveal modules not visible.” I initially thought it meant a drop-down would show modules to choose from that I navigate by dragging left or right 🤭🤦‍♂️🤷🏽‍♂️

  • +1 for reading the Tera Pro manual… it is comprehensive and well-written and a necessity for a synth of this complexity.

  • In 2017 @Virsyn wrote:

    ok, really deep manuals are victims of the app economy - highly specialised apps like Bark {Filter} just don't have

    the impact to make this feasible. We put the basics into the help pages, but for more you have to ask us.

    Impact means revenue. It’s great to see that @Virsyn (Harry Gohs on the App Store) yielded to the requests for manuals
    After all. AudioLayer and Tera Pro have pretty decent manuals embedded in the apps as a pop up on the Help/“?” Page.
    AudioLayer is 52 pages and Tera Pro is 66 pages.

    I think it was clear that everyone asking “for more” was not scalable.

    I recall many commenters complaining that they would never buy another @Virsyn app and this was before I bought one but after I did it has become an obsession of mine to collect the whole set… I have three to left to add: the 2 Vocoders and iSyn Poly.

  • @Gavinski said:

    @Ailerom said:
    I have plenty of questions but the most pressing one is how to load a new module and put it where I want it.

    You must read the manual - basically this synth works backwards

    Just read the manual, too hard to explain! But not hard once you get the hang of it. You basically click on empty slots, then sources show up and you choose which sources you want. Spend an hour, read the manual, you won't regret it

    This is rare for me but for once I did. And I still don't get it.

  • wimwim
    edited March 2023

    Maybe if you let us know what you understand about “Select a module as the input to something like an amp, mixer, or filter. The module will then be added?”, we can start to clear this up.

  • @Stuntman_mike said:
    Press + to create a basic patch which has to have a name.

    Thank you. Didn't think of or realise that would create a simple starter patch.

    @hacked_to_pieces said:
    This one always refreshes my memory at around the 4:30 mark.

    Will watch this one and hopefully it helps. Thanks.

    @wim said:
    It really isn't hard to explain. You add modules by setting them as an input to something like an amp or filter.

    This is really helpful and opened the window of understanding quite a lot. It seems now though that there is a limit to what routing is possible. Either that or it will just take some exploration time to see what can be added and where. It seems a little like a puzzle synth. e.g. how can I add that there without losing this.

  • wimwim
    edited March 2023

    Or maybe just start with the default new patch by opening the presets and using the + button. You'll get three oscillators, a mixer, a filter, and an amp. See how the mixer shows OSC 1, 2, and 3 connected. Try tapping one and changing the input to "(open)". Notice how that oscillator disappears? Now, select another type of oscillator, and note how that oscillator appears.

    Notice how the input to Filter 1 is the Mixer, and the Filter is the input to the amp. That's your signal flow. I wouldn't change that until you start to grok the way things are added and removed.

    A couple of other basics:

    • to expand a module that's showing, tap its title. That will reveal additional settings for the module.
    • the orange buttons at the bottom of the modules are what controls modulation for whatever is above them. For instance, oscillator 1 in in the default patch, LFO1 is hooked up to the pitch. The slider determines how much the LFO affects the pitch.
    • To change a modulation source, tap the button and select another.
    • To expand a modulation source to see and adjust it, long-press the button.

    I hope that helps.

  • @wim said:
    Or maybe just start ...........
    .......... I hope that helps.

    That is awesome. Thanks so much.

    Also, it's been a long time since I grokked anything. I think Edition 11 might have been the earliest 2000AD I could find.

  • @Ailerom said:
    This is really helpful and opened the window of understanding quite a lot. It seems now though that there is a limit to what routing is possible. Either that or it will just take some exploration time to see what can be added and where. It seems a little like a puzzle synth. e.g. how can I add that there without losing this.

    Yeh, complex routings are possible, but it gets mind bending pretty quick. You can do all kinds of things like serial and parallel filtering, fm, , sub mixes and other stuff I've not explored. I haven't done anything beyond just putting together basic subtractive synths and a little FM.

    TBH, I find my way around Nambu a little more readily, but have been getting better sounds out of Tera Pro. Both are fun to get lost in when not trying to actually create some music.

  • @wim said:
    TBH, I find my way around Nambu a little more readily,

    For sure. Nambu makes sense to me and I find my way around pretty easily. TPro is just a different paradigm for me.

  • Just to clarify one point that hasn't been mentioned here. Tera Pro is a semi-modular synth. The list of sources you see when tapping on a green input or orange modulator lozenge is the list of all the modules available. Thus, 3 oscs, 4 LFOs, etc. It's like you have a large hardware modular system and you're patching those specific modules. The "rack" on the screen shows a view some of the modules in the patch. You can long press on a modulator lozenge to view it.

    This means that you cannot add modules to a patch; you just connect the existing modules. And there's no where when you connect a module. TP will insert it in the view wherever it chooses.

  • edited March 2023

    @uncledave I was thinking the same (which clearly, it is), but it is framed as a modular synth:

    “128 voice Modular polyphonic Synthesiser” “Modular Analog/Digital Polysynth” “TERA PRO - THE MODULAR POLYSYNTH” “Modular polyphonic synthesizer with free wiring between modules.”

    The word “semi” is not used anywhere in the description or manual.

    I was thinking “semi-modular” as a way to describe Tera Pro to those who were confused by the architecture, but couldn’t find “semi” anywhere. I do feel the semantics is confusing some people. It is definitely an amazing-sounding synth with a lot of capabilities!

Sign In or Register to comment.