I have Windows M5 2 and it installed fine.
I downloaded and installed the update to 2.01 and now Live can't see the the VST and hangs.
Uninstalled everything and reinstalled ver 2.0 and all is well again.
Anyone else have this problem? If so then I'll put in a technote.
BTW: where's the info on ver 2.01's fixes?
Thx
Maybe platform specific but upgrading 2.0 to 2.01 woes
Moderator: James Steele
I didn't get the chance to try 2.0 (no Spectrasonics for me, booo) and I'm having trouble with 2.01 on Windows. The standalone is OK with the occasional crash/exit but the plug-in in Pro Tools isn't working at all well... yet.
I had to kick my graphics drivers up the backside in order for OpenGL (I'm guessing here) to let anything work, so I'm hoping this issue can be resolved similarly. I'm awaiting a tech support reply.
I like your memory leak theory - how do I check this? Just keep an eye on the "Mem Usage" in Windows Task Manager? Are you using any other host on Windows?
I had to kick my graphics drivers up the backside in order for OpenGL (I'm guessing here) to let anything work, so I'm hoping this issue can be resolved similarly. I'm awaiting a tech support reply.
I like your memory leak theory - how do I check this? Just keep an eye on the "Mem Usage" in Windows Task Manager? Are you using any other host on Windows?
Interesting - I've got the exact opposite in PTLE. M5v2's timing isn't even close to tight whereas v1's is fine. Of course this is all academic as v2 currently crashes as soon as it can!Sarcazm wrote:2.0 is pretty stable in Ableton Live (5.2), much more so that M5 1.2!
[By the way, I sincerely believe that I'll fix this problem, eventually. Naive optimism is the way forward!]
Hmm, timing with respect to what?3over3 wrote:Interesting - I've got the exact opposite in PTLE. M5v2's timing isn't even close to tight whereas v1's is fine. Of course this is all academic as v2 currently crashes as soon as it can!Sarcazm wrote:2.0 is pretty stable in Ableton Live (5.2), much more so that M5 1.2!
[By the way, I sincerely believe that I'll fix this problem, eventually. Naive optimism is the way forward!]
Can you give me an example using M52's included samples so I can check it in Live.
Timing as in accuracy - for instance, in PTLE it can't handle simple quantised 16ths at 120bpm - when I print the audio and look at the waveform, the beats fall nowhere near where they should be, just all around the actual beats, up to 30 ticks (=960ths of a quarter note) out from where they ought to be - both early and late. It all sounds a bit like a drunken drummer, or to be fair to drunken drummers, like a drunken keyboard player playing on their kit in a break between songs.
To do this I loaded either one sample (to LoopLab) or a small preset and triggered the same note (from an instrument track in Pro Tools) 16 times in one bar. As a control, I opened up MachFive 1 and got it to do the same thing - v1's timing's OK - not sample accurate, but OK - on my system. Each time, MachFive 2 would ultimately crash.
Actually, this is now old information as now I simply can't have M5v2 in Pro Tools - it loses the plot quickly, crashes and takes PT out with it. Before it goes, M5v2's polyphony readout claims it's playing in the region of 2000 notes, which it isn't.
To do this I loaded either one sample (to LoopLab) or a small preset and triggered the same note (from an instrument track in Pro Tools) 16 times in one bar. As a control, I opened up MachFive 1 and got it to do the same thing - v1's timing's OK - not sample accurate, but OK - on my system. Each time, MachFive 2 would ultimately crash.
Actually, this is now old information as now I simply can't have M5v2 in Pro Tools - it loses the plot quickly, crashes and takes PT out with it. Before it goes, M5v2's polyphony readout claims it's playing in the region of 2000 notes, which it isn't.
-
Shooshie
- Posts: 19820
- Joined: Sat Oct 16, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Dallas
- Contact:
Could you have a MIDI feedback loop somewhere, somehow? 2000 note polyphony sounds like what you'd get if you plugged MIDI in to MIDI out and vice-versa, and started playing notes into the loop.
But I have no idea; just trying to kickstart a little sideward thinking in hopes that you'll start to see the problem, whatever it may be.
Shooshie
But I have no idea; just trying to kickstart a little sideward thinking in hopes that you'll start to see the problem, whatever it may be.
Shooshie
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
It's good thinking, and much appreciated. I've been away from battling fine technology for a while, so will get on this asap. Fairly sure that Pro Tools can't make a MIDI feedback loop though - there's no MIDI thru from VIs.Shooshie wrote:Could you have a MIDI feedback loop somewhere, somehow? 2000 note polyphony sounds like what you'd get if you plugged MIDI in to MIDI out and vice-versa, and started playing notes into the loop.
But I have no idea; just trying to kickstart a little sideward thinking in hopes that you'll start to see the problem, whatever it may be.
Shooshie
The latest (and also quite wise) thinking from Tech Support is that I don't specifically meet the PC spec as I'm using a Sempron processor rather than the prescribed Pentium4. This doesn't quite seem to ring true, as the standalone's bearable and M5v1 insisted on a Pentium (III) too.
Any chip enthusiasts care to, er... chip in... with any reason why this should cause such a nightmare?
A big thanks - one mountain climbed!
Shooshie, you're a genius! Thanks for giving my brain a kick start with the magic words "MIDI feedback loop".
It's not possible in PT to accidentally make a MIDI feedback loop in the same way you might in the real world (a MIDI in patched to its own MIDI thru, for instance) - it simply shouldn't happen.
My first problem was that M5v2 was crashing instantly when starting in Pro Tools. A reinstall of MachFive 2 solved that, and gave me just enough leeway to notice that it only crashed when a MIDI note was sent to it from my external controller; not when loading a preset/sample; not when playing notes from M5v2's own keyboard in the mapping editor; and crucially not when Pro Tools' own MIDI tracks were patched into it.
Basically, when I played a note on my external keyboard, M5v2's polyphony readout would climb rapidly into the 2-3000 region, at which point it would crash. If I was lucky, I could remove the plug-in and start again. If not, it needed a restart.
At this point, my slow slow brain worked out that maybe Pro Tools' MIDI driver was faulty, but you can't just reinstall that, it needs a full reinstall, which for me required removal of PT7.1, install 7.0, update to 7.1 and finally the latest bugfixes - all of which meant I had to restart my PC about twenty-odd times.
Right now, MachFive 2.01 is stable in PT (well, ish - asking it to do difficult things too often isn't a wise idea).
The only problem is the timing is still appalling. Time to start climbing the next mountain...
It's not possible in PT to accidentally make a MIDI feedback loop in the same way you might in the real world (a MIDI in patched to its own MIDI thru, for instance) - it simply shouldn't happen.
My first problem was that M5v2 was crashing instantly when starting in Pro Tools. A reinstall of MachFive 2 solved that, and gave me just enough leeway to notice that it only crashed when a MIDI note was sent to it from my external controller; not when loading a preset/sample; not when playing notes from M5v2's own keyboard in the mapping editor; and crucially not when Pro Tools' own MIDI tracks were patched into it.
Basically, when I played a note on my external keyboard, M5v2's polyphony readout would climb rapidly into the 2-3000 region, at which point it would crash. If I was lucky, I could remove the plug-in and start again. If not, it needed a restart.
At this point, my slow slow brain worked out that maybe Pro Tools' MIDI driver was faulty, but you can't just reinstall that, it needs a full reinstall, which for me required removal of PT7.1, install 7.0, update to 7.1 and finally the latest bugfixes - all of which meant I had to restart my PC about twenty-odd times.
Right now, MachFive 2.01 is stable in PT (well, ish - asking it to do difficult things too often isn't a wise idea).
The only problem is the timing is still appalling. Time to start climbing the next mountain...
-
Shooshie
- Posts: 19820
- Joined: Sat Oct 16, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Dallas
- Contact:
Well, as I said before, I really have no idea! All I know is that this stuff can be terribly frustrating, and that "head-on" is not always the best way to tackle such problems. A lateral jolt is more often the thing that leads one to the right answer, even if it starts out wrong.
I'm glad you're on the track. Maybe the next mountain won't be so steep.
Shooshie
I'm glad you're on the track. Maybe the next mountain won't be so steep.
Shooshie
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
