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.

Unfiltered Audio Bass Mint iOS Public Beta

124»

Comments

  • Hi, @trickyflemming. Maybe I found one issue on the TestFlight-Bass-Mint v1.2.0 (1.2.0).

    Disclaimer/Excuse/Cop-out:
    I have no idea whether the after-mentioned issue is caused by the ‘Juce 6 updating to Juce 8’, or my iPadOS not being up to date, the former or the latter. (Or, maybe the after-mentioned issue is unrelated to Juce or iPadOS.)

    [This report is a bit long, so I use the Spoiler feature below.]

    *
    Issue: The AppleAppStore-Bass-Mint and the TestFlight-Bass-Mint each behave differently when selecting a preset.

    -In my environment, there is something unnatural about the behavior/phenomenon when a preset is selected/loaded for the TestFlight-Bass-Mint. In other words, it’s hard to select/load a preset.
    -On the other hand, there is no problem with the behavior/phenomenon when a preset is selected/loaded for the AppleAppStore-Bass-Mint. It works smoothly.

    Note:
    -In the following procedures, you (= tester) operate iPad (or iPhone?) with your finger. You do not use a mouse or apple pencil.
    -I think the following procedures can be applied to both standalone-TestFlight-Bass-Mint and AUv3-TestFlight-Bass-Mint. In other words, the same problem occurs in both standalone and AUv3, in my environment.

    *
    Procedures to select/load a preset on TestFlight-Bass-Mint:

    Failure procedure #A:
    Load TestFlight-Bass-Mint.
    Tap the current preset name "Default" and release your finger from the screen.
    Tap the "Factory Presets", and release your finger from the screen.
    Tap any one of the 7 factory preset folders(?), and release your finger from the screen.
    The 7 factory preset folders disappear(?) from the screen. [I think this behavior of the TestFlight-Bass-Mint is an issue.]

    Failure procedure #B:
    Load TestFlight-Bass-Mint.
    Tap the current preset name "Default" and release your finger from the screen.
    Tap the "Factory Presets" and hold your finger on the screen. And slide your finger to any one of the 7 factory preset folders(?), and release your finger from the screen.
    The 7 factory preset folders disappear(?) from the screen. [I think this behavior of the TestFlight-Bass-Mint is an issue.]

    Failure procedure #C:
    Load TestFlight-Bass-Mint.
    Tap the current preset name "Default" and release your finger from the screen.
    Tap the "Factory Presets" and hold your finger on the screen. And slide your finger to any one of the seven factory preset folders(?). And slide your finger to any preset in the preset list, and release your finger from the screen.
    The preset list disappears from the screen. And the selected preset is not loaded. [I think this behavior of the TestFlight-Bass-Mint is an issue.]

    *
    Success procedure #1:
    Load TestFlight-Bass-Mint.
    Tap the current preset name "Default" and release your finger from the screen.
    Tap the "Factory Presets" and hold your finger on the screen. And slide your finger to any one of the seven factory preset folders(?), and release your finger from the screen.
    Tap any preset from the preset list, and release your finger from the screen.
    The selected preset is loaded as is. [So, this procedure has no issue.]

    *
    -In other words, on TestFlight-Bass-Mint v1.2.0 (1.2.0), there is only 1 procedure out of 4 that allows testers to select/load a preset without problems.
    -On the other hand, AppleAppStore-Bass-Mint v1.1.5 has no issue on selecting/loading a preset. This is because the above-mentioned tapping, holding, sliding, and releasing operations from users side are all acceptable(?) by AppleAppStore-Bass-Mint v1.1.5 side.

    *
    My test environment:
    TestFlight-Bass-Mint / the latest v1.2.0 (1.2.0)
    iPadOS v16.7.2 (Note: The latest version on my device should be iPadOS v17.7.5. So I’m not an ideal tester. I’m sorry.)
    iPadPro 10.5 inch (2017)
    AUM / the latest v1.4.7 (352)

  • Excellent! Thank you for the report. Yes I thought it was difficult to change presets and was wondering if we had previously released it in such a state. Okay I'll look into seeing what changed on the pop-up menu code and try to make it less horrible.

  • @trickyflemming
    I had tried joining the beta and was told the beta wasn't accepting any new testers and
    then to my surprise there it was in my TestFlight so I downloaded it (as you do) and started testing.

    On my ancient Air 3 iOS 17.6.1 it crashed on first instantiation.
    The screen went black and when I shut it down a report was generated
    however I didn't send the report. (sorry about that )
    It took three times to get it running standalone.
    I run all apps standalone first before loading them into a DAW.
    Still that was the only crash I experienced, everything else seems really stable.

    The sound on the other hand is wicked.
    I tried it on regular stuff and then I tried it on my Eurorack rig on self oscillating filters.
    I'm using the self oscillating filters for bass, kick drums and snrs.
    Bass Mint sounds fab on them.

  • @trickyflemming @amusesmile
    Hi. I found one issue(?) on the TestFlight-Bass-Mint v1.2.0 (1.2.0).
    [I use the Spoiler feature below.]

    Issue(?):
    In my environment, while I control a certain knob (with my finger) with TOOLTIPS feature “enabled” in TestFlight-Bass-Mint v1.2.0 (1.2.0), the knob movement/animation is not smooth. (As if the frame rate is reduced.)
    On the other hand, AppleAppStore-Bass-Mint v1.1.5 does not have the same issue.

    Notes:
    -This issue occurs most clearly with SOFTEN knob.
    -The same or similar issue occurs with CUTOFF, SHELF and CLARITY knobs, but the movement/animation of these 3 knobs is smoother than the above-mentioned SOFTEN knob.
    -STRENGTH and OUT GAIN knobs do not have this issue. In other words, the movement/animation of these 2 knobs is smooth.

    -The same issue occurs under the all four of the conditions(?) below.
    Standalone(Vertical/Portrait)-TestFlight-Bass-Mint v1.2.0 (1.2.0)
    Standalone(Horizontal/Landscape)-TestFlight-Bass-Mint v1.2.0 (1.2.0)
    AUv3(Vertical/Portrait)-TestFlight-Bass-Mint v1.2.0 (1.2.0)
    AUv3(Horizontal/Landscape)-TestFlight-Bass-Mint v1.2.0 (1.2.0)

    -The same issue does not occur under the all four of the conditions below.
    Standalone(Vertical/Portrait)-AppleAppStore-Bass-Mint v1.1.5
    Standalone(Horizontal/Landscape)-AppleAppStore-Bass-Mint v1.1.5
    AUv3(Vertical/Portrait)-AppleAppStore-Bass-Mint v1.1.5
    AUv3(Horizontal/Landscape)-AppleAppStore-Bass-Mint v1.1.5

    *
    My test environment:
    TestFlight-Bass-Mint / the latest v1.2.0 (1.2.0)
    iPadOS v16.7.2 (Note: The latest version on my device should be iPadOS v17.7.5. So I’m not an ideal tester. I’m sorry.)
    iPadPro 10.5 inch (2017)
    AUM / the latest v1.4.7 (352)

  • @trickyflemming @amusesmile
    Additional Report:
    If problematic knob A and non-problematic knob B are operated at the same time, the problem of knob A will occur for both of the two knobs.

    Note: The order in which the two knobs are held changes the test result.

    Example:
    -First, the SOFTEN knob is held down. Then the OUT GAIN knob is held down. In this case, the movements/animations of the two knobs will not be smooth. (In other words, the aforementioned issue with the SOFTEN knob also occurs with the OUT GAIN knob.)

    On the other hand,

    -First, the OUT GAIN knob is held down. Then the SOFTEN is held down. In this case, the movements/animations of these 2 knobs are smooth.

  • @trickyflemming @amusesmile
    Additional Report:
    While the problematic knob is operated, the movement/animation of VISUALIZER is (also) not smooth.

  • Excellent testing so far, @cramdog! I think we'll need to move back to JUCE 6 since it seems there are some foundational issues that have been introduced. I'll post a new build on Tuesday.

  • Okay, 1.2.0 build 2 is now up on Testflight! Thanks to @cramdog's excellent testing and detailed reports, we've reverted to JUCE 6. This means the popup menus are massively improved and now behave like they used to. The import/export system still appears to work, but please try it out if you haven't. Also, please let me know about iOS 18 stability. I am unable to test on iOS 18, as I can't update my iPad without updating XCode, and updating XCode apparently breaks JUCE 6 at the moment.

  • edited February 2025

    @trickyflemming @amusesmile
    Hi. I tested and confirmed that all the issues I reported on this thread about TestFlight Bass Mint v1.2.0 (1.2.0) was fixed in TestFlight Bass Mint v1.2.0 (2). Thanks.

    *
    The following two issues may not be serious, but I report them just in case.
    [I use the Spoiler feature below.]

    *
    Issue #1:
    If a user preset "New Preset" is overwritten with "New Preset.uap" by ‘Import Presets...’ feature, a new "New%20Preset" is made in User Presets list/folder besides the aforementioned user preset "New Preset".

    -I don't think this problem (= same or similar problem) occurs when importing a uap file with a name other than "New Preset.uap". But I may be missing something on this issue.
    -If a user preset "New Preset" is overwritten with a zip file including "New Preset.uap" by ‘Import Presets...’ feature, the above-mentioned issue of the "New%20Preset" being made in User Presets list/folder does not occur.
    -I confirmed that this issue occurs with Standalone and AUv3 TestFlight Bass Mint v1.2.0 (2).

    *
    Issue #2:
    The sound output from Bass Mint is different between A and B below.

    A: When both “SOLO BASS” and “BYPASS” are enabled.
    B: When only BYPASS is enabled.

    -In this case, I guess the correct behavior of Bass Mint is that A and B both output the same BYPASSed sound. But I may be mistaken about something. So, if the different output sounds of A and B are the correct behavior of Bass Mint as you intended, I’m sorry.

    *
    My test environment:
    TestFlight Bass Mint v1.2.0 (2)
    iPadOS v16.7.2 (Note: The latest version on my device should be iPadOS v17.7.5. So I’m not an ideal tester. I’m sorry.)
    iPadPro 10.5 inch (2017)
    AUM / the latest v1.4.7 (352)

  • I am on iPad OS 18.2 and I have found no issues with stability so far.

    I have used the Bass Mint in Cubasis and Auria Pro.
    I have been using multiple instances in the same project on bass tracks and on vocal tracks.

    it is a very useful app.

  • edited February 2025

    Additional report:
    -If the aforementioned step/procedure (on Issue #1) in my previous post above is repeated, the User Preset will increase(?) as follows.

    New%20Preset
    New%2520Preset
    New%252520Preset

    -If a user preset name includes "%", a new user preset is also made by the aforementioned procedure.

    [EDIT]
    Sorry!! My aforementioned explanation may be inaccurate.
    I mistakenly thought that the default user preset name "New Preset" on user preset save was “special”. However, what is really special is SPACE. If the preset name includes SPACE, I guess the SPACE is replaced with "%20" in the aforementioned procedure. (Note: My explanation itself may be wrong, but I’m sure @trickyflemming and @amusesmile will understand my point correctly.)
    [/EDIT]

    [EDIT 2]
    On second thought, maybe I should have reported/explained as follows.
    -If a user preset name includes certain characters(?), importing a uap file exported from the user preset may add one extra unwanted user preset. And the name of this extra user preset includes codes(?) converted(?) from the characters(?) included in the original “user preset / uap file” name.
    [/EDIT 2]

  • @cramdog said:
    Additional report:
    -If the aforementioned step/procedure (on Issue #1) in my previous post above is repeated, the User Preset will increase(?) as follows.

    New%20Preset
    New%2520Preset
    New%252520Preset

    -If a user preset name includes "%", a new user preset is also made by the aforementioned procedure.

    [EDIT]
    Sorry!! My aforementioned explanation may be inaccurate.
    I mistakenly thought that the default user preset name "New Preset" on user preset save was “special”. However, what is really special is SPACE. If the preset name includes SPACE, I guess the SPACE is replaced with "%20" in the aforementioned procedure. (Note: My explanation itself may be wrong, but I’m sure @trickyflemming and @amusesmile will understand my point correctly.)
    [/EDIT]

    [EDIT 2]
    On second thought, maybe I should have reported/explained as follows.
    -If a user preset name includes certain characters(?), importing a uap file exported from the user preset may add one extra unwanted user preset. And the name of this extra user preset includes codes(?) converted(?) from the characters(?) included in the original “user preset / uap file” name.
    [/EDIT 2]

    @trickyflemming @amusesmile
    Issue(s):
    The following 4 versions have the same(?) issue(s) as quoted above.
    -I have only done very rough testing, so I may have missed something.
    -Sorry if these issues are in the process of being fixed.

    TestFlight lo-fi-af v1.2.0 (1.2.0)
    TestFlight Needlepoint v1.1.0 (1.1.0)
    TestFlight Silo v1.2.0 (1.2.0)
    TestFlight Tails v1.2.0 (1.2.0)

  • edited February 2025

    @trickyflemming @amusesmile
    I have a question.
    Is JUCE 8 used for the following four TestFlight apps?
    -The reason I ask this question is that prior information might be helpful when looking for issues related JUCE 8, such as pop-up menus (≒ preset-selection, TOOLTIPS, knob-animation).

    TestFlight lo-fi-af v1.2.0 (1.2.0)
    TestFlight Needlepoint v1.1.0 (1.1.0)
    TestFlight Silo v1.2.0 (1.2.0)
    TestFlight Tails v1.2.0 (1.2.0)

    (EDIT)
    Needless to say, if information about JUCE involves something like confidentiality(?) or special features of Unfiltered Audio apps or etc., you do not need to answer my question.

  • Thanks! I'm working on fixing the New Preset thing. Everything is back on JUCE 6 as JUCE 8 provided too many touch issues.

  • @cramdog Thanks again for the report. I was able to isolate the %20 issue. The file system uses URLs. When converting from a URL address to a JUCE file, I needed to trim off the escape characters right before the file is written. I'm going to upload new builds of everything momentarily.

  • edited March 2025

    @trickyflemming said:
    @cramdog Thanks again for the report. I was able to isolate the %20 issue. The file system uses URLs. When converting from a URL address to a JUCE file, I needed to trim off the escape characters right before the file is written. I'm going to upload new builds of everything momentarily.

    @trickyflemming
    I have confirmed that the %20 issue was fixed and does not happen in AUv3 and Standalone TestFlight Bass Mint v1.2.0 (3) in my environment. Thanks.

    *
    By the way, is the behavior of Bass mint written in the quote below (from the Spoiler on my post above on this thread) an issue? Or is it on purpose?
    [Note: I’m interested in this topic because I’m a beginner interested in a logic of routing order(?) of effects.]

    Issue #2:
    The sound output from Bass Mint is different between A and B below.

    A: When both “SOLO BASS” and “BYPASS” are enabled.
    B: When only BYPASS is enabled.

    -In this case, I guess the correct behavior of Bass Mint is that A and B both output the same BYPASSed sound. But I may be mistaken about something. So, if the different output sounds of A and B are the correct behavior of Bass Mint as you intended, I’m sorry.

  • edited March 2025

    I have confirmed that the %20 issues were fixed and do not happen in AUv3 and Standalone following apps. Thanks.

    TestFlight Needlepoint v1.1.0 (2)
    TestFlight Tails v1.2.0 (2)
    TestFlight Silo v1.2.0 (2)
    TestFlight lo-fi-af v1.2.0 (2)

    *
    By the way, the improvement in typing logic of TestFlight Tails v1.2.0 (2) is nice. Thanks.

  • edited March 2025

    [Note: This report of mine is not a request or suggestion for fixes. I’m just reporting behaviors of Beta apps in my environment as a precaution(?).]

    I think the following are user errors, not issues at all. But I report them below just in case.

    -It is possible to import user presets from TestFlight AUv3 Tails v1.2.0 (2) and TestFlight AUv3 Needlepoint v1.1.0 (2) into TestFlight AUv3 lo-fi-af v1.2.0 (2), in my test environment.
    (I don’t think this is an issue. So I didn’t do the same test with other Unfiltered Audio’s TestFlight apps’ combinations.)

    -It is possible to export a user preset from TestFlight AUv3 Tails v1.2.0 (2) when there is no user preset. And the exported zip file cannot be unzipped, in my test environment.
    (I don’t think this is an issue. So I didn’t do the same test with other Unfiltered Audio’s TestFlight apps.)

  • edited March 2025

    @trickyflemming @amusesmile
    Sorry, I forgot to write the names of the two recipients(?) of my two reports above.

  • @cramdog said:
    By the way, is the behavior of Bass mint written in the quote below (from the Spoiler on my post above on this thread) an issue? Or is it on purpose?
    [Note: I’m interested in this topic because I’m a beginner interested in a logic of routing order(?) of effects.]

    Issue #2:
    The sound output from Bass Mint is different between A and B below.

    A: When both “SOLO BASS” and “BYPASS” are enabled.
    B: When only BYPASS is enabled.

    -In this case, I guess the correct behavior of Bass Mint is that A and B both output the same BYPASSed sound. But I may be mistaken about something. So, if the different output sounds of A and B are the correct behavior of Bass Mint as you intended, I’m sorry.

    Hey! I finally double checked the code on this one. I'm spinning way too many plates at the moment:

    if(bypass && solo)
    {
        dryWet.set(1.0);
        preventBassProcessing = true;
        //set no processing
    }
    else if(bypass)
    {
        dryWet.set(0.0);
    }
    else
    {
        dryWet.set(1.0);
    }
    

    So this is working as expected and was requested by some pro mixers. The general idea is that you can still solo the dry bass band in bypass mode. That way you can make sure that the saturation or chosen effect is having an overall positive effect on the bands and not adding anything unwanted.

  • edited March 2025

    @trickyflemming
    Hi! Thanks for your reply!

    Oh no! You didn’t/don’t need to copy/paste the “if - else if - else” source code of Bass Mint for me! Why did you do it?!
    ⬇️

    @cramdog said:
    [Note: I’m interested in this topic because I’m a beginner interested in a logic of routing order(?) of effects.]

    ⬇️
    …Perhaps I may have used the wrong word, maybe I should have written ‘reason’ or ‘background’ instead of “logic”… In that case, my apologies! (Having said that, thanks!)

    *

    ,

    So this is working as expected and was requested by some pro mixers. The general idea is that you can still solo the dry bass band in bypass mode. That way you can make sure that the saturation or chosen effect is having an overall positive effect on the bands and not adding anything unwanted.

    Yes! I've wanted to know this (kind of) information for quite some time! But I was/am lazy so I couldn’t get a good opportunity/timing to ask you the question. Thank you so much!

Sign In or Register to comment.