BM3 Update is out

[Deleted User]

@Carnbot said:

@Fruitbat1919 said:

@Carnbot said:
So are you saying that apps like Riffer won't work, as in you can't record the midi from it, but it will trigger the synths?

Riffer isn’t AU midi so it won’t work in those slots anyway

Ok I think there's still an AU category problem perhaps, Riffer and Rozeta are AU midi instruments as seen in the apeMatrix categories, but aren't midi fx. Unless apeMatrix has the categories wrong. I feel like the Rozeta suite are AU midi instruments and not effects so shouldn't be in that list.

There are parts of the Rozeta suite that respond to MIDI input (e.g. Scaler) so they can function as both MIDI instruments and MIDI effects.

[Deleted User]

I’m going to share my take on Beatmaker 3 with the hope that some may find it useful rather than to persuade anybody to follow my approach.

The app is very ambitious and a relatively complex music creation app. With a multitude of workflow options. When you have more complexity you also increase the potential for problems. Plus it’s a smaller development team with limited resources.

In addition, iOS continues to evolve and getting the various app components in sync at the same time can be problematic too.

I purchased Beatmaker 3 because the developer had been creating apps since the beginning of iOS and the capabilities of Beatmaker 3 weren’t something offered in other apps in my opinion. When I started to use the app, there was definitely a need to spend a significant amount of time to learn it. After several months, I decided I would put the app on hold in terms of learning all of the in/outs of its functionality as I believed it was still being developed and would wait until it was in a more finished workable state to do so as I have many other apps I can use in the meantime.

When I start to see Beatmaker 3 videos and forum comments which suggest the app has reached this more finished state I’m waiting for, I’ll start investing the time to learn it at a deeper level.

hansjbs

@echoopera said:

@JohnnyGoodyear said:

@Dawdles said:

@JohnnyGoodyear said:

@echoopera said:
I dunno. I had a good two hours of fun with the latest update of BM3 last night. Call me primitive but i enjoyed making noise in the update. 🤪

The new Midi AU routing didn’t bother me. Sure the instrument had to be in KEYS mode to work, but i was able to record my Rozeta Arps just fine to clips and roll those recorded patterns into the timeline. But hey I’m an onward and upward sort of mental model fellow. I don’t subscribe to the sky is falling mental model anymore. Life is too beautiful for that rubbish.

+1

Why do people get so high and mighty about accepting compromise and ‘making do’? I’m an ‘onwards and upwards’ kind of guy too. Just that sadly this time that means leaving bm3 behind and using something else. That’s not a ‘being negative’ thing. Just a sensible decision to choose the best tool for the job for what I want to do. Which bm3 doesn’t appear to be for me for this stuff any more. It’s not a case of ‘sky is falling mental mode’, it’s just having enough wits to not try to hit a square peg in to a round hole. Which frustratingly ‘used’ to be a square hole

I think that you and I may feel differently on this matter and we also have a fundamental difference of opinion as to attitude and delivery. I think it's probably best for us both (and for everyone else on the bus ) if we live and let live on this one.

+1

Just let us weary travelers sort through the lot in life we’ve been given. A blessed one at that fwiw 🙏🏼🤪 because of the embarrassment of riches we have on iOS.

+1000

AndyPlankton

I blame @brambos...he started all this AU MIDI FX malarkey

AudioGus

@AndyPlankton said:
I blame @brambos...he started all this AU MIDI FX malarkey

Yes and they are now %100 VITAL TO ME EVER MAKING MUSIC AGAIN!!!! Freakout/rant/whine etc.

AndyPlankton

@AudioGus said:

@AndyPlankton said:
I blame @brambos...he started all this AU MIDI FX malarkey

Yes and they are now %100 VITAL TO ME EVER MAKING MUSIC AGAIN!!!! Freakout/rant/whine etc.

hahaha AU Midi FX - the crystal meth of iOS music making

AudioGus

@AndyPlankton said:

@AudioGus said:

@AndyPlankton said:
I blame @brambos...he started all this AU MIDI FX malarkey

Yes and they are now %100 VITAL TO ME EVER MAKING MUSIC AGAIN!!!! Freakout/rant/whine etc.

hahaha AU Midi FX - the crystal meth of iOS music making

Heh and all this time I thought crystal meth was the crystal meth of iOS music making,

Carnbot

@InfoCheck said:

@Carnbot said:

@Fruitbat1919 said:

@Carnbot said:
So are you saying that apps like Riffer won't work, as in you can't record the midi from it, but it will trigger the synths?

Riffer isn’t AU midi so it won’t work in those slots anyway

Ok I think there's still an AU category problem perhaps, Riffer and Rozeta are AU midi instruments as seen in the apeMatrix categories, but aren't midi fx. Unless apeMatrix has the categories wrong. I feel like the Rozeta suite are AU midi instruments and not effects so shouldn't be in that list.

There are parts of the Rozeta suite that respond to MIDI input (e.g. Scaler) so they can function as both MIDI instruments and MIDI effects.

oh yes, I'm aware of that
I just think because Rozeta is a suite of apps and not individual ones it's more confusing here for BM3 implementation going by this thread. (Not that I've tried it yet as I'm not using BM3 for now)

It seems like other apps like apeMatrix list them correctly in the instrument slot whilst there are only a few genuine AUMi midi plugins listed in midi FX category. In Apematrix or AUM of course it doesn't really matter as you aren't restricted by the routing categories, there are just midi in and out of apps.

But..Looks as though Intua are on it and will allow midi fx to have a better implementation and indeed maybe the new way is less confusing than the old routing system in BM3 which was always a bit tricky.

AndyPlankton

@AudioGus said:

@AndyPlankton said:

@AudioGus said:

@AndyPlankton said:
I blame @brambos...he started all this AU MIDI FX malarkey

Yes and they are now %100 VITAL TO ME EVER MAKING MUSIC AGAIN!!!! Freakout/rant/whine etc.

hahaha AU Midi FX - the crystal meth of iOS music making

Heh and all this time I thought crystal meth was the crystal meth of iOS music making,

Bosenberg or Heisenbos ?

[Deleted User]

The user and all related content has been deleted.

brambos

@Dawdles said:

@Dawdles said:

@recccp said:

@Dawdles said:

@WillieNegus said:
Thanks for the explanation @intua_vincent

I’m among those that am confident in Intua’s ability to make this app as close to perfection for my type of Beatmaking so I won’t question how they prioritize B3. It’s a complicated mess of brilliance.

I also empathize and understand those greatly disappointed and disenfranchised about this update rollout.

I will again mention that COMMUNICATION...even if it’s just an occasional post on their blog, newsle or forum...will do much to avoid toxic discussions. Why create a blog, newsletter AND forum if you don’t use it well?

It’s when uninformed loyal users who’ve invested a lot of time and passion into projects are left to their own assumptions, humor, outrage, emo, etc that things can get wacky. I believe the few devs at Intua I’ve seen to be confident, thick skinned and well adjusted. I can’t imagine they’re ever reading these threads in tears. Seriously. If anything, they probably get a chuckle every now and again between fulfilling their passion. I hope so.

I digress...can we now can put to rest this bullshit about B3 being abandonware? Intua is alive, well, listening and working to improve B3. Great.

@intua_vincent is aware of this community and that people are passionate about B3. Let’s respect that and work with him to aid their development if we truly care about the app. If you don’t, why are you here discussing it?

Finally, an apology to @intua_vincent and @mathieugarcia if they took offense to my living thread on their forum. I doubt they did. I think it’s more like a few isolated members of the forum decided they didn’t get the humor in my updating title anymore but in the event I’m wrong...my apologies.

I will be returning to my normal sarcastic self now.

I do ‘truly care about the app’. Because it ‘used to’ do what I needed it to in a unique environment.

But, if a dev opts to break one thing to fix another then that’s great if you need what gets fixed and didn’t use the thing that gets broken.. But if you’re in the vice versa then you’re fuqt... Looks like I’m a minority casualty and few other people were Utilising creative midi au routing before. So I take one for the team I guess....

Won’t be using Bm3 in the foreseeable future though, I have zero trust remaining now that other features won’t get altered in future that break my existing projects for editing and/or kills my workflow again. Stuff like that really shouldn’t be a concern with daw updates...

Enjoy going backwards people

I agree, it's not what I was expecting either. But if that's the price of accuracy and stability so be it. BM3 midi is still far from perfect, but I'm sure once the basics get sorted properly more flexibility will follow at some point.
For now I'm happy to see INTUA is still in the game, and hope that communication won't fade out.

Can someone explain to me clearly Vincent’s routing latency/stability reasoning and then I’ll shut up, promise example -

Pad 1 - Kick drum
Pad 2 - Snare
Pad 3 - Hihat
Pad 4- Ride
Pad 5 - Crash
Pad 6 - a reverb plug-in
Pad 8 - Rozeta collider
Pad 9 - Rozeta LFO
Pads 10-20 random one shot samples.

I decide I want -
-Collider to trigger 3 of those Random one shot pads. All from that one instance of Collider.
This isn’t possible in new bm3 because I can’t share Collider’s output to specific pads (suggested ‘pad link’ won’t work because it’ll trigger all linked samples together... Whereas I’d generally want some unique, sequenced hits per pad, not only the collider hits)

-LFO to mess with Collider.

-that same LFO to mess with reverb params.

how does the ‘new’ way reduce latency? I’d have to use like 6 extra instances of Rozeta to get vaguely the same results now without routing. But it would be a total mess and headache. How is that significantly more efficient in terms of latency? Each plugin is still being processed etc either way. Just way less efficiently in terms of plugin count and workflow with the new way?

The above is kind of a simplified example in an attempt to try to make sense enough for people to get the type of scenario I mean. Obviously the ‘new way’ becomes exponentially less efficient with more complicated/longer routings. Potentially 100s of Rozeta instances and 100s of banks. Just to achieve what used to be doable in one bank with like 10 Rozetas.

Someone school me!

@brambos you’re woke on this stuff, maybe you can do me a solid please dude and school me on this so it makes more sense to me? I’m not ‘enjoying’ throwing shade at the thread/forum, just naturally disappointed with the update so if I could understand the reason why it absolutely had to be implemented in the new limited way, without the old routing flexibility, I can go shed a couple silent tears and move on thanks!

I wish I could, but I don't know. I haven't tried routing or recording in the 3.0.11 release because I was told it wasn't implemented at all. Simply driving a synth using a MIDI plugin as input seems to work nicely in this release (and I appreciated the quick access button in the left-margin) so that's a start, but routing and recording AU MIDI was working in the mythical 3.1b I used to have months ago.

I don't have enough insights in the internals of BM3 to make statements about feasibility or difficulties. In theory it should be possible to handle all MIDI routing before handling audio rendering, but I can imagine it may be tricky to retrofit it into an architecture that was built before the AU MIDI concept was even invented (this may be compounded by the way AU MIDI is handled in iOS: the host may receive audio and/or MIDI from the same plugin simultaneously, and this MIDI may be meant for another plugin which has already been rendered... Just guessing here...).

ExAsperis99

We need a little levity, comrades.

AudioGus

@brambos said:

@Dawdles said:

@Dawdles said:

@recccp said:

@Dawdles said:

@WillieNegus said:
Thanks for the explanation @intua_vincent

I’m among those that am confident in Intua’s ability to make this app as close to perfection for my type of Beatmaking so I won’t question how they prioritize B3. It’s a complicated mess of brilliance.

I also empathize and understand those greatly disappointed and disenfranchised about this update rollout.

I will again mention that COMMUNICATION...even if it’s just an occasional post on their blog, newsle or forum...will do much to avoid toxic discussions. Why create a blog, newsletter AND forum if you don’t use it well?

It’s when uninformed loyal users who’ve invested a lot of time and passion into projects are left to their own assumptions, humor, outrage, emo, etc that things can get wacky. I believe the few devs at Intua I’ve seen to be confident, thick skinned and well adjusted. I can’t imagine they’re ever reading these threads in tears. Seriously. If anything, they probably get a chuckle every now and again between fulfilling their passion. I hope so.

I digress...can we now can put to rest this bullshit about B3 being abandonware? Intua is alive, well, listening and working to improve B3. Great.

@intua_vincent is aware of this community and that people are passionate about B3. Let’s respect that and work with him to aid their development if we truly care about the app. If you don’t, why are you here discussing it?

Finally, an apology to @intua_vincent and @mathieugarcia if they took offense to my living thread on their forum. I doubt they did. I think it’s more like a few isolated members of the forum decided they didn’t get the humor in my updating title anymore but in the event I’m wrong...my apologies.

I will be returning to my normal sarcastic self now.

I do ‘truly care about the app’. Because it ‘used to’ do what I needed it to in a unique environment.

But, if a dev opts to break one thing to fix another then that’s great if you need what gets fixed and didn’t use the thing that gets broken.. But if you’re in the vice versa then you’re fuqt... Looks like I’m a minority casualty and few other people were Utilising creative midi au routing before. So I take one for the team I guess....

Won’t be using Bm3 in the foreseeable future though, I have zero trust remaining now that other features won’t get altered in future that break my existing projects for editing and/or kills my workflow again. Stuff like that really shouldn’t be a concern with daw updates...

Enjoy going backwards people

I agree, it's not what I was expecting either. But if that's the price of accuracy and stability so be it. BM3 midi is still far from perfect, but I'm sure once the basics get sorted properly more flexibility will follow at some point.
For now I'm happy to see INTUA is still in the game, and hope that communication won't fade out.

Can someone explain to me clearly Vincent’s routing latency/stability reasoning and then I’ll shut up, promise example -

Pad 1 - Kick drum
Pad 2 - Snare
Pad 3 - Hihat
Pad 4- Ride
Pad 5 - Crash
Pad 6 - a reverb plug-in
Pad 8 - Rozeta collider
Pad 9 - Rozeta LFO
Pads 10-20 random one shot samples.

I decide I want -
-Collider to trigger 3 of those Random one shot pads. All from that one instance of Collider.
This isn’t possible in new bm3 because I can’t share Collider’s output to specific pads (suggested ‘pad link’ won’t work because it’ll trigger all linked samples together... Whereas I’d generally want some unique, sequenced hits per pad, not only the collider hits)

-LFO to mess with Collider.

-that same LFO to mess with reverb params.

how does the ‘new’ way reduce latency? I’d have to use like 6 extra instances of Rozeta to get vaguely the same results now without routing. But it would be a total mess and headache. How is that significantly more efficient in terms of latency? Each plugin is still being processed etc either way. Just way less efficiently in terms of plugin count and workflow with the new way?

The above is kind of a simplified example in an attempt to try to make sense enough for people to get the type of scenario I mean. Obviously the ‘new way’ becomes exponentially less efficient with more complicated/longer routings. Potentially 100s of Rozeta instances and 100s of banks. Just to achieve what used to be doable in one bank with like 10 Rozetas.

Someone school me!

@brambos you’re woke on this stuff, maybe you can do me a solid please dude and school me on this so it makes more sense to me? I’m not ‘enjoying’ throwing shade at the thread/forum, just naturally disappointed with the update so if I could understand the reason why it absolutely had to be implemented in the new limited way, without the old routing flexibility, I can go shed a couple silent tears and move on thanks!

I wish I could, but I don't know. I haven't tried routing or recording in the 3.0.11 release because I was told it wasn't implemented at all. Simply driving a synth using a MIDI plugin as input seems to work nicely in this release (and I appreciated the quick access button in the left-margin) so that's a start, but routing and recording AU MIDI was working in the mythical 3.1b I used to have months ago.

I don't have enough insights in the internals of BM3 to make statements about feasibility or difficulties. In theory it should be possible to handle all MIDI routing before handling audio rendering, but I can imagine it may be tricky to retrofit it into an architecture that was built before the AU MIDI concept was even invented (this may be compounded by the way AU MIDI is handled in iOS: the host may receive audio and/or MIDI from the same plugin simultaneously, and this MIDI may be meant for another plugin which has already been rendered... Just guessing here...).

3.1b has just been entered into the lexicon. All praise 3.1b

[Deleted User]

Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

stormywaterz

When you add a bank that pesky pop up window is gone but the browser window is now opened automatically which I like. The save button is nice. Working in the midi seems smoother but now you have to highlight your midi dot in the window to adjust it instead if tap around the area. I can get used to that. For me it’s a solid update. Running smooth. I sample, use plugins and mix with effects. I keep it simple. No more crashes so far. Thumbs up for intua for me. Sorry I don’t have in-depth review of all the midi stuff all that stuff blows my mind.

I am scarred to do a database scan because I don’t want to lock up my iPad for 15 hours. Anyone done that yet?

bleep

The mythical 3.1b is the fabled mince that was promised. Give it a winter and we'll have it!

I had a quick try yesterday, but failed to get sound from a pad if I tried to add Rozeta LFO to the pad to control knobs in Troublemaker. Is this because the au plugin eats up the midi in notes as well, or did I just set it up in a stupid way?

AudioGus

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It is the backbone of everything bm3 moving forward for me. Amazing

AudioGus

@bleep said:
The mythical 3.1b is the fabled mince that was promised. Give it a winter and we'll have it!

I had a quick try yesterday, but failed to get sound from a pad if I tried to add Rozeta LFO to the pad to control knobs in Troublemaker. Is this because the au plugin eats up the midi in notes as well, or did I just set it up in a stupid way?

First I have heard of the 'b'

LucidMusicInc

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

[Deleted User]

The user and all related content has been deleted.

Jumpercollins

@d4d0ug said:
I’m a little reluctant to post this here, because, well, it’s a workaround and I don’t want to get caught up in the craziness.... but.... I think I’ve found a way to record the midi using the RouteMidi au.

No sound on vid, don’t know why. You might find this useful....

Had a feeling today that the GB tool for midi RouteMIDI might work thanks for posting.

[Deleted User]

@LucidMusicInc said:

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

Ah ok, cheers. I’ll reinstall and have a play.

AudioGus

@MonzoPro said:

@LucidMusicInc said:

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

Ah ok, cheers. I’ll reinstall and have a play.

The transient slicer and high quality pitch shifting pushes it way past 10% for me. Your mileage etc

JohnnyGoodyear

@AudioGus said:

@MonzoPro said:

@LucidMusicInc said:

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

Ah ok, cheers. I’ll reinstall and have a play.

The transient slicer and high quality pitch shifting pushes it way past 10% for me. Your mileage etc

We def. need to see a short video from you showing us the needful viz the sampler in general and this new detection of transients which always sounds suspiciously like something developed for ICE.

[Deleted User]

@JohnnyGoodyear said:

@AudioGus said:

@MonzoPro said:

@LucidMusicInc said:

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

Ah ok, cheers. I’ll reinstall and have a play.

The transient slicer and high quality pitch shifting pushes it way past 10% for me. Your mileage etc

We def. need to see a short video from you showing us the needful viz the sampler in general and this new detection of transients which always sounds suspiciously like something developed for ICE.

😂🤦🏾‍♂️.

Come with the vid @AudioGus

[Deleted User]

The user and all related content has been deleted.

ExAsperis99

There are some reports on the BM3 Facebook group that using Lo-Fly Dirt causes crashes, and the fix seems to be delete Lo-Fly Dirt and reinstall.

tk32

I was skim-reading and didn't read your last two words @ExAsperis99 (above) - suffice to say I LOL'd hard

Skim-reading has become a necessary skill of late.

[Deleted User]

@AudioGus said:

@MonzoPro said:

@LucidMusicInc said:

@MonzoPro said:
Could someone post a really quick idiots guide (that’s me), to what’s better/fixed in the update, and what’s not/removed?

I’ve read somewhere that transient detection is working, and it’s good as a sampler, so I might reinstall if that’s the case.

Ta

It’s exactly 10% better than it used to be, is the best way it can be summed up. Maybe intua needs to hire some marketing interns as the whole .01 and now .011gate has exploded in their faces.

Ah ok, cheers. I’ll reinstall and have a play.

The transient slicer and high quality pitch shifting pushes it way past 10% for me. Your mileage etc

Cheers boss, plenty of miles on the old clock here.

ExAsperis99

@tk32 said:
I was skim-reading and didn't read your last two words @ExAsperis99 (above) - suffice to say I LOL'd hard

Skim-reading has become a necessary skill of late.

haha.
Works every time!