Notifications
Clear all

Unify 1.1.7 AU Sample Rate Issue in Maschine


klasus
(@klasus)
Eminent Member
Joined: 2 years ago
Posts: 36
Topic starter  

There's an issue with Unify 1.1.7 AU in Maschine 2.10.1 where the pitch of an Instrument changes after changing the Sample Rate of the Project. I was using the Patch "BPM Plucks Ripple Pool" and I noticed that the pitch was off after having changed the Sample Rate from 44.1 to 48 kHz.


Quote
Topic Tags
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 

@klasus

Thank you for mentioning this. When you say "there's an issue with Unify 1.1.7", are you implying that earlier Unify versions handled this correctly?


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 2 years ago
Posts: 36
Topic starter  

@getdunne

I can't tell, really. Usually I produce in 44.1 but this is for an animation job so I wanted to use 48 kHz right from the beginning. I noticed that the pitch was off in Unify when I exported the mix in 48 kHz. When I switched to 44.1 it sounded correct again. And when I switched back to 48 kHz it was off between 1 to 2 semitones again. It sounded like what happens when playing back a 44.1 sample at 48 kHz. Changing the Samplerate only affected Unify. Feels like it doesn't get notified that the sample rate has changed. Haven't tested this in Logic or with the VST yet.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @klasus

@getdunne

Changing the Samplerate only affected Unify.

Do you mean it DIDN'T affect Unify? If not, I'm confused.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 2 years ago
Posts: 36
Topic starter  

@getdunne

 

Changing the sample rate in Maschine makes Unify AU act weird. It doesn't conform to the change of the sample rate so the pitches of anything loaded into it are off. I can't tell if it worked correctly in previous versions of the AU or not.

I am using the VST for now because it is working corretly – but the AU is not. Hope this helps.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @klasus

@getdunne

I am using the VST for now because it is working corretly – but the AU is not. Hope this helps.

Ah, that's the critical detail! Thank you. I'll look into this.

The JUCE framework on which Unify is based attempts to support all major plug-in formats (VST2, VST3, AU) equally well, but there are occasional problems like this. VST2 is the oldest of the three, and tends to work best overall. We recommend using the VST2 if you can.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 2 years ago
Posts: 36
Topic starter  

@getdunne

Okay. I noticed another issue. I produce my music in Maschine Standalone and save the project. Then I close maschine and start Logic to work on the Project using the Maschine Plugin inside Logic to put the music to film. But having Unify VST or AU in a Maschine Project causes Logic to completely Freeze when openening the Maschine Project inside the Maschine Plugin inside Logic. I had to force quit Logic.

In other words: Unify Plugin inside Maschine Plugin inside of Logic = not working.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @klasus

@getdunne

Okay. I noticed another issue. I produce my music in Maschine Standalone and save the project. Then I close maschine and start Logic to work on the Project using the Maschine Plugin inside Logic to put the music to film. But having Unify VST or AU in a Maschine Project causes Logic to completely Freeze when openening the Maschine Project inside the Maschine Plugin inside Logic. I had to force quit Logic.

In other words: Unify Plugin inside Maschine Plugin inside of Logic = not working.

Oh dear. It may be some time before I can get to this, because I don't own Maschine and know almost nothing about it, but I will put it on the to-do list and get to it when I can.


ReplyQuote
Share: