I was using MRhythmizer to create a half-time effect on my song, specifically the "4 halfs" preset from FREAKQUICNY.COM - GROSS BEATZ VOL. 2. It sounded fine, but when I opened my Logic Pro X project on a different computer to mix it in the studio, the effect now sounds different and slightly off. I did not change any of the midi or any parameters in MRhythmizer so I have no idea why this would happen. The project was saved in the cloud so it now also sounds different on my original computer. I've tried opening a different instance of MR and recreating the effect, and reinstalling MR completely, but it still sounds different. I've attached a screenshot of my MR settings below. It's difficult to explain without being able to attach the two audio files but basically in the original effect the 8th notes sounded "halved" and played an octave lower and the length of a quarter note, and it now sounds similar to if I had just pitched the midi down an octave instead of stretching the audio, the 8th notes do not play for a longer period of time. It also sounds slightly off-beat as my automation moves from 100% wet to dry.
My specs:
iMac 27-inch 2020 OS Ventura 13.0.1 (original)
The studio computer was a Mac mini but I would have to check to model and OS
DAW: Logic Pro X Version 10.7.5
MRhythmizer output sounds different after opening project on a different computer
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'm afraid without actual audio and the project ideally, it's impossible to say anything. Try changing the audio settings to make them identical. Maybe something in the chain depends on that.
-
- KVRist
- 82 posts since 4 Mar, 2009
Ok, I've been meaning to post about what might be the same/similar issue.
I noticed it on a project where I had programmed MRhythmizer on a drum track for fill-ins and variations using a separate midi track with notes to change the pattern. On a later version of the project I found that the rhythms were very slightly out of sync and so the fill-in effects on the drum track were subtly altered and not sounding as good as on earlier versions of the project.
I took the project to pieces, tried copying the plugin and notes from an earlier version but was finding it was still out of sync. Yet, when I deleted all the other tracks (ie. all tracks except the drums and the midi notes controlling MRhythmizer) it played as it should compared with the earlier version.
After hours of investigation I was pulling my hair out. But I eventually worked it out: it turns out that having a side chain in any of the tracks involved causes a delay (or latency?) to the effect of MRhythmizer by a very subtle amount.
If you have any side chains on those tracks, that might be the cause.
I'm 99% sure I'll be able to make a re-produceable demonstration of the bug/issue. Will post it here and send to Melda support when I get a sec.
I'm on a Mac using Ableton 10
I noticed it on a project where I had programmed MRhythmizer on a drum track for fill-ins and variations using a separate midi track with notes to change the pattern. On a later version of the project I found that the rhythms were very slightly out of sync and so the fill-in effects on the drum track were subtly altered and not sounding as good as on earlier versions of the project.
I took the project to pieces, tried copying the plugin and notes from an earlier version but was finding it was still out of sync. Yet, when I deleted all the other tracks (ie. all tracks except the drums and the midi notes controlling MRhythmizer) it played as it should compared with the earlier version.
After hours of investigation I was pulling my hair out. But I eventually worked it out: it turns out that having a side chain in any of the tracks involved causes a delay (or latency?) to the effect of MRhythmizer by a very subtle amount.
If you have any side chains on those tracks, that might be the cause.
I'm 99% sure I'll be able to make a re-produceable demonstration of the bug/issue. Will post it here and send to Melda support when I get a sec.
I'm on a Mac using Ableton 10