MOTUnation.com

Something interesting, if the sample is in WAV format, i got the exact same problem as you have, ie. markers are resetted to initial values, no matter if i choose "Save" or "Save as...". Very boring...

Bye.

OK, we are ready for the 2.02 update. Drum roll........ .... ... .. . . . . .

looking good, Yukulele

Oh MOTU....
I almost spent another $199 with you.
I bought M5 right before the cutoff for free upgrade.
I'm glad I didn't buy in to this new version.

It really disappoints me to see these bugs. I wish so much for MOTU and for us all that MOTU would re-establish their long time reputation for things that "just work." I got very excited about MachFive2. It looked like an answer to things I'd hoped for. Now, with the problems inherent in the programming, I see that it's not. And that disappoints me beyond what I can or would put into words here. It makes me sad.

Maybe they'll fix it. I hope for that, and forgive me if I sound too dramatic for the situation at hand when I say that there's a lot more riding on this than a piece of software or getting the job done. MOTU, you've got the support and backing of everyone who buys your software. Don't think it's infinite. Don't take it for granted. We're tiring faster each day.

Shooshie

Shooshie wrote:... there's a lot more riding on this than a piece of software or getting the job done. MOTU, you've got the support and backing of everyone who buys your software. Don't think it's infinite. Don't take it for granted. We're tiring faster each day.
Shooshie

I hope they heard you, Shoosh.
I for one appreciate the rarity and significance of this statement from the 'Meister.

Shooshie wrote:We're tiring faster each day.

What's rather vexing to me is that, in my dealings with support, the responses I've gotten (very slowly at that) have sort of had the tone of "well, you're using it wrong" ('turn the loop on, then your starts will save'... but what if I don't want the sample to loop?) and not even had the decency to say, as they have to others here, "it's a bug, we're working on it."

Meanwhile, I have a program that's--for my purposes--a $200 paperweight; after waiting as long as it's been since version 2 was announced, my patience is really down to a sliver.

And really, what a whopper of a bug!

Peece,
T. Tauri

Hear, hear.

As some of us noted here a few weeks ago, this bug pretty much kills the usefulness of the product. It doesn't get much worse than that... A real shame.

I can confirm that this is also true on the Windows platform.

However, a workaround was to create a loop first, then delete the loop and save the sample (I did save the file before deleting the loop, but that may not be necessary). The new start/end points are then saved.

monkey man wrote:

Shooshie wrote:... there's a lot more riding on this than a piece of software or getting the job done. MOTU, you've got the support and backing of everyone who buys your software. Don't think it's infinite. Don't take it for granted. We're tiring faster each day.
Shooshie

I hope they heard you, Shoosh.
I for one appreciate the rarity and significance of this statement from the 'Meister.

I believe the word I was looking for was "poignance".

Just wondering if anyone else is having the problem i explained on the previous page of this thread:

I tried this procedure, and here, the result is much worst than a simple start/end markers loose : if i save with the same sample/name (which replace the original), the sample is just screwed up (3369bites). That was simple AIFF files...

But if i "Save as" with another name, everything is correct, even the start/end markers, etc.

The same test under Windows would be interesting too, IMHO.

Bye.

Yukulele wrote:Just wondering if anyone else is having the problem i explained on the previous page of this thread:

Just giving a try with 2.0 at the moment (w/ my G5 tower). Hasn't written anything problematic in the sample itself (plays fine in the finder, Peak), but I'm also managing to regularly crash DP and Logic 7 & 8 while trying to test.

If I turn on a loop and set the release to "not looped", then save (I've only tried saving directly to the same file so far this round); when I reload the patch, and play a note, I get some glitchy sounds, and then when I let it go, as soon as it reaches the endpoint, it crashes. If I manually change the start/end/loop points before I play a note, then it works OK.

Also, when I've accidentally (single)clicked on the AIFF sample I'm using to test with (residing in the same folder as the patch I'm saving), that crashes M5 & host.

I'll see how 2.01's doing when I'm next on my laptop with that installed.

Peece,
T. Tauri

Nobody else did the test with AIFF samples (make backups before testing!!!)?

Also, i'm a bit frustrated, the MOTU tech link i posted on the 14th of september is still "Unread"... This is not what i call support...

Bye.

As noted on the first page of this thread, I am experiencing this problem with .aif and .wav samples. However, for no apparent reason, occasionally an .aif file WILL save its loop and start/end settings.

In any case, this is all getting very tiresome. The bottom line is THIS PROGRAM IS BROKEN. It's not a hard-to duplicate obscure problem. It's a huge, glaring issue. They've known about it for weeks, and at this point it's up to them to diagnose and fix it.

I just tried again on 2.01, Yukulele, and couldn't corrupt the sample file.

Meanwhile can anyone else duplicate my crashes with loop release set to "unlooped"?

- Create a patch with a sample with the loop turned on & release to "unlooped"
- save patch, empty and reload patch
- play a note
- crash shortly after release of note?

(I've so far only tried this one with AIFF)

Peece,
T. Tauri