Re: What version of M5 are you guys using in OSX
Posted: Tue Nov 30, 2004 12:16 am
Dan,
What kind of system are you running? Engine? Software Version? Version of Machfive? Plugs?
I guarantee you: REGARDLESS of the system you are using, there are things that cause M5 to geek, and app fail. How much sample level editting are you doing??? Have you done much UVIX importation with version 1.2? How's that going? Short of trashing prefs on a regular basis, it's been a pain in my ass.
To be thorough, I've managed to achieve some pretty viable workarounds and am having more success editting, but the overall disposition I have at this point with MOTU is one of dismay. I don't want to have to incorporate time consuming, needless tasks to the way I edit. If I were to just go full speed editing in M5, it'd take a dump within the first few edits. I am gunshy to pushing M5 in any significant way. It's a shame such a great soft sampler is mired, at least for a majority of us...who are pushing it beyond changing fine tuning are release times. :-)p
As to some of the REX issues I've had, I've sussed out the major problem as being due largely to something as insignificant as 1 corrupt sample tanking DP upon playback. If anyone's having quits on a M5 sound/patch playback, that's probably the culprit. That really doesn't matter at this point though, as I'm using RMX for REX duties. It destroys M5 on that level.
And honestly, Dan, when you're in DP 4.5, and you save the file as "XXX" WHY on earth should it be saved as a 4.12 document??? Fine if you call that a system related issue, but DP versions previous never had this problem. Now, all of a sudden, its a Mac bug, and MOTU's wearing the halo?
Uhm...okay.
What kind of system are you running? Engine? Software Version? Version of Machfive? Plugs?
I guarantee you: REGARDLESS of the system you are using, there are things that cause M5 to geek, and app fail. How much sample level editting are you doing??? Have you done much UVIX importation with version 1.2? How's that going? Short of trashing prefs on a regular basis, it's been a pain in my ass.
To be thorough, I've managed to achieve some pretty viable workarounds and am having more success editting, but the overall disposition I have at this point with MOTU is one of dismay. I don't want to have to incorporate time consuming, needless tasks to the way I edit. If I were to just go full speed editing in M5, it'd take a dump within the first few edits. I am gunshy to pushing M5 in any significant way. It's a shame such a great soft sampler is mired, at least for a majority of us...who are pushing it beyond changing fine tuning are release times. :-)p
As to some of the REX issues I've had, I've sussed out the major problem as being due largely to something as insignificant as 1 corrupt sample tanking DP upon playback. If anyone's having quits on a M5 sound/patch playback, that's probably the culprit. That really doesn't matter at this point though, as I'm using RMX for REX duties. It destroys M5 on that level.
And honestly, Dan, when you're in DP 4.5, and you save the file as "XXX" WHY on earth should it be saved as a 4.12 document??? Fine if you call that a system related issue, but DP versions previous never had this problem. Now, all of a sudden, its a Mac bug, and MOTU's wearing the halo?
Uhm...okay.