Synapse Audio - Dune 3.5 Released

[Teksonik]

I get lots of cpu spikes with Dune 3.5 and Bitwig 4.1 (same with 4.0). This is with the new 16" M1-Pro MBP and project @96khz. I made a clip with maybe 4-6 notes polyphony and duplicated the track until there were 12 tracks and the spikes caused crackles. I switched to RePro-5 and even with 24 tracks there was plenty of cpu left.

Did you report this to Synapse? I'm on Windows so can't test any issues with M1.

Someone else reported a similar issue at the Synapse forums but it apparently has to do with the Bitwig Beta:

https://forum.synapse-audio.com/viewtop ... =0#p120507

I can pass your report along in case Richard or Marcin don't see it here but I'd suggest making reports at the Synapse forums as posts can get buried pretty quickly here.

[Biome_Digital]

When are we getting our BF sale at Synapse !!! Why are they keeping us waiting for so long !!

Richard did say....

We'll see about BF once the free demos for DUNE 3.5 are uploaded. The demos (Mac/PC) should be available later today.
Richard

The new demos dropped about an hour ago so....

It's still Wednesday here but I realize in places like Australia it's probably already December.

Patience I guess...not Black Friday yet......

If they are mutated they would not be the carefully created presets I made to start with.

I take pride in my work, I would hope others do too.

[Richard_Synapse]

I get lots of cpu spikes with Dune 3.5 and Bitwig 4.1 (same with 4.0). This is with the new 16" M1-Pro MBP and project @96khz. I made a clip with maybe 4-6 notes polyphony and duplicated the track until there were 12 tracks and the spikes caused crackles. I switched to RePro-5 and even with 24 tracks there was plenty of cpu left.

Is this with Multithreading enabled or disabled? (it should be disabled in this case). Also, which patch(es) exactly are you using/comparing? The CPU usage varies substantially depending on the number of layers/voices in a patch, which filters/fx are used, etc.

Richard

[Biome_Digital]

do you think you'd hear it?
sadly there's nothing you can do, as it's not like it retains any identifying data?

Actually the parent patch names are noted and saved in the patch info window but....well I'll just leave it at that.

Easily deleted

[AnX]

Nuff said...

[XorXisT]

I get lots of cpu spikes with Dune 3.5 and Bitwig 4.1 (same with 4.0). This is with the new 16" M1-Pro MBP and project @96khz. I made a clip with maybe 4-6 notes polyphony and duplicated the track until there were 12 tracks and the spikes caused crackles. I switched to RePro-5 and even with 24 tracks there was plenty of cpu left.

Same strange behavior here with Logic.

After some testing, I observed that DUNE uses the last CPU core max out (cause of crackles, I guess), and other cores remain consistent even as low as 25% cpu usage.

Hive 2 with the same method, all cores are mostly the same.

MBA M1, Logic 10.7.1, DUNE AU 3.512, audio settings: 8 (4 High Performance Cores), 128 samples

[vurt]

do you think you'd hear it?
sadly there's nothing you can do, as it's not like it retains any identifying data?

Actually the parent patch names are noted and saved in the patch info window but....well I'll just leave it at that.

Easily deleted

so my biotek bank is a go!

[pdxindy]

I get lots of cpu spikes with Dune 3.5 and Bitwig 4.1 (same with 4.0). This is with the new 16" M1-Pro MBP and project @96khz. I made a clip with maybe 4-6 notes polyphony and duplicated the track until there were 12 tracks and the spikes caused crackles. I switched to RePro-5 and even with 24 tracks there was plenty of cpu left.

Is this with Multithreading enabled or disabled? (it should be disabled in this case). Also, which patch(es) exactly are you using/comparing? The CPU usage varies substantially depending on the number of layers/voices in a patch, which filters/fx are used, etc.

Richard

thanks for the reply...

Multithreading was enabled, but it is the same with multithreading off.

However, I now have some further information. Bitwig has different plugin hosting options. I use "Together" as my default. When I switch to "Within Bitwig" the cpu spikes stop in Dune 3.5 and I can add 100 duplicate tracks of Dune playing 4-6 note polyphony without being close to cpu overload.

Bitwig is not sure if it is a Bitwig issue, a Mac OS issue, or plugin issue. They are investigating.

[cytospur]

Hopefully with better graphics

I think this was mentioned on the beta forum, possibly by Mark.

I mentioned applying genetics to the mod matrix, but you could achieve the same thing as Animoog that way I guess.

[Teksonik]

do you think you'd hear it?
sadly there's nothing you can do, as it's not like it retains any identifying data?

Actually the parent patch names are noted and saved in the patch info window but....well I'll just leave it at that.

------

Yea that's why I said I'll leave it at that......

[Teksonik]

Hopefully with better graphics
I think this was mentioned on the beta forum, possibly by Mark.

I mentioned applying genetics to the mod matrix, but you could achieve the same thing as Animoog that way I guess.

Genetics are applied to the MM now or did you have something else in mind?

I think the Animoog thing he's asking for is Randomize which is different from Genetics.

What would be the point of choosing three parent patches then excluding for example the LFO Genetics from the child patch?

What value would the LFO's have then? Default or the values in Parent 1 or Parent 2 or Parent 3 or ?

[cytospur]

I meant a more focussed way of applying Genetics in the MM. I already know that it works there, I just think it could be better than it is now. Blame it on my brevity

Genetics is a great idea, random not so much, unless you can apply some constraints, in which case you're halfway to making the patch anyway.

[Touch The Universe]

Wow, very generous BF offer, outstanding.

[Richard_Synapse]

Multithreading was enabled, but it is the same with multithreading off.

However, I now have some further information. Bitwig has different plugin hosting options. I use "Together" as my default. When I switch to "Within Bitwig" the cpu spikes stop in Dune 3.5 and I can add 100 duplicate tracks of Dune playing 4-6 note polyphony without being close to cpu overload.

Bitwig is not sure if it is a Bitwig issue, a Mac OS issue, or plugin issue. They are investigating.

Thank you for the reply, this is very good to know, should someone else stumble into this. So far we have very positive experience with Bitwig support, so in case we need their help or vice versa, it should be possible to sort it out.

A note on Multithreading on M1. All M1 cpus are currently divided into "performance" and "efficiency" cores. At this point we do not know exactly what the impact of this is regarding plugin multithreading. We could end up rendering some voices on an efficiency core, which may slow down things. Perhaps we should set MT=off on M1 by default, if it isn't already.

Richard

[XorXisT]

Same strange behavior here with Logic.

After some testing, I observed that DUNE uses the last CPU core max out (cause of crackles, I guess), and other cores remain consistent even as low as 25% cpu usage.

Hive 2 with the same method, all cores are mostly the same.

MBA M1, Logic 10.7.1, DUNE AU 3.512, audio settings: 8 (4 High Performance Cores), 128 samples

Just tested with Multithreading = OFF and voila! No more spikes and all cores are mostly the same %.

So yeah, Multithreading should be OFF by default.