BeatMaker 3 Update 3.0.14

Sequencer1

@Korakios said:

@Sequencer1 said:
@Korakios Launch BM3 first. Be sure the 'AUM (Port X)' IAA plugin is loaded to Pad 1 in a Bank. Add an Audio Track, have it's input be the appropriate Bank that you set up earlier. But it's easier to just record the stems in AUM and export to BM3 using 2x Files App in side-by-side mode.

Thanks! it works fine in AB3 too ,although I get some dozens of midi ports in BM3, more than 50 ports of the same AU (model D for example)

Screenshot?

Korakios

When I add an app via AB3 it creates new midi ports

Strizbiz

@echoopera said:
Got this going on today and so far i am remembering all the things i loved about BM3:

Wired for the following:
1-4 Macros
Drum Pads
Transport Controls
Octave-/+
Banks < | >
Solo Mute
Metronome on/off

Lots of good in here to enjoy.

Looks great, I’d love to see what I can do with BM3 and my APC40 mk2 but I’m afraid to update BM3 until I make sure the update didn’t break anything that already works for me.

Sequencer1

@Korakios said:
When I add an app via AB3 it creates new midi ports

Yup, I see 26 Basslines and 26 Model Ds listed. When using AB3. Don't get them when using AUM. I remember someone bringing this up long ago, but don't remember the reason. Anyone know?

skulptur_sound

Is this update as stable as the previous?? I’m wanting to update but am holding off just Incase. Please let me know.. how’s turnado working with it? Also fabfilter? Two of my main AUs.

BitterGums

@Lil_Stu07 said:
.. My biggest fear has been getting deep in to something, the app crashing and losing all that time. Really wanting this to be stable and regularly maintained..

Make sure you save often and save using the Save As function. Very reliable. The more time you spend with it the more you understand the workflow and the little housekeeping steps that keep things running smoothly.

stormbeats

@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

Gravitas

@WillieNegus said:

@espiegel123 said:
Is the consensus that this update is at least as stable as the version it replaces?

All good so far for me.👌🏽

Same here. 👌🏽

tk32

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

hansjbs

@tk32 said:

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

We can ask but it's definitely not something in their radar.

wim

It sucks for plugins that don't provide their own, but then you can always use bank-save for those relatively rare plugins. I prefer to save in the plugin if possible so that the preset is available in all DAWs. If you save in the host then it's not available to other hosts.

stormbeats

@tk32 said:

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

@tk32 fair point. But .... not every AU Plugin has their own preset management. Also it seems it was in the bm3 plans from the start because the option although greyed out “save au preset” is there in the save preset plugin list

Carnbot

@wim said:
It sucks for plugins that don't provide their own, but then you can always use bank-save for those relatively rare plugins. I prefer to save in the plugin if possible so that the preset is available in all DAWs. If you save in the host then it's not available to other hosts.

Yeah we need more hosts and plugins to enable AU preset sharing, probably most developers aren't even aware that it exists as a feature as Apple aren't exactly great at documenting features.

SevenSystems

@tk32 said:

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

Why would that be better? It means you have a disjointed experience and have to mentally switch between every single plug-in's own UI/UX for preset management, plus the burden on each plug-in's developer to actually implement it -- not to speak of the inability for the host to have global patch management across plug-ins (say, I want to browse all "Bass" sounds across all AUs.)

stormbeats

@SevenSystems said:

@tk32 said:

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

Why would that be better? It means you have a disjointed experience and have to mentally switch between every single plug-in's own UI/UX for preset management, plus the burden on each plug-in's developer to actually implement it -- not to speak of the inability for the host to have global patch management across plug-ins (say, I want to browse all "Bass" sounds across all AUs.)

@SevenSystems I agree 100% .

Samu

Starting with iPadOS13 iOS/iPadOS got standardized way to actually save presets.
Before that it was 'read only' meaning hosts could not store presets in a place that could be accessed by all other hosts.

And to cater users who for one reason or the other refuse to keep their iOS/iPadOS version at least somewhat up-to-date developers have to resort to creating custom preset managers to allow backup and sharing of presets among other things.

Now that iOS/iPadOS has a way to manage presets I suppose that is the way to go but that would mean that users wishing for more unified preset management should not fear iOS/iPadOS updates....

Even though iOS/iPadOS now has this 'new' way of storing presets that folder is not accessible to Files.app for easy backup.
(In practice I guess it's something similar location as ~/LIbrary/Audio/Presets/ on MacOS).

So yeah, some decisions are though to make but considering the sandboxed nature of iOS/iPadOS this is something we'll have to 'live with' for now and the most flexible one is to let the Plug-In handle the preset management if preset sharing across multiple hosts is needed.

I don't see NS2 as the 'holy grail' for preset management even though some like it.
(It's not that 'smart' when it comes to updating the preset list and keeping them in sync).

Even on the desktop very few hosts actually index all presets from all installed plug-ins...

Cheers!

hansjbs

Ok. So everyone that wants this feature go ahead and message Vincent to request this. We don’t tell Intua what to implement. We just help them test, try to catch as much bugs as possible and provide feedback before release

wim

@SevenSystems said:

@tk32 said:

@stormbeats said:
@tk32 do you know if the Intua team are adding Save AU presets. This is much needed

I think they feel it's better if the plugin provides its own preset management system.

And I tend to agree.

Why would that be better? It means you have a disjointed experience and have to mentally switch between every single plug-in's own UI/UX for preset management, plus the burden on each plug-in's developer to actually implement it -- not to speak of the inability for the host to have global patch management across plug-ins (say, I want to browse all "Bass" sounds across all AUs.)

Because if you save a preset in host A's preset system, then want to use that preset in host B, you can't because it isn't there. Start over for every ... single ... host.

Still ... a host without a preset save system as an option? That's half-assed (or just plain stubborn) IMO. Off the top of my head I can't think of another host that doesn't have the ability to save presets. (Though, to be fair, bank save is somewhat the same idea.)

I'm all for developer individuality. But when you're at odds with every other app out there ... maybe, just maybe, it's time to re-evaluate.

tk32

OK. Here are my arguments FOR/AGAINST preset management by the host...

(Happy for people to correct anything I get wrong)

FOR

• It would provide preset management for a small minority of plugins (mostly older ones) that do not provide their own preset system. Some examples are the Blamsoft plugins, Klevgrand Enkl.
• It would allow the potential for the host to build a unified preset browser so that presets could be chosen from one big list rather than having to remember and load the relevant plugin first. However, Note - this may be tricky if the plugin has it's own tagging system (see bullet 5 below)

AGAINST

• Except for a few small cases (mostly older plugins, see bullet 1 above), plugin-based preset management has become a standard. Devs know this is one of the things we always expect in new plugin releases.
• Any preset you store in the host would not be available in other hosts.
• You would end up with two places presets can be stored: the plugin or the host. This is messy. Would the host's browser have to mark original presets differently? Make them read-only?
• The host would have to maintain a very large database of presets that updates every launch (in case there are new plugins, or updated plugins with new patches available)
• Some plugins already have their own multi-tiered and complex preset browsers (eg Synthmaster One) which allow filtering by metadata. How would the host support this as they are unique to each plugin?
• Unless host preset management became universal across every possible AUv3 host, plugin devs would still have to provide their own preset browser, just in case. Now you have two competing systems.
• What happens for plugins that have IAP presets?
• What about the nice 'load random patch' buttons available in some plugins? Does pressing this override the host's preset? What list of plugins is it selecting from?

Having said all this, I can see a good argument for hosts allowing some kind of project-based state-saving for plugins that only get stored in the project, a bit like the memory feature on a calculator. There are times I would like to temporarily save several states of a plugin while I tweak away, knowing that I can A/B between them or switch back to an earlier state without having to save permanent presets just for this specific purpose.

SevenSystems

@tk32 some good points. Didn't think it through while I typed my rant sipping my coffee at Costa. So I mostly stand corrected 🙂

Korakios

Sooooo, still automation range is not fixed
I tried to use the AU parameter view for accessing multiple parameters but the knob speed is super slow, plus sometimes it causes audio glitches (must restart BM3)

PS. I guess midi fx post recording is not planned for 2020?

Samu

Who knows, maybe the next beta is already in the works or something...
(Lately I've mostly been sampling using MPC Beats, Renoise & Logic Pro X on the desktop using my iPad Air 2 as a sound module thru IDAM).

stormbeats

@Samu said:
Who knows, maybe the next beta is already in the works or something...
(Lately I've mostly been sampling using MPC Beats, Renoise & Logic Pro X on the desktop using my iPad Air 2 as a sound module thru IDAM).

@Samu I have the MPC 2.0 software for Mac Desktop which is the more advanced version of MPC Beats. I do not miss it at all. Too much menu diving for me. But MPC Beats might be easier on the eye. Might give it a spin but got so used to the touchscreen ipad/bm3

AudioGus

@Korakios said:
Sooooo, still automation range is not fixed

Someone mentioned that this is being worked on right now. It would be awesome if that also includes retaining automation for splitting and joining clips but just getting the value ranges sorted after all these years would be sweet.

hansjbs

@AudioGus said:

@Korakios said:
Sooooo, still automation range is not fixed

Someone mentioned that this is being worked on right now. It would be awesome if that also includes retaining automation for splitting and joining clips but just getting the value ranges sorted after all these years would be sweet.

. We just want to make AudioGus happy. That’s all.

AudioGus

@hansjbs said:

@AudioGus said:

@Korakios said:
Sooooo, still automation range is not fixed

Someone mentioned that this is being worked on right now. It would be awesome if that also includes retaining automation for splitting and joining clips but just getting the value ranges sorted after all these years would be sweet.

. We just want to make AudioGus happy. That’s all.

Awww, well throw a little somethin in there for yourself eh?

hansjbs

@AudioGus said:

@hansjbs said:

@AudioGus said:

@Korakios said:
Sooooo, still automation range is not fixed

Someone mentioned that this is being worked on right now. It would be awesome if that also includes retaining automation for splitting and joining clips but just getting the value ranges sorted after all these years would be sweet.

. We just want to make AudioGus happy. That’s all.

Awww, well throw a little somethin in there for yourself eh?

He has my list

Lil_Stu07

Just opened this up after a short iOS hiatus. And I must say, in no time flat I have a whole beat ready to sequence. It's running smooth as butter. Have yet to get this far with BM3. Fabfilter on every channel. No slowdown, no crash.

Stuntman_mike

Beatmaker!!!!!! 😠 Crashed in the middle of a fire track and I forgot to save... I still love BM3 though. 😆 REMEMBER: Save your tracks after you press stop.

FlowingRobes

Hi,
Here is 2024. Most recent bm3 vers.....3.0.16 I think.

I get 40-50 midi ports open in bm3.when using audioibus with bm3 and hosting auv3 in AB.

It also definitely needs some sort of auv3 preset management. Testing DPP's auv3 and I can't use the DPP presets in bm3.

Annnnd, the big 'winner".....when recording with quantize off with a percusion controller.....ie multi pad or my ekit .......its a freaking mess. Dropped notes, notes shifted..unusable to record midi. I believe it has to do with note gate time vs fast played notes. A "press roll" and about a third if the notes don't record or are placed at the first beat! A mess.

OTOH for my application the real time time stretching is still the best. I play ac and e drums and use my multi pad..dtx multi 12 on the keft side with tge 12 pads set to focus actions. and tap in a tempo with a foot pedal and bm3 stays locked to the tempo......link provided by midi link sync. The dtx sequencer locked with midi clock.

Edit...when testing bm3 midi recording I just used bm3. Even w/o an auv3. I can SEE the missed notes in a press roll.

BTW....I recorded in helium and atom2 hosted in ab. Recorded faithfully.

If this can't be fixed then bm3 becomes a REAL good loop player for me. Nothing more.

I might have to go have a cry if this is the case:-)

Edit..I posted in this thread because there are posts here documenting the multiple midi port bug and no auv3 preset management.

Does anyone know the best way to report bm3 bugs? Thank you for reading.

Edit I'm on a 8th gen iPad running 14.3. If that means anything.