Sorry to always post about my negatives and not so much about my positives which actually have been more then the negs.
Anyway, for the second time on 2 different files Motion has stopped working part way through the cut. This time it ran to 57% and just stopped, didn’t crash, just stopped sending commands. I thought I’d try clicking on “pause” then restarting it but that didn’t help, I was never able to restore the session.
I have an HP Pavilion G Series laptop, Win 10, 64 bit, 4 gig ram.
Unfortunately, as I understand it, Carbide Motion’s architecture makes it difficult to determine if this is caused by an EMI disconnect or CM crashing.