MIDI Designer Q&A - Recent questions in Defect (Confirmed, Not Fixed Yet)

SysEx select variable options button missing text - appears a blank box

Mon, 23 Feb 2026 01:13:13 +0000

In beta Version 10.10.0 (202602141940) and current release.

Button is present, has no text. If you know to press it to select settings, it will work.

Editing subcontrol sequence with named ticks overwrites named ticks text with subcontrol labels

Mon, 23 Feb 2026 00:56:44 +0000

Variable supercontrol with named ticks - go to the subcontrols panel, edit the subcontrols by dragging one to a new position - all existing names are overwritten with the labels of the subcontrols.

This is potentially a feature when the named ticks are vacant - populates the named ticks field with the subcontrol names. But not so much when you have entered other names.

ZD 3924, confirmed in beta 10.10.0 (202602141940)

Problems with SysEx Property Boxes (all OS)

Tue, 11 Mar 2025 12:51:15 +0000

Problem 1: (MacOS & iPadOS)

The SysEx property inspector box does not reliably populate Variable Options settings. The box will save settings. If you reopen the box to check your settings, it may not bring up your current settings, instead showing default settings. If you cancel out, your existing prior settings will still be viable. If you APPLY CHANGES, ensure that the variable options settings (V length, MSB first, S length) have been correctly entered.

You don't have to open the variable options box to loose the settings. If you change the SysEx characters, it will reset the variable options even if you never open the variables inspector.

(After having MD open for a while, MD might start reliably populating the box. Once that happens, it appears to continue working properly until the app is closed and restarted. I have not been able to recreate the stimulus that causes it to start behaving properly.)

Workaround: none. There is no workaround to check variable options settings, you can only reenter what you believe are the correct settings.

Problem 2: (iPadOS)

When you open the SysEx property inspector, the save / apply option does not initially appear. The box will (mostly*) NOT save settings in either sticky or non-sticky modes.

If you enter a V or S, the variable options box will not appear to make settings.

(*Occasionally, if you enter or change an L, V, or S, the properties will save correctly.)

Workaround: If you move to the Checksum box and make a change, APPLY CHANGES (and Variable Options, if a V or S has been entered) will appear, and the settings can be saved. If you don't need/want a checksum, change anyway, then change back to none. Then make any desired Variable Options settings and APPLY CHANGES.

[Bug] Cannot adjust page background properties on iPhone

Sun, 12 Jan 2025 07:19:06 +0000

[Fix queued for 10.6.6]

Can't upload images to a Question (Firefox, Windows 11)

Fri, 21 Jun 2024 10:39:40 +0000

Today I can't upload images to my Community Share Question using the image selection box. I've tried both jpg and png, but nothing is working.

Instead I resorted to inserting the image into the main text.

Has something changed?

Named Ticks text replaced with example text

Tue, 20 Feb 2024 23:02:03 +0000

When editing named ticks, text can be replaced with "example text"

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

Tue, 20 Feb 2024 20: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.

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

Mon, 12 Feb 2024 17: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.

Supercontrols Send Own Values notes

Mon, 08 Jan 2024 04:00:13 +0000

A few instances with button supercontrols where Supercontrols Send Own Values may not have the expected results

Options as supercontrol - send default value
- only sends values that are not already on default value
- this will propagate through intermediate controls that ARE at default to move controls that are NOT at default value

Options as supercontrol - send current value
- only sends subcontrol values (leafs)

Above both function as expected with continuous value supercontrols (knobs, sliders, etc.)

Send On Only
- button supercontrols will also send MIDI off values

My recommendation remains to avoid using the SuperControls Send Own Values option - is more disciplined programming to have a control EITHER be a Supercontrol or send MIDI, not both.

Added 2 & 3 to the observations sheet.

These are fairly obscure cases, prolly not high priority to address - better to avoid in layout construction

Via ZD 3432

Controls "supercontrols" properties box is missing the "Edit" option

Thu, 30 Nov 2023 01:53:23 +0000

The pane when attempting to delete a Supercontrol from a selected Subcontrol states "Touch to see - Swipe to delete". Touch to see works, but cannot swipe a spercontrol to delete using a mouse in Mac OS. Swipe works in the iPad. Suggest adding an Edit Button to bring up the Red delete selection as in deleting a Subcontrol from a Supercontrol, which is the workaround to the current issue.

MDP-Mac OS has a minor issue entering text in a label field

Mon, 30 Jan 2023 16:45:14 +0000

MDP-Mac OS has a minor issue entering text in a label field. When using a mouse to click in a text entry field, I occasionally (by habit I guess) move the mouse arrow out of the field. In this case typing on the keyboard will do nothing. I have to move the arrow back into the text entry field and typing will work.

In other words, clicking the mouse in the field places a flashing cursor to allow typing to begin. But moving the mouse arrow out of the entry field, removes the flashing cursor and typing on the keyboard has no affect.

The workaround, of course, is not to move the mouse after clicking or move it back and restart typing.

The YouTube video shows the issue.

https://youtu.be/QABYZZCLIJY

MDP-Mac OS crashes when moving a page

Mon, 30 Jan 2023 16:22:24 +0000

MDP-Mac OS crashes when attempting to move a page between banks. A problem report is created. The workaround is to Save the layout and open it in an iPad (or iPhone). Then move the page(s) and save. Finally reopen the iPad layout in Mac OS.

The YouTube video shows the attempt to move a page. https://youtu.be/pdm8OPTBtog

Re-Ordering Subcontrols Overwrites Preset Names

Tue, 25 Oct 2022 07:33:47 +0000

Not sure if this is a bug or if I've got something setup wrong!

I have a simple layout as pictured, and I've saved two presets into the preset picker.

If I then go into design mode, select the presets picker, relationships, subcontrols, edit - and re-order the two subcontrols, I get the message "Updated ticks for Presets for button subcontrols (2)"

When I go back and select the preset control the preset names have been overwritten with the button names. Is this right?

Sysex controls with "L" value don't respond to incoming MIDI

Tue, 16 Nov 2021 21:13:19 +0000

Controls with an "L" in their sysex string don't respond to incoming MIDI feedback, but they do if the sysex string is hard-coded with the same value.

Update: Some controls with an "L" in their sysex string DO respond to incoming MIDI feedback. I've updated the layout with examples.

Why does Motion Engine Layout (hack) continue to run in Design Mode?

Wed, 07 Jul 2021 12:32:53 +0000

The Enhanced Motion engine layout is a continuation of an earlier Question I raised regarding a PAN function and Answered by jkhiser. It will continue to run if not stopped in Design Mode. Actually, why does it even run at all? I think of the basic function as an oscillator (metronome) that can cycle forever. But is it stable? Notice the behavior of Start when first tapped. It remains lit for one cycle and goes out at the start of the second cycle. This modifies the up/down behavior of the Driver. The Snap Sub to Value is essential for the Halt and Stop. I use 10 ms. If not set properly, it may appear to freeze MDP.

Why am I unable to manually activate a stepper function Button Group?

Wed, 31 Mar 2021 00:44:32 +0000

Hi – I usually find how to fix something that doesn’t work right in MDP using trial and error. This is beyond me.I am getting an unwanted interaction between 2 Button Groups.

I have a layout for a Registration Stepper to control the Hauptwerk organ App. I am using a Mac Mini and MDP version 2.181. The issue exists without a connection to the computer or Hauptwerk. It is strictly in MDP. I monitor the Midi Out with MidiMonitor and don’t see any unusual Midi signals.

The main function on Block 1 and 2, Combinations pages, consists of 35 combination buttons configured in a button group linked to Fdr 77. Each combination button outputs Midi signals on Channel 6 with unique CC values. By itself, it works fine. It is independent of the Friesach Stops Pages which aren’t the issue.

A second function is labelled stepper. It triggers Fdr 77 to trigger the next or previous active button (without wraparound). I haven’t configured the recall button yet. Prev and Next work fine with the 35 buttons.

The issue is with the presets. They are used to preset one of the 35 buttons and are also a button group with Fdr 285. By themselves they work fine. Each preset button sets Fdr 77 to the specific combination button. It should stay active until another preset button is pressed. When used with the combination buttons and stepper, it behaves as desired.

The issue is, I also need the combinations to be manually selectable. If a preset is selected, I want to be able to manually select any combination button and have the last selected preset remain active. Sometimes it does, sometimes Fdr 285 goes to 36 rather than remaining where it was last set. The problem happens at different manual selection of combination buttons. It seems combination 19 and 20 usually fail, but other buttons fail based on the last preset selected. The correct Midi output is output for each manual button selected even if the error occurs. But I need the last selected preset to remain active so I can use the Recall button to reactivate that combination button.

What is causing the interaction of manual combination button selection in MDP to cause Fdr 285 to go to its highest value even though triggering via the next and prev buttons never affects Fdr 285? While Preset buttons affect the combination buttons, the combination buttons should not affect the preset buttons.

This sequence seems consistent. Press preset 2, Press preset 15, combination 15 lights, manually touch combinations 16, 17, 18, 19 and everything seems ok. Preset 15 remains lit. Manually press 20, it does not light, 36 does. Fdr 77 goes to 36 and Fdr 285 goes to 6, preset 15 goes off. It should stay on.

Starting again with preset 15, advance advance from there with the next button past 20, 21, 22. There is no problem. This is the desired behavior for manual selection.

Thanks, Don

Panel Member Controls for Hide in Play Mode Not Hidden

Mon, 30 Nov 2020 02:19:13 +0000

On the latest MD Next build I'm having an issue that I've had for a few builds - hidden panels are not hidden on first startup until I go into "Design" mode and then back out, then they are properly hidden.

You should already have my layout where I'm experiencing the issue, surprised you didn't notice. Check out Bank 1 Page 5, the buttons on the lower middle left that are overlapping are only supposed to appear with the dial above them.

Exclude from reset ignored for 0-0 controls

Tue, 21 Apr 2020 11:50:30 +0000

I have a bunch of buttons that select presets by a controller number. Typically this will be in the form: CC20, Value 9/9, Send On Only.

They work fine. I have set them also to be excluded from a reset. But on a reset *all* of these buttons are sending out their data! You can imagine the receiving device goes nuts!

However, if I set the values to 0/9 (not that it matters in reality with a 'Send On Only', everything works as it should.

A bug, or something I'm not understanding?

Note On/Note On doesn't respond to incoming messages

Wed, 08 Apr 2020 06:37:45 +0000

For my control surface emulator I was using Note On/Note On controls, which work fine outgoing, but incoming messages are ignored. I've spoken with James K Hiser on Facebook and he mentioned I should raise the problem here - he has also confirmed it is not working for him either.

Can this please be raised as a bug for fixing?

I've coded a StreamByter workaround for this problem, but this has raised another problem, in that the StreamByter plug-in does not accept the 'BLOCK' command!

For anyone curious, here are a few seconds of my emulator in action: https://youtu.be/idcXSP1MOOA

High value four byte Vs appear to not receive correctly

Tue, 07 Jan 2020 01:51:46 +0000

This was discovered by olav-rossland post at https://mididesigner.com/qa/7974/negative-and-positive-sysex-values-in-one-slider-solved

The negative values in the four byte V case seem to be skipping by 16s instead of tracking the incoming midi message.

The same negative values in the three byte V case track correctly.

Use the attached layout on two iPads transmitting to each other to see this behavior.

I extended the negative values to -256, and the problem still occurs at that point.

Dark Mode Bug: Writing not visible in Sysex Properties

Sat, 02 Nov 2019 16:50:29 +0000

Hi,

glad to have found your tool!

I'm working on a layout, and when trying to make use of Sysex messages, I ran into what looks like a bug. Any input I'm writing in the main Sysex Properties page isn't visible. Even when highlighted (see image) the characters are not visible. However, they appear when you apply the settings, and you can copy the characters from the main entry field and paste them elsewhere. That's somewhat, well, uncomfortable.

Restarted the iPad - didn't work. I tried to change the page's font colour - no success.

I'm using MP Pro 2 2.123 (build 191026) on an iPad Pro 1st gen (12.9") running iOS 13.1.2.

Thanks! (There might be some Sysex questions coming up... ;-) Looking forward to share my layout!)

Wolfgang

How can I disable the floating scroll and zoom icons in the lower right of the display?

Mon, 11 Feb 2019 18:18:52 +0000

I am using Ipad2's so never need to change the screen resolution. Last year, the pointing finger and arrow floating icons appeared in the lower right, and I understand why they are needed now that iPads have different resolutions. However I don't need them, and they make my buttons at the bottom right very difficult to select. I searched the manual for "zoom" and "pan" controls, thinking it must be a switch that I can turn off in the main MD config. Having not found any reference in the manual, I came here. I would like to know how to turn off the floating scroll and zoom function. Thanks!

Performance-Mode: Low-Memory Warnings and Crashes in Multi-Bank Layout

Sun, 11 Nov 2018 05:18:36 +0000

This template I’m working on for the nord drum 2 keeps crashing and flashing low memory warning (with no other apps open.) the app in general is eating through battery on the verge of making it an unusable app, more than any other app I’ve used. I’m on an iPad Pro 9.7 screen with 128 gb, should be sufffeciient. It happens as I flip back and forth between banks using the switch to bank buttons labeled Drum Pads, X/Y, and Controls depending on the page. I hope you can see something weird with this template though it’s no more complicated than any other template I’ve made. Thanks for the help!

StreamByter Delays Not Working

Tue, 06 Nov 2018 19:14:25 +0000

StreamByter Delay Not Working

SB appears the ideal fix to RD-2000 limitation of processing only eight Sysex at a time. To read a full page on one Load press, use the delay function to have SB delay 9-16 by 200 ms, 17-24 by 400 ms, etc.

But I am having problems getting it working.

I am using a dummy sysex header that tells SB how long to delay, and SB also replaces the dummy portion with correct data. By using the header, checksum remains correct.

SB code:

# If message header is F0 00 00, use fourth byte to determine delay amount

# then replace header with F0 41 10 00, plus remainder of message, delayed as specified

# Fourth byte, 20 = +D200, 40 = +D400, etc., selected by if statements.

IF M0 == F0 00 00 20 # Fourth byte = 20, so +D200

    ASS M1 = 41 10 00

    XX = XX +D200

END

# similar ifs for 40, 60, and 80 in fourth byte.

====

Also tried this alternate version

IF M0 == F0 00 00 20 # Fourth byte = 20, so +D200

    SND M0 41 10 00 M04 M05 M06 M07 M08 M09 +F +D200

    SND M0A M0B M0C M0D M0E M0F M10 +F +D200

END

F0 00 00 = XX XX XX +B # Block original message output

====

In both cases, the output sysex is changed appropriately, but not delayed.

Finally tried just this simple output rule:

F0 = XX + D2000

This should delay all Sysex by two seconds. Again, no delay.

Then tried

F0 = XX + D2000 +C

Both copies of message appear at same time.

What am I missing?

Jump to Page with One-Big-Page Freezes App

Wed, 01 Aug 2018 19:39:47 +0000

Hi

I have midi designer layout. I am using all 8 banks.
Config options are One big page and Change banks together.

Initially first page left=bank1 and right=bank5..
I made button which purpose is to change bank so that left=bank2 and right=bank6.
Button options
- subtype = jump to bank
- go to bank = 2

I think that after button push left bank should change to 2 and right to 6.

When i push button right bank changes to value = 0 ???
In that point nothing works anymore and i have to reload layout.

If i change buttons action to "Bank up" everything works ok (banks 2 - 6 ) but "jump to bank" freeze app with bank number 0.

Am i doing something wrong or is this bug.

Banku up works ok.

Reset to Defaults ignores exclude flag

Sat, 30 Jun 2018 21:39:31 +0000

I am using a "Reset to Default" button on the main page of my multi-page layout to let all controls on all pages send their default values. This basically works fine.

However, on some of my other pages I have some buttons that I don't want to send their default values when the "Reset to Default" button is tapped. Thus, I toggled the "Advanced > Reset to Defaults - Exclude" button for these buttons.

Unfortunately, this does not work - they still send their default values when the "Reset to Default" button is tapped.

Is this a bug, or is it just me not understanding what "exclude" means here? Thanks.

Can bit changer controls and presets be combined?

Fri, 22 Dec 2017 16:50:26 +0000

I am trying to create a layout to control some of the options on a Yahama EX5, which has a number of sysex control that are specified bit wise. I created a knob control to send the sysex message and a series of push buttons to set the bits. This seems to work fine. I then added a preset control knob and associated Store and Recall buttons. I then added the first control knob and all of the bit control buttons as subcontrols. When I recall a preset, buttons are recalled correctly but the knob which sends the sysex is not updated. Instead it sends out its current value. When I push the bit setting buttons, the knob moves to the correct position. Am I missing an option with respect to the sub/super control relationship that would make the preset recall work?

Thanks in advance.

Knob, Slider, Crossfader in 2.9: Resizing Label is Broken

Mon, 29 May 2017 14:19:38 +0000

Current release 2.9.0 Build 170512

In the previous release as you resized the label (Autosize - Off) you could see it change, now it doesn't change at all, the only way to get it to take effect is to reset the color after the resize, then it displays correctly, although if you want further changes you have to repeat the process. This seems to effect all sliders and knobs, buttons still appear to work ok.

Wandering Exit Button

Fri, 21 Apr 2017 07:32:18 +0000

Quite often during a development session I will turn bluetooth off (saves battery and no surprises on the MIDI box), after doing this you are returned to the MDP homepage, where you then select Design, the exit button is then placed in the middle of the right hand page (not ideal), and not its normal position at the top.

Lenny

Next 2.9.0 (201703202308): iPhone 6 / ios 10.2 / Round Button MultiLine Label Formatting Issue

Tue, 04 Apr 2017 12:56:29 +0000

I'm noticing in Play mode that the label formatting is off. It shifts to the top of the round button. When I enter Design mode and tap the button the formatting corrects itself until I go to Play mode.

See attached screen shots

Next 2.9.0 (201703202308): iPad 3, iPad 4 & iPad Air 2 bogging down

Sat, 25 Mar 2017 16:37:05 +0000

I was testing all three of my iPads and noticed in Design mode all three iPads would hang up when trying to move a control. I even disabled saved to Dropbox on all three iPads with no improvements. My layout was fairly simple, 64 momentary toggles transmitting note value and a couple of super controllers.

Any reports of this?

Presets do not send midi message

Thu, 19 Jan 2017 08:44:51 +0000

Last year using midi désigner , my 20 presets were working very well

Now, they do not send midi (changes are well seen on the ipad )

!!! I do not understand

My pc receive thé messages pushing on the instruments normal buttons so It is well connected

When i push on a preset the red little lamp at the top on thé right of the i pad should light

it does not !

Thank you for à explanation

Michel (your programme is wunderfull congratulation !!!

Open URL Ver 2 Crashes in iPhone 6

Tue, 21 Jun 2016 20:41:31 +0000

After multiple rescans Launch URL is not seeing any of my open apps. When I change the Launch URL value from None to Custom Launch URL the app crashes. I have duplicated this 5 times.

iOS 9.3.2

iPhone 6

MIDI Designer Pro 2.0.0

w/Extra Features Pack # 2

MIDI Designer XW: Amp Touch Sensitivity not right

Fri, 13 Nov 2015 21:52:45 +0000

Hi,

I am on iOS 8.4.1 with Casio XW Midi Designer 1.7.1 Build 1714.

The problem is that the Amp Touch Sens(itivity) Knob ,send wrong midi message. For Syn1 eg it sends

B0 63 30

B0 62 2A <--It should be 2B instead according to midi chart

B0 06 xx

Could you check that?

Are hardware MIDI inputs recieving data too slowly?

Fri, 30 Oct 2015 16:17:20 +0000

I am a long-time MD user and around the time of iOS 9 updates, I began having an issue with hardware midi inputs becoming "jumpy"...that is to say if a fast stream of data is sent from hardware, MD is only recognizing maybe 1 out of 5 values sent, with large and inconsistent gaps between values (i.e. rather than receiving 1-2-3-4-5-6-7-etc, MD is seeing only 1-5-9-18-26-etc).

I have spent a significant amount of time trying to diagnose this problem and identify any possible causes in my own setup, but after painstaking trial and error, I can only conclude the problem is happening in MD. Here are the facts I know:

- Any other iOS program is receiving the MIDI stream from my hardware normally...this is audible, but also was confirmed using "MIDI Wrench" to log data being input.

- The MIDI log in MD does show the same gaps in signal that are being heard.

- The problem occurs with any midi hardware I use to input. I initially thought maybe the issue was due to a synth that was sending dense clock signal and possibly jamming up the works...but the problem was identical when sending an isolated MIDI signal with no clock data being input.

-The problem occurs on both iPad and iPhone versions...and occurs identically when using any of my various MIDI interfaces.

-When slowing down the speed of the input MIDI stream, MD does begin to recognize all discreet values...it is as if there is some sort of governor on the amount of MIDI data being accepted.

-The midi output from MD works perfectly normally and is sending a clean/complete stream of data at any speed (assuming the data is generated from within MD...obviously any data received from hardware sources is output with the same gaps it was received with)

- I have looked into any MD settings that could be causing this, but can't find anything that would be related. I have "Batch Send Throttle" set to Zero, though if I understand the function correctly, it is unrelated anyhow.

Well, that's what I know. My primary use of MD is to receive and "translate" data from hardware MIDI sources, then output the modified data to other hardware or software. MD is so fantastic and has become crucial to the point that my setup is rendered almost useless by issue, as any MIDI gestures are chopped up before they are modified and output.

Thanks in advance for you thoughts and advice...I appreciate how committed you have been to maintaining and improving this program for the community who love it!

Should two CCs in one message be handled?

Sun, 20 Sep 2015 20:38:25 +0000

I am sending a lot of CCs to MIDI Designer as quickly as possible (to set the visual control values to match my device's), and I'm finding that some are received in messages that are 6 bytes long, and seem to be ignored (the controls are not set).

An excerpt from the log:

Message In: Cmd=176|Ch=07|Data1=009|Data2=003 | Length=3: B6 09 03
Message In: Cmd=176|Ch=07|Data1=010|Data2=002 | Length=3: B6 0A 02
Message In: Length=6: B7 00 29 B7 01 7F
Message In: Cmd=176|Ch=08|Data1=003|Data2=001 | Length=3: B7 03 01
Message In: Cmd=176|Ch=08|Data1=005|Data2=029 | Length=3: B7 05 1D

The B7 00 29 & B7 01 7F in the 6-byte message do not appear to be received as MIDI messages.

I see this behaviour when using a MIDI over Bluetooth (low energy) interface with the midimittr app presenting a standard MIDI interface to MIDI Designer on the iPad. I don't see this problem with a hardware MIDI interface (iRig MIDI). So I'm not sure whether the problem is that midimittr is not packaging the messages correctly, or that MIDI Designer is not handling the 6-byte message with two 3-byte MIDI messages in it.

Would appreciate any comments.

Thanks.

MIDI Designer is Crashing on Startup! iOS 9

Wed, 16 Sep 2015 19:21:24 +0000

In the Wi-Fi connections, I connected my iPad to itself (I think). MIDI Designer has crashed and now it crashes on every start. Help!!!

Using "Supercontrols Send Own Values", Supercontrol appends program change 0

Sun, 04 Jan 2015 23:19:24 +0000

Here's another repeatable anomaly I just found when "Supercontrols send own values" is enabled in Config-Options menu.

Turn on "Supercontrols send own values"

Create a button that sends a program change. Mine is on CH 3 - PC 96. which should produce C2 60 when pressed.

Exit design mode with the Log window up and touch the button. As expected, it sends "C2 60"

Edit the button by touching "supercontrol" in relationships. Do not attach any subcontrols.

Exit design mode and touch the button. Now you get "C2 60 C2 00".

An extra program change command is appended to the stream, negating the effects of the original program change.

Now create a bank change button, and add it as a subcontrol to the supercontol button. Exit design mode and test the button.

MD will send the correct bytes for the bank change (B2 00 00 B2 20 01) (CH3, Bank 1), then the correct program change (C2 60) but will still append the extra program change (C2 00).

This issue has something to do with the supercontrol being able to send its own MIDI because I can get it to work if I use two subs with a supercontrol.

Help!

"Send Test" Sends Incorrect Value for Prog Change/Bank Change etc. (Design Mode only)

Sun, 04 Jan 2015 20:16:48 +0000

Hi, I'm just working on my GR-55 project and using the log window, I noticed the following which I believe is a bug. I'm using 1.7.0 Build 1701.

Create a momentary button and set it to send a program change on channel 1.

open the MIDI log window and click to keep it open

Set the button to send a program change of 127. This should make MD send ""C0 7F". Click on "Send Test" and notice that the log window shows "C0 5F".

Now exit design mode and touch the button to see what it actually sends. The log will show it now sends the correct "C0 7F".

I think the value is being scaled somehow. If you put in a PC of 2, it sends 2. But if you put in 3, it still sends 2. If you put in 4, it sends 3. Put in 10, it sends 8.

This same bug manifests itself in bank changes.

Since it actually works right outside of design mode, this bug can be worked around, but it's going to drive a lot of people crazy who are trying to test things in design mode.