[davilla]

Do you still need my log again davilla ?

If turning off vblank sync resolves the issue you are seeing, no. If not, yes.

[roads]

Where do i turn it off? Did a search but have no clue.
And where can I activate tripplebuffer I read that on my search for vnlank it could help.

found the vblank, makes no difference the XBMC CPU is on 12
10+% and the framerate drops to 10-17/sec.

Does not matter if i set software or basic shaders or sync to monitor, hardware accel, whatever. Tried them all, minor difference.

played the movie 5 minutes

LINK to logfile

[davilla]

Where do i turn it off? Did a search but have no clue.
And where can I activate tripplebuffer I read that on my search for vnlank it could help.

found the vblank, makes no difference the XBMC CPU is on 12
10+% and the framerate drops to 10-17/sec.

Does not matter if i set software or basic shaders or sync to monitor, hardware accel, whatever. Tried them all, minor difference.

played the movie 5 minutes

LINK to logfile

Very odd, you have a 2.93 GHz iMac that can't handle bluray h.264 with software ffmpeg. My 2.4GHz MacBook can do that even under 10.6.

Let me see same thing with VDA enabled and renderer set to auto or ARB.

[roads]

Its not h264 its 1080p uncompressed. The file has 33gb.
here is your new log its just the same auto and hardware accel.

LINK to logfile

[davilla]

Its not h264 its 1080p uncompressed. The file has 33gb.
here is your new log its just the same auto and hardware accel.

LINK to logfile

Ahh, please learn the technology. Bluray uses a m2ts container and can have one of three video encoded formats, those formats are mpeg2, h264 and vc1. That is bluray spec. From your file, ffmpeg says the following;

01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Input #0, mpegts, from '/Users/pb/Movies/21 Grams (2003) Blu Ray/00000.m2ts':
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Duration: 02:04:30.79, start: 11.608967, bitrate: 35570 kb/s
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Program 1
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Stream #0.1[0x1100]: Audio: pcm_bluray, 48000 Hz, stereo, s16, 1536 kb/s
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Stream #0.2[0x1101]: Audio: dca, 48000 Hz, 5.1, s16, 1536 kb/s
01:12:19 T:2953850880 M:2517790720 INFO: ffmpeg[B0103000]: Stream #0.3[0x1200]: Subtitle: pgssub


^^ See, h264. If this was uncompressed video, it would way exceed 33Gbs in size. Uncompressed 1080p is 90-100 mega-BYTES per seconds. Do the math, it's huge.

Now to your xbmc.log

NOTICE: Open - VDADecoder Codec failed to open, status(-12470), profile(100), level(41)

-12470 means kVDADecoderHardwareNotSupportedErr, VDA decoder is saying it's not supported under your hardware. Which is very silly. There's something very wrong here. You have 2.93GHz Core2Duo which should be plenty fast enough for software ffmpeg, you should have VDA decoder, yet the API says no. Not sure what to say except something is not right here.

[roads]

Thanks for explaining, always thought that its uncompressed as XBMC does not show a h264 sign in the database.
So what can I do? Is there any line I can add in the advanced setting to try or a Mac program that checks or modifies the graphics cards settings? (triple buffer helped a lot of perople in the forums)
When debg mode is on CPU1 is 0%, CPU2 is 0% and XBMCCPU is 117-120 continuously.

[snowdrift]

Now to your xbmc.log

NOTICE: Open - VDADecoder Codec failed to open, status(-12470), profile(100), level(41)

-12470 means kVDADecoderHardwareNotSupportedErr, VDA decoder is saying it's not supported under your hardware. Which is very silly. There's something very wrong here. You have 2.93GHz Core2Duo which should be plenty fast enough for software ffmpeg, you should have VDA decoder, yet the API says no. Not sure what to say except something is not right here.

I could be wrong, but this isn't because the graphics card in question is a nVidia GeForce GT 130 and that's not supported by VDAdecoder, is it? Or is that just wierd XBMC logging for a supported card.

Code:

NOTICE: GL_RENDERER = NVIDIA GeForce GT 130 OpenGL Engine

The Video Decode Acceleration Framework Reference says "This reference describes the Video Decode Acceleration framework available on Mac OS X 10.6.3 and later with Mac models equipped with the NVIDIA GeForce 9400M, GeForce 320M or GeForce GT 330M."

[roads]

I read that the GT130 is supported. How can I make sure the accelerator is running in other programs? Why is VLC running smoothl? (even if at the end of the movie it gets buffer problems?)

[roads]

Meanwhile, Apple also details which GPUs will be supported for their upcoming OpenCL API. OpenCL will allow developers to easily offload additional processing tasks to the computer's GPU. Some tasks may find greater benefit from this than others, but could potentially offer substantial performance boosts. The list of supported GPUs include:

- NVIDIA Geforce 8600M GT, GeForce 8800 GT, GeForce 8800 GTS, Geforce 9400M, GeForce 9600M GT, GeForce GT 120, GeForce GT 130.
- ATI Radeon 4850, Radeon 4870

This is from macrumors, cant find an official site.

[snowdrift]

Meanwhile, Apple also details which GPUs will be supported for their upcoming OpenCL API. OpenCL will allow developers to easily offload additional processing tasks to the computer's GPU. Some tasks may find greater benefit from this than others, but could potentially offer substantial performance boosts. The list of supported GPUs include:

- NVIDIA Geforce 8600M GT, GeForce 8800 GT, GeForce 8800 GTS, Geforce 9400M, GeForce 9600M GT, GeForce GT 120, GeForce GT 130.
- ATI Radeon 4850, Radeon 4870

This is from macrumors, cant find an official site.

The VDADecoder API and OpenCL are two different things as far as I'm aware.

[roads]

So you think the card is unsupported yet XBMC tries to use it and that’s why it jitters?

[fingon]

Judging by the log, it fails at init, uses software, and doesn't behave correctly for some other reason..

[fingon]

Interestingly enough, it seems that even some 720p material fails horribly at times with vblank on + hardware decoding. Turning to software results in those cases resulted 0 drops. Quite odd.

[roads]

So what now, any one looking into this or that’s it?

[roads]

You wont like this, Plex is playing the file smoothly jitter free.