Komplete 2 FM7 not compatible with old songs!

OS: Win XP Home
Host: Logic 5.5.1 platinum

I had the FM7 allready before I purchased Komplete 2, so quite some of my songs do contain it... however, when I load these songs, Logic will tell me "FM7 not available". This obviously isn't true because I can just select the FM7 being installed with Komplete 2 fine.
Now I had to temporarily remove it and replace it with the older version.
I've also been putting the new FM7 DLL back into some temporary subfolder to replace settings song by song, but now, all to my amazement, it WON'T load my old Logic presets at all! So there's not even the chance to save presets from the older version, load the new version and then load the patch... gonna do it song by song, using the FM7's own load/save menu.
Fortunately I did at least have the FM7 before - but what If I'd took a song to another machine, being done with the old version while the new machine only had the Komplete version?

Really, can't such things be checked before the user is running into trouble?

 

I have just run into the same situation on the Mac OSX version. Any older song that contains an FM7, shows up as "plug in not available". Not good.

regards,
Jon

 

I for one will keep using the old FM7 version for my own projects.
As the new version is incompatible and as there seems to be some major screw up happening in the operator's envelope menu (see my other thread) there's not much of a chance I'd like to rely on this version.
Too bad I will have to use it for the university where we only have Komplete installed...

 

Did you try to activate the old version, export the self-made presets to load them into the K-Edition lateron?
This is a s*load of work, but perhaps it might function...

 

I can run both versions parallely, so old songs actually load fine.
But, as I need to be compatible with 12 university machines that ONLY run Komplete 2, I will havve to convert all the patches first.

Also, as said before, FM7/K2 is more buggy than the old version - so, what to do?

I really can't believe any of N.I.s betatesters checked for backwards compatibility as it's 100% reproduceable it's NOT compatible!

When I'm betatesting new versions of software (which I do quite sometimes), one of the VERY first things I have in my book is checking for backwards compatibility!

 

AFAIK, this isn't even a *new* version. It's the exact same version number as the old one, just in a bundled package. Regardless, I also do beta testing for a number of companies as well. backwards compatibility is always the *first* thing that is checked. I'd be quite surprised if this plug in went through any beta testing whatsoever. Really there is no excuse for this, and more so, there is no excuse why a fix hasn't been posted yet.

regards,
Jon

 

Well... I agree, it's the same version by numbers, but then, there's some new bug(s) introduced, at least in the PC version.
When you click on the envelopes copy/save/load pulldown it's getting all nasty. The envelope loading pulldown will appear whenever you click anywhere in the interface. You can only get rid of it when wildly widdling around with mouse and clicks (haven't found a scheme yet). Of course this makes working with pre-saved envelopes completely useless.

So, my suspection is it's actually a "new" version even if it wasn't supposed to be one.
The backwards incompatibility would just be another prove for that.

And yes, I also think this should've been fixed allready.
Not everybody is in the same lucky position like me to run both the old and new version parallely.

 

Lol, this reminds me of a discussion in the Waves Forums where people found that the (at that time new) PACE copy protection / authorization could damage system's config and make DAWs unusable - incl. the plugíns it was brought with...
Dunno what´s up with it as I don´t use them, but in the FM7 vs. K2 issue, I think of something similar:
The K2 authorization is bundled for all plugíns incl. FM7.

-> Komplete2-FM7 MUST be different from the separately sold FM7 package.

 

Hi all,

we are aware of this issue (the Komplete 2 FM7 ID differs from the "old" one). An update which fixes this bug will be out soon.

Sorry for the inconvenience!

Best regards,
Sascha Kubiak
______
Product Management, NI

 

I can't believe this latest update, which passes AU Val . . . .is still incompatible with older songs. Honestly, how hard could it be to get this fixed correctly?

 

There's not even an update for the Windows version AT ALL.
Seriously, this should've been a freaking fast maintainance update IMMEDIATELY after it was "detected".

But well then - NI seems to be too busy selling all sorts of pay-updates, which basically should be free (at least partially, do I need to mention Battery?) along with soundbanks.

VERY bad update policy if you ask me!
And it's defenitely not the first time this is happening!

 

We have the problem, that changing back the FM7-ID to the non-komplete FM7-ID would make the songs that are created with Komplete version incompatible. We really discussed alot about the problem and came to the conclusion, that the best solution is to use the Komplete FM7-ID. We are really sorry for the inconvenience!

Best regards,
Steffen
--
Developer, NI

 

Hm, maybe next time you should ask your fellow testers to check for compatibility issues more thoroughly.
At least that's allways the first thing I do!

- Sascha

 

What testers? It's quite obvious this was never tested at all. What's really pathetic is that we reported this so many months ago . . . just days after Komplete 2 was released. That would have been the time to address it. And how long would it have taken way back then to fix this problem? 5 minutes? 10 minutes? Waiting to deal with the issue months after we reported it here, and yet more months after your own Product Manager confirmed the problem and promised a fix "soon" is ridiculous. It's not an inconvenience. It's a deal-breaker, a show stopper . . . and a lost customer. Go ahead and try to sell me any of your new products. I dare ya.

 

Fortunately, for me it's not exactly a showstopper, I can keep both versions installed on my machine, but it still requires some work to transfer stuff to other machines (which is what I'm doing rather often as I'm teaching this stuff in some media lab).

General thing is, as of lately (well, not exactly just lately), I got a pretty bad feeling regarding NIs product maintainance policy.

There's some other VERY serious bug in FM7/Komplete/Windows (it's going all havoc once you click on the envelope presets) which hasn't been adressed either. It's more than 3 months ago that I reported it.

Similar things would be valid for Battery - I mean, HOW many years have it been since a LOT of users requested to adress some issues? OK, those weren't exactly bugs, and while I am certainly aware that whenever I license some software there's some "as is" passage in the contract - yet, I actually DO expect some inbetween updates adressing certain issues which aren't bugs but highly annoying. In case of Battery there's TONS of those.
But now, all wer see is another upgrade we have to PAY for.
Also, instead of adressing long time issues, NI seems to prefer to come up with something new instead all the freaking time.
Yes, I know that this is a tough market, so you gotta be upfront regarding new stuff in order to make a living of it (let alone run a company), still, I doubt that in the long run things work out well this way. Almost any plugin contained in the Komplete 2 line that I've been using more or less intensively could pretty well be updated.
Yeah sure, there have been a few updates, but those were allways only adressing bugs. Not a single annoyance has been adressed, let alone some new features being implemented.

Maybe that's just what we will see more often in the future... companies not giving away anything for free anymore (apart from bug fixes) but charging money for each and every update.
Perhaps it's time to concentrate a bit more on the smaller companies. Their developers tend to listen to their customers.

 

Hi Sascha,

please remember.....

 

It has already been stated that there won't be a fix. This is incredible - absolutely! People at NI need to discuss these things with users of their software, not among the developer team. Unbe-funkin-lievable.

 

Hello,

first of all NI would like to apologize for this compatibility issue. To gain a common understanding, I will provide some background information:
- There are two versions of FM7, one full version and one Komplete 2 version.
- The FM7 version for Komplete 2 needed to be modified due to a change of the copy protection scheme.
- In the course of this modification work, a mistake happened: the ID was changed.
- This bug was not detected while testing.
- Since the ID was changed the full version FM7 projects are not compatible anylonger with the FM7 Komplete 2 version.
- Since there are many Komplete 2 FM7 users, who don't own a FM7 full version, we cannot change the ID of the FM7 Komplete 2 version again -> their FM7 Komplete 2 projects wouldn't be compatible anylonger with the "new" FM7 Komplete 2 version. The confusion would be even bigger
- There is a workaround: Save your FM7 presets with the FM7 full version projects (using the full version of FM7) and load them into the FM7 Komplete 2 version projects (using the Komplete 2 version of FM7).

I hope this works for you. Again, we are sorry for the inconveniences.

All the best,
Sascha Kubiak
_________
Product Management, NI

 

But it was detected immediately by Sascha Franck and myself, and therein lies the problem.

We reported it. A month later you told us NI were aware of the problem and it would be fixed. 2 months after that, NI tells us now it's too late to be fixed. Brilliant! Just put things off until it's too late! Why didn't I think of that?

This is exactly why I won't be buying Absynth 3, Battery 2, NI Komplete Care, or anything else you come up with. I don't trust your beta testers, and I don't trust your support schedule. As I stated way back at the beginning of this thread . . . . there aren't even any modifications to the FM7 itself. We're screwed because of copy protection! You're more concerned with your program getting kracked, than you are with the cusotmers who actually PAID for your software. And that's just plain wrong.

regards,
Jon

 

That means, I must save approx. 100 - 150 FM7-Presets, 'cause I've used the FM7 very often. Not so good...

Regards