[Nikolaj]

Whenever I try to play a certain type MKV file XBMC crashes to ATV main menu after 10-15 seconds.

I use optical/coax as sound output, 5.1

ATV2 4.4.4
XBMC 11.0-BETA2 Git:20120120-f76c547
Xeebo

MEDIA
H264 - MPEG 4
1920x1080
Framerate 23.976216
AC3
3F2R/LFE
48000Hz
448kb/s

Files are stored on a QNap 419P and shared via FTP and all my devices are wired through gigabit and I can pay the files fine on my desktop.

XBMC.log http://pastebin.com/M3R0VR46
syslog http://pastebin.com/9VJt1NrN
Crashreport http://pastebin.com/0gSVCLjq

[Maetrik]

Morskabsboxen ReportCrash[1956]: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2012-02-06-150819.plist

Looks like OOM.

[Nikolaj]

Morskabsboxen ReportCrash[1956]: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2012-02-06-150819.plist

Looks like OOM.

Out of Memory?
If you are referring to low memory issues do you have any suggestions how to get around these?

[Maetrik]

Unfortunatly, i dont. Maybe one of the devs does as i'm not that good in reading crash reports or syslogs

[Nikolaj]

Unfortunatly, i dont. Maybe one of the devs does as i'm not that good in reading crash reports or syslogs

Hmm, I try to keep the system pretty sleek and use a light skin. Hope some clever dev will come with a golden solution!

[Memphiz]

Whenever I try to play a certain type MKV file XBMC crashes to ATV main menu after 10-15 seconds.

I use optical/coax as sound output, 5.1

ATV2 4.4.4
XBMC 11.0-BETA2 Git:20120120-f76c547
Xeebo

MEDIA
H264 - MPEG 4
1920x1080
Framerate 23.976216
AC3
3F2R/LFE
48000Hz
448kb/s

Files are stored on a QNap 419P and shared via FTP and all my devices are wired through gigabit and I can pay the files fine on my desktop.

XBMC.log http://pastebin.com/M3R0VR46
syslog http://pastebin.com/9VJt1NrN
Crashreport http://pastebin.com/0gSVCLjq

Code:

Open - using avcC atom of size(42), ref_frames(13)

13 ref frames on 1080p - never ever dude (this is out of spec - normally 5 ref frames on 1080p are ok for the hw decoder)...

Beside that - just for info - you used nfs for that file - not ftp

[Nikolaj]

Code:

Open - using avcC atom of size(42), ref_frames(13)

13 ref frames on 1080p - never ever dude (this is out of spec - normally 5 ref frames on 1080p are ok for the hw decoder)...

Beside that - just for info - you used nfs for that file - not ftp

Honestly I did not know about reference frames until now, but I get the idea and the quality of the video is incredible taking its relatively small size into consideration thanks to the high number of ref frames. Any idea how to reduce the number of ref frames (OSX)?
Thanks for the heads up on NFS Now the transfer protocol is on the table - any opinion on which is better/faster; NFS, FTP, SMB, other?

[Memphiz]

NFS is best of course ... ... you can reencode that file with handbrake. Don't think change of ref frames isn't possible without reencoding...