Transcode buffer causing problems

[Chrisoim]

Hi, I'm at my wits end with this:

1- Intel i7 930 @2.8GHz, 16GB RAM, Windows 7 home premium 64Bit, using PMS 1.50.1
2- Streaming to PS3
3- PC GBE->Router GBE-> PS3
4- All of the encoders cause problems as does pure streaming
5-
Ok, So I used to have the fatal memory error so i downsized my Transcode buffer to 400MB and everything seemed fine, however recently I started having problems with .avi files larger than 400MB (less than 400MB would work fine), they would just go crazy, video freezing while audio continued then it would reverse and the audio would freeze while the video caught up. looking everywhere i found a solution which involved setting the transcode buffer at 600MB. This worked flawlessly with my .avi files, but caused the fatal error again. So i tried editing the PS3.bat file but windows 7 being a pain wouldn't let me save the altered file to the correct place, so i went to "proper" administrator mode and edited the file to use javaw -Xmx2048M, since i have a lot of RAM it seemed like it would give plenty of room for 600mb buffer and for the program to run and do it's thing.

So after rebooting, I tried the .avi files and they worked fine again, tried an MKV, and the thing pretty much skipped massive sections of the movie, looked at debug and there was no fatal error message, so i ran it again and noticed the transcode buffer never exceeded 100mb before it went back to 0 and started filling again. I dropped the setting to 400mb again, and the .MKV played fine filling up the buffer quickly and staying full, but once again larger .avi files (any avi bigger than the transcode buffer) would freeze and jump its way through.

I notice it only affects .avi files greater than the transcode buffer which suggests (even though the buffer stays empty when playing the avi files) that the media server is trying to buffer the entire file rather than stream it directly (sorry i'm not too sure how it functions) and often only when it gets near the middle to end of the file (IE when it is nearing the 400mb point of the file)

I've tried all the solutions i could find on this board but they only fix one or the other either my files which need transcoding work fine or my avi files work fine, never both. it is driving me insane, I have to keep restarting PS3 media server with a different transcode buffer to watch my videos.

I have yet to try a >600mb .avi file but i suspect it will cause problems too, i will let you know.

I'm sorry i don't have a debug available now, i have to keep quitting to try new settings. I will do lots of tests tomorrow and try and save the debug file.

I hope someone can help me, because it is really frustrating to get to the end of a movie or show and have it become unwatchable at the interesting parts!

It should be noted I have watched my resource monitor during the freezes and pauses and there is plenty of CPU and RAM free, and network utilization barely registers

I thank anyone who can help me solve this in advance.

*Update*: it now appears all avi files are having problems again, regardless of size

[Raptor399]

so after some testing i am still having the same issue. When playing non transcoded files my debug log gets filled with the following:

Code: Select all

[New I/O server worker #2-1] DEBUG 11:32:32.792 Using size-limiting stream (75951054 bytes)
[New I/O server worker #2-2] DEBUG 11:32:32.823 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-3] DEBUG 11:32:33.165 Using size-limiting stream (75819982 bytes)
[New I/O server worker #2-4] DEBUG 11:32:33.447 Using size-limiting stream (73591758 bytes)
[New I/O server worker #2-5] DEBUG 11:32:33.478 Using size-limiting stream (75819982 bytes)
[New I/O server worker #2-6] DEBUG 11:32:34.133 Using size-limiting stream (73460686 bytes)
[New I/O server worker #2-7] DEBUG 11:32:34.278 Using size-limiting stream (75557838 bytes)
[New I/O server worker #2-8] DEBUG 11:32:34.881 Using size-limiting stream (73329614 bytes)
[New I/O server worker #2-9] DEBUG 11:32:34.914 Using size-limiting stream (75426766 bytes)
[New I/O server worker #2-10] DEBUG 11:32:36.012 Using size-limiting stream (73198542 bytes)
[New I/O server worker #2-11] DEBUG 11:32:36.040 Using size-limiting stream (75164622 bytes)
[New I/O server worker #2-12] DEBUG 11:32:37.020 Using size-limiting stream (74640334 bytes)
[New I/O server worker #2-13] DEBUG 11:32:37.292 Using size-limiting stream (73067470 bytes)
[New I/O server worker #2-14] DEBUG 11:32:37.953 Using size-limiting stream (74378190 bytes)
[New I/O server worker #2-15] DEBUG 11:32:39.086 Using size-limiting stream (72805326 bytes)
[New I/O server worker #2-16] DEBUG 11:32:39.153 Using size-limiting stream (74116046 bytes)
[New I/O server worker #2-1] DEBUG 11:32:39.570 Using size-limiting stream (72674254 bytes)
[New I/O server worker #2-2] DEBUG 11:32:39.825 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-3] DEBUG 11:32:39.887 Using size-limiting stream (72543182 bytes)
[New I/O server worker #2-4] DEBUG 11:32:39.930 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-5] DEBUG 11:32:40.170 Using size-limiting stream (72412110 bytes)
[New I/O server worker #2-6] DEBUG 11:32:40.210 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-7] DEBUG 11:32:40.521 Using size-limiting stream (72281038 bytes)
[New I/O server worker #2-8] DEBUG 11:32:40.550 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-9] DEBUG 11:32:40.899 Using size-limiting stream (72149966 bytes)
[New I/O server worker #2-10] DEBUG 11:32:40.929 Using size-limiting stream (73853902 bytes)
[New I/O server worker #2-11] DEBUG 11:32:41.185 Using size-limiting stream (72018894 bytes)
[New I/O server worker #2-12] DEBUG 11:32:41.718 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-13] DEBUG 11:32:41.936 Using size-limiting stream (71625678 bytes)
[New I/O server worker #2-14] DEBUG 11:32:41.975 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-15] DEBUG 11:32:42.526 Using size-limiting stream (71494606 bytes)
[New I/O server worker #2-16] DEBUG 11:32:42.724 Using size-limiting stream (73591758 bytes)

non stop, hope this helps improve the chances of any possible resolution!

thanks

[taconaut]

It seems recent pms releases use more memory then older ones; this is an issue we will look into. Can't say if it is pms itself or used transcoding libraries.
Meanwhile, the solution is to increase the memory available to the java vm running pms (xmx), if you've got enough. Click

[Raptor399]

so after some testing i am still having the same issue. When playing non transcoded files my debug log gets filled with the following:

Code: Select all

[New I/O server worker #2-1] DEBUG 11:32:32.792 Using size-limiting stream (75951054 bytes)
[New I/O server worker #2-2] DEBUG 11:32:32.823 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-3] DEBUG 11:32:33.165 Using size-limiting stream (75819982 bytes)
[New I/O server worker #2-4] DEBUG 11:32:33.447 Using size-limiting stream (73591758 bytes)
[New I/O server worker #2-5] DEBUG 11:32:33.478 Using size-limiting stream (75819982 bytes)
[New I/O server worker #2-6] DEBUG 11:32:34.133 Using size-limiting stream (73460686 bytes)
[New I/O server worker #2-7] DEBUG 11:32:34.278 Using size-limiting stream (75557838 bytes)
[New I/O server worker #2-8] DEBUG 11:32:34.881 Using size-limiting stream (73329614 bytes)
[New I/O server worker #2-9] DEBUG 11:32:34.914 Using size-limiting stream (75426766 bytes)
[New I/O server worker #2-10] DEBUG 11:32:36.012 Using size-limiting stream (73198542 bytes)
[New I/O server worker #2-11] DEBUG 11:32:36.040 Using size-limiting stream (75164622 bytes)
[New I/O server worker #2-12] DEBUG 11:32:37.020 Using size-limiting stream (74640334 bytes)
[New I/O server worker #2-13] DEBUG 11:32:37.292 Using size-limiting stream (73067470 bytes)
[New I/O server worker #2-14] DEBUG 11:32:37.953 Using size-limiting stream (74378190 bytes)
[New I/O server worker #2-15] DEBUG 11:32:39.086 Using size-limiting stream (72805326 bytes)
[New I/O server worker #2-16] DEBUG 11:32:39.153 Using size-limiting stream (74116046 bytes)
[New I/O server worker #2-1] DEBUG 11:32:39.570 Using size-limiting stream (72674254 bytes)
[New I/O server worker #2-2] DEBUG 11:32:39.825 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-3] DEBUG 11:32:39.887 Using size-limiting stream (72543182 bytes)
[New I/O server worker #2-4] DEBUG 11:32:39.930 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-5] DEBUG 11:32:40.170 Using size-limiting stream (72412110 bytes)
[New I/O server worker #2-6] DEBUG 11:32:40.210 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-7] DEBUG 11:32:40.521 Using size-limiting stream (72281038 bytes)
[New I/O server worker #2-8] DEBUG 11:32:40.550 Using size-limiting stream (73984974 bytes)
[New I/O server worker #2-9] DEBUG 11:32:40.899 Using size-limiting stream (72149966 bytes)
[New I/O server worker #2-10] DEBUG 11:32:40.929 Using size-limiting stream (73853902 bytes)
[New I/O server worker #2-11] DEBUG 11:32:41.185 Using size-limiting stream (72018894 bytes)
[New I/O server worker #2-12] DEBUG 11:32:41.718 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-13] DEBUG 11:32:41.936 Using size-limiting stream (71625678 bytes)
[New I/O server worker #2-14] DEBUG 11:32:41.975 Using size-limiting stream (73722830 bytes)
[New I/O server worker #2-15] DEBUG 11:32:42.526 Using size-limiting stream (71494606 bytes)
[New I/O server worker #2-16] DEBUG 11:32:42.724 Using size-limiting stream (73591758 bytes)

non stop, hope this helps improve the chances of any possible resolution!

thanks

Yes, that helps quite a bit.

I'm not sure how streaming should be affected by any size of buffer. To repeat an old rant: surely any processor can copy bytes faster than any network or device playback can handle. A 10K buffer ought to be sufficient.

That said, the error message you posted can only occur at one spot, and I found a bug there.
Fix committed, thanks!

[happy.neko]

To repeat an old rant: surely any processor can copy bytes faster than any network or device playback can handle. A 10K buffer ought to be sufficient.

The rant may be old, but its still valid! And PS3 clearly has internal buffer because I can stream videos over 100 mbits network with bitrate pikes exceeding it without stuttering.

[MKUltra]

Sorry to re-ignite this, but watching mkv files has been painful ever since the default transcode buffer was lowered to 400mb. If I am watching an mkv file I constantly experience intermittent freezing. I even tried increasing the heap space memory in the info.plist file to-Xmx2048M and this did not help. I am using Build: 02688dc84 (2012-03-15). Any suggestions?

[Raptor399]

Sorry to re-ignite this, but watching mkv files has been painful ever since the default transcode buffer was lowered to 400mb. If I am watching an mkv file I constantly experience intermittent freezing. I even tried increasing the heap space memory in the info.plist file to-Xmx2048M and this did not help. I am using Build: 02688dc84 (2012-03-15). Any suggestions?

Sounds like the mkv files stutter for you no matter what memory or buffer size you use?
Maybe it is not buffering that is causing the problems, but the transcoding quality.

[troek]

i am having similar problems with .mkv files. it plays fine for about 5-10 minutes, sometimes longer, then the video just starts fast forwarding ahead of the audio. my buffer shows about 200mb during this, but i noticed my cpu load drops to about 0% and stays there until i restart the video from another point. (edit) file has subtitles.

1- AMD quad core 9650 8gm ram vista 64 PMS version 1.52.0
2- Device you are streaming to PS3
3- WIFI DLINK DIR-615
4- Which engine you are using if you're transcoding (MEncoder, AviSynth/MEncoder, TSmuxer) not sure?

6-INFO 2012-04-03 21:32:11.503 [pool-7-thread-1] Checking IP: 192.168.1.118 for Playstation 3
INFO 2012-04-03 21:32:12.008 [New I/O server worker #1-5] Checking shared folder: C:\Users\Hess\Videos
INFO 2012-04-03 21:32:13.042 [main] The server should now appear on your renderer
INFO 2012-04-03 21:32:16.106 [pool-7-thread-1] Renderer Playstation 3 found on this address: 192.168.1.118
INFO 2012-04-03 21:32:18.115 [pool-7-thread-1] Address /192.168.1.118 has an estimated network speed of: 16 Mb/s
INFO 2012-04-03 21:33:06.081 [New I/O server worker #1-7] Starting transcode/remux of [yibis]_One_Piece_415_[720p][69A477D0].mkv
INFO 2012-04-03 21:33:06.381 [StartPlaying Event] renderer: 192.168.1.118, file: C:\Users\Hess\Videos\One Piece 401-450\[yibis]_One_Piece_415_[720p][69A477D0].mkv
INFO 2012-04-03 21:50:18.410 [AWT-EventQueue-0] Configuration saved to: C:\ProgramData\PMS\PMS.conf

[MKUltra]

the issue for me, and I still need to confirm, was that the maximum bandwith in the General Configuration tab was set to "0" instead of the default 110 mb/s.

[MKUltra]

the issue for me, and I still need to confirm, was that the maximum bandwith in the General Configuration tab was set to "0" instead of the default 110 mb/s.

i have confirmed that the issue was maximum bandwith set to "0" and HTTP Engine V2 was not selected.