-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magenta Studio Takes an eternity to load in Ableton Live 10 Suite #28
Comments
Sorry you're experiencing this. It may be that your computer does not have sufficient memory. What OS are you using and how much memory does it have? |
Hi Adam,
I have got 8 Gig of Ram and I am running it on an iMac. Sierra.
I make sure I clear all my RAM as well before loading Live. Mac Keeper can do this pretty well.
Cheers
Jeff Evans
… On 10 Jul 2019, at 2:36 pm, Adam Roberts ***@***.***> wrote:
Sorry you're experiencing this. It may be that your computer does not have sufficient memory. What OS are you using and how much memory does it have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#28>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMSIJ5NFEOU3VGDGHDNCIH3P6VRLBANCNFSM4H7KN5SA>.
|
Hi Adam,
I am running a quad core 2.5 Ghz iMac. Not a new model though. It is still on Sierra. It’s running Ableton and Studio One V4 very well. It has 8 Gig of Ram as previously mentioned. I would love to be able to get this to load quicker for sure but maybe in my case I just have to wait it out etc.. I have not tried the stand alone though as yet.
Does the built in Max for Live need to know where this file lives?
I have installed it from various locations and the load time seems to be the same. I use Ableton Live 10 Suite in a live situation. I wont be using Magenta though in a live setting all that often I would imagine. More a studio experimental thing for me anyway.The modules are fantastic though in what they do.
Cheers
Jeff Evans
|
@Jemusic Is this when you first drop the plugin on a track or when you open up a saved session? When the plugin is added to your session for the first time, the entire package is copied over to your user library which takes a little while because there are so many large files. i've noticed this, especially if you've got a spinning drive instead of a SSD, i can imagine this would take a while because of all the little files that it needs to copy over. |
Hi there,
Thanks for getting back.
Firstly i did have my user drive on an external drive and I was loading it from there but I have since moved that back to the internal drive and put the plugin there as well. Still takes a long time to load. I have let Ableton know where the user drive is.
Question. Do the Max for live settings for the program or the plugin have anything to do with this? (In Ableton I mean)
I am loading it onto a midi track, not opening up a session. Everytime I load the plugin, it takes the same long time e.g. 90 seconds or more. Even after loading it and clicking on the top right hand corner to save it again (.adv file) it still takes a long time to load. Its like it is loading for the first time every time.
It crashed Live at one point too. Froze the program so it was unusable. Had to reboot etc.. Maybe it needs checking at your end too perhaps not sure. If it can be improved in terms of loading that would be great for me.
Thanks for straying in touch. I am open to any suggestions of course.
Cheers
Jeff Evans
|
Hi gents I'm experiencing very long loading time aswell on a Windows 10 - i7-8750H - 16Go of RAM and SSD I'll try to flush my RAM as Jeff mentioned to see if i get any difference but i thought it might be interesting for you to know it is not an isolated occurence. I'll get back to you if i find any workaround. Benjamin |
Magenta Studio takes an eternity to load into Ableton Live 10 Suite for me. Well over a minute. Is this normal? Even after loading the modules take a while to load as well. So much so I don't feel like even using it. Is there something wrong here?
The text was updated successfully, but these errors were encountered: