MOTUnation.com

Has anyone here tried repeating the step-by-step in my first post and not had a problem?

Peece,
T. Tauri

This is a problem that I have discovered as well. The batch processing is great for loop direction (I'm trying to make things one shot) but it does not save. You can change it and play it properly until you save it then it reverts to no loop information.

Essentially, as far as I can tell this makes it impossible to use Mach 5 II 2.01 as a sampler because your loop information is not saved.

Most upsetting. Most upsetting.

I have actually found Mach 5 II to be very buggy and not reliable. Don't get me wrong. I like the interface and the potential power but I have had way more crashes than I did on version I. Now, mind you... version 1 was upgraded as it went along and we are only on version .01 but this is really bad.

Christopher Conley

I too am finding M5 II generally much more crash-prone than M5 I.

Once they work out the kinks, I have to say the program has some really inspiring new features. But I hope they're scrambling around the clock to fix this whoppper of a bug. A sampler that won't save loops? Yikes.

As ttauri asked - anybody NOT experiencing this bug in MachFive II v2.01?

I thought it was just me who was having this problem. I did a search and came across this thread. Whew, I was getting nervous there thinking it was just me who had this problem. Anyway, MOTU, you need to fix this real fast. I might have to go back to hardware samplers.

I just did a MOTU Techlinks. Hope this helps us.

I also posted a Techlink about this. Everyone who has Mach 5 2.01 should do a tech support link so they know that it is present on everyones system - not just a couple.

CC

I posted a techlink about this on the morning of August 30th. Today is Sept 4th (the end of the day), and my submitted techlink is still unread by them. Hope they had a nice relaxing weekend...

charlzj wrote:I posted a techlink about this on the morning of August 30th. Today is Sept 4th (the end of the day), and my submitted techlink is still unread by them. Hope they had a nice relaxing weekend...

Don't worry, they'll get to you.

I've put in several techlinks and it takes about 3 days for them to get back (Windows platform anyway).

right you were Sarcazm - Just got this reply from them:

"This is a problem we are aware of and are working on. Thank you for your patience with this matter. I will post here when an update for Mach Five 2 is available."

So they're on it...

Wow I must have missed this before.

Yes this is happening to me too, with loading M5 version 1 presets I had made. The X-fade is there when I load it, but like was said before, no combination of saving preset, sample, whatever, will save the X-fades with the preset.

All I can do is use the (old) M5 preset where they work, or have to do the X-fades all over again. I can't edit, them because I would loose X-fades when I saved my work.

I got the same MOTU tech support reply - great.

CC

Motu better solve this issue quick. I'm thinking bout switching to Kontakt or Sampletank. Maybe even going back to hardware.

I imagine that MOTU will solve this quick but I might end up eating my words... or post...

tick, tock...

ttauri wrote:- Create new preset in M5v2 (standalone or plugin instance) and load a sample
- adjust start or end point
- save program and sample
- unload from M5
- reload (and then in my case: start/ends revert to prior locations)

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.

Happily i had backup of the original samples, but this is a nasty bug indeed!

I'm sending a bug report to MOTU tight now...

Bye.