New Moog Animoog Z AUV3 Released!

_smund

I've read on the Roli Seaboard Blocks homepage that the original animoog didn't have support for slide, how is that with animoog z?
How do I look into changing what parameters the Seaboard changes in there?

uncledave

@pedro said:
How about imaginando’s LK? I am about to buy the matrix, but I made a simple test, figured out how to record from AZ to LK, and just recorded a few bars of random notes and sliding on AZ keyboard, and LK records the notes and CC84, which is... portamento? I didn’t see any pitch bend but I run out of time. I’ll have try again later. Anyway, it didn’t playback the same, but maybe I did something wrong.
Does anyone know if it works in this scenario?

Edit: wait, I perhaps didn’t choose a good preset on animoog. Should be one with “glide”. I bought the matrix iap on LK already (was going to, regardless), and I suspect it will work with the right preset.
And another thing I think I did wrong was I recorded only one channel. For mpe to be captured it must record all channels cause it takes one per voice, right?
Gonna try again later but I have great hopes.

But I still have this question:
“ I must be really dumb, but where is the map CCs button that overlays the numbers on animoog? Can’t find it anywhere...”

Settings, MIDI, Map CCs. Shows boxes (Animoog) or circles (Animoog Z) on the mappable controls. No numbers until you map something.

solncekreeze

@pedro said:
How about imaginando’s LK? I am about to buy the matrix, but I made a simple test, figured out how to record from AZ to LK, and just recorded a few bars of random notes and sliding on AZ keyboard, and LK records the notes and CC84, which is... portamento? I didn’t see any pitch bend but I run out of time. I’ll have try again later. Anyway, it didn’t playback the same, but maybe I did something wrong.
Does anyone know if it works in this scenario?

Edit: wait, I perhaps didn’t choose a good preset on animoog. Should be one with “glide”. I bought the matrix iap on LK already (was going to, regardless), and I suspect it will work with the right preset.
And another thing I think I did wrong was I recorded only one channel. For mpe to be captured it must record all channels cause it takes one per voice, right?
Gonna try again later but I have great hopes.

But I still have this question:
“ I must be really dumb, but where is the map CCs button that overlays the numbers on animoog? Can’t find it anywhere...”

pedro

@uncledave @solncekreeze thanks guys, I must be blind. I swear I looked into settings *facepalm*

oat_phipps

So I want an MPE controller now, primarily to control Animoog. Am I right in hearing that the Roli Seabords have problems with iOS? What is the best cost-friendly MPE keyboard on the market?

Thanks in advance for any help or sarcastic jokes

Tarekith

The new red Qunexus does MPE quite easily now.

Artvarg

I have an issue with AZ in AUM. If I play a clip from Atom 2 it works as expected the first time, but as soon as the clip repeats AZ is not outputting any sound anymore. AZ doesn’t even react to its own keyboard or the AUM keyboard at this point. As soon as I reload or change the preset it’s back to normal.
Any one know what might be going on? 🤔

oat_phipps

@Artvarg said:
I have an issue with AZ in AUM. If I play a clip from Atom 2 it works as expected the first time, but as soon as the clip repeats AZ is not outputting any sound anymore. AZ doesn’t even react to its own keyboard or the AUM keyboard at this point. As soon as I reload or change the preset it’s back to normal.
Any one know what might be going on? 🤔

I had this exact same problem last night with the forthcoming MIDI Tape Recorder app (beta). I couldn’t recreate it however.

sclurbs

Still hoping for a @Gavinski tutorial on this one

Artvarg

@oat_phipps said:

@Artvarg said:
I have an issue with AZ in AUM. If I play a clip from Atom 2 it works as expected the first time, but as soon as the clip repeats AZ is not outputting any sound anymore. AZ doesn’t even react to its own keyboard or the AUM keyboard at this point. As soon as I reload or change the preset it’s back to normal.
Any one know what might be going on? 🤔

I had this exact same problem last night with the forthcoming MIDI Tape Recorder app (beta). I couldn’t recreate it however.

That’s strange. I‘ll see if I can recreate it again in the next days and see how different sequencers behave.

Jumpercollins

Great track.

Edward_Alexander

@Tarekith said:
The new red Qunexus does MPE quite easily now.

Does it have to be a “red” one?

mojozart

@Edward_Alexander said:

@Tarekith said:
The new red Qunexus does MPE quite easily now.

Does it have to be a “red” one?

The v2.0.6 firmware will eventually be backported, but for now it is RED only.

aaronpc

@mojozart said:

@Edward_Alexander said:

@Tarekith said:
The new red Qunexus does MPE quite easily now.

Does it have to be a “red” one?

The v2.0.6 firmware will eventually be backported, but for now it is RED only.

You can get the 2.0.6 firmware now for the Qunexus. Still waiting on the Quneo port though.

Carnbot

Yes I’ve installed the new firmware on my black QuNexus

Carnbot

There's a great new update with a free sound and timbre pack today, celestial dynamics

oat_phipps

New update with a small free 10 preset 4 timbre pack, and a price increase for the full unlock to $20. Still a steal. BUT…

@MoogMusicInc BAD NEWS: The update has introduced crackling (pops) for me on a 2020 iPad Pro newly updated to 15.2 and rebooted. Using the Digeridoo preset in the new preset pack for reference. This goes for standalone and AU at 48k. Interestingly, the standalone and AU performed flawlessly in AUM at buffers of 64, and seemed less poppy at 128. At default 256 and 512 in both versions, the problems occur. Dunno if the 15.2 iOS update or the Animoog update is the culprit, but you guys seem excellent and quick at figuring these things out.

Also note these tests were fiddling around over a just a matter of 10 minutes, so maybe it just needed a good warmup, but until now I’ve NEVER experienced pops or crackling with Animoog, especially as the only app open or only AU hosted.

MoogMusicInc

@oat_phipps said:
New update with a small free 10 preset 4 timbre pack, and a price increase for the full unlock to $20. Still a steal. BUT…

@MoogMusicInc BAD NEWS: The update has introduced crackling (pops) for me on a 2020 iPad Pro newly updated to 15.2 and rebooted. Using the Digeridoo preset in the new preset pack for reference. This goes for standalone and AU. Interestingly, the standalone and AU performed flawlessly in AUM at buffers of 64, and seemed less poppy at 128. At default 256 and 512 in both versions, the problems occur. Dunno if the 15.2 iOS update or the Animoog update is the culprit, but you guys seem excellent and quick at figuring these things out.

Thanks for the report, there were absolutely no changes to the audio engine, so we doubt Animoog Z caused this regression. We'll have a closer look though.

your friends at Moog

oat_phipps

@MoogMusicInc said:

@oat_phipps said:
New update with a small free 10 preset 4 timbre pack, and a price increase for the full unlock to $20. Still a steal. BUT…

@MoogMusicInc BAD NEWS: The update has introduced crackling (pops) for me on a 2020 iPad Pro newly updated to 15.2 and rebooted. Using the Digeridoo preset in the new preset pack for reference. This goes for standalone and AU. Interestingly, the standalone and AU performed flawlessly in AUM at buffers of 64, and seemed less poppy at 128. At default 256 and 512 in both versions, the problems occur. Dunno if the 15.2 iOS update or the Animoog update is the culprit, but you guys seem excellent and quick at figuring these things out.

Thanks for the report, there were absolutely no changes to the audio engine, so we doubt Animoog Z caused this regression. We'll have a closer look though.

your friends at Moog

Thanks, I added a little caveat at the end as this was very unscientific and rough, but appreciate the lightning speed response! Happy holidays!

auxmux

Is MelodyBud a new app?

Poppadocrock

@auxmux said:
Is MelodyBud a new app?

In beta, from @cem_olcay

Poppadocrock

New Animoog Z update with a free preset pack, and other stuff…

Edit - realized I’m approximately the 4th person to post this, lol.

DMfan

@oat_phipps said:
@MoogMusicInc BAD NEWS: The update has introduced crackling (pops) for me on a 2020 iPad Pro newly updated to 15.2 and rebooted. Using the Digeridoo preset in the new preset pack for reference. This goes for standalone and AU at 48k. Interestingly, the standalone and AU performed flawlessly in AUM at buffers of 64, and seemed less poppy at 128. At default 256 and 512 in both versions, the problems occur. Dunno if the 15.2 iOS update or the Animoog update is the culprit, but you guys seem excellent and quick at figuring these things out.

Also note these tests were fiddling around over a just a matter of 10 minutes, so maybe it just needed a good warmup, but until now I’ve NEVER experienced pops or crackling with Animoog, especially as the only app open or only AU hosted.

iPad Air 4, iPadOS 15.2, preset Didgeridoo, all buffer sizes, no issues for reference. Very strange.

/DMfan🇸🇪

CracklePot

Updated and sounds great to me.
No audio problems.

Skyblazer

@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

oat_phipps

@Skyblazer said:
@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

Had the import question as well. And I’m no longer having problems with it.

MoogMusicInc

@Skyblazer said:
@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

Thanks for the bug report, we'll look into that Hold behavior.

If you imported presets through the zip file method, any imported file that you didn't manually open and re-save will automatically benefit from the legacy import improvements in this version.

If you opened a legacy preset and then saved it, it will have been converted to the newer format and not adopt the improvements in this release.

The changes are extremely minor though and only affected presets where the comets were placed extremely precisely at timbre limits. For 99% of the legacy preset this will be imperceptible.

❤️ Your friends at Moog

circledsquare

@MoogMusicInc said:

@Skyblazer said:
@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

Thanks for the bug report, we'll look into that Hold behavior.

If you imported presets through the zip file method, any imported file that you didn't manually open and re-save will automatically benefit from the legacy import improvements in this version.

If you opened a legacy preset and then saved it, it will have been converted to the newer format and not adopt the improvements in this release.

The changes are extremely minor though and only affected presets where the comets were placed extremely precisely at timbre limits. For 99% of the legacy preset this will be imperceptible.1

❤️ Your friends at Moog

Thanks for the update and the presets!

Any word on fixing the automatic tag assignment during import of newer Animoog OG presets (the ones using the v4 preset style, basically anything created in the last few years)? This is blocking me from migrating to Animoog Z, and other people were having trouble with this if you look back in this thread. It means that freely available patches from Rustik (some of his), a few others and from me as well don't get any tags, so it is difficult to browse them. I would just revert my patches back to v2, but I often use the longer paths which are not supported in v2.

Also, a random question: why are most of the Animoog Z patches set to 4 voices instead of 16? For people who don't know to change this, this makes Animoog Z seem more limited than it is since there is excessive voice stealing, seems very counter-productive to me.

oat_phipps

@circledsquare said:

@MoogMusicInc said:

@Skyblazer said:
@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

Thanks for the bug report, we'll look into that Hold behavior.

If you imported presets through the zip file method, any imported file that you didn't manually open and re-save will automatically benefit from the legacy import improvements in this version.

If you opened a legacy preset and then saved it, it will have been converted to the newer format and not adopt the improvements in this release.

The changes are extremely minor though and only affected presets where the comets were placed extremely precisely at timbre limits. For 99% of the legacy preset this will be imperceptible.1

❤️ Your friends at Moog

Thanks for the update and the presets!

Any word on fixing the automatic tag assignment during import of newer Animoog OG presets (the ones using the v4 preset style, basically anything created in the last few years)? This is blocking me from migrating to Animoog Z, and other people were having trouble with this if you look back in this thread. It means that freely available patches from Rustik (some of his), a few others and from me as well don't get any tags, so it is difficult to browse them. I would just revert my patches back to v2, but I often use the longer paths which are not supported in v2.

Also, a random question: why are most of the Animoog Z patches set to 4 voices instead of 16? For people who don't know to change this, this makes Animoog Z seem more limited than it is since there is excessive voice stealing, seems very counter-productive to me.

For the latter, I’m certain it’s CPU performance reasons.

MoogMusicInc

@circledsquare said:

@MoogMusicInc said:

@Skyblazer said:
@MoogMusicInc Found a small bug. When the keyboard view is maximized, and you swipe the preset selector left or right, the highlighting of the "Hold" button isn't updated to reflect a preset where it's enabled or disabled.

Also, in the update notes where it says, "Improvements to legacy import correctness", is that applied retroactively, or should I re-import?

...and thanks for the free preset pack!

Thanks for the bug report, we'll look into that Hold behavior.

If you imported presets through the zip file method, any imported file that you didn't manually open and re-save will automatically benefit from the legacy import improvements in this version.

If you opened a legacy preset and then saved it, it will have been converted to the newer format and not adopt the improvements in this release.

The changes are extremely minor though and only affected presets where the comets were placed extremely precisely at timbre limits. For 99% of the legacy preset this will be imperceptible.1

❤️ Your friends at Moog

Thanks for the update and the presets!

Any word on fixing the automatic tag assignment during import of newer Animoog OG presets (the ones using the v4 preset style, basically anything created in the last few years)? This is blocking me from migrating to Animoog Z, and other people were having trouble with this if you look back in this thread. It means that freely available patches from Rustik (some of his), a few others and from me as well don't get any tags, so it is difficult to browse them. I would just revert my patches back to v2, but I often use the longer paths which are not supported in v2.

Also, a random question: why are most of the Animoog Z patches set to 4 voices instead of 16? For people who don't know to change this, this makes Animoog Z seem more limited than it is since there is excessive voice stealing, seems very counter-productive to me.

We don't know of any tag assignment problems. The logic for assigning tags is done based on the folder structure because the original Animoog didn't have tags nor groups, just categories that were essentially folders. This is why we recommend importing through a zip archive that is taken from the original Animoog's document folder. If you have any other problems, please contact us at [email protected], it's hard to keep track of all online messages that are posted.

The original presets are imported as 4 voices because that's what they were designed for. Many of them have envelope behaviors that sounds very overloaded if voice stealing doesn't limit the active voices to 4.

❤️ Your friends at Moog