Loopy Pro: FIRST LOOK

ipadbeatmaking

@scrufftv said:
@ipadbeatmaking thanks, I see it has great midi functionality but the transport controls are often left out, AUM for example. You can midi map them to a note or cc in AUM but not the midi transport commands sent. Just wondering if the sync and transport is taken from ableton link for external devices, or if it is direct. Direct would be superb.

Ahhh…interesting point. Is the midi transport command hui/mcu?

scrufftv

Not from any of the hardware grooveboxes boxes I have. I've been down that route actually, Auria Pro takes MCU and I got that synced and transport perfectly with a Behringer BCR and the other hardware, but that is a large pain.

wim

@scrufftv I think you're referring to MMC control MIDI Beat Clock messages. I'll give that a try in the beta if no-one else beats me to it.

For the most part, if it works, it will only be for the standalone. Most hosts don't pass along clock and MMC to plugins (AUM being the only exception I've found).

wim

... and the answer is YES, @scrufftv.

MMC MIDI Beat Clock messages for transport control is definitely supported, along with the same excellent MIDI Clock In / Out, and time offset support as Audiobus 3.

Fingolfinzz

I’m trying to send the clock to a Volca sample through midi and the sync is double the bpm so I’m getting eighth notes when I want quarter notes etc, is there any way to adjust that?

Toastedghost

@gregsmith said:
@Mickaël said:

Just a quick test of slicer control and recording sequence.

So awesome isn’t it! Like mini mpc’s.

I get that there’s a lot of call for easy templates and starting points for common use cases, but the real fun is playing around and figuring out some of the infinite ways it can be used. In the beta people have been using it so differently, from simple loopy HD type stuff, to complicated layouts designed to emulate ableton’s session view.

And this alongside Drambo, AUM, etc.

Super cool, how are you triggering the grid box samples?

wim

@Fingolfinzz said:
I’m trying to send the clock to a Volca sample through midi and the sync is double the bpm so I’m getting eighth notes when I want quarter notes etc, is there any way to adjust that?

Does the same happen if you send clock from AudioBus or AUM instead?

Fingolfinzz

@wim It works fine in AUM but I haven’t checked on Audiobus yet. I know Korg does a different sync but I’m sending the clock to my interface which is connected to the Volca with a midi cable

dvi

I was getting glitchy results using the Digitakt to send clock and transport (MMC). Loopy receives them but funny things happen. Routing through Audiobus is perfect and not a big hassle (digitakt ->audiobus->loopy). I’ve also set three of the DT’s MIDI channels to record/start/stop loops and it’s a fantastic set up.

wim

@Fingolfinzz said:
@wim It works fine in AUM but I haven’t checked on Audiobus yet. I know Korg does a different sync but I’m sending the clock to my interface which is connected to the Volca with a midi cable

If it's working OK from AUM that would tend to point to a bug in Loopy. However, when I test to other apps (I don't have any hardware to test to) such as miRack, the clock is correct.

Is it at all possible that you have a loop? That the Volca is sending clock back to iOS? That's the only thing I can think of. If not, then the thing to do would be to see if some of the beta testers can try with the same or other hardware.

wim

@dvi said:
I was getting glitchy results using the Digitakt to send clock and transport (MMC). Loopy receives them but funny things happen. Routing through Audiobus is perfect and not a big hassle (digitakt ->audiobus->loopy). I’ve also set three of the DT’s MIDI channels to record/start/stop loops and it’s a fantastic set up.

I'm positive Michael will want to sort this out though. He's worked hard to make the best clock implementation on iOS for Audiobus, so I'm sure he'll want no less for Loopy.

espiegel123

@wim said:

@dvi said:
I was getting glitchy results using the Digitakt to send clock and transport (MMC). Loopy receives them but funny things happen. Routing through Audiobus is perfect and not a big hassle (digitakt ->audiobus->loopy). I’ve also set three of the DT’s MIDI channels to record/start/stop loops and it’s a fantastic set up.

I'm positive Michael will want to sort this out though. He's worked hard to make the best clock implementation on iOS for Audiobus, so I'm sure he'll want no less for Loopy.

I hope all this made its way to Michael over on Slack. If so, it is probably just a matter of his getting to that part of the list of things to address. If they haven’t been reported to him over there, please do.

dvi

@wim @espiegel123 yup I’ve been posting to the slack quite a bit (hopefully not too much).

@michael is incredibly responsive and has looked into all of these issues—I’m confident it will be sorted in no time!

TheSoundKid

Oh my god Waiting with More money & my Launchpad X

Jocphone

Trying to join the Slack thing I get this message. Is this a problem with Slack? (I don't know what Slack is yet)

AndyPlankton

@wim said:

@Fingolfinzz said:
@wim It works fine in AUM but I haven’t checked on Audiobus yet. I know Korg does a different sync but I’m sending the clock to my interface which is connected to the Volca with a midi cable

If it's working OK from AUM that would tend to point to a bug in Loopy. However, when I test to other apps (I don't have any hardware to test to) such as miRack, the clock is correct.

Is it at all possible that you have a loop? That the Volca is sending clock back to iOS? That's the only thing I can think of. If not, then the thing to do would be to see if some of the beta testers can try with the same or other hardware.

I get the same doubled clock when sending it to the LP Pro sequencer. The sequencer runs at double speed. Lucky for me the LP Pro allows me to run the patterns at 1/2 clock speed if I wish, so I am doing that as a workaround for now.

ashh

@wim been thinking that a Touch OSC template might be a good way into LP for noobs. Like, a 5 page (or whatever) template that exposes all the features. What do you think?

scrufftv

@wim said:
... and the answer is YES, @scrufftv.

MMC for transport control is definitely supported, along with the same excellent MIDI Clock In / Out, and time offset support as Audiobus 3.

Good to know, thanks for trying this out @wim

rs2000

@scrufftv said:
Anyone know if transport control from external midi hardware is supported? Being able to record loops started and stopped from the transport controls of the Digitakt for example. Ideally not through a workaround with Midi link sync and Ableton link, a direct connection.

Syncing with MIDI Clock includes exchange of MIDI status messages for start, stop and continue. I haven't tried with my Digitakt yet but the current Loopy HD runs perfectly in sync.
Clock sync is different from MMC which I'd be surprised if supported by Loopy Pro.

ashh

@rs2000 said:

@scrufftv said:
Anyone know if transport control from external midi hardware is supported? Being able to record loops started and stopped from the transport controls of the Digitakt for example. Ideally not through a workaround with Midi link sync and Ableton link, a direct connection.

Syncing with MIDI Clock includes exchange of MIDI status messages for start, stop and continue. I haven't tried with my Digitakt yet but the current Loopy HD runs perfectly in sync.
Clock sync is different from MMC which I'd be surprised if supported by Loopy Pro.

You'd be surprised if clock sync was supported?

espiegel123

@AndyPlankton said:

@wim said:

@Fingolfinzz said:
@wim It works fine in AUM but I haven’t checked on Audiobus yet. I know Korg does a different sync but I’m sending the clock to my interface which is connected to the Volca with a midi cable

If it's working OK from AUM that would tend to point to a bug in Loopy. However, when I test to other apps (I don't have any hardware to test to) such as miRack, the clock is correct.

Is it at all possible that you have a loop? That the Volca is sending clock back to iOS? That's the only thing I can think of. If not, then the thing to do would be to see if some of the beta testers can try with the same or other hardware.

I get the same doubled clock when sending it to the LP Pro sequencer. The sequencer runs at double speed. Lucky for me the LP Pro allows me to run the patterns at 1/2 clock speed if I wish, so I am doing that as a workaround for now.

Can bug discussion please be kept over on the Slack channel?

ashh

@espiegel123 said:

@AndyPlankton said:

@wim said:

@Fingolfinzz said:
@wim It works fine in AUM but I haven’t checked on Audiobus yet. I know Korg does a different sync but I’m sending the clock to my interface which is connected to the Volca with a midi cable

If it's working OK from AUM that would tend to point to a bug in Loopy. However, when I test to other apps (I don't have any hardware to test to) such as miRack, the clock is correct.

Is it at all possible that you have a loop? That the Volca is sending clock back to iOS? That's the only thing I can think of. If not, then the thing to do would be to see if some of the beta testers can try with the same or other hardware.

I get the same doubled clock when sending it to the LP Pro sequencer. The sequencer runs at double speed. Lucky for me the LP Pro allows me to run the patterns at 1/2 clock speed if I wish, so I am doing that as a workaround for now.

Can bug discussion please be kept over on the Slack channel?

You should have a red and blue flashing avatar and a klaxon sounding off when you respond to a post.

espiegel123

@ashh said:
@wim been thinking that a Touch OSC template might be a good way into LP for noobs. Like, a 5 page (or whatever) template that exposes all the features. What do you think?

It could be done in Loopy Pro itself. No need for an app people might not have. Loopy has widgets for dials sliders and buttons. All can receive or send MIDI.

ashh

@espiegel123 said:

@ashh said:
@wim been thinking that a Touch OSC template might be a good way into LP for noobs. Like, a 5 page (or whatever) template that exposes all the features. What do you think?

It could be done in Loopy Pro itself. No need for an app people might not have. Loopy has widgets for dials sliders and buttons. All can receive or send MIDI.

Picture the scene: Steve Jobs and Tim Apple are looking at a phone.

Steve: so I've been working on a phone that has a much better battery life. It even has a screen!

Espiegel: Gott in Himmel! Vot is vrong vis The Brick? It vill nefer get loscht and we can add der battery bek pek.

Tim: ok guys, time to take it outside again.

espiegel123

@Jocphone said:

Trying to join the Slack thing I get this message. Is this a problem with Slack? (I don't know what Slack is yet)

Slack is basically a chat environment used by a lot of work environments. Did you try using a different email address?

Jocphone

@espiegel123 said:

@Jocphone said:

Trying to join the Slack thing I get this message. Is this a problem with Slack? (I don't know what Slack is yet)

Slack is basically a chat environment used by a lot of work environments. Did you try using a different email address?

No I didn't. I chose the new Apple provided 'hide my email'. Don't really want to sign up for the latest fashion in social sites and I try to limit how often I give out my email. It's alright though I will just continue to post here.

rs2000

@ashh said:

@rs2000 said:

@scrufftv said:
Anyone know if transport control from external midi hardware is supported? Being able to record loops started and stopped from the transport controls of the Digitakt for example. Ideally not through a workaround with Midi link sync and Ableton link, a direct connection.

Syncing with MIDI Clock includes exchange of MIDI status messages for start, stop and continue. I haven't tried with my Digitakt yet but the current Loopy HD runs perfectly in sync.
Clock sync is different from MMC which I'd be surprised if supported by Loopy Pro.

You'd be surprised if clock sync was supported?

No I meant MMC but yeah I wasn't clear indeed 😅

wim

@Jocphone said:

@espiegel123 said:

@Jocphone said:

Trying to join the Slack thing I get this message. Is this a problem with Slack? (I don't know what Slack is yet)

Slack is basically a chat environment used by a lot of work environments. Did you try using a different email address?

No I didn't. I chose the new Apple provided 'hide my email'. Don't really want to sign up for the latest fashion in social sites and I try to limit how often I give out my email. It's alright though I will just continue to post here.

It was confusing. They give the option to sign in with your Apple ID then don't let you in with it. They sent a link to sign in and that link signed me in directly with no account or password. I can't figure out the logic behind that. but oh well I did it anyway.

In my opinion is Slack isn't something you want to mess with then posting here is fair game. I'd be the same if Facebook was the preferred platform.

wim

@ashh said:
@wim been thinking that a Touch OSC template might be a good way into LP for noobs. Like, a 5 page (or whatever) template that exposes all the features. What do you think?

Good thinking @ashh, but I can't think of anything TouchOSC would bring to the party. Everything I can think of that you might want to do with TouchOSC can be done in Loopy Pro. It has custom widgets (things like sliders and knobs) that can be placed anywhere on a page. Heck, you can even use Loopy just as a control surface for other apps with no loops at all ... in an AUv3 no less.

wim

@rs2000 said:

@scrufftv said:
Anyone know if transport control from external midi hardware is supported? Being able to record loops started and stopped from the transport controls of the Digitakt for example. Ideally not through a workaround with Midi link sync and Ableton link, a direct connection.

Syncing with MIDI Clock includes exchange of MIDI status messages for start, stop and continue. I haven't tried with my Digitakt yet but the current Loopy HD runs perfectly in sync.
Clock sync is different from MMC which I'd be surprised if supported by Loopy Pro.

You are completely right. I was referring to MIDI Beat Clock Messages but mistakenly called them MMC. Thanks for the correction!