New firmware and drivers for both Minitaur and Sub Phatty will be posted soon, please follow. We’re checking these versions in-house right now, and will upload them once confirmed as stable.
Meanwhile, will you be able to list all historical, known Sub Phatty and Minitaur issues here, so we can check them out and log for fixing ? If you also know about new Sub 37 issues, please do as well.
We’re also checking older reports made on the main forums, so you may also link them directly.
[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.
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)
This is an issue that others and i experience while playing legato. Sometimes sound suddenly stops in the middle of the melody or whatever you’re playing. It can be greatly annoying because it ruins the whole point of what you’re doing at that moment. Ofcourse you can play on, but a note was stopped prematurely.
This occurs randomly with all presets, also in PanelMode and also with midi standard and/or usb input. No CV connections.
Maybe i should also mention that i watched and heard it happen to my friend too, but he was playing a Sub37. Perhaps this could be a case of a shared bug?
[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.
I´ve read the same problem in a couple of Post, but the discussion usually fade out in another thinks like “amplifier trigger mode” or things like that. i´m sure it´s not that. If you play a loop, each loop have to sound the same and in this case, my synth missed a key.
It happens in ableton and when i´m playing the keyboard too.
To be able to reproduce this, I’ll need a preset syx and an Ableton Live session which demonstrates this issue, in a way that it will show up if I use the specific preset and Ableton loop.
Also, which firmware have you been running so far, and do you still see this problem using latest 2.1.8 beta ?
[MTR] Using the 3.1 beta editor, I’ve saved some bad presets which don’t load correctly.
[MTR] When sending presets to the device, the patch number is incremented an extra time after each preset (not sure if this is by design).
[MTR] I have experienced a missing note behavior while playing notes to the midi in port while the USB midi port was visible/enabled in Cubase but actually assigned on any track or object output. My theory was some kind of data or timing conflict was going on. I disabled the usb midi port in Cubase to get consistent note playback.
Are you able to determine which parameters are not saved, or not saved correctly ?
Can you send me some of these bad presets ? (use the Editor to save them as syx)
I’m not sure I understand, what steps should I take and what should I follow ?
I see, we will post new firmware and driver for MTR very soon. Will you be able to check this again and see if it still happens ?
(MTR)- I too have trouble with ‘bad’ patches saved with the editor. mine all seem to have something to do w/ the amp velocity sensitivity parameter. if I create a patches that uses velocity sens; when saved, it wont sound unless I pound on the keyboard (= needs LOTS of velocity to trigger note). re-tweaking the velocity sens parameter fixes it. (unless I resave w/ the editor or reload patch)
If I save using the Minitaur’s hardware patch save, it works fine.
I understand. So basically patches are saved correctly when not using the Editor, but do not - when saved from the Editor ? Is that correct also in your case, puredrums ?
Different issue for mine, I’m seeing the patch load in the Editor based on feedback in the gui but no change in the sound and it still plays the previous preset…
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.
For second issue, if I hit Send to transfer presets, I see something like this as being on the device:
000 Panel Settings
001 BrighterFifth
002 Init
003 Dark Growl
004 Init
005 Ferdinand
006 Init
(and so on…)
This was unfamiliar/unexpected behavior, but I could see how it could also be by design to allow for easy management of variations for say a live gig where there is the intro and verse versions of a standard sound.
I’m very excited to test the upcoming firmware and driver. Thank you for supporting and listening to the community!
[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
It happens randomly in every preset, and not necessary playing a loop. I mentioned a loop to keep clear that is not a “playing” mistake.
Reading what Space Lee wrote, I find it very similar to his problem. And yes, i´m using 2.1.8 beta.
I´ll try recording it, but it happens not very often (that´s why is not a big issue) but of course never should happend.
