M5v2 - Sample start/ends not saving - anyone else? RESOLVED
Moderator: James Steele
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
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
Mac Pro 5 (Early 2009) - 6 - Core, 32 gig RAM, Radeon RX 580. Mojave 10.14.6. DP 10.1
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?
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?
Mac dual 2.7G G5
OSX 10.4.9
4.5G ram
Pro Tools HD3 Accel
PT 7.3.1
192 I/O
OSX 10.4.9
4.5G ram
Pro Tools HD3 Accel
PT 7.3.1
192 I/O
Don't worry, they'll get to you.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...
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...
"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...
Mac dual 2.7G G5
OSX 10.4.9
4.5G ram
Pro Tools HD3 Accel
PT 7.3.1
192 I/O
OSX 10.4.9
4.5G ram
Pro Tools HD3 Accel
PT 7.3.1
192 I/O
-
- Posts: 2232
- Joined: Thu Jan 13, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: USA
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.
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.
Re: M5v2 - Sample start/ends not saving - anyone else?
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...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)
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.
Sound Designers.Org founder
Mac Pro 2,66GHz - 5GB RAM - OS X.5.8 - M5 2.02
Mac Pro 2,66GHz - 5GB RAM - OS X.5.8 - M5 2.02