MOZAIC - Create your own AU MIDI plugins - OUT NOW!

pejman

@wim thanks for reply and help .
Is it possible to make for example an arpeggiator with AUV3 support with swift playground that can connect with other apps that support midi and midi clock option support?

You said :
“You can deploy a full program on your own devices with a free Apple Developer account. You can't distribute it to others though without a paid developer account. With a paid developer account you can have others test it using TestFlight once the test version is approved by Apple and eventually list it in the App Store.”

This means that I have to write the codes by xcode for example and then by apple developers I can use it on my device but only for myself if I don't want to pay money to apple ?

You said: You can't just write any app and use it on devices without going through Apple in some way.

It means that the designed app must be registered at least in apple developer so that we can use it personally on our device ?

wim

@pejman said:
It means that the designed app must be registered at least in apple developer so that we can use it personally on our device ?

Yes. Unless you build it in Swift Playgrounds, then you can run it from within the Playgrounds app.

uncledave

@pejman said:
Is it possible to make for example an arpeggiator with AUV3 support with swift playground that can connect with other apps that support midi and midi clock option support?

You can do quite a lot with Mozaic. And it already has all those tedious real-time features built-in. It feeds you MIDI messages one at a time, you can send messages as desired, and you can just focus on the algorithm. You can share your project on PatchStorage, or simply by email. No messing with developer accounts, test codes, and so forth.

wim

@pejman said:
@wim thanks for reply and help .
Is it possible to make for example an arpeggiator with AUV3 support with swift playground that can connect with other apps that support midi and midi clock option support?

That would be a huge stretch to do with Swift Playgrounds. I wouldn't waste my time looking into that personally.

pejman

@uncledave said:

@pejman said:
Is it possible to make for example an arpeggiator with AUV3 support with swift playground that can connect with other apps that support midi and midi clock option support?

You can do quite a lot with Mozaic. And it already has all those tedious real-time features built-in. It feeds you MIDI messages one at a time, you can send messages as desired, and you can just focus on the algorithm. You can share your project on PatchStorage, or simply by email. No messing with developer accounts, test codes, and so forth.

@uncledave
Hello .Thank you for your guidance. I have been teaching mozaic coding through my good friends @espiegel123 @wim @_ki @McD for a long time and so far I have written 23 patches which is extremely valuable to me, but for some reason I have not uploaded them to patch storage until now .

But what I mean by making an arpeggiator is a professional arpeggiator, with ability note programming and shift notes earlier than the orginal time. This is impossible in mozaic.

wim

@pejman said:
But what I mean by making an arpeggiator is a professional arpeggiator, with ability note programming and shift notes earlier than the orginal time. This is impossible in mozaic.

Hi @pejman. This comment is interesting to me. Can you explain what you mean by "shift notes earlier in time"?

pejman

Hi @wim ❤️

Cream mobile arpeggiator Available on the App Store https://apps.apple.com/us/app/cream-mobile/id890886111
This is the app I wanted to make a midi controller for, through mozaic along with creating lfos, which I needed a lot of lfos for, and I've been learning for a long time to color the pads for 12 patterns. This arpeggiator has 4 tracks, which means basically 4 arpeggiators, each with 12 patterns. Unfortunately, this app does not support AUV3. I've been using this arpeggiator for 9 years, it's amazing to me.

pejman

@wim What I mean by playing notes earlier than their actual time is that when the notes are already arranged, in a specific step, one or several notes are played earlier than their original time, which is possible in an arpeggiator like this and cannot be expected from mozaic.

uncledave

@pejman said:
@wim What I mean by playing notes earlier than their actual time is that when the notes are already arranged, in a specific step, one or several notes are played earlier than their original time, which is possible in an arpeggiator like this and cannot be expected from mozaic.

I believe you could implement this in Mozaic. Clock it faster, and look ahead to the next event when wanting to play it earlier. Bit of a data management nightmare however. It's likely more effective to shop around the many arps and sequencers already available for iOS.

pejman

@uncledave said:

@pejman said:
@wim What I mean by playing notes earlier than their actual time is that when the notes are already arranged, in a specific step, one or several notes are played earlier than their original time, which is possible in an arpeggiator like this and cannot be expected from mozaic.

I believe you could implement this in Mozaic. Clock it faster, and look ahead to the next event when wanting to play it earlier. Bit of a data management nightmare however. It's likely more effective to shop around the many arps and sequencers already available for iOS.

Unfortunately, as far as I've researched, there is no such arpeggiator in the App Store that has the ability to shift for selected steps. I have use Bleassarp, steppolyarp, chaosarp

wim

@pejman said:
@wim What I mean by playing notes earlier than their actual time is that when the notes are already arranged, in a specific step, one or several notes are played earlier than their original time, which is possible in an arpeggiator like this and cannot be expected from mozaic.

I don't see why you couldn't do that in Mozaic.

An arpeggio is just an arrangement of notes in a grid where each "cell" is a point in time. Shifting particular notes earlier in time is just a matter of having a fine enough grid and altering the time that the note should trigger.

Let's say your arpeggiator normally worked in 16th note increments. Regular quarter notes would trigger on step 1, 5, 9, and 13.

If you wanted to be able to shift individual notes in 128th note increments, you'd change that to a grid with 128 steps and trigger regular quarter notes on step 1, 32, 64, and 96. Now you can choose to adjust particular notes earlier or later in time, for instance: 1, 30, 64, 96. It's just a matter of having a fine enough grid, and keeping track of the original scheduled time and the time offset for each step.

Coming up with a UI that works well for an arpeggiator in Mozaic seems like it would be a challenge though. But writing an app from scratch? That has a huge learning curve and takes a lot of work even if you already know what you're doing.

pejman

@wim said:

@pejman said:
@wim What I mean by playing notes earlier than their actual time is that when the notes are already arranged, in a specific step, one or several notes are played earlier than their original time, which is possible in an arpeggiator like this and cannot be expected from mozaic.

I don't see why you couldn't do that in Mozaic.

An arpeggio is just an arrangement of notes in a grid where each "cell" is a poin

It's an interesting idea. I'll have to think about it. Although it's a little flexible, I think it's possible.