Microfreak and DAW MIDI Loop

[jpdsnz8822]

Anyone successfully get this working with a DAW? I am having feedback loops as soon as I move the cutoff knob while using MIDI. I have gotten it to work with MIDI over USB though.

I pulled my MIDI adapters out to check them and they were really hard to get off. I noticed dents on the adapter connectors. Could this cause these feedback loops or is it software related?

I also noticed that I cannot record the output of sequences to my DAW as MIDI notes regardless of the setting in utility, is anyone else experiencing this?

[rgarner]

Yes, having huge trouble with it. With Local Off and connected to Logic Pro X on any MIDI channel I cannot get it to behave in the same way as any of my other synths. I'm alright only as long as I transmit or receive *only*. I can't leave both input and output connected such that it can be selected when the track is selected as with any other synth (Sub 37, Prologue, Behringer Model D).

My biggest issue is when changing presets with the knob; a huge number of CC messages is sent when this happens, and these seem immediately to feed back unless Knob Send CC is OFF. Once they have done so the synth is frequently left in an unresponsive state or a state where response to MIDI notes has massive lag.

I'm keeping it because as a polyphonic AT keyboard it's quite nice and quite fast, but its MIDI implementation is frustrating and all but unusable for me right now. I hope Arturia release a fix. It would be lovely to hear that they're working on new firmware, but every company is of course usually absolutely silent on these matters these days.

[Mecanek]

Yes, having huge trouble with it. With Local Off and connected to Logic Pro X on any MIDI channel I cannot get it to behave in the same way as any of my other synths. I'm alright only as long as I transmit or receive *only*. I can't leave both input and output connected such that it can be selected when the track is selected as with any other synth (Sub 37, Prologue, Behringer Model D).

My biggest issue is when changing presets with the knob; a huge number of CC messages is sent when this happens, and these seem immediately to feed back unless Knob Send CC is OFF. Once they have done so the synth is frequently left in an unresponsive state or a state where response to MIDI notes has massive lag.

I'm keeping it because as a polyphonic AT keyboard it's quite nice and quite fast, but its MIDI implementation is frustrating and all but unusable for me right now. I hope Arturia release a fix. It would be lovely to hear that they're working on new firmware, but every company is of course usually absolutely silent on these matters these days.

I have the exact same issue. I can only tweak the knobs, record the MicroFreak and hear what I’m doing if I have local on, record to another channel, and afterwards switch it to MF’s channel for playback. If I set local off and have to rely on MIDI to play and tweak the MF through my DAW (Ableton), I get this CC loop that freaks out the MF. It happens both through USB and MIDI. The MIDI Thru setting doesn’t change anything.

Gutted. Bought it last week and fell in love with it instantly, but thinking about returning it now, because it feels very unstable.

[Mecanek]

Technical support says they’re working on it 
‘This is a known and logged issue, the display is indeed acting like the knobs were touched when using MIDI CC's, and also causing feedback.

The DevTeam is working as we speak to fix this on a future Firmware update.’

[rgarner]

Hey Mecanek, thanks a ton, that was what I was hoping to hear. I said to the guy in the (physical!) shop I bought it from when he asked how it was "yeah, it's absolutely brilliant and also almost unusable in a studio".

[ShapedNoise]

Let me add my name to the list of people disappointed by the clusterFCUK that is the midi implementation.

There are SO MANY fails with it.  seemingly Random assignments of CC numbers ignoring the GM protocol totally.
The almost complete unusablity of it as a midi controller given its failure to implement LOCAL OFF properly.

Its really annoying as it offers so much, but fails at the first hurdle. All that need tio be done is for ARTURIA to understand LOCAL OFF properly.

Hey Guys! PLEASE sort this! :+)

LOCAL OFF

[Mecanek]

Well, that's disappointing: I've been waiting for a firmware update since august but here it is and this issue still isn't resolved 

[ShapedNoise]

Its really disappointing that the V 2.0.3 update has not fixed this issue.

Yes, having huge trouble with it. With Local Off and connected to Logic Pro X on any MIDI channel I cannot get it to behave in the same way as any of my other synths. I'm alright only as long as I transmit or receive *only*. I can't leave both input and output connected such that it can be selected when the track is selected as with any other synth (Sub 37, Prologue, Behringer Model D).

My biggest issue is when changing presets with the knob; a huge number of CC messages is sent when this happens, and these seem immediately to feed back unless Knob Send CC is OFF. Once they have done so the synth is frequently left in an unresponsive state or a state where response to MIDI notes has massive lag.

I'm keeping it because as a polyphonic AT keyboard it's quite nice and quite fast, but its MIDI implementation is frustrating and all but unusable for me right now. I hope Arturia release a fix. It would be lovely to hear that they're working on new firmware, but every company is of course usually absolutely silent on these matters these days.

I have the exact same issue. I can only tweak the knobs, record the MicroFreak and hear what I’m doing if I have local on, record to another channel, and afterwards switch it to MF’s channel for playback. If I set local off and have to rely on MIDI to play and tweak the MF through my DAW (Ableton), I get this CC loop that freaks out the MF. It happens both through USB and MIDI. The MIDI Thru setting doesn’t change anything.

Gutted. Bought it last week and fell in love with it instantly, but thinking about returning it now, because it feels very unstable.

[Germain.arturia]

Hi everyone,
as answered on other related posts, yes we definitely having issues with CC handling with DAWS when the MF is in local off.
just for the record, and you may have all noticed it , no more CC is sent when changing presets or powering up the unit on firmware 2.0.3.
We're currently gathering all complains regarding the 2.0.3 update, and will work hard with devs to solve these issues ASAP.

thanks for your patience, and sorry for the inconvenience.

best regards,

[Mecanek]

Technical support says they’re working on it 
‘This is a known and logged issue, the display is indeed acting like the knobs were touched when using MIDI CC's, and also causing feedback.

The DevTeam is working as we speak to fix this on a future Firmware update.’

Almost a year ago now 

[anglerfish96]

I spent *hours* trying to figure this out! ARGH!

[Mecanek]

As much as I’m excited by the new vocoder function and I do enjoy the MicroFreak in general, it’s really disappointing to see new firmware without the fixes that were promised more than a year ago 

[csurieux]

As much as I’m excited by the new vocoder function and I do enjoy the MicroFreak in general, it’s really disappointing to see new firmware without the fixes that were promised more than a year ago 

Indeed, we are so many expecting these fixes.
Nice vocoder add, but still impossible to send even a simple CC 7 to manage output level.