dannyoneill

Thanks Rich, nice to know there are people out there who would bother getting back to others even after years!! I am finding quite a few discussions online about how GarageBand likes to form links to media rather than import it if possible and is causing issues saving to internal drives even in some circumstances. Admittedly a very slightly different issue, but might come down to same root cause. I will experiment with storing our media in different locations prior import to see if that has an effect. By different locations I mean on mounted network shares, via symlinks, more directly with full paths, also from local repositories.

I know this is very old but in case anyone is looking for this: I have the same (original post, not the hijack) issue: - 32 brand new 2018 Macs on very latest OS - Gigabit network to fast SAN. Tested and get 90-95MB/s (byte not bit) transfer to the macs, can test that on about 7 macs concurrently before bandwidth starts to fall off. If I do all 32 we get about 35MB/s. - Those tests are to their network shares which are smbfs mounted shares on a very fast SAN. - Students can all stream music and video (HD) from the network simultaneously with no issues. Can save directly to the shares with Sibelius under all circumstances, including very large (GBs) files at the end of the lessons. HOWEVER, as per OP, our students have the following issue saving with GarageBand: - they can open from the network drives very quickly - they can save directly to the network drives very quickly - EXCEPT AFTER THEY ADD A MUSIC FILE IN GARAGE BAND, and then they cannot save, in fact GarageBand crashes. - When this happens I test whether the mount is still okay and its fine - I can separately still transfer files to the share. Including very large files. The only work-around we have is to (same as OP) tell students to save to the desktop and then copy the file to the network share separately. It works, but it relies on 11-18 year olds remembering a save and copy procedure they don't normally have to do, this then results in lost work. I have been using network traffic capture software to monitor what GB asks MacOS to do when saving, comparing to the times when you have not added a music track and there ARE marked differences. Haven't had time to analyse fully yet so not sure technically what is happening, but apparently the app does ask for something different in some way and its not just the size of the file, I have tried very large GB saves without imported tracks and they work just fine. No solution, but I have just the same as the OP I think and so I'm sure there are others out there with the same who don't deserve to be placated with "try getting faster switches". This IS a quite genuine and specific issue. I will post back if I discover what is happening.