![]() Sharing projects has huge dependancies on these two features. It might now be obvious why we added soundpack sharing, and audio import for iPhone. This struck us about 6 months ago when we started with our 'Ecosystem' project, to bring our apps closer together for our users. It really does add technical challenges, but interesting also pretty big philosophical user issues. with two ipads and projects all across the spectrum in terms of keys you can do an actual dj set said: this is pretty much the functionality i always wanted since i can bake projects in different keys now for actual harmonic mixing. ![]() it would also explain why the projects are saved in a different catagory. they just added launchpad support to open said projects. Im guessing the reason for this is its still technically a blocs wave project that is open. Seems so obvious, must be something technical/problematic. So you can add sound pack sounds into your project in Blocs Wave before exporting the project to LaunchPAD. However back in January both Blocs Wave and LaunchPad was updated with "Sound pack Sharing", meaning any sound packs purchased in either app will be available in both. ![]() I should have added that when you import a Blocs Wave project into Launchpad, you cannot add loops to that project from within Launchpad. Someone else asked me the same thing in a YouTube comment. I guess Im thinking this might mean any launchpad loop can now be edited in blocswave. Great update and now I dont have to work it out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |