Maschine 2 AND Machine 3 Software Running on the same computer?

2»

Answers

  • D-One
    D-One Moderator Posts: 3,527 mod

    That means theres no auto-migration then, at least in Logic.

  • Lionzinio
    Lionzinio Member Posts: 125 Advisor

    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.

  • D-One
    D-One Moderator Posts: 3,527 mod
    edited November 6

    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.

  • Moover
    Moover Member Posts: 6 Member

    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?

  • ozon
    ozon Member Posts: 1,786 Expert

    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.

  • D-One
    D-One Moderator Posts: 3,527 mod
    edited November 17

    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.

Back To Top