Maschine 2 AND Machine 3 Software Running on the same computer?
Answers
-
That means theres no auto-migration then, at least in Logic.
0 -
Or it's been intelligently done. As in, if Maschine 2 exists on the system do not update. Which would be a graceful way of going about it.
1 -
My impression was that if the DAW supports auto-migration then it will auto migrate, this was talked about in the beta but I dont remmber 100%. Not many DAW's support migration, Cubase does for example which is expected since Steinberg made VST.
If it's smart or not depends on the customer, eventually M2 wont work… when it doesn't I'd like my projects to auto migrate and not spent the insane amount of time I spent manually converting all my projects that had KKV2 > KKV3, VST2 > VST3, Kontakt, etc… It took me 2 weeks… But this was Ableton's fault for not support auto-migration.
While for other users not migrating is better… for the time being.
0 -
Now that I have the maschine 3 update, is there any reason that I need to keep maschine 2. Will 3 open 2 projects automatically? Will there be any unforeseen problems? will 3 access the 2 factory library automatically?
0 -
No. Yes. Yes. Yes.
Check the Maschine 3.0 Library preferences. You will find that Maschine 2 Library and the Maschine 2 user content folder were automatically added.
0 -
If you have DAW projects using Maschine 2 Plugin then you will need it, it doesn't auto replace it for Mv3, afaik. Also, Maschine 2 has it's own user folder with exports (including drag-and-drop), sample edits, etc… I'd be very, very, VERY carefull going about deleting that.
I wouldn't delete it, especially not this early, Maschine 2 is just 250 MB so it's not like it takes any significant disk space… Theres issues, bugs, and I am sure we will find more the more we use it.
I would also highly advise anyone when opining v2 projects in v3 to save to a new project file, if something breaks and users overwrite the projects then theres no going back since V3 is not backwards-compatible.
2 -
I recently updated to Machine 3 while keeping 2 on my computer running the latest Windows 10 update. I have been experiencing issues. My controller most of the time will not connect to Vs 3. It shows the standby display. I will exit out and load Vs 2 and it works great. Go back to 3 and sometimes it will connect but eventually go completely dark as if turned off. I have gone through the forums and tried different solutions but nothing helps. I am even running the software as administrator. Running as administrator sort of helped, allowing it to connect briefly as described earlier. I just wanted to let you guys know my experience so that folks can see there is definitely a potential for issues on windows 10.
Edit: I forgot to mention the various ways I have tried using Machine. First, I could not get the plugin for either version of Machine software to load in Ableton. M2 standalone works every time but not M3.
M3 will start but the controller will go total dark and not operate within about 2 minutes.
I have uninstalled the new Machine 3 software and reinstalled twice and both times could work on a project for a while with no issues. But if I close the software /shut down the computer. Problems come back.
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 66 NI News
- 871 Tech Talks
- 4.4K Native Access
- 17.2K Komplete
- 2.2K Komplete General
- 4.7K Komplete Kontrol
- 6.1K Kontakt
- 1.1K Reaktor
- 401 Battery 4
- 900 Guitar Rig & FX
- 458 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 8K Traktor
- 8K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators