pouya Posted December 29, 2020 Share Posted December 29, 2020 Hi, It seems that Logic Pro cannot save the settings for Vintage Mellotron properly. I add Mellotron to an instrument track and adjust its settings. Then I save the project and quit Logic Pro. Once I reopen the project, the Vintage Mellotron settings are visually there but when I try to play, it plays pure sine wave. Does anybody else experienced the same issue? Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted December 30, 2020 Share Posted December 30, 2020 I think that is a bug as it happen here as well. Saving the edited preset doesn't help. Even loading a new Mellotron instance onto a different track with the newly saved custom preset, while the other track's mellotron edited preset is still working fine, does what you describe... Quote Link to comment Share on other sites More sharing options...
pouya Posted December 30, 2020 Author Share Posted December 30, 2020 Thanks for your reply. As you mentioned there is no workaround. I had to take a screenshot of the Mellotron window. Every time I reopen the project, I have to go to the Mellotron track, reload the preset and adjust the settings to match the screenshot. Fortunately there are only few knobs to adjust, otherwise it would have been a tremendous waste of time. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted December 31, 2020 Share Posted December 31, 2020 I guess that the workaround would probably be to bounce-in-place the track or create a sampler instrument from it using Auto Sampler. Quote Link to comment Share on other sites More sharing options...
favdave Posted February 4, 2021 Share Posted February 4, 2021 Oh man! I just ran into this bug! Very annoying, but thankfully the settings are few. I cannot use autosampler because I automated the Blend function throughout. It sounds so cool it's worth the hassle. Funny how it makes me feel better knowing that it's not my fault. IT'S NOT MY FAULT! Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 5, 2021 Share Posted February 5, 2021 No, it's not your fault! Quote Link to comment Share on other sites More sharing options...
favdave Posted February 5, 2021 Share Posted February 5, 2021 Quote Link to comment Share on other sites More sharing options...
ValliSoftware Posted February 5, 2021 Share Posted February 5, 2021 Works here. I made changes to the Mellotron, saved the project, then opened the project and my settings were saved and played correctly. I also saved it as my own preset, started a new project, loaded the same instrument, then recalled my saved preset and everything played just fine. This was on my MacMini M1, see sig for details. Quote Link to comment Share on other sites More sharing options...
nev17 Posted February 5, 2021 Share Posted February 5, 2021 Same bug here. Quote Link to comment Share on other sites More sharing options...
ValliSoftware Posted February 5, 2021 Share Posted February 5, 2021 So far the difference I see is I'm on 11.2 and on a M1. For Intel, maybe go to 11.2 Quote Link to comment Share on other sites More sharing options...
favdave Posted February 5, 2021 Share Posted February 5, 2021 (edited) So far the difference I see is I'm on 11.2 and on a M1.For Intel, maybe go to 11.2 Ahhhhh no! I am always at least one OS version behind because of stability. They break more than they fix. I can work around the mellotron patch, but not other breakages I never upgrade till an OS version has been out for a year... Edited February 7, 2021 by favdave Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted February 7, 2021 Share Posted February 7, 2021 Wise decision! Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted March 5, 2021 Share Posted March 5, 2021 I can confirm this bug here. Quote Link to comment Share on other sites More sharing options...
10pa Posted April 9, 2021 Share Posted April 9, 2021 Hi! As crazy as it is, but this helped: https://discussions.apple.com/thread/252488958 Cheers! Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted April 9, 2021 Share Posted April 9, 2021 Hi!As crazy as it is, but this helped: https://discussions.apple.com/thread/252488958 Cheers! Wow, great, thanks for posting the workaround! I suppose you could probably make an alias and rename it, and waste less than 1kB. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 9, 2021 Share Posted April 9, 2021 Hey, thanx 10PA and David for your input! I'll give that a try... Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 14, 2021 Share Posted April 14, 2021 Well, that suggested workaround: "...If you go to Macintosh HD//Library/Application Support/Logic/Sampler Instruments/Mellotron and duplicate the Mellotron.exs file, then label the duplicates 3 Violins.exs, 8 Choir & Flute.exs you won't have this problem anymore..." ...did not work here. (Neither duplicating the exs file or the alias method) Quote Link to comment Share on other sites More sharing options...
10pa Posted April 14, 2021 Share Posted April 14, 2021 Simply develop the idea of that tip. And it'll work. I duplicated the exs file and named it exactly as the Mellotron preset I use. Or you can duplicate it multiple times and rename so it mirrors the preset names (of course with .exs after that name). I'm sure, that'll work. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 15, 2021 Share Posted April 15, 2021 (edited) Hmmm, that's odd! The plugin presets that I had created and that weren't working yesterday are now working as expected. But the custom plugin presets I create today aren't. I have duplicated to either exs or exs alias files for every factory preset and for the optional selectable component from within the GUI's 2 menu as well. I also duplicated same named after the newly created custom plugin presets but to no avail for those created today... Closing and starting a new project and/or quitting and relaunching Logic isn't helping, the new custom Mellotron plugin presets created today aren't working, they keep sounding as blank sine wave... Edited April 15, 2021 by Atlas007 Quote Link to comment Share on other sites More sharing options...
10pa Posted April 15, 2021 Share Posted April 15, 2021 Yeah, I checked with factory presets only. That's enough for me. Did you report a bug to Apple? Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 15, 2021 Share Posted April 15, 2021 Ok... I am puzzled! Now if I saved as a patche it works... Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 15, 2021 Share Posted April 15, 2021 Yeah, I checked with factory presets only. That's enough for me.Did you report a bug to Apple? Yes I did! Quote Link to comment Share on other sites More sharing options...
Andy Trox Posted November 26, 2022 Share Posted November 26, 2022 Guys, just save instrument here: "Your HD"/Library/Application Support/Logic/Plug-In Settings/Vintage Mellotron Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.