Imported from the Apple Support Forums via the Wayback Machine 🔗
Just set up a bunch of Mac Pro Intel workstations to replace our dual and quad G5s. All clients are direct attached to fiber. All stations running 10.4.9 and Xsan 1.4.1.
New issues we're seeing are Shake cannot consistently render onto the Xsan volume (when it could perfectly with the G5s!). Sometimes the rendered QuickTime are 32k files. Not at all what we want.
Also the Finder has many display issues. Logging out or restarting helps to clear that up. But this is really bad. Terminal shows all files fine, but the Finder is corrupt.
Anyone else seeing these issues, or have solutions? Or is this just plain Intel Mac Pro + Xsan + Shake bug?
Imported from the Apple Support Forums via the Wayback Machine 🔗
Strange news!
Niklas Algren on the Shake listserv discovered something about the issue of Shake (on Intel Mac Pros) rendering 32k QuickTimes on Xsan volumes:
(Thanks to Chris Noellert on the Xsan list for sharing this workaround, which I have tested and verified).
Basically, Shake on Intel-based macs will randomly fail to render Quicktime fileouts with non-local destinations (nfs/smb/xsan). The console will echo error 43.
Now, for the fun part; it will only fail if the length of the complete output path is an odd number Smile
I.e. /Volumes/temp/abcd.mov will render fine, /Volumes/temp/abc.mov will fail.
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Seems that the problem is bigger than Shake, it is actually a QuickTime + Intel + non-hfs filesystems problem.
Making QuickTime in Shake, with the AJA DPX translators, or exporting out of QuickTime can all result in the same errors: corrupt files with unusually small file sizes. 32 Kb or 512 Kb matching the blocksize of your SAN.
Thanks to Dan in xsanity forums for pointing this out.