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.

Nanostudio 2 update

1202123252633

Comments

  • @ohwell said:
    @brambos I noticed in 2017 posts of yours that you mention the iPad being a much bigger market for you - you mention 5x more of your sales being on iPad, I think? Has the gap between the iPad and iPhone markets changed for you since then? What's your take on the likelihood of that balance being reshuffled by some game changing production environment that combines auv3 support with a truly outstanding iPhone workflow? (I'm asking because from my outsiders' perspective (I really don't know the ins and outs of this) it looks like there should in theory be a very big potential for growth in the iPhone music production market: at minimum, the sheer mobility of the phones gives them an edge neither tablets or PC's can directly compete with; there is also the sheer number of people with iphones on them at all times. I'm asking this question in the NS2 thread because of the point I made in reply to @alecsbuga .)

    My dashboard tells me the following (2017, all my apps aggregated):

    • iPad 77%
    • iPhone 23%
    • iPod Touch 0.08%

    I don't see a massive shift towards iPhone, in spite of bigger iPhone models becoming more ubiquitous. iPad remains the dominant device for music creation and I doubt any single music app is going to change that. At these scales, a 5"+ increase in screensize gives such a massive increase in usability for complex interactions that iPads will always have the usability edge over phones.

    Just because you can run something on a phone, doesn't mean you should.. and the market seems to agree ;)

  • edited November 2018

    @ohwell said:
    Was that on iPhone? It's crazy how big the vaccum is atm for iPhone production environment with truly smooth workflow. That's what first got me hyped about NS2 - now I'm hyped about the whole thing..

    Initial upcoming release will be iPad only - iPhone support will be added later, probably spring 2019 .. Majority of app's UI already IS iPhone ready but it needs a little bit of polishing here and there ..
    -> http://forums.blipinteractive.co.uk/node/11956#comment-34598

  • Very interesting! Thanks for those numbers @brambos. Are all of your apps universal? You have an impressive range of apps and I’d be curious if there is any sort of ‘rhyme or reason’ for which apps sell on iPad but not iPhone. I can’t imagine not using both iDevices - the combination is a dream.

  • @brambos Hmm. I am probably totally wrong (I honestly don't know this market well). The point you are making about the relation between screen size and usability is especially interesting. It's actually part of what was driving my armchair/amateur guess. I mean, for both small screen and bigger touch screens, arriving at truly outstanding workflows for complex apps like music production environments (like BM3/NS2/etc) is a huge UI design challenge, one that can't be solved well by mindlessly reproducing the UI features of their PC equivalent. But precisely because usability is that much worse on smaller screen, the UI design challenge in the case of phones is that much greater. My probably misguided thought was that it's a challenge that can nonetheless be met for phones too, it's just exceedingly difficult.

    I have in mind not just the fact that apps like NS1 seem (not sure) to have done a way better job with the challenge than the current available equivalents with auv3 support. There's also the fact that so much iOS music app design has taken an iPad first approach, for the very good reason you point out. That's the kind of (likely inaccurate) considerations that made me optimistic that we just haven't seen how useable phone UIs can get for music production environments with auv3 support.

  • @dendy said:
    Initial upcoming release will be iPad only - iPhone support will be added later, probably spring 2019 .. Majority of app's UI already IS iPhone ready but it needs a little bit of polishing here and there ..
    -> http://forums.blipinteractive.co.uk/node/11956#comment-34598

    Yup I was up to date on that! I meant about your production in the car on NS1, whether that was on the phone.. :)

  • That was @alecsbuga who was being efficient in his car.

    I can tell you that the workflow is great between iPhone & iPad. I will use NS on iPhone to create/tweak presets, get new ideas started in the sequencer (beats, chords, etc.), tinker with melodic ideas, etc. Then I can easily transfer the project to my iPad to make use of great iPad only apps. Also I will often just complete the project entirely on the iPhone. There are plenty of great sounding apps for iPhone to help inspire me. Getting those sounds into NS2 will be a whole lot easier than it is in NS1.

  • @Slam_Cut That just sounds great!!!

    Question about NS2. I didn't realize until this weekend that NS2 will be auv3 only/no IAA synths/effects. Do folks know whether it will (eventually) allow using something like Audiobus to host IAA only synths/effects as a workaround? (So, e.g. support Audiobus midi and audio I/O?)

  • edited November 2018

    @ohwell

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    NS2 will contain MIDI OUT so you will be able to send midi from NS to any other app (synth) running on your device, then somehow record its audio output (audioshare, aum,...) and then load this audio into NS2

    Of course thus is workaround, how to get audio loops from external non-AUv3 synths to NS, no direct supprt of IAA/AB, at least in initial release

  • I used NS1 on iPad. Except for Samplist I don't have loads of apps on my iPhone. I just find it frustrating. I love GrooveRider but it's a pain to use on the iPhone. Not to mention KEW... they just put it in there to make more money :))

  • @dendy said:
    @ohwell

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    NS2 will contain MIDI OUT so you will be able to send midi from NS to any other app (synth) running on your device, then somehow record its audio output (audioshare, aum,...) and then load this audio into NS2

    Of course thus is workaround, how to get audio loops from external non-AUv3 synths to NS, no direct supprt of IAA/AB, at least in initial release

    Funny how everyone was begging for AU iOS apps and now that AU is taking over people are asking about IAA which, I believe, is on its way out. What IAA only apps are that critical to your workflow and can’t be replaced by AU apps?

  • wimwim
    edited November 2018

    That’s really too bad about no AudioBus support. I can live without IAA and AB midi, but no AB audio means I’ll probably rarely use it.

    I’m sure I’ll buy it anyway ‘cause that’s what I do. But meh. :/

    Sorry for the negativity. I’m just genuinely disappointed.

  • @dendy said:
    @ohwell

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    NS2 will contain MIDI OUT so you will be able to send midi from NS to any other app (synth) running on your device, then somehow record its audio output (audioshare, aum,...) and then load this audio into NS2

    Of course thus is workaround, how to get audio loops from external non-AUv3 synths to NS, no direct supprt of IAA/AB, at least in initial release

    You obviously got it wrong mate. You can resample an IAA or AUv3 directly inside the app.
    It used to work in NS1 also via Audiobus. Recording in Audioshare while sending MIDI to the app then copying and pasting in NS... is way too much of a hassle.

    Hope this helps.

  • @anickt
    What IAA only apps are that critical to your workflow and can’t be replaced by AU apps?

    you mean me ? No single one :-) I already deleted all synths / fxs not supporting AUv3, looking to the future. AB/IAA was very important in some phase of iOS music apps evolutin but now it's time to say goodby to these technologies...

    @wim
    I’m sure I’ll buy it anyway ‘cause that’s what I do. But meh.

    Maybe one day you foumd new workflow, which will work for you also without AB, you never know ;) With every new AU instrument/effect importance of AB/IAA only apps is lower and lower ...

  • @anickt said:

    @dendy said:
    @ohwell

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    NS2 will contain MIDI OUT so you will be able to send midi from NS to any other app (synth) running on your device, then somehow record its audio output (audioshare, aum,...) and then load this audio into NS2

    Of course thus is workaround, how to get audio loops from external non-AUv3 synths to NS, no direct supprt of IAA/AB, at least in initial release

    Funny how everyone was begging for AU iOS apps and now that AU is taking over people are asking about IAA which, I believe, is on its way out. What IAA only apps are that critical to your workflow and can’t be replaced by AU apps?

    IAA it's not on its way out. AUv3 is much more difficult to implement than just piping your app's output buffers to IAA.

  • @alecsbuga

    no no... NS1 had AB support... NS2 will have not... just AUv3.

  • wimwim
    edited November 2018

    @alecsbuga said:

    You obviously got it wrong mate. You can resample an IAA or AUv3 directly inside the app.
    It used to work in NS1 also via Audiobus. Recording in Audioshare while sending MIDI to the app then copying and pasting in NS... is way too much of a hassle.

    Hope this helps.

    Are you saying that it will run inside AudioBus and accept audio from it? That’s contradictory to what I understood from @dendy’s comment.

    @dendy said:

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    I’d like to get this sorted out. Kind of a buzzkill if it’s true.

  • edited November 2018

    @dendy said:

    @anickt
    What IAA only apps are that critical to your workflow and can’t be replaced by AU apps?

    you mean me ? No single one :-) I already deleted all synths / fxs not supporting AUv3, looking to the future. AB/IAA was very important in some phase of iOS music apps evolutin but now it's time to say goodby to these technologies...

    @wim
    I’m sure I’ll buy it anyway ‘cause that’s what I do. But meh.

    Maybe one day you foumd new workflow, which will work for you also without AB, you never know ;) With every new AU instrument/effect importance of AB/IAA only apps is lower and lower ...

    You deleted Samplr? Noooooo!

  • wimwim
    edited November 2018

    @dendy said:
    Maybe one day you foumd new workflow, which will work for you also without AB, you never know ;) With every new AU instrument/effect importance of AB/IAA only apps is lower and lower ...

    Highly unlikely. I already use AU apps almost exclusively, but AudioBus remains central to that workflow. Look, I’m looking forward to NS2 too, but as another tool alongside everything else I use. I’m never, ever going to be working in it or any other host exclusively. AudioBus is what ties it all together for me.

    If NS2 doesn’t play well with others, it will get be of much less use to me.

  • edited November 2018

    @wim said:

    @dendy said:
    Maybe one day you foumd new workflow, which will work for you also without AB, you never know ;) With every new AU instrument/effect importance of AB/IAA only apps is lower and lower ...

    Highly unlikely. I already use AU apps almost exclusively, but AudioBus remains central to that workflow. Look, I’m looking forward to NS2 too, but as another tool alongside everything else I use. I’m never, ever going to be working in it or any other host exclusively. AudioBus is what ties it all together for me.

    If NS2 doesn’t play well with others, it will get be of much less use to me.

    OK. I sense the hares running. I guess we need a definitive: NS2 AB or not AB?

  • No AB in NS2. I don’t find this limiting. It is super easy to use MIDI > AB/IAA with AudioShare and import the results into NS2. When NS2 is available.

    A question for each individual as to how many steps they will take to use other apps in a DAW. Keep in mind that iOS music production is still in development. It’s not a perfect environment. I think there is room for multiple paths, and I see no reason to ditch IAA/AB from my workflow. Even though AUv3 seems to be the future, there is not enough standardization on the implementation of code for that to be 100% reliable right now.

  • wimwim
    edited November 2018

    I guess we’ll know for sure once it arrives. I know I’ll get it anyway. But, this is supposed to be the happy squishy love fest thread. I’ve spoken out of turn and apologize. I’ll go away now.

  • The user and all related content has been deleted.
  • @alecsbuga said:

    @anickt said:

    @dendy said:
    @ohwell

    No IAA/AB support, only AUv3. You can record audio from IAA synth for example using AudioShare and then open it in NS2 and put to sampler...

    NS2 will contain MIDI OUT so you will be able to send midi from NS to any other app (synth) running on your device, then somehow record its audio output (audioshare, aum,...) and then load this audio into NS2

    Of course thus is workaround, how to get audio loops from external non-AUv3 synths to NS, no direct supprt of IAA/AB, at least in initial release

    Funny how everyone was begging for AU iOS apps and now that AU is taking over people are asking about IAA which, I believe, is on its way out. What IAA only apps are that critical to your workflow and can’t be replaced by AU apps?

    IAA it's not on its way out. AUv3 is much more difficult to implement than just piping your app's output buffers to IAA.

    Yes it is.

  • @anickt In due time there probably won't remain many IAA in my workflow. In many cases it's just a matter of preferring some apps that don't offer auv3 to their auv3 counterparts for some purposes. (Ignoring the ones I know for a fact are going to be auv3 soon, just to name a few: iPulsaret, Stria, Sparkle, SeekBeats, Elastic drums + fx, Samplr, Impaktor...) Don't know of any auv3 that can replace Bias amp/Tonestack yet. Not going to prevent me from enjoying NS2 though.. :)

  • @ohwell said:
    @anickt In due time there probably won't remain many IAA in my workflow. In many cases it's just a matter of preferring some apps that don't offer auv3 to their auv3 counterparts for some purposes. (Ignoring the ones I know for a fact are going to be auv3 soon, just to name a few: iPulsaret, Stria, Sparkle, SeekBeats, Elastic drums + fx, Samplr, Impaktor...) Don't know of any auv3 that can replace Bias amp/Tonestack yet. Not going to prevent me from enjoying NS2 though.. :)

    B)

  • @Slam_Cut said:

    @hansjbs said:
    :D :D :D . whatever you guysvare smoking I want some. Looks like you guys didn't use any other DAW before ios.

    When I started in the mid 90’s the DAW were awkward. I mostly sequenced and the Ensoniq SD-1 was great for that. I later bought DAW like Sonar, but it had a steepnlearning curve and life situation didn’t allow me to spend many hours for weeks at a time to really get to grips with Sonar. Later tried Abelton. When I got an iPhone 3gs I tried BM. I could dabble with these things, but it wasn’t until NS1 that I was able to click with a DAW. That it was on my iPhone meant I could work in short snipets. Setting up to work my hardware studio with DAW was not so quick and easy. I was far more successful completeing tracks in NS1 than any other set up. That doesn’t mean I think NS1 was better than Sonar or Abelton, it just worked for ME. Results may vary.

    @zhoe said:

    @hansjbs said:

    @Slam_Cut said:
    . If we look back to the development of iOS music apps, NS1 was a big reason the bar was raised back before iOS apps could even handle MIDI. A lot of the BM2/3 fans should thank NS1 for inspiring the BM devs to raise the bar. .

    Huh???? What?????
    BM1 came out almost the same time the app store became a thing back in 2008. They are pioneers in this.
    Nanostudio came out July 2010

    BM2 came out February 2011 (Which they started developing more than a year prior) so intua inspired a lot of developers that decided to make apps we enjoy today. So who inspired whom to raise the bar???

    Hear hear. BM was the first, I bought it in 2008 for my iPod Touch that predated iPhone 1. No one wanted to invest in iOS music making at the time. A few iOS versions later Nanostudio was launched, along with some other apps that also saw the horizon. But, let's repeat and underline it once and for all, Intua were the pioneers.

    I did not say NS1 came first. I used BM and it was not up to what I needed in a music creation environment. NS1 was 4 years in development (started development in 2006) and when it hit, I think it offered so much more than any other app that it seriously raised the bar. There may be people who don’t share this opinion, and they are welcomed to their opinions, but I think the majority of iOS musicians from that era would agree. I don’t know the developers at Intua, so I don’t know what inspired them to create BM2, but it sure seemed like they wanted to raise the bar on BM, and since NS1 was their main ‘competition’ they must have taken its feature into consideration when developing BM2, so it looked like they were inspired by NS1. I don’t think this was a bad thing, and it doesn’t matter wether or not they were inspired by NS1. I don’t mean to single out BM 1-3. I only mentioned it as lots of people are drawing conclusions or asking for comparisons based on BM. All devs must be aware of other apps and try to rise to the level of other apps or exceed them. That is natural. I think all apps are benefitting from the rising quality of other apps, and the development of the formats that allow these apps to be used together: AB/IAA/AUv3 etc.

    Fair play, but you did say "A lot of the BM2/3 fans should thank NS1 for inspiring the BM devs to raise the bar. ."
    I've only wanted to acknowledge the true pioneers, and that was Intua and the Beatmaker 1. When NS came on the scene, there were quite a lot of music apps around (compared to when BM1 came out), so, of course, BM2 later on built on everyone else including NS1, which was a better app than BM1, but it also came a few years later. I was happy to play with BM1 which was pretty basic, but I managed to write some ideas on it, on the go. And even if I wanted to use other apps, there was a void, zero nothing. So, instead of thanking NS1, why not thank Intua for creating the first sample-sequencer on iOS. And then we can thank everyone else, including NS who raised the bar even further. I think that was the sentiment of the poster who replied to your post. All I can say, competition is healthy and we all benefit from it. But I will always give more props to the pioneer. Now all praise Cubasis for example, Steinberg was one of the last to join the IOS music making scene. They waited to see whether it'd make sense. That's why the early devs will always have a special place in my iPad's heart ;)

  • @zhoe said:

    @Slam_Cut said:

    @hansjbs said:
    :D :D :D . whatever you guysvare smoking I want some. Looks like you guys didn't use any other DAW before ios.

    When I started in the mid 90’s the DAW were awkward. I mostly sequenced and the Ensoniq SD-1 was great for that. I later bought DAW like Sonar, but it had a steepnlearning curve and life situation didn’t allow me to spend many hours for weeks at a time to really get to grips with Sonar. Later tried Abelton. When I got an iPhone 3gs I tried BM. I could dabble with these things, but it wasn’t until NS1 that I was able to click with a DAW. That it was on my iPhone meant I could work in short snipets. Setting up to work my hardware studio with DAW was not so quick and easy. I was far more successful completeing tracks in NS1 than any other set up. That doesn’t mean I think NS1 was better than Sonar or Abelton, it just worked for ME. Results may vary.

    @zhoe said:

    @hansjbs said:

    @Slam_Cut said:
    . If we look back to the development of iOS music apps, NS1 was a big reason the bar was raised back before iOS apps could even handle MIDI. A lot of the BM2/3 fans should thank NS1 for inspiring the BM devs to raise the bar. .

    Huh???? What?????
    BM1 came out almost the same time the app store became a thing back in 2008. They are pioneers in this.
    Nanostudio came out July 2010

    BM2 came out February 2011 (Which they started developing more than a year prior) so intua inspired a lot of developers that decided to make apps we enjoy today. So who inspired whom to raise the bar???

    Hear hear. BM was the first, I bought it in 2008 for my iPod Touch that predated iPhone 1. No one wanted to invest in iOS music making at the time. A few iOS versions later Nanostudio was launched, along with some other apps that also saw the horizon. But, let's repeat and underline it once and for all, Intua were the pioneers.

    I did not say NS1 came first. I used BM and it was not up to what I needed in a music creation environment. NS1 was 4 years in development (started development in 2006) and when it hit, I think it offered so much more than any other app that it seriously raised the bar. There may be people who don’t share this opinion, and they are welcomed to their opinions, but I think the majority of iOS musicians from that era would agree. I don’t know the developers at Intua, so I don’t know what inspired them to create BM2, but it sure seemed like they wanted to raise the bar on BM, and since NS1 was their main ‘competition’ they must have taken its feature into consideration when developing BM2, so it looked like they were inspired by NS1. I don’t think this was a bad thing, and it doesn’t matter wether or not they were inspired by NS1. I don’t mean to single out BM 1-3. I only mentioned it as lots of people are drawing conclusions or asking for comparisons based on BM. All devs must be aware of other apps and try to rise to the level of other apps or exceed them. That is natural. I think all apps are benefitting from the rising quality of other apps, and the development of the formats that allow these apps to be used together: AB/IAA/AUv3 etc.

    Fair play, but you did say "A lot of the BM2/3 fans should thank NS1 for inspiring the BM devs to raise the bar. ."
    I've only wanted to acknowledge the true pioneers, and that was Intua and the Beatmaker 1. When NS came on the scene, there were quite a lot of music apps around (compared to when BM1 came out), so, of course, BM2 later on built on everyone else including NS1, which was a better app than BM1, but it also came a few years later. I was happy to play with BM1 which was pretty basic, but I managed to write some ideas on it, on the go. And even if I wanted to use other apps, there was a void, zero nothing. So, instead of thanking NS1, why not thank Intua for creating the first sample-sequencer on iOS. And then we can thank everyone else, including NS who raised the bar even further. I think that was the sentiment of the poster who replied to your post. All I can say, competition is healthy and we all benefit from it. But I will always give more props to the pioneer. Now all praise Cubasis for example, Steinberg was one of the last to join the IOS music making scene. They waited to see whether it'd make sense. That's why the early devs will always have a special place in my iPad's heart ;)

    Thank you for understanding where I was coming from.

  • @zhoe said:

    But, let's repeat and underline it once and for all, Intua were the pioneers.

    I did not say NS1 came first.

    This point was already posted and I do not disagree. I was there. I was using BM1

    Fair play, but you did say "A lot of the BM2/3 fans should thank NS1 for inspiring the BM devs to raise the bar. ."
    I've only wanted to acknowledge the true pioneers, and that was Intua and the Beatmaker 1.

    I never agued that they were not pioneers. They were. Do you just want an NS1 user to say it? “Beatmaker was first and Intua were THE pioneers.”

    This was never the point and I think if you look back on this threas you’ll see there was a growing number of comments comparing BM & NS. One person asked the question that has been asked a lot on this thread “What does NS2 have that BM2/3 doesn’t?” That’s the only reason I brought up BM. I agree that BM was first, Intua were pioneers, and showed what was possible on iOS. NS1 came along and taised the bar. BM2 raised thier bar after that and I think (my opinion) that Intua were inspired to raise their bar due to what NS1 achieved. And I think (again just opinion) BM 2/3 users should be glad of the ‘competition’ (which it really isn’t) that made their app better. Not that any of this really matters. It was just a throw away line on my part, no insult intended, and I see no reason for BM2/3 users to take offense at what I say. I will try in the future to put things in more PC/delicate terms to avoid offense, or more likely just not mention BM2/3 ever again.

    So, instead of thanking NS1, why not thank Intua for creating the first sample-sequencer on iOS. And then we can thank everyone else, including NS who raised the bar even further.

    Agreed. Again this was not really my point, but if you want to extrapolate, yeah we should thank all that came before that makes the current iOS music production scene possible, including Apple, which I hate to say. My point really shouldn’t be twisted into an idea that I forgot to thank everyone who has been involed in developing.

    I think that was the sentiment of the poster who replied to your post.

    Perhaps so, that wasn’t clear, and perhaps I missed something. I’m not going to go back now and try to reread it. This has already gotten to be laboriously long and I think we’ve split hairs long enough and should stop beating the dead horse. If you have any more questions, please feel free to ask, but I don’t want to rehash the ‘inspired by’ question unless really and truly necessary. Does that sound good to you? And for the record I am not nor have I disagreed with the points you’ve made. I just think you misunderstood my point, which is super common on forums like this and shy I try to avoid poting in general. I only make exception for Nanostudio because I really believe in the product.

  • @anickt said:

    @lovadamusic said:

    @kinkujin said:
    I think this thread, and the next one about the next long-awaited app (eg. Drambo?) is just the thing we do. We need this 'thing' to represent our dreams and aspirations. I mean, this is how I get through the day. Life can be very boring and redundant and boring ... so we come here and get all amped up about the new something because it is something we can actually get excited about.

    So us passionate music-types, get all invested in this non-tangible thing until it's released. Then when it lands we will just pummel it because it didn't live up to the hopes we had ascribed to it - realistic or not. I'm guilty of this myself, more than once.

    In the case of NanoStudio, the dev seems to be a perfectionist and doesn't seem to make promises he can't keep. But, I'm sure I'll (we'll) find something to be disappointed about in it. I'd hate to be a developer. So much psychology.

    At the risk of being a downer, if anyone today, with all the affordable music-making capability we have, is sitting around bored waiting for the new thing that's going to make their dreams come true, it's never going to happen. Look for a new dream or a new hobby. On the contrary---passionate music-types should be wishing they had more hours in the day to take advantage of what they already have.

    I doubt if (for most people on this forum) anyone is “sitting around bored waiting for the new thing...”. For me anyway, it’s a matter of efficiency and getting the most done in the hours (or minutes) of the day that are available for music making. There are apps that contribute to that goal and those that don’t. Based on experience with NS1, NS2 will be one of those apps.

    "We need this 'thing' to represent our dreams and aspirations. I mean, this is how I get through the day. Life can be very boring and redundant and boring ... so we come here and get all amped up about the new something because it is something we can actually get excited about."

    If the shoe don't fit... ?

    Musicians I've known have always made music with whatever they can get their hands on, and it's never been boring. Seems today, for some "passionate music types," it's more about the technology.

  • edited November 2018

    Musicians I've known have always made music with whatever they can get their hands on, and it's never been boring. Seems today, for some "passionate music types," it's more about the technology.

    For last 8 years i dit a lot of music with NS1, then BM2, then Gadget .. this doesn't change anything on fact i'm super excited aboout NS2, it will be my DAW of choice for next years because of some unique features which are not present in any other available iOS DAW. Features which will make my workflow more easy, less painful than in other DAWs, it means i will be more creative, more productive.. that's all. I think a majority of "hyped" people in this tread see it same way.. It's not that we are "waiting" for NS2 and doing nothing .. It's called progress, evolution. It's people nature to still looking forward.

This discussion has been closed.