MIDI Designer Q&A - Recent questions and answers

Roland TR Pattern and Kit Display - Demo of new 10.5.0 SysEx string capability

Mon, 03 Jun 2024 05:28:42 +0000

SysEx Strings Demo with Roland TR 6s / TR 8s

This simple layout demos the MIDI Designer new ability to read text data from MIDI devices.

Enable Tx and Rx edit data on the TR.

Use the query buttons to load the list of patterns and kits into the pickers.

Once loaded, use the pickers to select and display current pattern, next pattern, and current kit names.

If you edit a pattern or kit name on the TR, requery to update the layout.

Behind the scenes on the query:

Depressing query button causes the following sequence:

Disable transmit from picker (don’t want to drive hardware all over while reading names) - Xmt Relay 1
Enable picker MIDI receive - Rcv Enable Relay
Scan (request) the 128 names - Scanner
Disable picker MIDI receive - Rcv Enable Relay
Enable transmit from picker - Xmt Relay 1
Recall active pattern / kit prior to scan action - Xmt Relay 1

Named Ticks with 0 or 127 values enable / disable the controlling buttons in the correct sequence. We add an extra tick before turning off receive to ensure the last name report is received.

No StreamByter is required to implement kits.

Inbound StreamByter is used for patterns to compress the V values from 20 00 - 2F 70 to 0-127 to simplify use as a SuperControl. We could use a 16384 named ticks control to do the remap, but that is more cumbersome than doing the remap in StreamByter.

Look for this capability to get added to the existing MIDI Designer layouts.

Answered: How to create a colour indicator

Sun, 02 Jun 2024 15:35:59 +0000

No easier way at present.

To show the track colors on the TR managers I stack 13 panels, one with each color, then have color managers as shown. 11 tracks with 13 panels each. Done it once, and not sure I will do it again. I really need to adjust the colors to be closer to the hardware, but digging into the piles of panels is not trivial.

LAYOUT: CHASE BLISS BLOOPER

Wed, 29 May 2024 14:12:38 +0000

29th May 2024: Blooper Layout Version 1

How to use: 1) Install Midi Designer from the Apple App store 2) Download the layout file below and load it into the app 3) Open app menu -> config -> save layout. Optional - but it will save you a bit of time if you are switching layouts in future

Connecting:

Wired: Plug your iPad/iPhone into a USB enabled midi device that’s hooked up to a Chase Bliss compatible Midi box. I have tested this with a HX Stomp.
Bluetooth: I highly recommend the CME Widi jack. Use a midi box that's switchable to work with Chase Bliss pedals (Ring active). Because it's switchable you can then use any stereo TRS cable. I am using the Disaster Area Midi Box 4. Do not try using a Widi jack plugged directly into the Mood pedal's midi input - it won't work because the TRS cable CME use is wired up the standard way.

Midi Channel: Set to 9. You can easily change these by:

Tapping the More menu (top centre) then design mode
Double tap a tab and go to the controls pane.
Click Renumber controls (Channel & CC), and pick the channel you want to change everything on the tab to. Make sure Channel only is selected,
Tap apply.
Repeat the process for each tab with controls on them (it's quick and should take 1-2min to do). Save your layout so settings are retained (under More/Config/Actions/Save Layout As)

----

Presets:

Saving in-app presets: Use the ticker to pick the slot -> Hit Save -> Label your preset
If you want to see what the preset saving module is connected to or edit them:
- Go into design mode -> double tap the ticker -> Relationships tab.
- Then look at the subcontrols
- To add subcontrols: Hold your finger over the "drag to subcontrol" button then gliding it over the control. Then hit apply and save your layout.
- To remove subcontrols: Swipe from right to left on the list. Then hit apply and save your layout.

A NOTE ON PRESETS:

If you are adding in-app presets, make sure you save your layout at the end of a session. This will write them to the layout file. Open the App Menu -> Tap Config -> Then tap Save Layout in the Actions Tab
If you happen to open design mode you'll notice there's a lot of panels with controls that are hidden in play mode (the yellow boxes). Don't delete them - they are super or sub controls, and necessary for mapping and functionality to work. Feel free to tweak other controls though - e.g if you want to change a colour/size, move them elsewhere or switch out a dial of a fader etc.

A tip for those wishing to edit things: When you load this layout in it will be locked from making changes. But if you go into design mode, then tap on the padlock you can unlock elements to make changes. The app refers to 'Others' for controls (e.g buttons & sliders).

-----

If you'd like to make your own midi layout or modify what I created, Scott UHL Music has a really great video on how to use the app

----

If you spot anything that has not been mapped correctly, let me know and I'll do my best solve them - You can see what commands are going out by using the log function in the more menu. If you enjoy using this layout I'd love to know in the comments or via Instagram.

----

Disclaimers

This is a non-official layout. Use at your own risk. Joel and the Chase Bliss team have given my their blessing though.

I am not connected to Chase Bliss, and I don't work for Midi Designer. I made this for my personal use, and thought I'd post it here so other people can enjoy using it.

For Midi Designer Pro app issues please contact the Midi Designer support team

For issues with pedal hardware or software please contact Chase Bliss.

Layout: Akai MIDImix

Sat, 25 May 2024 21:51:57 +0000

Layout for Akai MIDImix with all features
and included complete working lights

[

Answered: New Data Type - SysEx String

Sun, 12 May 2024 15:47:49 +0000

Use case 1

SysEx strings populate a picker that shows custom program, tone, or patch names for recall. The picker is a supercontrol- subcontrols recall the selected patch/tone/whatever.

Loading supercontrol

While loading, enable / disable disconnects it from the subcontrols, and “capture” string option turned on

A “macro” steps through the patches, recalling and storing the names

Can also build a single recall to bring in a single changed name instead of scanning through entire control.

Using supercontrol

capture string is turned off, enable turned on

Operating the picker activates subcontrols that recall the desired patch

Use case 2

Display current selected patch / tone / whatever name

In this instance, recall only then use as a label value source.

Wired connection between iPad and computer

Tue, 30 Apr 2024 20:44:32 +0000

Thought I'd share this. I have no affiliation with the company in question; I'm just a satisfied customer.

My solution to date for a wired connection between iPad and laptop has been a pair of mio USB/MIDI cables, connected by a pair of back-to-back DIN socket adapters.

A couple of weeks ago I discovered the device below, decided to give it a chance, and all seems well. It features an advantage over my old solution, in presenting 4 virtual MIDI ports at each end of the connection, which could open up new possibilities.

Unfortunately the only explanatory video I've seen of this device is in Spanish, but I could get the gist, at least enough for me to part with my money.

https://sevillasoft.com/index.php/midi-usb-usb

Roland TR-8S Manager

Sat, 20 Apr 2024 05:05:22 +0000

This is the same layout at the TR-6s, with the additional five tracks for the TR-8s.

See https://mididesigner.com/qa/10061 for more information.

For ease of maintenance, the layout is built with the TR-6s model ID, then SB is used to remap to the TR-8S model ID. This makes it easier to add functionality once to both layout versions. If you borrow controls to use in other layouts, you may want to change the model ID on the controls from 6D to 45 instead of relying on the SB translation, especially if you have other TR controls.

Dan and I have been bouncing ideas around as we build these TR layouts. One question is can you do an auto-load after kit changes? Yes, but how do you know the user has finished scrolling through kits? You don't want the settings scanner to start while the kit is still scrolling, potentially loading 1/2 of one kit settings, 1/2 of another. You can set a timer, but you might not want to always wait for the timer, or again you might start scrolling again. So we just do a subtle prompt. If the layout detects a kit change, but LOAD has not been activated, the LOAD button changes color as a prompt. initially had an arrow appear next to the button, but the color change is more subtle.

If you knew that only a single kit change would come in, such as under DAW control, you could automate the LOAD.

Roland TR-6S Manager

Thu, 18 Apr 2024 04:06:23 +0000

Mixer

Traditional mixer view, with key track and kit parameters.
Current kit name and number are at top.
Load settings after kit change. Load button will change color when LOAD is required.

Functional flow view of all effects and key settings.
To the right are quick-setting buttons, including DRY, which disables all effects
Load when first used, and after changing Master Effect from MD

The TR must be connected via computer for this layout to work. The TR does not send SysEx over DIN MIDI necessary for the layout to function.

Check back as we add more capability.

See https://mididesigner.com/qa/10063 for TR-8s version

You can test this version on the 8s with the following SB code:

Output

If M00 == F0 41 10 00
If M04 == 00 00 6D
Ass M06 = 45
End
End

Input

If M00 == F0 41 10 00
If M04 == 00 00 45
Ass M06 = 6D
End
End

Answered: Roland TR-8S Sysex: What's what?

Wed, 10 Apr 2024 15:28:29 +0000

First cut at some specific message addresses

Answered: How to deal with toggle/non-toggle CC button?

Tue, 09 Apr 2024 00:14:05 +0000

To check, you need to to send Cc xx 00 Cc xx 7F to toggle state either on or off.

Solution 1: Make a knob, MIDI is desired Cc channel & number, named ticks, three ticks, values are 127, 0, 127

Make a button, toggle, no send / receive, supercontrol of the knob, options as super - snap to value. Start at 10ms and adjust timing as needed.

Solution 2: We can also trap in StreamByter, change any instance of Cc xx to the 00 7F sequence, esp now that Dan has fixed delays.

Something like:

If M0 == B2 32 # desired Cc and channel here
   SND B2 32 00
   SND B2 32 7F +D100 # Adjust delay as needed
   Block
END

Prolly more solutions.

Answered: [Manual] What does "Make Screenshots" do?

Mon, 08 Apr 2024 17:22:23 +0000

[DRAFT]

Example Output

https://www.youtube.com/shorts/BVKDWzf1zRc

Screenshot facility takes all combinations of screenshots, downsizes them a bit and saves them to the Documents folder for the App.

iPad will do all combinations, but respects One Big Page and Change Banks Together.
For iPad layouts on iPhone
1. App will create all combinations, but respects One Big Page and Change Banks Together
2. App will check if there are combinations from iPad on disk (hopefully a subset) and will use those to determine which shots to limit to.
3. App will take three screenshots per page -- left, middle and right -- which works in Portrait mode.
For iPhone layouts on iPhone: App will shoot all pages in all banks.

Live keyboard rig control surface (GigPerformer)

Mon, 01 Apr 2024 16:34:08 +0000

This is my layout for controlling my plugins. All midi controls my Mac running Gig Performer 4 which hosts my plugins:-

Piano - Synthogy Ivory 3, Rhodes - Rhodes pro V8, Synth - Synthmaster 2, Kontakt with voice and brass samples, Hammond - Hammond B3x plugin.

I use image panels from free png images from the internet of buttons that I superimpose at various transparencies over the stock MD buttons and knobs. The hammond I have also used a wood image on the panel. The other panels have a black image panel with tranparency that has some highlights on it to make it look more real.

I use panels to reveal and hide to keep my live status simple and clear. I have to use a ‘shape’ that is black to hide or dim that is attached to a transparent panel, as the stock ‘black’ panel is dark grey and doesn’t quite work. I have kept the hiding panels slightly transparent and not completely black so that I can still make out the volumes positions etc before I switch on that sound.

i’ve also put orange ‘dummy’ buttons behind the Rhodes knobs to give them an orange ring glow.

Hope this is useful to someone.

Answered: Streambyter delay confuses MD layout

Mon, 01 Apr 2024 15:56:12 +0000

Corrected in Next Beta 10.3.0, 20240331.2144. Times look pretty good both in and out.

Answered: StreamByter Delays Not Working

Mon, 01 Apr 2024 15:55:30 +0000

Corrected in Next Beta 10.3.0, 20240331.2144. Times look pretty good both in and out.

Answered: Utilizing MIDI Designer Pro with analog gear

Sun, 31 Mar 2024 03:05:35 +0000

Hello, could you upload your layout?

Create Virtual StreamByter "Through" Path

Tue, 19 Mar 2024 05:46:08 +0000

From the help desk files - a user is attempting to use the MD StreamByter rules as they would be in a stand-alone instance of StreamByter - between a hardware keyboard and an iPad music app.

But - the MD architecture supports StreamByter rules for processing MIDI messages going to or from the control surface in support of MD controls, not, for example, to transpose all notes from the keyboard to the music app.

Sending information THROUGH MD requires creating a pair of controls, one for input, one for output, for each individual message to be passed.

This hack uses SB to create a new, virtual SB path for two or three byte messages, enabling StreamByter processing between two external devices under MD control. We still need a single pair of controls to send a stimulus from input rules to output rules when there is data waiting to send.

The hack support most SB processing on the message stream, with a few limits - any dynamic changes (i.e., controlled by the MD surface) must use SB II rules. You can use SB 1 rules in the input processing, but they cannot be modified by control surface actions.

Logic:
Input rules
- Filter input messages (default is all two or three byte types, can tighten filter - such as only notes on CH 5)
- Perform any static transformation (fixed channel change, fixed transform)
- Shove the messages into the global array (queue)
- Activate the trigger message, waking up output rules
Output rules
- locate next unsent ouput message in the G array
- Perform any dynamic transformation - such as transpose by a variable amount set on control surface
- Send the modified message
- Repeat until queue is empty

The example does a transpose of all notes on channel 4 by the amount set on the control surface.

The hack only works for two and three byte messages. It could be rearchitected to handle some short SysEx messages, but that would be much more complex.

The new virtual route is shown via the orange arrows in the diagram. With the hack, all SB message path possibilities are covered: input, output, feedback, and through.

Note - there is a "through" option for many inputs in the connections page. But this is a straight pipe, and does not enable SB processing on that path.

Additional details in the SB comments.

To use in a production layout, you will need the input and output rules, the two stimulus controls, customize the filtering, static, and dynamic rules as desired, and add any controls and code to store the dynamic control values.

This hack is pretty much limited to a two device architecture.
- In typical use, MD would typically be in a star architecture - i.e, at the center, talking to and listening to all devices.
- But flow processing means it now needs to be between two devices, listening to one device, sending to a second device.
- These two architectures are pretty much exclusive, especially as you go beyond two devices.
- This is why the MIDI Fire app remains a much better solution for the general case - letting you drop a SB module as needed specifically between one particular device output and the desired output, and using MD if needed to control the SB modules.

Answered: Can we have StreamByter sub-routines implemented?

Mon, 11 Mar 2024 23:44:36 +0000

Implemented in 10.2.0

Answered: Stream Byter Subroutines don't work

Mon, 11 Mar 2024 23:42:30 +0000

Implemented in 10.2.0

Answered: Multiple MIDI ports?

Mon, 11 Mar 2024 23:26:33 +0000

Sort of a duplicate of 9662. Going to add this as a reference for that user request in the database.

Request is to behave more like Ableton (for example), where you target input / output to a particular port as well as channel.

Trying to think how to deal with legacy layouts. By default - all ports enabled for all controls? Port control is an advanced feature? Other ideas?

And the reverse problem - as soon as you start configuring to be very specific on ports, then you have the reconfigure problem if the interface changes - if you use Ableton or Logic for example, you know about having to reconfigure when plugging in a new device. For example, my Jupiter X layout doesn't care which port the Jupe is on. But if I have to specify, it could be found on:

Jupiter Xm MIDI Out 1 / In 1
Jupiter Xm Bluetooth
via WIDI DIN adapter
via a multi-unit adapter (iConnect Audio 4+, in my case)
via a generic DIN adapter

Chase Bliss Warped Vinyl Hi-Fi

Sun, 10 Mar 2024 18:43:44 +0000

UPDATES:

15th March: Fixed follow Midi Clock toggle

Connecting to the pedals:

Wired: Plug your iPad/iPhone into a USB enabled midi device that’s hooked up to a Chase Bliss compatible Midi box. I have tested this with a HX Stomp.
Bluetooth: I highly recommend the CME Widi jack. Use a midi box that's switchable to work with Chase Bliss pedals (Ring active). Because it's switchable you can then use any stereo TRS cable. I am using the Disaster Area Midi Box 4. Do not try using a Widi jack plugged directly into the pedal's midi input - it won't work because the TRS cable CME use is wired up the standard way.

Midi Channels: You can change these by going into design mode. Then double tapping each tab and going to the controls pane. Repeat the process for each of the tabs and banks

Presets:

Saving in-app presets: Use the ticker to pick the slot -> Hit Save -> Label your preset
Recalling in-app presets: Use quick toggle buttons below slider.
Labelling preset toggles: 1) Go into 'Design Mode' 2) Tap the padlock to uncheck 'Others' (to allow changes) 3) Double tap the toggle to bring up a menu where you can title your preset button (if already unlocked you can skip the second action)

IMPORTANT:

If you are adding in-app grouped presets, make sure you save your layout at the end of a session. This will write them to the layout file. Open the App Menu -> Tap Config -> Then tap Save Layout in the Actions Tab
If you happen to open design mode you'll notice there's a lot of panels with controls that are hidden in play mode ( the yellow boxes). Don't delete them - they are super or sub controls, and necessary for mapping and functionality to work. Feel free to tweak other controls though - e.g if you want to change a colour/size, move them elsewhere or switch out a dial of a fader etc.

Me on Instagram: https://www.instagram.com/yaaasounds/

Disclaimers

Chase Bliss have given me a thumbs up, but note this is a non-official layout.
I am not connected to Chase Bliss, and I don't work for Midi Designer. I made this for my personal use, and thought I'd post it here so other people can enjoy using it
For Midi Designer Pro app issues please contact the Midi Designer support team
For issues with pedal hardware or software please contact Chase Bliss.

Answered: Add support for Roland five byte device codes in check sums

Sat, 09 Mar 2024 00:16:19 +0000

We have our first board that needs this fix - Roland SPDX-Pro.

Here is a StreamByter output rule that fixes the checksum for this device. I don't have a five byte device to test against, but this returned correct checksums for my test matrix.

In the MD control SysEx format, select one of the current Roland checksum formats to ensure the message has a checksum. Doesn't matter which as this does a complete checksum recalc. We just need the CS position to exist in the message.

Update - original incorrectly had 12 in ID position five - correct value for SPDX Pro is 16

Paste from line below to bottom in StreamByter output rules

# Temporary fix for Roland five byte device ID checksums
# Red Heron Music
# March 8, 2024

# SPDX Pro sample two byte data message
# F0 41 10 00 00 00 00 16 12 20 00 00 41 V1 V0 Cs F7
#  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F 10 (ML = 11)

# Checksum calculation starts at position M0A, goes to ML - 3, checksum in position ML - 2

# i0 - CheckSum
# i1 - Loop variable 
# i2 - Last position

If Load
    Alias i0 ChkSum
    Alias i1 Loop
    Alias i2 Last
End

If M0 == F0 41 10 00 # Roland Device
    If M4 == 00 00 00 16 # SPDX Pro, replace 16 for other Roland five byte devices

        Ass ChkSum = 0
        Ass Loop = 9
        Mat Last = ML - 2 # Checksum position

        While Loop < Last # we get ML - 3 by using < in test
            Mat ChkSum = ChkSum + Mi1 # Loop - alias not allowed on indirect
            Mat Loop = Loop + 1
        End

        Mat ChkSum = ChkSum % 80
        Mat ChkSum = 80 - ChkSum
        Mat ChkSum = ChkSum % 80

        Ass Mi2 = ChkSum # Last - Alias not allowed on indirect
    End
End

Answered: StreamByter does not recognize $08 and $09 (and related values) as valid decimal values

Fri, 01 Mar 2024 23:37:03 +0000

Drop the leading 0 after the $ and it should work

Yamaha FGDP-50 Drum Pad

Fri, 01 Mar 2024 20:41:04 +0000

The Yamaha FGDP-50 Finger Pad is a toy for drummers, but it's quite fun to play. This layout gives you direct access to Kit selection.

There's more to the MIDI Spec, and I might add more functionality later.

FGDP-50 MIDI Spec [ link ] [ all manuals ]
Named Ticks Maker in Google Sheets [ link ]
Info on the FGDP-50 [ link ]

Roland TR-6S & TR-8S Remote Control and Basic Sequencer

Wed, 28 Feb 2024 05:34:27 +0000

TR 6s / 8s Variation and Pattern Controls

Provides:

Precise stop on downbeat
Remote control of variations and fill settings
Manual or automatic sequence through a set of variations
Manual or automatic sequence through a set of variations and patterns

This is a work in progress. Watch for updates as I complete development as discussed below.

Connection:

Unfortunately, the data needed for this layout only comes via USB (at least I have not figured out switch settings to get it out DIN MIDI), so the connection has to be via a computer with the appropriate Roland driver.

Setup:

Check MIDI Designer Config / Pedalboards / Pedalboard supercontrols affect only current pages subcontrols - ON for right page - see image
Complete steps 1-5 in the setup block
For remote control of step advance, via note or Cc, make appropriate settings in remote control settings
The default settings can be changed in the StreamByter input rules - locations are labeled

This layout writes data to

system settings - Tx and Rx edit data ON
pattern variation settings - variations selected, fill, cycle, and auto-fill

No other data should be impacted. To preserve existing pattern variation settings, turn off auto-save.

Pages

Left
- Beat display, start, stop now & stop end controls
- current variation & kit # and title
- Tempo
- “exclusive” or “inclusive” selection of current variations
  - Inclusive will not allow turning off all variations - TRs get weird when this happens
- Scatter display - illuminates when the “scatter” fill is active
- The pattern selector at top left does NOT do a beat synchronized change
Start / Stop control (TR has a four beat count in for remote start)
Three right pages, with increasing levels of control
- Manual sequencing of variations
- Manual / Automatic sequencing of variations
- Manual / Automatic sequencing of variations and patterns

For pattern sequencing, this forces the pattern change on the next downbeat by clearing current variations.

Some things that should be possible:

Extended fills & transitions. Make two or more patterns similar, use the first A-H for normal bars, use second A-H for enhanced fills and transitions (two or four bars vs one), etc.

Sequencer

Choices are
- Auto / Manual run (manual advances on step button or remote control)
- If Auto, number of bars to repeat before next step
- Whether to stop at end of bar (after repeats in auto)
- Use the STEP button or remote control to advance in play, the +1/-1 buttons are for use in editing
- The three sets of sequencer steps are independent
I am working on a more advanced sequencer, adding
- for each step, selection of # of bars to repeat, or wait for manual advance (vamping, etc.)
- loop an arbitrary selection of steps # of times (up to last 10 steps, up to 10 times, etc.)
- jump to arbitrary nearby (not just next step) (+/- 64 steps)
- dynamic indexing by songs (vs 200, 400, 600, …)

So I would not try to load your complete playlist in the current version. But if you do save data in the sequencers, save the layout to save your work.

The “sequencer” works at the measure level, not sequencing notes, but the drum machine settings for next measure, and how many times to repeat the measure, etc.. Then loads the settings to the Tr so it is ready for next downbeat.

Limitations

Roland have not provided the SysEx definition for the TRs, this implements what I have been able to decode so far. Really no magic here, just watching the data sent by the TRs in run or when communicating with the editor.
Some things still working toward:
- Display currently playing variation
- Remote actuation & display of fill (this will actuate Scatter, but only for the remainder of current bar)
I have not spent much time assessing the “fill cycle” behavior with change of settings, could be some work here to make more predictable.
The SB code could be more compact if subroutines worked in MIDI Designer - the lack of subroutines forces a more linear thought process (which might actually be more logical)
This control uses a quantity of SysEx traffic. There may be architectures where this may not be optimum.
If the TR is connected, you can use any of the variation controls to program sequencer steps. If the TR is not connected, you have to use the dial in sequencer settings block.
This was tested on the 6s.

Free vs Premium

Remote variation control and manual sequencing work in Free - this should give a feel if the capability is something potentially useful for your workflow
Remaining capability requires Premium

I have not tried to replicate capability in the Roland TR editor - it works for what it does. My focus is on things the editor cannot do.

Thanks to "mike" on StreamByter forum who got me re-engaged on this effort.

https://www.youtube.com/watch?v=xwG0IfNU2b4

Answered: Named Ticks text replaced with example text

Wed, 28 Feb 2024 01:32:11 +0000

Look at the picker text, then select subcontrols, use hamburgers to rearrrange the order of some subcontrols. Look at the named ticks after the change

MDP X on Mac can create unequal sized pages

Tue, 20 Feb 2024 22:47:55 +0000

New layout on Mac may create unequal sized pages on 'new' layout. Finally captured one of these layouts - usually just delete and start again.

Workaround - try new layout again, or resize layout.

Deleting "enable" button freezes the parent control, relationship not cleared on delete

Tue, 20 Feb 2024 22:46:05 +0000

Assign an enable button to a control. Delete the button without deleting the relationship - stops all output from the control

Workaround - Go to the frozen control and unselect the deleted control from button enables box.

Problem is you may have forgotten the relationship when you delete the button, spend lots of time trying to figure out why your layout stops working.

MDP2 fails to open an MD Pro-X layout

Tue, 20 Feb 2024 02:35:33 +0000

I opened an old layout in MDP PROx to verify it. I did not make any changes, but saved it. I mailed it to an interested user. He was unable to open it. He stated he was using MD Pro 2 (2.131) on IOS 10.3.3. The message is “…was created with a higher version of MD…”.

Is there any version of MDP Pro2 that can open a layout saved in MDP PROx?

DSI Tetra (with Sys-Ex receive)

Sat, 17 Feb 2024 18:40:12 +0000

This is not a passive editor. By hooking up both MIDI in and out to/from the Tetra you can use the 'Retrieve Program' button in the Layout, and the Tetra will send the currently buffered Program (by Sys-Ex dump) to MD. This Layout will then reflect the received Program data for analysis and editing. You can also initiate a Program dump from the Tetra's own menu.

This Layout contains buttons for Oscillator 1 and 2 'Wave Reset'. These parameters are not mentioned in the Tetra manual.

There is a 'Basic Patch' button that recalls the DSI equivalent from MD's Preset 10 location.

I have included a couple of note on/off trigger buttons for the sequencer.

I embraced the two-page format for this Layout. I have chosen what I consider to be useful combinations for L/R pages.

* Early versions of this Layout required 'Supercontrols Send Own Values' to be switched on in MD's Config - Options. If this was not done then the oscillator shape buttons would not function. This requirement was removed from Version 5 onwards.

There are limitations:

I have not implemented edit access for all of the 'Global' parameters. Some of them are problematical (switching off NPRN reception would disable this Layout, for instance!). Retrieving Global data will display current Global parameter values, however.
I have not addressed Layers or Combos. I don't use these myself, so the considerable amount of work to expand the Layout is not justified.
Programs must be saved using the Program Write procedure on the Tetra itself.
Although it should be possible to edit the Assignable Parameters 1-4 from MD, I found that any message received by the Tetra reset these Parameters to zero. I have made the MD controls read-only, so they will have to be edited on the Tetra itself.

Add NPRN offset to Panel options?

Wed, 14 Feb 2024 11:52:08 +0000

I'm creating a lot of NPRN controls, and much of this is repeated with offset - Env 1, 2, 3, LFO 1, 2, 3, 4, etc. The panel offset option only allows for controller number offset. Can an NPRN offset (MSB/LSB) please be considered?

Answered: In PROx, Panels with controls can be duplicated, but not with Make Similar behavior.

Wed, 14 Feb 2024 00:53:23 +0000

When first duplicating a panel with controls, the duplicate controls have the same MIDI parameters. If MIDI Receive is selected, the controls with activate each other, appearing to behave as Copies. The right answer is to offset the Channel and/or CC values in the duplicate panel(s).

the video will be public at midnight tonight (2/13). https://youtu.be/LUr5qPeKFHM

I am not getting email responses to Q&A submitals

Tue, 13 Feb 2024 15:32:27 +0000

Lately I have submitted several Ask a questions and get no email responses. I have the Email me checked when submitting. My active email address is listed. I have to go to Q&A periodically to check for responses to questions I just submitted. Worse yet, if someone responds to an older submittal I will never know. Please check into this.

For example https://mididesigner.com/qa/9862/prox-panels-controls-duplicated-with-make-similar-behavior I have not received an email that there were responses.

I will double check the email address listed for this submittal.

Answered: MIDI "Display Value" only goes down to -99

Tue, 13 Feb 2024 14:52:05 +0000

See my approach to quickly and easily naming ticks.

https://mididesigner.com/qa/9826/hack-to-format-copy-and-paste-named-ticks-from-excel-template?show=9826#q9826

RheyneMIDI - control surface for Ableton

Tue, 13 Feb 2024 04:26:02 +0000

Here's the Ableton control surface I've been using for many years, mainly handling audio return channels for various instruments in my live looping setup, both hardware and software. I've included a copy of an Ableton template with the controls from pages 1-4 mapped to the MIDI Designer template. Each channel contains a reverb, delay and filter, with the channel header's colors in Ableton matching those in the MIDI Designer template. The top two knobs in each group controls the reverb amount and mix, the bottom two knobs control the delay's amount and mix, and the x/y pad controls the filter's cutoff and resonance. The on/off switch for each plugin is also mapped.

Page 5 is mapped to various lighting cues and external gear, and is included here as a starting point for your own use. All of the controls are mapped to MIDI channels 2 and 3, which was done to avoid conflicts with other hardware in my studio.

If anything isn't working correctly, please let me know and I'd be happy to fix it.

Jon B (@RheyneMusic)

MIDI Apply Now Sysex Properties in Mac OS and iOS Fails and is inconsistent with Control Change behavior

Mon, 12 Feb 2024 19:25:00 +0000

In MDPx for Mac OS and iOS, applying a Sysex Property MIDI value change may/will fail. Case in point, when activated with red dot, there is no way to make a MIDI value change since Apply Now never appears. When activated with green dot, the Apply Now only appears at the bottom right, but not at the top left. Thinking clicking the return arrow to close the window will apply any change, it does NOT in either mode. I have occasionally changed the Sysex value and hit the return arrow as I normally would, only to have my change fail and having to go into a troubleshooting mode.

If I remember to select the green dot mode and Apply Now at the bottom right, the Apply Now appears at the top left and closing the window will take the change and everything is fine. However, I should only have to apply once and not twice in the green dot mode, particularly if I am changing several controls at the same time.

I tried the Control Change MIDI value and it works in either red or green dot mode. Making a change makes the Apply Now appear at the top left as usual.

Why doesn't the Apply Now appear at the top left for MIDI entries of the Sysex Property panel? I sense a few other changes have occurred in Mac OS, such as the convenient numeric keypad with upper case hex letters and V and L no longer appears as it does in iOS.

If Sysex Properties is selected, I suggest the Apply Now becomes a choice at the top left. The user then has the option to not make a change and select the go back arrow, make a change and have the change take when closing the panel, or Cancel, which does appear. At least if he made a change and didn't want to keep it, he has several ways out.

Getting wi-fi disconnected often now - and reconnecting doesn't work

Sun, 11 Feb 2024 14:13:02 +0000

Something I've been noticing since MDX (didn't seem to happen in Beta). Never had much a problem in the past, but now I get wi-fi disconnected frequently. Disconnecting and reconnecting manually in the Config - Connections dialogue doesn't work, even though the connection is ticked. I have to shut down/re-start MDX.

This could be due to other issues, but it seems too coincidental to not mention it.

Where is email layout info in Mac OS?

Sat, 10 Feb 2024 15:17:43 +0000

I am unable to find the selection to email metadata in MDP ProX for Mac OS. It is not in Config > Actions > Advanced anymore. In the iPad there is a Mail Metadata option. In Mac OS, there is no such option in Config menu. The Share to Mail in the Apple File Menu only attaches the ,mididesigner file. I find it useful, especially for large layouts to identify controls for assigning Midi parameters. Please bring it back.

Thanks

Answered: How to deal with MCU messages

Sat, 10 Feb 2024 06:23:53 +0000

Make your mute buttons toggle, turn off send on only, ensure they are all Note ON / ON.

With those changes, the mute buttons works fine here against a simulator. Timing doesn't matter, the inbound message takes control of button state.

To change all eight mute buttons output to 7Fs with one line, use:

Set NVR 0

90 10-17 00 = 90 XX 7F

Re: What I need is a button that sends out a message, but only reacts to an incoming message to set its lit/dim state.

That is essentially what is happening once you make the changes above. As configured, the natural button state normally will match what the DAW is sending for status. If they get out of sync, the DAW status will flip the button to the correct condition.

^{p.s., check your knobs that are used only for grouping buttons. You prolly want them NO MIDI SEND / RECEIVE to preclude random surprises elsewhere in your setup.}

Walrus Audio Meraki Analog Stereo Delay

Sun, 04 Feb 2024 18:45:39 +0000

Here is a layout to control the Walrus Audio Meraki pedal.

----

Midi Channel: It is set to 5. You can change it by going into design mode. Then double tapping each tab and going to the controls pane. Repeat the process for each tabs with controls on them.

Chase Bliss Dark World

Sun, 04 Feb 2024 18:42:39 +0000

Here is a layout to control the Chase Bliss Audio Dark World pedal.

Huge thanks to mitchelldr for the inspiration from his layout for the Thermae !

To be noticed: On the Dark World, Dip Switches cannot be controlled over midi, so loading presets can lead to various results depending on the Dip Switches state.

----

Midi Channel: It is set to 3. You can change it by going into design mode. Then double tapping each tab and going to the controls pane. Repeat the process for each tabs with controls on them.

Chase Bliss Audio Gen Loss MkII

Sun, 04 Feb 2024 18:31:31 +0000

Here is a layout to control the Chase Bliss Audio Gen Loss MkII pedal.

Huge thanks to yasir for the inspiration ! I used the layout he made for the Mood MkII, and learned a lot, using it as a base and modifying it to fit with the Gen Loss MkII. Checkout his other layouts too.

Few usage notes (copied from yasir mood mkII layout):

Saving in-app presets: Use the slider to pick the slot -> Hit Save -> Label your preset

Recalling in-app presets:

Option 1 (Most useful): Use quick toggle buttons below slider.
- If you want to label the toggles: 1) Go into 'Design Mode' 2) Tap the padlock to uncheck 'Others' (to allow changes) 3) Double tap the toggle to bring up a menu where you can title your preset button (if already unlocked you can skip the second action)
Option 2: Use the slider to go to the preset slot. Then tap 'Recall'.

IMPORTANT:

If you are adding in-app presets, make sure you save your layout at the end of a session. This will write them to the layout file. Open the App Menu -> Tap Config -> Then tap Save Layout in the Actions Tab
If you happen to open design mode you'll notice there's a lot of panels with controls that are hidden in play mode ( the yellow boxes). Don't delete them - they are super or sub controls, and necessary for mapping and functionality to work. Feel free to tweak other controls though - e.g if you want to change a colour/size, move them elsewhere or switch out a dial of a fader etc.

Dip Switches: These work by sliding your finger over the control from left to right.

----

Midi Channel: It is set to 6. You can change it by going into design mode. Then double tapping each tab and going to the controls pane. Repeat the process for each tabs with controls on them.

Moog Mother 32 Semi-Modular Synthesizer

Sun, 04 Feb 2024 08:56:06 +0000

Very straight forward implementation on the Mother 32. For CC, you only have portamento time and toggle, and a sustain toggle.

PC messages 1-65 will load one of the corresponding sequences, and 71-86 will choose from available options to output a signal from the “Assign” output on the Mother 32 patch bay. I’ll include the page from the manual explaining each.

My first project on Midi Designer. I'd like to add more functionality in the future, like selecting sequences through bank/sequence combinations to be more in line with how the Mother stores them. For now, you will have to do the math to find your sequence. :(

Hope this is able to help somebody out!

Answered: What about me? I paid for MIDI Designer Pro 2

Sat, 03 Feb 2024 17:33:54 +0000

February 20, 2024 - Course Correction

On January 25, 2024, we transitioned to a free app -- MIDI Designer Pro X -- with an optional subscription. We heard the disappointment from our existing customers, and we want to correct course.

Today, we are making some changes (now out since MIDI Designer Pro X 10.1.0). Everyone who purchased MIDI Designer Pro 2 prior to our switch to subscription on January 25, 2024 will have lifetime access to all existing features before the 10.0 update.

This includes the core MIDI Designer Pro experience that users know and love and all features that were previously purchased as IAPs (including Stream Byter plugin, Extra Features Pack and Cloud Backups). Future features we develop may also be included, depending on their complexity and cost to maintain.

We are a small company, so we designed the original one-year access plan as a precautionary measure since we were not certain if we could support lifetime access. We sincerely apologize for putting our current users in this position.

Without you, we would not be here today. We deeply value each and every one of you. Your feedback and layouts power MIDI Designer Pro and have helped shape the app into what it is today. Thank you.

Sincerely,
Dan, JK and the MIDI Designer Team

[leaving the below post because it still provides valuable insight into the reasoning]

Why Subs 1/x: One-Time Purchase Problems

We explained a lot of the reasons that we went with subs in our "Why Subs" video here. The fundamental goal is to get MD into the hands of as many users as possible for free.

https://youtube.com/shorts/C7s90R50WVg

Why Subs 2/x: The Death of the Lemur, the Legend

But the short vid really begs the question: why do we need users to pay over and over again, instead of just once?

As many of you know, Lemur -- a legendary MIDI controller offered on iOS and Android -- was removed from the App Store in 2022. MIDI Designer was headed quickly in the same direction. Software development is extremely expensive and we cannot just stop. The pressure is constant and furious:

Apple keeps updating iOS, iPadOS and macOS, requiring fast developer response, code changes, and communication changes.
The tech continues to advance -- new hardware, MIDI 2.0 is coming out, etc. -- so we cannot sit still either.
User feedback requires response, new-feature development and app refinement to keep users happy and get new users.

Why Subs, 3/x: Leave my App alone!

Some users have said, "why don't you leave MDP2 alone, offer no updates ever, remove it from the App Store when it doesn't work, and make a new app?" This approach has multiple, hard problems:

How would we communicate to potential new buyers of MDP2 that it's already dead as far as updates are concerned?
How would we communicate to old MDP2 users that we're going to remove the App from the App Store because Apple broke it via update?
how would we determine the App is dead? When it's somewhat broken on the latest iOS version due to an Apple upgrade? How would we know if the break is bad enough to sunset the App (no updates, no downloads)?
How do we explain to new users which App to purchase? We cannot have the App in the App Store not for purchase.
etc. etc.

Why Subs, 4/x: You're Just Doing This to Make Money!

While we're hoping that Premium can, eventually, fund app development, support and other activities in full, the answer is NO. We're doing this to offer the App for free -- with a limited feature set (no page changes, notably) -- to all users with no limits. Eventually, YES, it would be nice to buy a sushi dinner once in a while for the team, but initially the goals are meager: to get MD into the hands of as many users as possible, and to cover costs and fund current and future development.

We've been rolling since 2012, have issued 85+ updates, and users seem happy. Now it's time for me, Dan with our team -- mostly JK on support/community and various users who help out with things like translation -- to attempt to cover costs and avoid having to remove the App from the App Store.

I get it, MIDI Designer is essential to me, how can I help?

If you love MIDI Designer, think about how to do your part to keep us from going the way of the Lemur.

Consider buying a Premium Sub now. You can turn on "Ignore App Purchase Date" under config to start your sub right now instead of waiting for your loyalty year to expire.
Think about how to promote MD on the Internet. Do you have photos or videos to share? Hit us at up team [at] mididesigner [dot] com and let's see how we can work together.

Thanks for checking out MIDI Designer!

Dan

Dan :: Software Author & CEO :: MIDI Designer :: dream | create | play

Mailing a layout no longer 'subject lined' automatically

Fri, 02 Feb 2024 13:24:04 +0000

I used to use the email feature to send copies of my layouts to myself and have them redirect to a safe folder, based on the content that MD automatically created in the subject line.

I know there's the 'Share' option now, but it doesn't do the subject line content for me. Deliberate, or an oversight?

PLEASE can I have the auto subject line back?!

Answered: MDP is cutting off background app music from other apps

Mon, 29 Jan 2024 00:37:02 +0000

Config → MIDI → "Stay Alive in Background" to OFF. This will solve your problem.

Answered: MIDI Designer hangs on start! What to do?

Sun, 28 Jan 2024 02:56:20 +0000

Steps to resolve:

Force quit and restart the App.
If force quitting doesn't help, reboot your device. In theory, this should be the same as force quitting, but in the field we've seen that it often sorts everything out.
If a reboot doesn't do it.... Using the Files app, rename everything in your MIDI Designer directory.
1. autosave.mididesigner
2. config.xml
3. sometimes, you have an autosave-presets... rename this too
Force quit and restart.
Load your renamed autosave!
Worst case: delete and reinstall the App. Backup your files first using the Files app!
If the problem happens again immediately, send an email to support via Config -> Actions

https://www.youtube.com/shorts/79RyatEcQ4s

Answered: MDX iPhone 'This layout has problems'

Sun, 28 Jan 2024 00:50:56 +0000

Bug fix came out already. Should fix for you. Please comment back either way, thanks!

LAYOUT: Simple MIDI Monitor

Thu, 25 Jan 2024 17:48:37 +0000

This is a simple MIDI monitor, that has saved me lots of time and trouble. It gives an indication of what data is reaching MIDI Designer, including MIDI channel, note on/off + velocity, pitchbend, controllers + value, program changes, and channel/poly aftertouch. Poly aftertouch also shows the note the aftertouch message is attached to. There is also a button that briefly flashes when a sys-ex message is received.

This Layout, although basic, can help to solve MIDI problems.

Hack to Format, Copy, and Paste Named Ticks to/from an Excel Template

Thu, 25 Jan 2024 03:21:32 +0000

Easily format, create, and edit Named Ticks in Midi Designer Pro2 using Copy and Paste from an Excel Template. The Excel template is used to parse and format the Named Ticks data from MDP2. Then it can easily be modified, copied, and pasted back into Named Ticks Edit pane for Knobs, Sliders, and other similar controls. This is a quick and simple hack to populate Named Ticks from a prepared list without entering it manually into MDP’s Edit Named Ticks.

Open the Excel file and save it as a template. Then to use, Select New from Template. The template contains step-by-step instructions. The video describes the procedure in detail.

This is a follow up to https://mididesigner.com/qa/9769/named-ticks-program-sequential-random-midi-stepper-outputs

The video describes the procedure in detail.

https://youtu.be/2zNuhP06ROw

Metronome Hack using MidiFire Dynamic Clock

Thu, 25 Jan 2024 02:26:24 +0000

This MDP2 design features a Metronome tempo control hack implemented within the iPad. It features the Dynamic Clock module in the MidiFire app by Audeonic to generate a Beats per Minute clock. The design has a tempo range from 20 to 200 Beats per Minute. The clock drives a simple 4 beats per measure display which can be expanded to include other selectable beats per measure or other functions. The Layout can also easily be modified for other tempo control implementations, ranges, and values to suit your needs. It can easily be added to any functional layout you currently use

The MidiFire Scene consists of ‘MD Pro 2’ input and output interfaces with Midi Designer. The principal element is the Dynamic Clock, which generates a midi output at a rate equal to 24 times the displayed BPM. There are input and output StreamByter modules connected to the dynamic clock. The input StreamByter receives Midi messages to start, stop, and set the tempo from MDP. The output SB divides and outputs Midi messages to MDP representing each of the 4 Beats.

The Clock Control consists of a Slider to control the Tempo of the MidiFire Dynamic Clock. It’s main feature is the use of Named Ticks to display the tempo and the corresponding term.

The video provides details of the design and the MidiFire StreamByter Code.

https://youtu.be/ur61LCYGQPs