![]() ![]() ![]() ![]() It is connected to same port as usual and I haven’t touched anything. Not sure whether related to this issue or not, but one day was all good and the next it is not longer recognised in Ableton nor in Midi control center, even though the device seems to be working fine (lights and everything). On top of that, my ML mk2 has stopped working. If I try to register it I got, as expected, a message saying this product has already been registered, as you can see in the last screenshot. After installing both ALs, AL IV appears as not activated and says I don’t have a license. ![]() Within ML mk2 I’v got two AL versions to install, the second one, as you can see in the second screenshot is AL Lite, which is the AL IV. I’ve tried uninstalling and installing everything again and the situation remains the same.Īs you can see in the screenshots, I’ve got two MiniLabs activated. You’ll have to try again it look like, if you need Arturia technical support. It’s very strange, if you have done this, and you have’nt got a auto generated reply. Please tell the solution if you find/ get one.īTW: When you said “my portal” when sending email to Arturia, then did you mean you where logged into your Arturia account and contacted Arturia through a support formular? Based on the given informations, this issue make no sense then. If you have tried all my suggestions in this thread and it still does’nt work, then i don’t know what else to do. I have no idea how the install of MiniLab 3 in it self should have anything to do with this issue, if you still own and have all the rights including to AL4 from your MK2 ownership intakt. Just in case that could make a difference. You can also try to deactivate and reactivate AL4 on your Arturia accounts My Products page. You can allways try to uninstall AL4 and ASC manually like you can read here:, and then perhaps restart the computer before installing again. Have you at any point had your MiniLab MK2 deregistred? So it look like a pure ownership confirmation/ activation issue of some kind. How can that be?Īs your MiniLab 3 package seem to work, then it does’nt look like a network issue.Īpparantly you can run the applications on your computer. So the main issue is, that you say that while you still own AL4 and say that ASC show it’s activated, then it run in demo mode anyway. I assume it’s the same for other legacy presets from AL4 that’s not in ALV by default. You say you have the preset you mention, but it does’nt look like, you have the permission to include and use it in ALV. But i can’t see the software in the packages is activated. I can see your Minilab product packages are registrated, so your hardware is registrated. I also can’t see anything about AL4 running in demo mode. In the screenshot you posted in your previous post i can’t even see it’s Analog Lab in the background, as it does’nt look like it is. If you should have posted another screenshot, then i can’t see it. Normally support reply within 24 hours, unless they have much to do. Something is wrong, if you have no response from Arturia at all. Have’nt you got a auto confirmation mail from Arturia, that they have recieved your mail, and with a note about when you can exspect reply? If not, then please check your spam folder first. Let ALV be open for some time, while the database rebuild.ĭid you try to deactivate and activate AL4 again? Not sure how to understand you on this. Be sure you don’t have it in the main preset folder and then open ALV in standalone mode to build a new database file. In that case, then - to be secure - move your current db.db3 file located in your main preset folder at the resource folder path to another location. Have you checked if it’s located in the preset folder? If it’s there, then perhaps your preset database might be corrupt. There does not seem to be any way to resolve this except to continue using logic in rosetta, which is a bit ridiculous at this point in time.If the preset Ambient is the ARP 2600 V3 preset, then i have it in ALV. I have tried a full audio unit reset "disable failed units" does nothing since no units are failed and all are "successfully validated". There is apparently no way to identify which plugin(s) is the problem, so no help from Logic Pro there. Clicking "recover" triggers an "overview creation" calculation, which when finished goes right back to the same alert (quitting and restarting also does nothing). AU crash alert in Logic Pro X native mode, yet all 3rd Party plugins validated/compatible Running Logic Pro 10.7.8 Ventura 13.4 on Mac Studio M1 Ultra in native mode (bc I want the processing power I paid for over a year ago)ĭespite the fact that all 3rd party plugins are up to date and Apple silicon compatible, and are all "successfully validated" in the plugin manager (which I cannot open unless in rosetta, or in an empty project in native mode, due to the inability to resolve this alert). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |