MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Well M5 v1 doesn't support keyswitching for one, although it is promised in v2 .... maybe that was part of the issue.
I also remember finding my own limitations with M5's sample looping features compared to my old hardware Akai sampler. In the end I had to abandon my plan to transfer my Akai library to M5 because of it. TBH I've not even tried doing the same in K2 though... it could just be that the Akai was older and had features which just aren't fashionable now...
Maybe the VSL team just got fed up with M5's miniscule 'squinty eye' graphics ....
Frodo wrote:Evidently, however M5 is structured to work, it has totally mystified the VSL team and they abandonned their efforts with M5 completely. It raises the question-- how "universal" a sampler is M5? I also wonder if other developers have encountered the same problems.
Well, VSL shuffled all their efforts into their Orchestra Cubes, right? That took care of that. No more dependence on third-party samplers.
Smart.
Aside from that, yeah M5 1 lacks the key-switching abilities K2 supports. And it seems some folks had some trouble translating file formats with it, but it always worked great for me.
Frodo wrote:Evidently, however M5 is structured to work, it has totally mystified the VSL team and they abandonned their efforts with M5 completely. It raises the question-- how "universal" a sampler is M5? I also wonder if other developers have encountered the same problems.
Well, VSL shuffled all their efforts into their Orchestra Cubes, right? That took care of that. No more dependence on third-party samplers.
Smart.
Aside from that, yeah M5 1 lacks the key-switching abilities K2 supports. And it seems some folks had some trouble translating file formats with it, but it always worked great for me.
The Cube is a whole different ball of wax as a new-fangled rompler. They are still supporting EXS24, Halion, Kontakt, etc., with their Opus/Horizon series. It's just a shame that MachFive had to be eliminated from among the earlier formats supported for whatever reason.
Frodo wrote:It's just a shame that MachFive had to be eliminated from among the earlier formats supported for whatever reason.
I think the reason it was never favored by sound developers is that there is no way to copy protect the samples. Most of those romplers have this type of protection built-in...
Frodo wrote:It's just a shame that MachFive had to be eliminated from among the earlier formats supported for whatever reason.
I think the reason it was never favored by sound developers is that there is no way to copy protect the samples. Most of those romplers have this type of protection built-in...
I've often wondered what the $11k price tag covers. With the need for a serial number and Syncrosoft key to run the library, one would think it wouldn't be much of a problem as far as copy protection.
But according to VSL, it had nothing to do with copy protection and more with how M5 works that frustrated them to the point of surrender. Not sure of all the details-- but as mentioned, they still support K2, GIGA, Halion, and EXS24 with their Horizon/Opus 1 series. The Cube is self contained, so it just leaves me wondering.
Since the UVI engine isn't made by MOTU, they could have ran into a snag. It's curious that the Spectrasonics stuff (Atmosphere, Trilogy, Stylus) is made by the same people, but yet they haven't released UB versions yet either...
Since the UVI engine isn't made by MOTU, they could have ran into a snag. It's curious that the Spectrasonics stuff (Atmosphere, Trilogy, Stylus) is made by the same people, but yet they haven't released UB versions yet either...
C
Am I mixed up about something in this thread?
I have been running a UB beta for Stylus since February. Granted it's a beta and not a final version, but where there's a will, there's a way.
Since the UVI engine isn't made by MOTU, they could have ran into a snag. It's curious that the Spectrasonics stuff (Atmosphere, Trilogy, Stylus) is made by the same people, but yet they haven't released UB versions yet either...
C
Am I mixed up about something in this thread?
I have been running a UB beta for Stylus since February. Granted it's a beta and not a final version, but where there's a will, there's a way.
Hey mon:
It's a yes and no answer with this one. This is from Spectrasonics:
Atmosphere/Trilogy/UVI engine
As many people know, our popular Atmosphere and Trilogy instruments use a special version of the UVI engine, which Spectrasonics originally licensed from Univers Sons - not our own in-house developed S.A.G.E. (Spectrasonics Advanced Groove Engine) technology that Stylus RMX uses.
The Intel Mac transition is a major one for all music software companies to make, but it's much easier to make this transition with in-house developed technology. This is one of the main reasons why we have been able to make the transition to Universal Binary for Stylus RMX so quickly.
Therefore, it's going to take much more time for our Atmosphere and Trilogy customers to be able to make the transition to the Intel Mac world than it has for Stylus RMX users.
Although we cannot announce the specifics or a timetable yet about our plans for Atmosphere and Trilogy, we can say that we are fully committed to their future development and long-term growth - and these future plans will of course include native support for Universal Binaries on Intel Macs.
RCory wrote: It's curious that the Spectrasonics stuff (Atmosphere, Trilogy, Stylus) is made by the same people, but yet they haven't released UB versions yet either...
mon wrote:
Am I mixed up about something in this thread?
I have been running a UB beta for Stylus since February. Granted it's a beta and not a final version, but where there's a will, there's a way.
You've been using Stylus RMX not the original Stylus - which I suppose has been discontinued now...
OR... M5.2 has been so well optimized that it has downloaded, installed and been running all this time and none of us knew it. The only known bug is that the screen only stays active a nano second, so unless you're Superman, it remains a useless addition to our arsenal.
We should write a joint letter to MOTU requesting that they slow down the application. Anyone got papers?
