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.

Bm3 keeps crashing!

Daath7Daath7
in General App Discussion

I'm having a lot of problems with Beat Maker3 crashing. Every time I try to create something it crashes. Not just apps but beat slicing also. I'm on an iPad Pro 9.7 so I should be good. Anyone else having this issue?

«1

Comments

  • mireko_2mireko_2

    first thing after installing a big new app if your having problems, try a hard reset.
    hold the power and home buttons in until the ipad resets (this is only a power cycle, won't loose data or programs).

  • AudioGusAudioGus

    Oh yah it crashes like super crazy! Best app ever though!

  • ElGregoLocoElGregoLoco

    As my man @Audiogus said...

    If you fix the crashes and cracklings in BM3, it would be the best music app ever... And then what would we be talking about here man. Lol.

  • OscarSouthOscarSouth
    edited July 2017

    I don't know what you guys are doing to this app! I've been using it every day on my Mini4 and haven't had any crashes at all. Had MIDI connection problems one time which a restart fixed.

    I'm mainly using 2/3 slicer banks to create quick little beats (to keep life interesting!) then hosting 3/4 extra AU's which I'm practising mundane performance shit with through a keyboard and pad controller (development period so raising my game in 'live sequencing').

    As the hours tick away I start drifting to the sequencer for variation..

    I've run it for 6+ hour sessions like this with no crashing. Feels solid, for this use case at least.

  • [Deleted User][Deleted User]

    @OscarSouth said:
    I don't know what you guys are doing to this app! I've been using it every day on my Mini4 and haven't had any crashes at all. Had MIDI connection problems one time which a restaurant fixed.

    I'm mainly using 2/3 slicer banks to create quick little beats (to keep life interesting!) then hosting 3/4 extra AU's which I'm practising mundane performance shit with through a keyboard and pad controller (development period so raising my game in 'live sequencing').

    As the hours tick away I start drifting to the sequencer for variation..

    I've run it for 6+ hour sessions like this with no crashing. Feels solid, for this use case at least.

    Same here, apart from the weird saving glitches I haven't had a single crash (Air 2).

  • OscarSouthOscarSouth

    **edit (since quoted): 'restart' was auto corrected to 'restaurant'

  • ElGregoLocoElGregoLoco

    I'm considering more and more trying to fully reinitialize my iPad Air2 and reinstall everything properly... It will be a long long process, and I'm not even sure I have enough storage left on my old computer to save all my current projects/data which are currently on the iPad...
    I'm still trying to avoid such a painful process, but if might be the only way to ensure that I have the best configuration to run BM3...
    First time this happens to me since my first iPad...

  • gonekrazy3000gonekrazy3000

    @ElGregoLoco said:
    I'm considering more and more trying to fully reinitialize my iPad Air2 and reinstall everything properly... It will be a long long process, and I'm not even sure I have enough storage left on my old computer to save all my current projects/data which are currently on the iPad...
    I'm still trying to avoid such a painful process, but if might be the only way to ensure that I have the best configuration to run BM3...
    First time this happens to me since my first iPad...

    The air2 is a lot more stable than all the pros and even the 2017 iPad. Seems like there is something wrong with the A9 processor and above when it comes to stability with music apps. A reinitialize might actually help with your air2. I restored from a backup when I installed iOS 10.3 and it's been working beautifully.

  • LucidMusicIncLucidMusicInc
    edited July 2017

    10 (or more) things in no order that I find can reduce crashing

    1. Set the latency settings above 512
    2. Use Audiobus instead of IAA
    3. Use the timeline over scenes
    4. Keep saving and copying (BM3 makes a lot of new samples when recording and processing) when you save those get written to disk instead of staying in RAM
    5. Resample midi patterns to audio (easier to play an audio clip rather than a synthesiser or patern with short audio clips triggered)
    6. Tempo, try working at half time
    7. FX, obviously too many FX will eat up too much memory
    8. Polyphony, keep it below 16, 8 to be safe
    9. Converting stereo samples to mono and minding the EQ, excessively loud audio with too much mid and low can crash the app as well as damage your headphones/speakers/hearing
    10. Turn off unneccessay processes like other apps, blutooth m, wifi, iCloud sharing etc etc etc
    11. IOS 10.3 is probably the most stable iOS
    12. You need several gigabytes of available storage in reserve for optimal performance
    13. Certain plugins/third party apps can't be resample effectively in BM3, and will need to be resampled with another app like AudioShare (Machine is one example, Sampletank another)
  • echooperaechoopera

    I'm on a new 10.5 and have made at least 5 tracks in BM3 with no problems. Haven't really experienced any crashes or production stopping scenarios but the occasional glitches.

    What are you guys doing to get all the crashes? I've been routing Midi to my external synths and using multiple Scenes. I'm never going back to the old ways of doing things B)

    Looking forward to new update though.

  • mathieugarciamathieugarcia

    Keep an eye for update 3.0.1, we fixed plenty of bugs.
    Here are the update notes: https://intua.net/forums/discussion/4856/beatmaker-3-0-1-current-status-and-change-log

    Cheers!

  • echooperaechoopera

    @mathieugarcia said:
    Keep an eye for update 3.0.1, we fixed plenty of bugs.
    Here are the update notes: https://intua.net/forums/discussion/4856/beatmaker-3-0-1-current-status-and-change-log

    Cheers!

    Thanks for a stellar release and follow through. Making great software is hard. We're here to support you with crazy beats :#

    We truly appreciate all the effort which went into BM3 and will go in to evolving it.

    Never lose sight of this.

  • AudioGusAudioGus
    edited July 2017

    @echoopera said:
    I'm on a new 10.5 and have made at least 5 tracks in BM3 with no problems. Haven't really experienced any crashes or production stopping scenarios but the occasional glitches.

    What are you guys doing to get all the crashes? I've been routing Midi to my external synths and using multiple Scenes. I'm never going back to the old ways of doing things B)

    Looking forward to new update though.

    For me most of the crashes have been while using the slicer on wavs of around five minutes or so in length while manipulating about 80 or so slices. Because of this I tend to do most of the editing in an external daw to line things up nicely for a quick grid based 'slice to pads' operation in BM3. Functionaly BM3 would be more than capable without the crashes.

  • echooperaechoopera

    Oh. Which iPad and size are you on? Also how much space do you have left? I know audio apps become notoriously unstable when there isn't enough space left on device.

  • AudioGusAudioGus

    @echoopera said:
    Oh. Which iPad and size are you on? Also how much space do you have left? I know audio apps become notoriously unstable when there isn't enough space left on device.

    2017 ipad, 128gigs with about 50gigs free.

  • echooperaechoopera

    Cool. Just curious, have you tried any other samplers on iOS with that many slices on them? Like Reslice, iMPC Pro or BM2? Hopefully they patch this in the upcoming update.

  • AudioGusAudioGus

    @echoopera said:
    Cool. Just curious, have you tried any other samplers on iOS with that many slices on them? Like Reslice, iMPC Pro or BM2? Hopefully they patch this in the upcoming update.

    No, nothing with more than 16 slices.

  • Giant_PeachGiant_Peach

    @LucidMusicInc said:
    10 (or more) things in no order that I find can reduce crashing

    1. Set the latency settings above 512
    2. Use Audiobus instead of IAA
    3. Use the timeline over scenes
    4. Keep saving and copying (BM3 makes a lot of new samples when recording and processing) when you save those get written to disk instead of staying in RAM
    5. Resample midi patterns to audio (easier to play an audio clip rather than a synthesiser or patern with short audio clips triggered)
    6. Tempo, try working at half time
    7. FX, obviously too many FX will eat up too much memory
    8. Polyphony, keep it below 16, 8 to be safe
    9. Converting stereo samples to mono and minding the EQ, excessively loud audio with too much mid and low can crash the app as well as damage your headphones/speakers/hearing
    10. Turn off unneccessay processes like other apps, blutooth m, wifi, iCloud sharing etc etc etc
    11. IOS 10.3 is probably the most stable iOS
    12. You need several gigabytes of available storage in reserve for optimal performance
    13. Certain plugins/third party apps can't be resample effectively in BM3, and will need to be resampled with another app like AudioShare (Machine is one example, Sampletank another)

    If these are the rules for having a problem free time, what the hell are we making music on an iPad for? Obviously it’s not fit for such a demanding task.

  • Giant_PeachGiant_Peach
    edited January 2018

    I have seen zero (0) support for those of us having terrible experiences and issues with BM3 or any other app. There is this stupid culture of no negativity and constant dick sucking praise all over the iOS music community when we should be able to air our terrible experiences so Apple, the developer community, and the consumer community can work together frankly and openly to solve problems and make things better.

    I have a 2017 12.9” 512 GB Pro and BM3 crashes literally every half hour no matter what I do or how little or great I push it. I’ve hard reset, and in fact, I just got it—I literally set up my new iPad with a 11.2.2 install and clean fresh apps no restoring from the cloud and BM3 constantly crashes and I can get barely any IAAs to work in it.

    Addictive Pro crashes relentlessly, there is no noise coming from the noise generator.

    Some people with my model and iOS version can duplicate my experience. Others think I’m crazy cause their experience is flawless. But when I and others like me come forward, Mathieu comes in to say “Cheers,” and that’s about it. I’m getting tired of it. Someone, someone, from Apple, or Intua, or Virsyn, should be able to give me SOME information about my experience. And I get nothing. Nothing at all.

    It’s infuriating.

  • dendydendy
    edited January 2018

    @El@ElGregoLoco
    If you fix the crashes and cracklings in BM3, it would be the best music app ever...

    Never get crash with BM3, but for me it is worst DAW on iOS ever :-)) Completely unusable for me, unintuitive messy UI/UX and lot of missing festures from BM2 ... BM2 was waaay better DAW...

    BM3 crashes literally every half hour no matter what I do

    hm maybe that's why i never got crash... everytime i run it and try do something meaningfull with it, i get mad, pissed of and totally disappointed after 20 minutes and then i turn it off and go back to BM2 :-)))

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • dendydendy
    edited January 2018

    .

  • RUST( i )KRUST( i )K

    You know how Freeware is........ ;)

  • Giant_PeachGiant_Peach
    edited January 2018

    @RUST( i )K said:
    You know how Freeware is........ ;)

    :D

  • LucidMusicIncLucidMusicInc

    @Giant_Peach said:

    @LucidMusicInc said:
    10 (or more) things in no order that I find can reduce crashing

    1. Set the latency settings above 512
    2. Use Audiobus instead of IAA
    3. Use the timeline over scenes
    4. Keep saving and copying (BM3 makes a lot of new samples when recording and processing) when you save those get written to disk instead of staying in RAM
    5. Resample midi patterns to audio (easier to play an audio clip rather than a synthesiser or patern with short audio clips triggered)
    6. Tempo, try working at half time
    7. FX, obviously too many FX will eat up too much memory
    8. Polyphony, keep it below 16, 8 to be safe
    9. Converting stereo samples to mono and minding the EQ, excessively loud audio with too much mid and low can crash the app as well as damage your headphones/speakers/hearing
    10. Turn off unneccessay processes like other apps, blutooth m, wifi, iCloud sharing etc etc etc
    11. IOS 10.3 is probably the most stable iOS
    12. You need several gigabytes of available storage in reserve for optimal performance
    13. Certain plugins/third party apps can't be resample effectively in BM3, and will need to be resampled with another app like AudioShare (Machine is one example, Sampletank another)

    If these are the rules for having a problem free time, what the hell are we making music on an iPad for? Obviously it’s not fit for such a demanding task.

    iPads are portable

  • CracklePotCracklePot

    @LucidMusicInc said:

    @Giant_Peach said:

    @LucidMusicInc said:
    10 (or more) things in no order that I find can reduce crashing

    1. Set the latency settings above 512
    2. Use Audiobus instead of IAA
    3. Use the timeline over scenes
    4. Keep saving and copying (BM3 makes a lot of new samples when recording and processing) when you save those get written to disk instead of staying in RAM
    5. Resample midi patterns to audio (easier to play an audio clip rather than a synthesiser or patern with short audio clips triggered)
    6. Tempo, try working at half time
    7. FX, obviously too many FX will eat up too much memory
    8. Polyphony, keep it below 16, 8 to be safe
    9. Converting stereo samples to mono and minding the EQ, excessively loud audio with too much mid and low can crash the app as well as damage your headphones/speakers/hearing
    10. Turn off unneccessay processes like other apps, blutooth m, wifi, iCloud sharing etc etc etc
    11. IOS 10.3 is probably the most stable iOS
    12. You need several gigabytes of available storage in reserve for optimal performance
    13. Certain plugins/third party apps can't be resample effectively in BM3, and will need to be resampled with another app like AudioShare (Machine is one example, Sampletank another)

    If these are the rules for having a problem free time, what the hell are we making music on an iPad for? Obviously it’s not fit for such a demanding task.

    iPads are portable

    I like to finger my stuff.

  • TheVimFuegoTheVimFuego

    @CracklePot said:

    @LucidMusicInc said:

    @Giant_Peach said:

    @LucidMusicInc said:
    10 (or more) things in no order that I find can reduce crashing

    1. Set the latency settings above 512
    2. Use Audiobus instead of IAA
    3. Use the timeline over scenes
    4. Keep saving and copying (BM3 makes a lot of new samples when recording and processing) when you save those get written to disk instead of staying in RAM
    5. Resample midi patterns to audio (easier to play an audio clip rather than a synthesiser or patern with short audio clips triggered)
    6. Tempo, try working at half time
    7. FX, obviously too many FX will eat up too much memory
    8. Polyphony, keep it below 16, 8 to be safe
    9. Converting stereo samples to mono and minding the EQ, excessively loud audio with too much mid and low can crash the app as well as damage your headphones/speakers/hearing
    10. Turn off unneccessay processes like other apps, blutooth m, wifi, iCloud sharing etc etc etc
    11. IOS 10.3 is probably the most stable iOS
    12. You need several gigabytes of available storage in reserve for optimal performance
    13. Certain plugins/third party apps can't be resample effectively in BM3, and will need to be resampled with another app like AudioShare (Machine is one example, Sampletank another)

    If these are the rules for having a problem free time, what the hell are we making music on an iPad for? Obviously it’s not fit for such a demanding task.

    iPads are portable

    I like to finger my stuff.

    Careful there, I can hear the PC sirens a-calling. :o

  • Giant_PeachGiant_Peach

    @AudioGus said:
    Oh yah it crashes like super crazy! Best app ever though!

    So then.....it can’t be the best app ever. See how that works? If something doesn’t work, it can’t be the best of its kind. See?

  • AudioGusAudioGus
    edited January 2018

    @Giant_Peach said:

    @AudioGus said:
    Oh yah it crashes like super crazy! Best app ever though!

    So then.....it can’t be the best app ever. See how that works? If something doesn’t work, it can’t be the best of its kind. See?

    Being subjective 'best' is all about personal criteria... in my case points were awarded for features and power. Points were also subtracted for crashes... it still won best app ever for me. See how that works? ;) ;)

  • Giant_PeachGiant_Peach

    @AudioGus said:

    @Giant_Peach said:

    @AudioGus said:
    Oh yah it crashes like super crazy! Best app ever though!

    So then.....it can’t be the best app ever. See how that works? If something doesn’t work, it can’t be the best of its kind. See?

    Being subjective 'best' is all about personal criteria... in my case points were awarded for features and power. Points were also subtracted for crashes... it still won best app ever for me. See how that works? ;) ;)

    Yeah sure. Me and iPad and BM3 are in a big tiff right now. BM3 has power and features no iPad app has, but if it’s crashing every half hour like clockwork to me its features are of absolutely no use to me.

Sign In or Register to comment.