Groove Agent Pattern Player: limitations with odd meters (7/8) and MIDI round-trip

Cubase
1

Hello,

I’m posting this partly to confirm my understanding of Groove Agent’s current design, and partly as feedback for possible future development (e.g. GA 6).

Use case:
I was experimenting with creating a small reusable library of jazz brush drum patterns in 7/8, with the intention of:

  • composing patterns metrically in Cubase

  • auditioning them live via Groove Agent pattern pads

  • exporting / reusing the MIDI later

This works very cleanly in Cubase’s Pattern Editor / Drum Editor, but I ran into some limitations once patterns were moved into Groove Agent’s Pattern Player.

Observed behaviour (as I understand it):

  1. Groove Agent’s Pattern Player appears to be internally bar-based around 4/4, even when the host project is in an odd meter (7/8 in my case).

    • A 1-bar 7/8 MIDI pattern is coerced to a 4/4-based length (e.g. “0 bars 4 beats”).

    • There does not seem to be a way to define “1 bar = 7 beats” inside GA itself.

  2. Once patterns are loaded into pattern pads and treated as performance patterns:

    • Drag-and-drop MIDI round-trip back to the Cubase timeline is no longer consistently available.

    • There is no explicit UI indication that a pattern has changed from “MIDI object” to “agent-owned performance pattern”.

  3. This makes GA’s Pattern Player very effective for 4/4 live triggering, but fragile for odd-meter compositional pattern work, especially when patterns are intended to be archived and reused later.

To be clear:
I’m not suggesting this is a bug — it seems to be a design choice aligned with GA’s original loop-oriented focus. Cubase itself handles odd meters perfectly; the limitation appears specific to GA’s Pattern Player abstraction.

Questions / feedback:

  • Is it correct that GA’s Pattern Player cannot currently treat odd meters (e.g. 7/8) as true “bars” internally?

  • Is there any recommended workflow for users who want both:

    • metrically accurate odd-meter composition, and

    • live pattern auditioning inside GA

  • For future versions, would Steinberg consider:

    • explicit meter-aware pattern lengths, or

    • clearer UI feedback when patterns become performance-only objects?

I’ve found that, for odd meters, Cubase’s native Pattern Editor / Drum Editor is currently a more reliable place to compose patterns, with Groove Agent best used purely as a sound engine or live performance tool.

Thanks for any clarification, and for the continued development of the platform.

Best regards