Moog Mariana VST/AU/iOS Bass Synth

[vertibration]

2023 and people still watching CPU. Maybe Im spoiled with the M1/2/3 macs.

Well… when the system can’t do much more after loading just an instance, maybe cpu is a concern.
Maybe my Macbook Air is a “low end entry level” for the M1 line, but the cpu load is noticeable even on such machine.

If a plugin sounds really good, then it’s worth considering getting a new more powerful pc, it’s the same old story… I remeber when Diva appeared, my pc at the time couldn’t really handle it… I don’t know if Moog Mariana needs some code optimization or if the cpu load is actually needed, anyway it’s a fact that it requires more power than average and it’s on the heavy side for current machines.

A M1 doesn’t cut well enough in this case, I’m afraid I’d need a more powerful computer unless I resort to freezing tracks (which is always an option, albeit not so desiderable). But things will move on to more powerful computers, eventually. It’s just an heavy synth for the current times.

I have an M1 mac mini, everything you said about M1 is utterly false

[Ou_Tis]

2023 and people still watching CPU. Maybe Im spoiled with the M1/2/3 macs.

Well… when the system can’t do much more after loading just an instance, maybe cpu is a concern.
Maybe my Macbook Air is a “low end entry level” for the M1 line, but the cpu load is noticeable even on such machine.

If a plugin sounds really good, then it’s worth considering getting a new more powerful pc, it’s the same old story… I remeber when Diva appeared, my pc at the time couldn’t really handle it… I don’t know if Moog Mariana needs some code optimization or if the cpu load is actually needed, anyway it’s a fact that it requires more power than average and it’s on the heavy side for current machines.

A M1 doesn’t cut well enough in this case, I’m afraid I’d need a more powerful computer unless I resort to freezing tracks (which is always an option, albeit not so desiderable). But things will move on to more powerful computers, eventually. It’s just an heavy synth for the current times.

I have an M1 mac mini, everything you said about M1 is utterly false

Could it be dependent on the DAW? Or other factors?

[vertibration]

2023 and people still watching CPU. Maybe Im spoiled with the M1/2/3 macs.

Well… when the system can’t do much more after loading just an instance, maybe cpu is a concern.
Maybe my Macbook Air is a “low end entry level” for the M1 line, but the cpu load is noticeable even on such machine.

If a plugin sounds really good, then it’s worth considering getting a new more powerful pc, it’s the same old story… I remeber when Diva appeared, my pc at the time couldn’t really handle it… I don’t know if Moog Mariana needs some code optimization or if the cpu load is actually needed, anyway it’s a fact that it requires more power than average and it’s on the heavy side for current machines.

A M1 doesn’t cut well enough in this case, I’m afraid I’d need a more powerful computer unless I resort to freezing tracks (which is always an option, albeit not so desiderable). But things will move on to more powerful computers, eventually. It’s just an heavy synth for the current times.

I have an M1 mac mini, everything you said about M1 is utterly false

Could it be dependent on the DAW? Or other factors?

No......as long as you have an M1, and your DAW is native (most are) plugins run efficiently. Whatever that person said about M1 sounds to me like his macbook air is probably an intel mac, and he chose to say things about M1 macs that just arent accurate in the slightest.

[aijaijaijai]

Sounds great and like the modulation possibilities.
6 instances were too much for M1 16" in Logic X with buffer set at 512. Had to bounce them to audio, so I'd say the CPU load is quite extreme.
It should be bigger on the screen. I'd like to be able to turn down selected oscillators up or down at the same time.
The possibility see all of the pages at the same time.

[aijaijaijai]

2023 and people still watching CPU. Maybe Im spoiled with the M1/2/3 macs.

There's way too little processing power in M1 16" 32GB.
I work with 100-200 tracks quite often so I just run out of CPU.

[zerocrossing]

I fail to see what this plugin offers that others do not

Nothing, really, except for its character, which is pretty unique. I put it up against a bunch of synths with Moog filters, and none of them were remotely like it, including a hardware Moog filter clone.

well it does feature fulll (virtual) CV-connectivity with the moogerfoger plugins, which is sick.

I saw that, but I didn’t have time to get to checking out out, but I will today. One of Moog’s representatives mentioned that it is capable of FM “under the hood.” I didn’t see anything obvious that allowed that, but I also didn’t crack open the manual, so perhaps I need to do some homework. That kind of thing should be fairly obvious. I’m no expert, but I’ve been using synthesizers since the 80s, so I sort of know where to look, and I didn’t see anything.

[midi sentinel]

Is this the very last Moog Bass Synthesizer emulation that I'll ever need?

A game changer, one might say

[simmo75]

Well, this was unexpected:

https://www.moogmusic.com/products/mariana

$49 intro price. Must...resist...

--
Marco

Might get iOS version as it still works on desktop as au3

Are you sure?

[sin night]

2023 and people still watching CPU. Maybe Im spoiled with the M1/2/3 macs.

Well… when the system can’t do much more after loading just an instance, maybe cpu is a concern.
Maybe my Macbook Air is a “low end entry level” for the M1 line, but the cpu load is noticeable even on such machine.

If a plugin sounds really good, then it’s worth considering getting a new more powerful pc, it’s the same old story… I remeber when Diva appeared, my pc at the time couldn’t really handle it… I don’t know if Moog Mariana needs some code optimization or if the cpu load is actually needed, anyway it’s a fact that it requires more power than average and it’s on the heavy side for current machines.

A M1 doesn’t cut well enough in this case, I’m afraid I’d need a more powerful computer unless I resort to freezing tracks (which is always an option, albeit not so desiderable). But things will move on to more powerful computers, eventually. It’s just an heavy synth for the current times.

I have an M1 mac mini, everything you said about M1 is utterly false

Could it be dependent on the DAW? Or other factors?

No......as long as you have an M1, and your DAW is native (most are) plugins run efficiently. Whatever that person said about M1 sounds to me like his macbook air is probably an intel mac, and he chose to say things about M1 macs that just arent accurate in the slightest.

It’s a M1 Macbook Air, not an Intel (that was my previous macbook). And I stand on what I wrote, I used the synth in standalone mode (maybe that’s the culprit?) and I had those numbers in the OSX application monitor. I may try rebooting my mac to be extra-safe, but those were the numbers yesterday evening.
I’ll try again after dinner and provide screenshots for reference.

[vertibration]

One instance gives me about 30% CPU. I think that is high, but not horrendous. I ran about 8 instances before it started to crap out. Are you having a problem with just one instance? Is that the issue here? If so, it doesnt seem like something is adding up.

[sin night]

So, I reboot my Macbook Air M1 and this is the result with Mariana in standalone mode.

Moog Mariana Macbook Air M1.jpg

The samplerate is 44.100 and the buffer size is 512. I'm using the internal audio. The CPU load seems dependent on how much modulation is going on.

Is it a problem? Well, I think my Macbook Air M1 can handle a few instances of Mariana, but then it's an issue if I don't have enough power to load other synths or effects to complete the project... unless I freeze, of course. Which I may actually do if needed, but it's less convenient than keeping everything live.

[aMUSEd]

Anyone know how long the intro price is?

[thecontrolcentre]

42

[sin night]

So, I tried Mariana as a plugin in Ableton Live.

Spoiler/tip: don't rely just on your daw meters when it comes to performances, use the system tools.

I measured the cpu usage of Live (since Mariana is running inside it as a plugin).

When I started Ableton Live, the daw monitor shows 0% load while the system monitor reports about 7-8%

Live no Mariana.jpeg

After loading just one instance of Mariana with the "Reese JD" preset (the same as my standalone tests), Ableton reports 30% while the system reports about 48%

Live 1x Mariana.jpeg

Then I loaded a second instance with the same "Reese JD Preset". Ableton reports about the same as before (actually, it says 27% in my screen! it went down by loading a second instance! but then it went back to 30%), while the system monitor reports about 77%.

Live 2x Mariana.jpeg

The values are comparable/compatible with what I saw in standalone mode.

I would just trust the system monitor.

[sin night]

So, about 40% for the first instance, then about 30% for every additional instance. Add your host overhead on top (another 7-10%). Just for loading the plugin, I didn’t play any note.

That preset uses a bit of modulation, so it’s slightly heavier than the majority of the presets (but I think I went through a few even heavier).

So, these are the numbers I measured.