BM3... Will there EVER be another major update?

stormbeats

@wim said:

@stormbeats said:

@wim said:
@stormbeats, no problem. Here ya’ go...
Audiobus preset 'Xequence To GR-16 Pads': http://preset.audiob.us/7wm8zcMJR0B7lHj

@wim brilliant thanks :-)
@wim Does this mean each pad will have its own track If possible can you upload a screenshot. Iam thinking I can than route each GR track/pad from Xequence into seperate tracks into bm3 which can then give GR effects per pad though I think @SevenSystems said pad seperates can only be applied in the drums app. Anyway Iam hogging the bm3 thread so will experiment a bit.
Cool

I think you’re misunderstanding. Pads doesn’t do anything to audio. It only sends midi to apps. Think of it like a hardware midi controller, except that it’s on your device. GR-16 doesn’t send multiple audio outputs, so the audio can’t be split among pads in BM3. For that you’d need to lobby Jim Pavlov to add multiple Audiobus / IAA outputs to GR-16.

@wim yes your right i worked it out . Ive not used midi in a long time as was hardware MPC for many years :-)

[Deleted User]

The user and all related content has been deleted.

[Deleted User]

The user and all related content has been deleted.

wim

@tja said:

@wim said:
@stormbeats, no problem. Here ya’ go...
Audiobus preset 'Xequence To GR-16 Pads': http://preset.audiob.us/7wm8zcMJR0B7lHj

I loaded his, but did not get sound when playing the pads in Xequence.

I then noticed that Xequence did not have set MIDI out configured, so I set this this to AudioBus, assuming that it would work then. But it did not.

What needs to be configured in which App, please?

I thought this would be handled by the AudioBus profile

EDIT: Need to set the MIDI in both Xequence and GR-16 to AudioBus, then it worked. I thought that this would be saved in the AudioBus profile....

I cannot grasp, what mfxConvert is going there

mfxConvert is converting a range of notes to a single note on different channels.

Note / Channel Conversions
From	Ab3/1	A3/1	Bb3/1	B3/1	C4/1	Db4/1	D4/1	Eb4/1
To	C3/1	C3/2	C3/3	C3/4	C3/5	C3/6	C3/7	C3/8
From	C3/1	Db3/1	D3 / 1	Eb3/1	E3/1	F3/1	Gb3/1	G3/1
To	C3/9	C3/10	C3/11	C3/12	C3/13	C3/14	C3/15	C3/16

MrSmileZ

So I decided to jump on beatmaker3 today instead of the MPC live. Crash city! This app is too unstable to use in any serious capacity. I crashed saving a file, I crashed loading a bank, 👾crash crash crash! After around 5 crashes I think I will just wait until an update is released before I try again. I didn’t remember it being this wonky before...maybe I just did all the right things?

tk32

@MrSmileZ said:
So I decided to jump on beatmaker3 today instead of the MPC live. Crash city! This app is too unstable to use in any serious capacity. I crashed saving a file, I crashed loading a bank, 👾crash crash crash! After around 5 crashes I think I will just wait until an update is released before I try again.

Sorry to hear you had so many crashes.

I’ve had the complete opposite experience over the laast few months and —touch wood— haven’t had a hard crash for absolutely ages.

Do you think there maay have been something particular you were doing that may have made it more unstable than usual?

For example... I only use AUv3 nowadays. Really helps with stability.

MrSmileZ

It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

CracklePot

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

Are you using the latest updated everything? Maybe an iPad model related issue?

MrSmileZ

12.9 pro gen 1 (I don’t experience crashes with anything else mind you)
Latest update installed.

tk32

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

I've heard reports that if you load large audio files into the BM3 sampler and continually make lots of trim and edits without re-saving the audio file, the memory management can get out of hand and eventually leads to a hard crash.

We have not managed to identify a concrete set of steps that recreate this issue, but my advice - particularly if you are making lots of trims and edits to large samples - is to (a) save the project regularly and (b) save-out the edited audio files periodically. Saving an edited WAV and then reloading it on the pad seems to help flush RAM and keep BM3 stable - although this is only a 'community hypothesis', and has not been confirmed by the developers (yet).

Hope this helps

[Deleted User]

The user and all related content has been deleted.

AudioGus

@tk32 said:

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

I've heard reports that if you load large audio files into the BM3 sampler and continually make lots of trim and edits without re-saving the audio file, the memory management can get out of hand and eventually leads to a hard crash.

We have not managed to identify a concrete set of steps that recreate this issue, but my advice - particularly if you are making lots of trims and edits to large samples - is to (a) save the project regularly and (b) save-out the edited audio files periodically. Saving an edited WAV and then reloading it on the pad seems to help flush RAM and keep BM3 stable - although this is only a 'community hypothesis', and has not been confirmed by the developers (yet).

Hope this helps

I can pretty much make BM3 crash on command just by auto slicing 64+ slices and then manually playing back slices in the 64+ range by double tapping the slice in the edit window to play them back.

wim

@tja said:

@wim said:

@tja said:

@wim said:
@stormbeats, no problem. Here ya’ go...
Audiobus preset 'Xequence To GR-16 Pads': http://preset.audiob.us/7wm8zcMJR0B7lHj

I loaded his, but did not get sound when playing the pads in Xequence.

I then noticed that Xequence did not have set MIDI out configured, so I set this this to AudioBus, assuming that it would work then. But it did not.

What needs to be configured in which App, please?

I thought this would be handled by the AudioBus profile

EDIT: Need to set the MIDI in both Xequence and GR-16 to AudioBus, then it worked. I thought that this would be saved in the AudioBus profile....

I cannot grasp, what mfxConvert is going there

mfxConvert is converting a range of notes to a single note on different channels.

> > > > > > > > > > > >

Note / Channel Conversions
From	Ab3/1	A3/1	Bb3/1	B3/1	C4/1	Db4/1	D4/1	Eb4/1
To	C3/1	C3/2	C3/3	C3/4	C3/5	C3/6	C3/7	C3/8
From	C3/1	Db3/1	D3 / 1	Eb3/1	E3/1	F3/1	Gb3/1	G3/1
To	C3/9	C3/10	C3/11	C3/12	C3/13	C3/14	C3/15	C3/16

Many thanks!

So, you are sending different notes to different channels, but in this case just to different pads of GR-16.

I suspect that this requires Xequence to send to AudioBus, as AudioBus sends it to mfxConvert and this again to AudioBus.

GR-16 then requires again AudioBus as MIDI In, set to Poly and Virtual MIDI to Off?
The MIDI configuration is not properly contained in the preset.

OK, each pad in GR-16 is controlled by its own channel, corresponding to its pad number. To trigger the pad itself, as if you were touching the pads on screen, you send a C3 on that pad number. This is a difficulty for Xequence because each “instrument” is only one channel. So, mfxConvert is taking different notes on a single channel, and converting them all to C3, but on different channels per note. (See the table) I hope that makes sense.

As far as the routing goes: Xequence is the input in an AB midi lane. The Xequence “instrument” is pointed at AudioBus channel 1. Next comes mfxConvert in the FX slot, to make the conversions. The AB output is Virtual Midi > GR-16 > All Channels. GR-16 is loaded in an AudioBus audio lane, but it doesn’t have to be. So, the routing isn’t as complicated as you listed. Just AB out to GR-16.

You could do the same in AUM as well.

Korakios

@AudioGus said:

@tk32 said:

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

I've heard reports that if you load large audio files into the BM3 sampler and continually make lots of trim and edits without re-saving the audio file, the memory management can get out of hand and eventually leads to a hard crash.

We have not managed to identify a concrete set of steps that recreate this issue, but my advice - particularly if you are making lots of trims and edits to large samples - is to (a) save the project regularly and (b) save-out the edited audio files periodically. Saving an edited WAV and then reloading it on the pad seems to help flush RAM and keep BM3 stable - although this is only a 'community hypothesis', and has not been confirmed by the developers (yet).

Hope this helps

I can pretty much make BM3 crash on command just by auto slicing 64+ slices and then manually playing back slices in the 64+ range by double tapping the slice in the edit window to play them back.

Lol, that (plus automations NEVER worked properly on a single one project) was the main reason I deleted that blip-blip-blip app.... (among PLENTY of others ) .

AudioGus

@Korakios said:

@AudioGus said:

@tk32 said:

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

I've heard reports that if you load large audio files into the BM3 sampler and continually make lots of trim and edits without re-saving the audio file, the memory management can get out of hand and eventually leads to a hard crash.

We have not managed to identify a concrete set of steps that recreate this issue, but my advice - particularly if you are making lots of trims and edits to large samples - is to (a) save the project regularly and (b) save-out the edited audio files periodically. Saving an edited WAV and then reloading it on the pad seems to help flush RAM and keep BM3 stable - although this is only a 'community hypothesis', and has not been confirmed by the developers (yet).

Hope this helps

I can pretty much make BM3 crash on command just by auto slicing 64+ slices and then manually playing back slices in the 64+ range by double tapping the slice in the edit window to play them back.

>

Lol, that (plus automations NEVER worked properly on a single one project) was the main reason I deleted that blip-blip-blip app.... (among PLENTY of others ) .

Curious what your main tools/style of output is...?

Korakios

@AudioGus said:

@Korakios said:

@AudioGus said:

@tk32 said:

@MrSmileZ said:
It was all sample related/file related things with no effects at all...no external stuff....no other apps running

Hopefully there is an update inbound and this app hasn’t been abandoned

I've heard reports that if you load large audio files into the BM3 sampler and continually make lots of trim and edits without re-saving the audio file, the memory management can get out of hand and eventually leads to a hard crash.

We have not managed to identify a concrete set of steps that recreate this issue, but my advice - particularly if you are making lots of trims and edits to large samples - is to (a) save the project regularly and (b) save-out the edited audio files periodically. Saving an edited WAV and then reloading it on the pad seems to help flush RAM and keep BM3 stable - although this is only a 'community hypothesis', and has not been confirmed by the developers (yet).

Hope this helps

I can pretty much make BM3 crash on command just by auto slicing 64+ slices and then manually playing back slices in the 64+ range by double tapping the slice in the edit window to play them back.

>

Lol, that (plus automations NEVER worked properly on a single one project) was the main reason I deleted that blip-blip-blip app.... (among PLENTY of others ) .

Curious what your main tools/style of output is...?

I had a roland sp606 and vp9000 combo,with a kp3 , regret I sold them. Never crashed ,fun to use... Sampling, slicing,never-ending fx, rearranging, re-slicing!!!!...Geist was the only piece of software I liked, but now I am looking at mpc software instead of Geist2. Maschine can't chop more than 16 samples for per/pad fx and push2 seemed more complicated for me (still watching videos). Both of them don't support poly aftertouch (no mpe) and maschine doesn't even support aftertouch....
Maybe for simplicity I might grab an mpc touch and use the ipad as fx heaven ,with StageLight as midi/audio looper, but I don't want to waste money, so no rush !
I had high expectations for BM3 , it should be universal a year ago , launching the desktop version this year and preparing for hardware integration . But many others love it ,so all good. I shouldn't rant, but the video triggered something!

MrSmileZ

I have both the akai force and the mpclive...
I will say this all day long...

As a sampler, when it works...Beatmaker3 is more powerful than the MPC Live/Akai Force-easier editing, faster pad set up, more editing options, better timestretch, modulations galore, and AU plug ins.

Mpclive and force: hands on...no competition, hardware integration to the software inside the units is fantastic...q-link knobs automatically assign per page, touch screen workflow is there, excellent pads, round robin, better swing values, more chord options including user progressions...and when hooked to a windows or Mac OS computer becomes infinitely more powerful. Plus the live runs on batteries so it’s truly portable. Something about being on these units just increases a music vibe...but maybe that’s just me.

Sound vs sound...the mpclive sounds better to my ears than Bm3.

CracklePot

Wouldn’t be better to release more frequent, minor updates?

It seems the long periods of time between major updates makes people all anxious and impatient.

AudioGus

PS/BTW/ETC: I am so stoked with how well BM3 is operating on my new 10.5. Loading up old projects that started to choke my 2017 base model I am now able to do tons of silky smooth AUfx and mixer automation that was just getting too cumbersome before. The trick will be to keep enough cpu/mem bandwidth for mixing now and not eat it up with AU synth layers. Whoot/stoked/etc.

stormbeats

BM3 is king . No crashes for me . Not switched on any of my hardware samplers since I realised the power of bm3. Yes a few tweaks here and there but nothing major. Audio effects per pad and can make a full production anywhere. There is a valid reason why Intua take time to update. When they do they do it with class

[Deleted User]

Happy to see it works for some.
Tbh I never managed to get to the point where cpu would be an issue. It always distracts me before that.
There are plenty of known problems, but at least you can work around those, learn to avoid them... my main problem is the inconsistent behavior, what works today might not work tomorrow. The last app from my collection that reminds me of the iOS from 3-4 years ago.
Midi is still a mess, even simple audio/sample playback tasks are unreliable.

[Deleted User]

The user and all related content has been deleted.

stormbeats

@tja said:

@stormbeats said:
BM3 is king . No crashes for me . Not switched on any of my hardware samplers since I realised the power of bm3. Yes a few tweaks here and there but nothing major. Audio effects per pad and can make a full production anywhere. There is a valid reason why Intua take time to update. When they do they do it with class

Could you describe your regular working steps in BM3?
Anything with MIDI?

@tja hi not too much midi but here and there and had no issues with midi at all
I’am more a sampling producer. Bm3 is very powerful. Few tweaks needed for the sample edit window (shaky start/end handles) and the zero snap bug but all else is excellent.

hansjbs

@stormbeats said:

@tja said:

@stormbeats said:
BM3 is king . No crashes for me . Not switched on any of my hardware samplers since I realised the power of bm3. Yes a few tweaks here and there but nothing major. Audio effects per pad and can make a full production anywhere. There is a valid reason why Intua take time to update. When they do they do it with class

Could you describe your regular working steps in BM3?
Anything with MIDI?

@tja hi not too much midi but here and there and had no issues with midi at all
I’am more a sampling producer. Bm3 is very powerful. Few tweaks needed for the sample edit window (shaky start/end handles) and the zero snap bug but all else is excellent.

I sample and work with midi and AUV3 apps. Last crash I had using BM3 was about a month ago and that was because I was trying to use KB-1 as is. Once I got Audiveek's app no more issues. Works flawlessly over here and I use BM3 everyday.

stormbeats

@hansjbs said:

@stormbeats said:

@tja said:

@stormbeats said:
BM3 is king . No crashes for me . Not switched on any of my hardware samplers since I realised the power of bm3. Yes a few tweaks here and there but nothing major. Audio effects per pad and can make a full production anywhere. There is a valid reason why Intua take time to update. When they do they do it with class

Could you describe your regular working steps in BM3?
Anything with MIDI?

@tja hi not too much midi but here and there and had no issues with midi at all
I’am more a sampling producer. Bm3 is very powerful. Few tweaks needed for the sample edit window (shaky start/end handles) and the zero snap bug but all else is excellent.

I sample and work with midi and AUV3 apps. Last crash I had using BM3 was about a month ago and that was because I was trying to use KB-1 as is. Once I got Audiveek's app no more issues. Works flawlessly over here and I use BM3 everyday.

@hansjbs it seems a lot of people dont understand the app. It starts with the “mind” .Good to hear a fellow bm3 user using it in a way that works well . Peace

YZJustDatGuy

Introducing AUv3 does make BM3 more likely to crash but I’ve had it crash in the sampler a few times as well. I’ll be trimming something and it’ll just crash. Doesn’t happen too often tho. I use airplane mode + WiFi & Bluetooth. For some reason audio apps are more stable that way

AudioGus

I find adding, removing, re-adding, removing and automating AU fx is a minefield of crasheroo.

ipadthai

I haven’t read this thread but I just finished a Chinese meal and my fortune cookie said, “He who wait for BM3 update wait a very rong time.”

AudioGus

@ipadthai said:
I haven’t read this thread but I just finished a Chinese meal and my fortune cookie said, “He who wait for BM3 update wait a very rong time.”

that is so rong. how dare you.

AudioGus

@stormbeats said:

@hansjbs said:

@stormbeats said:

@tja said:

@stormbeats said:
BM3 is king . No crashes for me . Not switched on any of my hardware samplers since I realised the power of bm3. Yes a few tweaks here and there but nothing major. Audio effects per pad and can make a full production anywhere. There is a valid reason why Intua take time to update. When they do they do it with class

Could you describe your regular working steps in BM3?
Anything with MIDI?

@tja hi not too much midi but here and there and had no issues with midi at all
I’am more a sampling producer. Bm3 is very powerful. Few tweaks needed for the sample edit window (shaky start/end handles) and the zero snap bug but all else is excellent.

I sample and work with midi and AUV3 apps. Last crash I had using BM3 was about a month ago and that was because I was trying to use KB-1 as is. Once I got Audiveek's app no more issues. Works flawlessly over here and I use BM3 everyday.

@hansjbs it seems a lot of people dont understand the app. It starts with the “mind” .Good to hear a fellow bm3 user using it in a way that works well . Peace

First you get the muscle memory. Then you drop the beats. Oh and a 10.5 didn't hurt.