(2012-01-16, 14:50)Benjopa Wrote: I have exactly your same problem
I have an ATV2 connected wireless to a Time Capsule 2 TB with AFP. The SMB solution is not good because with SMB there are many many problems of bufferings and so the movie are awfuls.
@ Memphiz:
If you Know that all these problems are AFP related, why don't you try to patch them? AFP is very important for users like me with a Time capsule, a Airport extreme or a Mac.
However, thanks for your work
I came across this thread while searching for some insight into why XBMC crashes in the middle of a video or when I pause a video that is accessed via an AFP share. You have a valid point. Since AFP is the de facto, most widely used protocol for file sharing on the LAN in the Mac world, why isn't it
REALLY supported? I even had one of the devs tell me that most devs are using OS X for their development, so why is this OS X protocol not supported? I found this on the Kodi Wiki for
AFP:
Quote:XBMC has AFP (Apple Filing Protocol) client support for media on all platforms. We don't recommend using it, as AFP support in XBMC is very buggy right now.
Attention.png AFP in XBMC is kind of broken and you shouldn't use it:
Most users are reporting crashes when using AFP. This mostly is detectable by seeing something like "1174.20:17:33 T:145559552 ERROR: LIBAFPCLIENT: I have no idea what this is a reply to, id 29249." at the end of the xbmc.log.
The code library we use for AFP is not maintained by the developer anymore, and even Apple seems to be phasing out AFP. Users who have crashing with AFP are advised to switch to another file sharing protocol (e.x. smb or nfs).
Oh really? Then WHY is the AFP protocol allowed at all when adding a video source, if you know it will probably cause crashes. And why, after all this time, wasn't a simple exception handler written to simply trigger an error message and gracefully recover from the error? That's something I run into a lot with this software. If there is a problem opening or resuming a stream, instead of just timing out and throwing an exception and displaying an error message and recovering from the exception, XBMC just crashes. Exception handling is a fundamental requisite of any code worth its salt. There isn't a single media player I know of that crashes just because it can't open a stream. Crashing is not an option. And yet, it seems to be the
only option with this software. I suggest that, instead of releasing new versions with cutesy names and lots of little frills, you concentrate on fortifying the core code so it doesn't crash at the drop of a connection. Then maybe people like Benjopa and I won't need to complain about things we shouldn't have to complain about in the first place…
Meanwhile, I switched to NFS. I get it--AFP is NOT supported. There is an excellent article on setting up NFS sharing in the Wiki:
NFS sharing from OS X
It is a little more difficult to set up than adding a share from System Preferences, but not that difficult. So far it is working really well and is probably the best option for OS X users. I deliberately paused a video and left it for an hour, and when I came back, it played without crashing. This is the first time I was able to do this since first adding the AFP share. No more AFP, not that I have any love for it anyway… And SMB is not really a good option as Benjopa points out. Not only is it slow, and can cause crashes, and can prevent a remote Mac from going to sleep unless it is dismounted, it is mostly for Windows and so is a pain to set up and requires third-party drivers and mucking with configuration files for each NTFS drive if you want write capability. I would advise avoiding SMB.
