Yes you're right... this circumstance is not the best, but as far as i can say... as long engine will be updated, inde will be too, because the development is still the same, and it's not much effort if the code is available to make provide it for both. I'll get more information about the release of the latest inde soon (i've send an e-mail) and i'll let you know as soon i have this information.EvilDragon wrote:NoSoniX wrote:That's not completely correct.
Independence is a Magix (formerly Yellow Tools) product. We have licensed Engine as player for us, Best Service.
Independence is not our main product and won't be. You can load up engine libraries in Independence but that's all, because they use the same code. Magix does the support for Independence, we only for engine.
In cause that engine is the "main" product for our libraries it's important to release the updates as soon they are available... that's mostly before magix will post their updates.
If you have questions about Independence, contact the customer support of magix. They will let you know when they will release the newest version.
We at bestservice don't have influence what happens with Independence.
Please let me know if you have further questions.
Thanks for the reply. Indeed I feared this might be the case. Magix's support isn't stellar unfortunately, and they are obviously quite behind in development of Indy vs what Engine is now... Not your fault, of course, it's their fault. But I fear this disjoint between Indy and Engine might only grow further apart as time progresses, and Magix might not be willing to cope with it, and it's a problem, because ideally the main sampler and the player should be done by one and the same company, to provide simultaneous updates to both the main and the player... You know, like it happens with competition (NI and MOTU)...
