Pro 3 with DAW Hardware Intrument goes crazy

[Petur]

My Pro 3 with the latest BETA OS 1.0.2.3 does not play well with Bitwig Studio or Ableton Live when I create a Hardware Intrument with a "Program Change" midi message. I'm using USB as midi connection.

When I switch a preset with a Program Change command from a DAW the Pro 3 goes nuts. The sequencer in Pro 3 starts blinking like a christmas tree on crack and some crazy noises comes from the instrument. Sometimes it just freezes up completely. This happens every time when a preset have the Pro 3 sequencer running notes or automation automatically.

I've tried to disarm the track in the DAW to avoid midi feedback but it does not help. I think this is a midi feedback issue for sure but I'm unable to figure out what is causing this. For me it smells like a bug in the Pro 3. This only happens with Program Change message from DAW. It works like a charm when I play it standalone.

I was wondering if I'm the only one with this issue so I can return it before it's too late...I don't want to - so I'm really hoping this a firmware bug.

Is possible to roll back the firmware to see if that makes it better?

Current settings :

Midi Out : USB
Midi Clock : Slave s/s
Local : All off


P.

[alexpen]

My Pro 3 with the latest BETA OS 1.0.2.3 does not play well with Bitwig Studio or Ableton Live when I create a Hardware Intrument with a "Program Change" midi message. I'm using USB as midi connection.

Works fine here, however I'm using DIN MIDI.
Here is how it looks in Bitwig, selecting U1/P5

[h4ndcrafted]

I’m assuming yr using USB , mine does the same, just freezes on the second note on if you are using gate mode.

Unusable in USB at the moment , in Ableton at least.

[Petur]

Ok, thanks guys.

I think I tried the DIN MIDI, I'm going to try that again to see if that's the case.

P.

[cbmd]

All these sound like they are related to a MIDI feedback loop.  Please remember to turn LOCAL CONTROL off when actively connected to and from a DAW or leave LOCAL CONTROL on and mute the MIDI track output to the synth in the DAW.

FWIW DAWs have started adding 'hardware instrument' tracks which combine MIDI and audio tracks into one monolithic track.  As such, you cannot simply mute the MIDI portion of the track without also muting audio.  If you use these types of tracks, you will need to set local control off.  If you would rather leave local control on, you will need to use a MIDI and an audio track in place of the hardware instrument track, and mute the MIDI track's output.

[h4ndcrafted]

Yes I thought midi loop, as it’s fine as soon as I unplug usb, but I have local off, it seems to freeze up whatever I do.

But if it’s working ok for others it must be something I’m doing. Just trouble shooting what. But I think I’ve run out of ideas.

I’m going to try again tonight. Thanks for all your hard work!

Oh
I am using Ableton’s instrument plugin , I’ll try it without, local is def off though.

[Petur]

Same here, mine does not funtion as it should ( Yes, the local is off and the track is disarmed ). It allways goes nuts when I swtich a patch (with program change MIDI message) that has a running sequence or automation built in the patch.

Doesn't matter if its connected  through USB or MIDI DIN.

I've multiple hardware synths connected and Pro 3 is the only one giving me backwards high five.

Looking forward for the next firmware update

P.

[cbmd]

If you are using Ableton, you also need to make sure to set the MIDI param send/receive to CC.

[h4ndcrafted]

Changing to CC fixed it partially, but still won’t change pitch in gated mode.

Sounds like a double trigger, as if the note from Ableton is playing first just before the first note in the pro 3s sequencer .

If I don’t leave a small gap between notes . I.e if I have legato note, I just get the sequencer lock up like this

https://youtu.be/cLrDZpxgrLo

[nkl998]

Same problems here with Ableton. Whatever I do I cannot use the synth with Ableton like this. I'm returning it, that's it.

Changing to CC fixed it partially, but still won’t change pitch in gated mode.

Sounds like a double trigger, as if the note from Ableton is playing first just before the first note in the pro 3s sequencer .

If I don’t leave a small gap between notes . I.e if I have legato note, I just get the sequencer lock up like this

https://youtu.be/cLrDZpxgrLo

[nkl998]

If you are using Ableton, you also need to make sure to set the MIDI param send/receive to CC.

Same problems here with Ableton. Whatever I do I cannot use the synth with Ableton like this. I'm returning it, that's it.

[Petur]

I understand your frustration, but they are fixing those issues and new beta firmware OS should be coming soon.

FYI I downgraded my firmware to version 1.0 and lot of the crazy bugs were no longer present, but onboard controls generate midi feedback loops in DAW (Filter Cutoff, etc...) and sometimes I have switch it off and back on to get midi notes messages to the DAW.

That downgrade procedure gave me hope that this is all fixable, I could keep my Pro 3 and knowing that it's not a faulty unit

[cbmd]

Same problems here with Ableton. Whatever I do I cannot use the synth with Ableton like this. I'm returning it, that's it.

Changing to CC fixed it partially, but still won’t change pitch in gated mode.

Sounds like a double trigger, as if the note from Ableton is playing first just before the first note in the pro 3s sequencer .

If I don’t leave a small gap between notes . I.e if I have legato note, I just get the sequencer lock up like this

https://youtu.be/cLrDZpxgrLo

A known feedback loop caused in gated mode has been fixed on the latest OS:

https://forum.sequential.com/index.php/topic,4216.0.html