Library split after 1.5 update

After I installed the 1.5 update I have my library split up and I can't figure out how to merge sections.

For example, I now have "NI Projects" and "NI Projects 1.5", "Kits" and "Kits 1.5", "Instruments" and "Instruments 1.5".

I just installed 1.6 and thankfully it didn't add a third section!

If the brute force option is best, I don't mind completely uninstalling/erasing Maschine and redoing it from scratch. I don't really have much saved that I would care about losing. Is the 1.6 a full installer, and is there anything special I have to do to uninstall Maschine in OS X other and delete the plist and application data folder?

 

It splits by design, I believe. So you can see which is the additional 1.5 content. However, it annoyed me too, so I just removed the 1.5 tags as all of the samples and things that are tagged with a 1.5 tag are also tagged with the regular one. Make sense?

1.6 won't have added a third section anyway, because there was no additional library content. Yet. There might be upon official release (don't hold me to it though, just speculation).

As for uninstalling etc. There's no need and the 1.6 installer isn't a full installer, I don't think. You need to have 1.5 installed to install 1.6. I think...

 

Awesome, thanks! I was worried that I had some kind of file corruption but if it's by design then I can totally live with it and I'll try the tagging you mentioned.

 

I'd guess for some the knowledge of which samples came with which update in the software might be useful. And I suppose NI can't count on everyone keeping all the factory tags anyway, so had to tag the 1.5 samples as well just in case. I don't know, just speculating for the reasons.

But for me, I didn't like it. I just wanted them all tagged as what they were. Which installer they came from isn't important to me.

I hope no-one chimes in and tells us that they were tagged that way for a critical reason and everything will breakdown in 3.76 days now we've de-tagged them! :S

 

Yeah, the additional tags were presumably just so existing users could find and audition the new content easily.