[MTR][SPH] Please list historical, known MTR/SPH issues

[AjS]

@GilW

@AjS

OK I think i got it. Where can I send you a short video for you to watch?

Please send it to gil (at) moogmusic dot com

If too large you may use wetransfer.

Done!

[GilW]

Thanks, got it. Will check this asap.

[THX5]

@GilW

@THX5

[MTR] I have my Sub37 driving the Minitaur directly via a MIDI cable (well, into the Slim Phatty first, then to the Minitaur via MIDI Thru). Very randomly, the Minitaur will freeze / hang up and stop responding completely. Doesn’t seem to be any particular MIDI sequence that triggers the freeze; just happens for no apparent rhyme or reason. It doesn’t happen very often. A simple power cycle of the Minitaur, by unplugging then plugging the power supply back in, solves the problem. Its really just a nuisance for me, but if I was performing live, it could be an issue

How often does it happen ? and which exact firmware version is currently installed in your MTR ?

Thanks !

Hi Gil,

It doesn’t happen very often. Hard to quantify other than it’s happened maybe 5 or 6 times in the past few months.

Firmware is 2.1.4.

Thanks.

[GilW]

@THX5

Firmware is 2.1.4

I’ll send you the latest firmware beta on email shortly. Lets see if the problem still persists.

[GilW]

@AjS

[SPH] There is this issue that I always have since the first day:
Sometimes, when i´m playing, a key does´t sound. Just one, the next one works perfect. Not a particular key neither a particular moment.
It´s a random problem, and I take that conclusion because if I play a Midi Loop with Ableton connected to the Sub Phatty, you can hear everything fine until the synth missed a key. Big and annoying issue I can live with, but I prefer no to have anymore.

Hi again,

I received your video. This happens because the second preset you are using has some Glide set to it, and the first note played using this preset is glided-to from the previous note played using the first preset. It’s not really a bug, I’ve reported this in the past as what seems to be a wrong behavior.

[GilW]

@bichuelo

[MTR]Any parameter I map to the inputs, works perfectly well when I plug an EP-3 to it, even if I pass through the CV mixer and attenuator of the CP-251. But if I try to send a CV control from another moogerfooger or the CP-251 it does not work, whether I send 0-5V or -5 to +5V. When there is something plugged, it sends the parameter to its maximum value then goes back to zero when I plug it out. This happens on every attenuator position. Furthermore, when the parameter assigned is VCO 2 Pitch, the range has an offset when I send powered signals and I am not able to go past the middle position on the knob. But if I plug the EP-3, it works fine. I am using firmware 2.1.7

Thanks, I’ve documented your report and waiting for an official response from Amos regarding what exactly should be expected in that case.

@Matthias32

Changing the destinations of cv mapping sometimes has no result (the default parameter keeps following the cv signal)
i’m using a cp251 to generate the voltages. Latest official firmware & editor. Sometimes it seems as if the control voltage induced change to a parameter is still happening after cable and signal have been removed. Power on-off resets everything.

This doesn’t seem right to me, reported on.

[GilW]

@Matthias32

sometimes after changing patches no sound is produced anymore, until you move the ‘velocity sens’ dial of the vca in the under the hood functions (or combo of buttons on the unit)

1. Which firmware version of the MTR are you running ?
2. Does it happen when changing preset using the Editor ?
3. Does it happen if you don’t use the Editor and change presets on a controller which controls the MTR ?

[GilW]

@Puredrums

[MTR] I’ve sent some examples of the bad preset loading behavior. I was doing some more testing to figure out repro steps and came across a different odd preset behavior(*edit which I cannot reproduce again but can send the glitchy preset if it’s of interest). I started with a good preset in the editor, went to the panel and adjusted cut off/resonance a bit and saved to a new preset. After closing and re-opening the editor, preset was different, reduced to just a short filter opening briefly sort of sound, as though it picked up only the knobs that had moved on the panel in the preset’s data.

Thanks, I replied to your email with more questions. Lets keep the discussion there.

[AjS]

@GilW

@AjS

[SPH] There is this issue that I always have since the first day:
Sometimes, when i´m playing, a key does´t sound. Just one, the next one works perfect. Not a particular key neither a particular moment.
It´s a random problem, and I take that conclusion because if I play a Midi Loop with Ableton connected to the Sub Phatty, you can hear everything fine until the synth missed a key. Big and annoying issue I can live with, but I prefer no to have anymore.

Hi again,

I received your video. This happens because the second preset you are using has some Glide set to it, and the first note played using this preset is glided-to from the previous note played using the first preset. It’s not really a bug, I’ve reported this in the past as what seems to be a wrong behavior.

Ok, thanks!
There is any possibility to get it right?

[GilW]

@AjS

There is any possibility to get it right?

As noted, reported as improvement suggestion.

[charbot]

[MTR] Found another “bug” with Minitaur editor: when using both the editor and an external midi keyboard (mine, in this case is a alesis vortex,)
patch changes sent from the keyboard do not register on the editor. Patches do change on the minitaur, but the editor doesnt follow along. Changing patches manually on the minitaur ( w/ hold glide + osc wav button ) works and is acknowledged by the editor.

Also- Have betas been going out? Havent received any emails. using the latest “official” releases.

[GilW]

@charbot

[MTR] Found another “bug” with Minitaur editor: when using both the editor and an external midi keyboard (mine, in this case is a alesis vortex,)
patch changes sent from the keyboard do not register on the editor. Patches do change on the minitaur, but the editor doesnt follow along. Changing patches manually on the minitaur ( w/ hold glide + osc wav button ) works and is acknowledged by the editor.

Also- Have betas been going out? Havent received any emails. using the latest “official” releases.

Confirmed and reported. Unfortunately, the new beta is being delayed but is expected to start soon.

[GilW]

@THX5

It doesn’t happen very often. Hard to quantify other than it’s happened maybe 5 or 6 times in the past few months.
Firmware is 2.1.4.

Hi !

Can you see any improvement using latest beta firmware and Editor ?

Does anyone else experience any spontaneous freezing using latest 2.1.11 ?

Thanks !

[THX5]

Hi Gil,

Yes, the latest Beta firmware so far has been a big improvement for me. I have not had the random freeze or filter drift issue occur since installing the firmware.

I should be able to really exercise the Minitaur this weekend. I’ll let you know if I run into any of these, or other, issues.

[GilW]

Thanks for the update,

We are about to upload a new version today or tomorrow, so it would be best to use that one.

Will post on email once ready.

[GilW]

@THX5

@GilW

@THX5

[MTR] I have my Sub37 driving the Minitaur directly via a MIDI cable (well, into the Slim Phatty first, then to the Minitaur via MIDI Thru). Very randomly, the Minitaur will freeze / hang up and stop responding completely. Doesn’t seem to be any particular MIDI sequence that triggers the freeze; just happens for no apparent rhyme or reason. It doesn’t happen very often. A simple power cycle of the Minitaur, by unplugging then plugging the power supply back in, solves the problem. Its really just a nuisance for me, but if I was performing live, it could be an issue

How often does it happen ? and which exact firmware version is currently installed in your MTR ?

Thanks !

Hi Gil,

It doesn’t happen very often. Hard to quantify other than it’s happened maybe 5 or 6 times in the past few months.

Firmware is 2.1.4.

Thanks.

Thanks, please inform us if and when it happens again. Here is seems to be stable on Windows.

[THX5]

Hi Gil,

I haven’t had this issue occur since upgrading to the newer firmwares. So far, so good.

Thanks,

[GilW]

Thanks for the update!

[bichuelo]

@bichuelo

[MTR] I have a weird behavior of the CV mappings, for several versions, although I can’t be sure in which version it worked correctly.

Any parameter I map to the inputs, works perfectly well when I plug an EP-3 to it, even if I pass through the CV mixer and attenuator of the CP-251. But if I try to send a CV control from another moogerfooger or the CP-251 it does not work, whether I send 0-5V or -5 to +5V.
When there is something plugged, it sends the parameter to its maximum value then goes back to zero when I plug it out. This happens on every attenuator position.

Furthermore, when the parameter assigned is VCO 2 Pitch, the range has an offset when I send powered signals and I am not able to go past the middle position on the knob. But if I plug the EP-3, it works fine.

I am using firmware 2.1.7

This seems to be working better on firmware 2.1.14
However, the range is limited to somewhere around 85% at maximum (when calibrated to +1v). If I use the default CV calibration or +4v I get a much narrower range, and if I use the default CV calibration it narrows down to less than 70%. Is this the expected behavior? I thought I could get to 100% somehow.
I am sending the +1V, +4V or +5V from my CP-251 prior to pressing the corresponding button on the editor. Is this the correct way to calibrate?

[GilW]

@Matthias32

2nd on the minitaur Cv issues.
Changing the destinations of cv mapping sometimes has no result (the default parameter keeps following the cv signal)
i’m using a cp251 to generate the voltages. Latest official firmware & editor.
Sometimes it seems as if the control voltage induced change to a parameter is still happening after cable and signal have been removed. Power on-off resets everything.

sometimes after changing patches no sound is produced anymore, until you move the ‘velocity sens’ dial of the vca in the under the hood functions (or combo of buttons on the unit)

These issues should be solved on next firmware beta v2.1.18. Will you be able to confirm ?