Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

GR-16 as AU hosted in Cubasis 3 issue

FPCFPC
in General App Discussion

Hope someone can help

New to GR-16 so don't really know what I'm doing...

Got a GR-16 pattern that I want record into CB3. Plays fine until I want to record it. Hitting record on CB3 records some note data into the track but when I play it back the sounds don't correspond to the original pattern. Eg: all beats just play back a random drum sound (crash cymbal) that wasn't even part of my original pattern.

Am I missing something basic in GR-16 or CB3?

Gave up on Beathawk for exactly the same reason but Drum Computer is fine. Any help would be much appreciated.

Comments

  • SamuSamu

    Considering GR16 uses all 16 midi channels I’m not sure Cubasis can even handle that properly...
    Cubasis is one midi-channel per track unless using MPE in which case editing is very limited.

    I’d suggest stem export from GR-16 and import the audio to Cubasis.

  • FPCFPC

    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

  • SamuSamu
    edited March 2021

    @FPC said:
    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

    All pads in Drum Computer transmit on the same midi channel if I’m not mistaken.
    GR16 is more like a multi-timbral sound module, each pad/sound needs it’s own track.

    Now if Cubasis had support for Multi In/Out AUv3 audio/midi plug-ins things would be different.
    Then you cold easily do this by creating a track for each pad in GR16 and get all the midi notes on separate tracks.

    Cubasis is Cubasis it evolves but not as fast as we’de like it to...

  • FPCFPC

    @Samu said:

    @FPC said:
    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

    All pads in Drum Computer transmit on the same midi channel if I’m not mistaken.
    GR16 is more like a multi-timbral sound module, each pad/sound needs it’s own track.

    Now if Cubasis had support for Multi In/Out AUv3 audio/midi plug-ins things would be different.
    Then you cold easily do this by creating a track for each pad in GR16 and get all the midi notes on separate tracks.

    Cubasis is Cubasis it evolves but not as fast as we’de like it to...

    Thanks again Sumi. I was tired and frustrated last night. Exporting audio from GR-16 and building in Cubasis is obviously the way to go.

    Cheers

  • rs2000rs2000

    @FPC said:

    @Samu said:

    @FPC said:
    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

    All pads in Drum Computer transmit on the same midi channel if I’m not mistaken.
    GR16 is more like a multi-timbral sound module, each pad/sound needs it’s own track.

    Now if Cubasis had support for Multi In/Out AUv3 audio/midi plug-ins things would be different.
    Then you cold easily do this by creating a track for each pad in GR16 and get all the midi notes on separate tracks.

    Cubasis is Cubasis it evolves but not as fast as we’de like it to...

    Thanks again Sumi. I was tired and frustrated last night. Exporting audio from GR-16 and building in Cubasis is obviously the way to go.

    Cheers

    It might sound odd but the way I'd solve that issue is to used sliced breakbeats or audio files with 16 drum samples appended to each other. With the slice markers set correctly, this way you can have up to 16 different drum samples on one track.
    Cubasis 3 should be able to route MIDI between different tracks too, in order to use the other 15 channels as well but I bet @LFS knows how to do that.

    Another option would be to use a MIDI plugin (Steambyter, Mozaic) as a C3 MIDI effect which translates note ranges on one channel into your favorite note ranges on different MIDI channels.

  • FPCFPC

    @rs2000 said:

    @FPC said:

    @Samu said:

    @FPC said:
    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

    All pads in Drum Computer transmit on the same midi channel if I’m not mistaken.
    GR16 is more like a multi-timbral sound module, each pad/sound needs it’s own track.

    Now if Cubasis had support for Multi In/Out AUv3 audio/midi plug-ins things would be different.
    Then you cold easily do this by creating a track for each pad in GR16 and get all the midi notes on separate tracks.

    Cubasis is Cubasis it evolves but not as fast as we’de like it to...

    Thanks again Sumi. I was tired and frustrated last night. Exporting audio from GR-16 and building in Cubasis is obviously the way to go.

    Cheers

    It might sound odd but the way I'd solve that issue is to used sliced breakbeats or audio files with 16 drum samples appended to each other. With the slice markers set correctly, this way you can have up to 16 different drum samples on one track.
    Cubasis 3 should be able to route MIDI between different tracks too, in order to use the other 15 channels as well but I bet @LFS knows how to do that.

    Another option would be to use a MIDI plugin (Steambyter, Mozaic) as a C3 MIDI effect which translates note ranges on one channel into your favorite note ranges on different MIDI channels.

    Thanks for chipping in RS but whatever it is that you've suggested sounds beyond my meagre capabilities! To keep things simple I'll just stick with arranging export audio clips in Cubasis.

  • FPCFPC

    @FPC said:

    @rs2000 said:

    @FPC said:

    @Samu said:

    @FPC said:
    Ok I'll try that, thanks Samu.

    I know everyone has a different work flow/idea of what they think an app should do, but FFS it just seems obvious to me: just output midi data from an AU sequencer (instrument not 'midi Effect' like Rozeta) and have the host DAW accurately record it and play it back.

    I done buying anything else (hostable AUv3) with its own sequencer, I'll just use Cubasis and stop wasting time. That's Beathawk, Pureacid and GR-16 now. Maybe I'm being a drama queen here and should just accept it's not possible but Drum Computer lays down its note info into C3 and plays back exactly the right sounds...

    All pads in Drum Computer transmit on the same midi channel if I’m not mistaken.
    GR16 is more like a multi-timbral sound module, each pad/sound needs it’s own track.

    Now if Cubasis had support for Multi In/Out AUv3 audio/midi plug-ins things would be different.
    Then you cold easily do this by creating a track for each pad in GR16 and get all the midi notes on separate tracks.

    Cubasis is Cubasis it evolves but not as fast as we’de like it to...

    Thanks again Sumi. I was tired and frustrated last night. Exporting audio from GR-16 and building in Cubasis is obviously the way to go.

    Cheers

    It might sound odd but the way I'd solve that issue is to used sliced breakbeats or audio files with 16 drum samples appended to each other. With the slice markers set correctly, this way you can have up to 16 different drum samples on one track.
    Cubasis 3 should be able to route MIDI between different tracks too, in order to use the other 15 channels as well but I bet @LFS knows how to do that.

    Another option would be to use a MIDI plugin (Steambyter, Mozaic) as a C3 MIDI effect which translates note ranges on one channel into your favorite note ranges on different MIDI channels.

    Thanks for chipping in RS but whatever it is that you've suggested sounds beyond my meagre capabilities! To keep things simple I'll just stick with arranging exported audio clips in Cubasis.

  • LFSLFS
    edited March 2021

    Hi @FPC, Hi @Samu, Hi @rs2000,

    Shared this thread with Jim Pavloff, to further exchange about it.
    Alongside, AUv3 Multi Out support is on our list, highly prioritised.

    Best,
    Lars

  • jimpavloffjimpavloff

    @FPC said:
    Hope someone can help

    New to GR-16 so don't really know what I'm doing...

    Got a GR-16 pattern that I want record into CB3. Plays fine until I want to record it. Hitting record on CB3 records some note data into the track but when I play it back the sounds don't correspond to the original pattern. Eg: all beats just play back a random drum sound (crash cymbal) that wasn't even part of my original pattern.

    Am I missing something basic in GR-16 or CB3?

    Gave up on Beathawk for exactly the same reason but Drum Computer is fine. Any help would be much appreciated.

    Seems like not a Cubasis issue. @LFS

    @FPC Please try this: Go to GR-16 menu -> Settings -> "Midi In Mode" and set it to "Poly" (allowing to receive all 16 midi channels by GR). Also, set "Start With Host" to Off to ensure Groove Rider's "Play" button will not start together with Cubasis transport, to allow only recorded notes to be played, not the internal pattern. This should solve the problem.... Please let me know if it works for you.

  • jimpavloffjimpavloff

    @FPC p.s. consider using Track Freeze in CB3 instead of recording raw midi data, it can be simpler and bring less chaos, depending on your workflow of course.

  • SamuSamu

    @jimpavloff said:
    @FPC p.s. consider using Track Freeze in CB3 instead of recording raw midi data, it can be simpler and bring less chaos, depending on your workflow of course.

    And in that case remember to create an empty midi-event first since Cubasis won't freeze an empty track even if the AUv3 outputs audio...

  • FPCFPC
    edited March 2021

    @jimpavloff,@LFS,@Samu

    Yes! :) Switching MIDI in mode to poly worked. Thank you Jim for helping. It works exactly as I would hope.

    Thanks too Lars for flagging this to Jim and Samu for being as helpful as ever.

    Nice one B)

  • LFSLFS

    @FPC said:
    @jimpavloff,@LFS,@Samu

    Yes! :) Switching MIDI in mode to poly worked. Thank you Jim for helping. It works exactly as I would hope.

    Thanks too Lars for flagging this to Jim and Samu for being as helpful as ever.

    Nice one B)

    Hi @FPC,

    Glad to read that the issue could be solved, thanks to the immediate feedback provided by @jimpavloff - Thanks Jim!
    Also, thanks to @Samu for being helpful too!

    Stay well everyone,
    Lars

Sign In or Register to comment.

© Vanilla Keystone Theme 2025