Latest Mac OS X beta build

[mfoord]

I'm using the purlpleskunk 131 build (Mac OS X Lion on a Mac Pro). So far it is basically working very well - so thanks to all!

I still get some "buffering" or "stuttering", even with Java heap set to 2048M (I have 10G overall memory and transcoding is set to use 6 of the 8 cores). This is to a PS3 where both the Mac Pro and the PS3 are on a wired connection.

I am *still* getting the last few seconds of media files chopped. (Primarily H264 encoding in mkv containers.) The movie plays up until about 8 seconds short of the end and then stops. A minute or two later it may play another few seconds.

I'm using the x86_64 build, from the Lion SDK. 2011-08-07 (increased max heap size). I manually edited the info.plist to increase the Java heap.

[tin]

I'm using the purlpleskunk 131 build (Mac OS X Lion on a Mac Pro). So far it is basically working very well - so thanks to all!

I still get some "buffering" or "stuttering", even with Java heap set to 2048M (I have 10G overall memory and transcoding is set to use 6 of the 8 cores). This is to a PS3 where both the Mac Pro and the PS3 are on a wired connection.

I am *still* getting the last few seconds of media files chopped. (Primarily H264 encoding in mkv containers.) The movie plays up until about 8 seconds short of the end and then stops. A minute or two later it may play another few seconds.

I'm using the x86_64 build, from the Lion SDK. 2011-08-07 (increased max heap size). I manually edited the info.plist to increase the Java heap.

Did changing the heap size result in a noticeable change from the average 50MB buffer limit?

[Raptor399]

I still get some "buffering" or "stuttering", even with Java heap set to 2048M (I have 10G overall memory and transcoding is set to use 6 of the 8 cores). This is to a PS3 where both the Mac Pro and the PS3 are on a wired connection.

Did changing the heap size result in a noticeable change from the average 50MB buffer limit?

It ought to result in far less messages "Could not allocate..." and the buffer should grow more easily from its 50 MB starting point than in the default 768M Java heap situation.

[mfoord]

Did changing the heap size result in a noticeable change from the average 50MB buffer limit?

I changed the heap size from 1024M (I think - pretty sure it wasn't 768 which I was expecting) to 2048M in info.plist. It did seem to result in *less* stuttering, but not *none*.

Which buffer is only 50MB by default?

[mfoord]

An additional issue. On one movie, seeking was jumping me to random locations! I'll try with another (wife currently watching Lovefilm so can't try right now...).

[Raptor399]

Which buffer is only 50MB by default?

Transcoding buffers initially start with 50000000 bytes (see BufferedOutputFile, line 42 and 179). Once that number of bytes is reached, an attempt will be made to grow the buffer to the maximum memory size that was configured in PMS (different from the Java heap size).

[lobo85]

In both 1.30.1 and 1.31.0 ssa/ass subtitles are broken, when I am transcoding a mkv I get a "This data is corrupted" message from the PS3. I'd appreciate any help that I can get.

[mfoord]

Transcoding buffers initially start with 50000000 bytes (see BufferedOutputFile, line 42 and 179). Once that number of bytes is reached, an attempt will be made to grow the buffer to the maximum memory size that was configured in PMS (different from the Java heap size).

Thanks.

[tin]

Changing the heapsize from 1024MB to 2048MB in the info.plist file didn't raise the 50MB buffer limit. Any other ideas?

[Raptor399]

Changing the heapsize from 1024MB to 2048MB in the info.plist file didn't raise the 50MB buffer limit. Any other ideas?

I've made some changes in r800 that will help.