problem with macros and data wheel in PROG mode

greets

I've been using Bome's midi translator for controlling the MPC with macros. I keep getting this one annoying "bug?" in the program mode (not all the time), the data wheel works not like it's supposed to, it's in scrolling mode and I can't get it to work as usual, i.e. choose samples, change the tuning, etc... The cursor just keeps jumping from one field to the next.

Any ideas how to fix this?

thanks in advance

This isn't an answer to your question, but maybe it's a good idea to focus on the actual music your making instead of the things your doing now. I had my way with Bomes/midicontrollers/shortkeys/macros a while back using Ableton and Studio One, lost a lot of time figuring out stuff i didn't need in the first place.

Just my 2 cents.

I know what you're saying, but I really need these macros, without them using the mpc becomes a real pain for me.

I reckon it must be a bug because it only happens in the program screen, perhaps some macros are too fast for the mpc.

wow, good to see more people using macros.
post up the macro and its function and i'll see if i can get it to work sometime.

do you mean the bome translator file?

well, the midi file preferably, assuming you're using the standard button layout as posted here

viewtopic.php?t=146154&f=25

Bathmutz wrote:it's a good idea to focus on the actual music your making instead of the things your doing now

Speaking of..

yeah, that's crazy.
if you have to walk 2 miles to get water for your horses, you ought to take the time to dig a ditch.
i can't tell you how much time my macros save me, and how much more they open up jjos.

consciously or subconsciously, you are less likely to use features that are inconvenient because you don't want to go through the harangue of getting to them. like specific midi CC edit pages.

ok here is the Bome preset

just copy and paste this into a text file and save it with bmtp extension.

Make sure that outgoing midi message corresponds to the buttons in the MIDI to Button screen of JJOS.

[Project]
Version=1

[Preset.0]
Name=Program Rename
Active=1
Name0=Program Mode
Incoming0=MID19F2C64
Outgoing0=MID19F5464
Options0=Actv01Stop00OutO00
Name1=Shift
Incoming1=MID19F2C64
Outgoing1=MID19F3E64
Options1=Actv01Stop00OutO00
Name2=UP
Incoming2=MID19F2C64
Outgoing2=MID19F3B64
Options2=Actv01Stop00OutO00
Name3=Shift - Note Off
Incoming3=MID19F2C64
Outgoing3=MID19F3E00
Options3=Actv01Stop00OutO00
Name4=WINDOW
Incoming4=MID19F2C64
Outgoing4=MID19F5364
Options4=Actv01Stop00OutO00
Name5=Right
Incoming5=MID19F2C64
Outgoing5=MID19F4064
Options5=Actv01Stop00OutO00
Name6=Right
Incoming6=MID19F2C64
Outgoing6=MID19F4064
Options6=Actv01Stop00OutO00
Name7=Right
Incoming7=MID19F2C64
Outgoing7=MID19F4064
Options7=Actv01Stop00OutO00
Name8=Left
Incoming8=MID19F2C64
Outgoing8=MID19F3564
Options8=Actv01Stop00OutO00
Name9=Data +
Incoming9=MID19F2C00
Outgoing9=MID19F3364
Options9=Actv01Stop01OutO00

This macro is triggered by a G#2 Note (Velocity 100) on ch. 16.

It jumps straight to the Naming screen and lets you rename or copy/paste a programs name (of current track).

The problem that I described in the first post happens after you finished with renaming and close the window. A "solution" is to keep pressing the cursor up and left buttons 'till the DATA wheel starts to function properly.

I will try the piz midi looper, pretty sure it will work much better than Bome since I can make the macros much slower.

if you're using REAPER with SWS extensions, you can do it even easier than with PIZ -
create a midi file, save it, and then load it into the SWS resources: media file

then you can assign a keyboard/midi note to trigger this midi file and fire it off at your MPC

unfortunately i can't read that bome preset unless you translate each midi note into its accountable action, then i can recreate it. but try feeding it to the mpc slower (you can even scrub through the action and watch each key press if you create the midi file in a DAW) and see where it goes wrong.

Nym wrote:but try feeding it to the mpc slower (you can even scrub through the action and watch each key press if you create the midi file in a DAW) and see where it goes wrong.

I only have Bome classic, it does not have the action delay option that the Pro version has.

unfortunately i can't read that bome preset unless you translate each midi note into its accountable action, then i can recreate it.

Every translator in the preset is named after the function it does, so e.g. the first translator:

Name0=Program Mode
Incoming0=MID19F2C64
Outgoing0=MID19F5464
Options0=Actv01Stop00OutO00

opens up the program mode, i.e. it sends midi note 19F5464 (HEX) to the MPC to open the Program window.

Shift = Shift button press, UP = cursor Up, Shift - Note Off = Release of the shift button and so forth. You could change the Outgoing midi note to correspond to your "midi to button" assignments or you could change the midi to button settings in the MPC.

But ye, I think the midilooper method is better and is a quicker way to make macros. I'm actually thinking of installing energyXt and using midilooper as VST plugin.