Strange issue with record arming tracks on new mac
Posted: Wed Sep 23, 2015 7:47 pm
So I just got a new mac mini (late 2012 i7 2.3) to replace my aging late 2009 mini. I used migration assistant via firewire to set up the new mac exactly as the old one was. Everything seemed to go fine.
However, when I open any project that I keep on my Lacie external fw drive (which is where I store most of my work), I get a weird message something like "the file 0001.wav could not be opened" every time I try to record arm a track. After I click "ok" on this message, there is about a 10 second lag and then the track does eventually record arm. Go to arm the next, same behavior and so on...I googled this message and noticed that a couple other users had run into this problem, but there wasn't much conversation generated and no real conclusions reached.
Here's what I know:
- This doesn't happen for projects that I have stored on the internal drive
- This DOES happen if I open a project on the FW backup clone of this external drive
- This doesn't happen for new projects that I create and store on this external drive
- If I make a copy of one of the affected projects on the external drive and open it, this problem does not exist.
Because of the last point above, I'm not overly concerned and know how to get past this and work on stuff. But I'd sure love to know WHY this is happening. Perhaps someone with more general computer knowledge than myself can put the above clues together to hazard a guess? All I've done to troubleshoot beyond the above observations is to repair the disk and permissions in disk utility, but that didn't change anything..
thanks in advance!
However, when I open any project that I keep on my Lacie external fw drive (which is where I store most of my work), I get a weird message something like "the file 0001.wav could not be opened" every time I try to record arm a track. After I click "ok" on this message, there is about a 10 second lag and then the track does eventually record arm. Go to arm the next, same behavior and so on...I googled this message and noticed that a couple other users had run into this problem, but there wasn't much conversation generated and no real conclusions reached.
Here's what I know:
- This doesn't happen for projects that I have stored on the internal drive
- This DOES happen if I open a project on the FW backup clone of this external drive
- This doesn't happen for new projects that I create and store on this external drive
- If I make a copy of one of the affected projects on the external drive and open it, this problem does not exist.
Because of the last point above, I'm not overly concerned and know how to get past this and work on stuff. But I'd sure love to know WHY this is happening. Perhaps someone with more general computer knowledge than myself can put the above clues together to hazard a guess? All I've done to troubleshoot beyond the above observations is to repair the disk and permissions in disk utility, but that didn't change anything..
thanks in advance!