PS4 disconnecting every 20 minutes

Discuss media renderers like Xbox 360, TVs, smartphones, etc.
erick diangilis
Posts: 161
Joined: Sun May 22, 2016 8:25 am

Re: PS4 disconnecting every 20 minutes

Post by erick diangilis »

no i don't have this problem with the ps4 even after the 2.50 update from the media player. ;)
ninjamanco
Posts: 1
Joined: Wed Nov 02, 2016 10:13 pm

Re: PS4 disconnecting every 20 minutes

Post by ninjamanco »

Wade-Wilson wrote:Hey guys, so I dont know if anyone is still having this issue. But I just got this program two days ago and it was happening to me.So after a little bit of investigating(and reinstalling) I noticed that it really only started happening after I removed a folder from being shared. A couple of minutes after removing one, I would get kicked out. So I reset the program and was looking at the logs as it kept happening and I noticed every time it happened it was attempting to look at a previously played video from the folder that was removed. Hit reset cache on the "Navigation/Shared Settings" tab, reset the server and it hasnt happened since. Hope this helps someone else. If it does let me know :).
Just did that and solved my problem!
}{yBr!D^
Posts: 12
Joined: Thu May 12, 2016 12:32 pm

Re: PS4 disconnecting every 20 minutes

Post by }{yBr!D^ »

I reset my cache as well, it was a temp fix... then it started acting up again. It does the same with with Plex via the native DLNA browser of the Samsung unit (TV or Bluray) for me, this has been an on going issue... I don't know if it's the router or the PC itself or the devices............
dennisvanderpool
Posts: 1
Joined: Sun Jan 08, 2017 12:28 pm

Re: PS4 disconnecting every 20 minutes

Post by dennisvanderpool »

I started using UMS this week, awesome app, but was having the same disconnection issue.
Changed the preferIPv4 to false instead of deleting, but that didn't work for me.

I've resolved the issue. In my case it was caused by the following:

3 Devices: Sony TV -> iMAC (Running UMS) -> Fileserver share (SMB) containing movie

I saw java.io.exception messages that connection was closed.
I've copied over the movie i was watching to my iMac so that it becomes

2 Devices: Sony TV -> iMAC (Running UMS) -> File locally on iMac

And i could watch the rest of the movie for more than 1,5 hours without an issue.

I hope it helps someone :D
Chappers
Posts: 1
Joined: Tue Jan 31, 2017 4:55 am

Re: PS4 disconnecting every 20 minutes

Post by Chappers »

I am still having this problem with the PS4. I did try to refresh the shared folders but made no difference.
christinegrant98
Posts: 1
Joined: Thu Feb 09, 2017 10:17 pm

Re: PS4 disconnecting every 20 minutes

Post by christinegrant98 »

I have faced some issues with my PS4. After searching a lot I have found some great solutions regarding all the errors.
you can find your error and its solution. Many are listed here http://errorcodespro.com/ultimate-ps4-error-code-list/. Thanks
sunnysonic
Posts: 2
Joined: Thu Feb 09, 2017 12:16 pm

Re: PS4 disconnecting every 20 minutes

Post by sunnysonic »

Open the file ums.bat in C:\Program Files (x86)\Universal Media Server with a texteditor. Then remove the paramater

Code: Select all

-Djava.net.preferIPv4Stack=true
from the line so that the line looks like this:

Code: Select all

start javaw -Xmx768M -Dfile.encoding=UTF-8 -classpath update.jar;ums.jar net.pms.PMS
and save it.

Then start your server through this batch file and at least with me all my problems were gone.

Thanks everybody for the tips as probably also this forgoes the crash when a share is not found.
Nadahar
Posts: 1990
Joined: Tue Jun 09, 2015 5:57 pm

Re: PS4 disconnecting every 20 minutes

Post by Nadahar »

I've just read through this thread, and my conclusion (I don't have a PS4 for testing) is that this is most likely a network configuration issue.

To clear up some confusion, "java.net.preferIPv4Stack=true" is a Java setting that tells the Java Virtual Machine (which runs UMS) to prefer IPv4 over IPv6 if both are available. This setting can be be to either "true" or "false" when launching Java (from the command line) or from a script. "info.plist" is an OS X specific file, so it doesn't exist on other platforms.

UMS doesn't support IPv6, neither do most of the renderers out there. IPv6 support was added to the DLNA specification in the 2016 revision, and our UPnP library doesn't support IPv6 either. What is a mystery to me is how this can make any difference, as I'm very sure that I remember that UMS sets this to "true" during initialization anyway, overriding the value you might set at launch. The reason for this is very simple: as UMS only supports UPnP on IPv4 and so does most UPnP/DLNA devices, we don't want Java to only use IPv6 if both IP stacks are available. That will result in UMS not being able to "see" the renderers and vice versa.

It's still impossible to ignore that so many of you have reported that turning off IPv4 for Java has helped with the issue. There must be something else going on, as UMS will enable it again. There must be some obscure thing happening if UMS is initialized in IPv6 mode before switching to IPv4 that influences the connection with the PS4.

The DLNA standard has a procedure to follow if a device switches IP address while online, where the device is required to inform all other devices and then respond to both addresses for a given grace periode before only using the new IP address. This is not implemented in UMS as far as I know, it's one of those cases that seems so unlikely that noone really want to put the time in to make it. If the PS4 acquires a new one every 30 minutes or so, UMS won't "understand" if the PS4 tries to inform UMS of the change. When the grace periode is over, the PS4 will stop responding to it's previous address and the connection will break.

One user in this thread wrote that giving the PS4 a fixed IP(v4) address solved it. This is the most logical and sound "fix" if things are the way I suspect. Another option is to edit the DHCP server in your router. Most DHCP servers will let you assign a fixed IP address to a given MAC address. It's not possible to give an universal description of how to do this since that comes down to the individual router configuration, but usually you can get a list of leased addresses if you go into the DHCP section of the router. The MAC address is usually shown in this list, and can be copy/pasted when you "reserve" a given IP for a given MAC address. A MAC address is like a "serial number" for each network interface. Binding a specific address to the PS4's network interface's MAC address will mean that the router will always assign the PS4 the same IP when it asks for an address.

It would be interesting if some of you could try that and see if that resolves the problem. If this is the situation, the PS4 developers has some interesting hobbies. The default lease time is usually somewhere around 64 hours, and it's hard to see a good reason to keep switching IP address.
w00tx
Posts: 8
Joined: Fri Mar 25, 2016 3:28 am

Re: PS4 disconnecting every 20 minutes

Post by w00tx »

Nadahar wrote: Tue May 09, 2017 2:19 pm I've just read through this thread, and my conclusion (I don't have a PS4 for testing) is that this is most likely a network configuration issue.

To clear up some confusion, "java.net.preferIPv4Stack=true" is a Java setting that tells the Java Virtual Machine (which runs UMS) to prefer IPv4 over IPv6 if both are available. This setting can be be to either "true" or "false" when launching Java (from the command line) or from a script. "info.plist" is an OS X specific file, so it doesn't exist on other platforms.

UMS doesn't support IPv6, neither do most of the renderers out there. IPv6 support was added to the DLNA specification in the 2016 revision, and our UPnP library doesn't support IPv6 either. What is a mystery to me is how this can make any difference, as I'm very sure that I remember that UMS sets this to "true" during initialization anyway, overriding the value you might set at launch. The reason for this is very simple: as UMS only supports UPnP on IPv4 and so does most UPnP/DLNA devices, we don't want Java to only use IPv6 if both IP stacks are available. That will result in UMS not being able to "see" the renderers and vice versa.

It's still impossible to ignore that so many of you have reported that turning off IPv4 for Java has helped with the issue. There must be something else going on, as UMS will enable it again. There must be some obscure thing happening if UMS is initialized in IPv6 mode before switching to IPv4 that influences the connection with the PS4.

The DLNA standard has a procedure to follow if a device switches IP address while online, where the device is required to inform all other devices and then respond to both addresses for a given grace periode before only using the new IP address. This is not implemented in UMS as far as I know, it's one of those cases that seems so unlikely that noone really want to put the time in to make it. If the PS4 acquires a new one every 30 minutes or so, UMS won't "understand" if the PS4 tries to inform UMS of the change. When the grace periode is over, the PS4 will stop responding to it's previous address and the connection will break.

One user in this thread wrote that giving the PS4 a fixed IP(v4) address solved it. This is the most logical and sound "fix" if things are the way I suspect. Another option is to edit the DHCP server in your router. Most DHCP servers will let you assign a fixed IP address to a given MAC address. It's not possible to give an universal description of how to do this since that comes down to the individual router configuration, but usually you can get a list of leased addresses if you go into the DHCP section of the router. The MAC address is usually shown in this list, and can be copy/pasted when you "reserve" a given IP for a given MAC address. A MAC address is like a "serial number" for each network interface. Binding a specific address to the PS4's network interface's MAC address will mean that the router will always assign the PS4 the same IP when it asks for an address.

It would be interesting if some of you could try that and see if that resolves the problem. If this is the situation, the PS4 developers has some interesting hobbies. The default lease time is usually somewhere around 64 hours, and it's hard to see a good reason to keep switching IP address.

I'm out of ideas and it is driving me insane :twisted:
I don't even have DHCP enabled on my router so I got a static IP to my PS4 and it still keeps disconnecting every 20-30 minutes.
I have turned off IP6 completely, I even Went as far as disabling the teredo tunneling pseudo interface

What I dont understand is why it goes from this:

Code: Select all

DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 55 Osgiliath
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:55: start 11270.221000, end 11419.704000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 56 The Last March of the Ents
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:56: start 11419.704000, end 11571.605000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 57 The Nazgul Attack
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:57: start 11571.605000, end 11850.050000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 58 Forth Eorlingas
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:58: start 11850.050000, end 11996.613000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 59 The Flooding of Isengard
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:59: start 11996.613000, end 12281.815000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 60 The Tales That Really Mattered
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:60: start 12281.815000, end 12333.241000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 61 Fangorn Comes to Helm's Deep
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:61: start 12333.241000, end 12374.866000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 62 The Final Tally
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:62: start 12374.866000, end 12498.573000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 63 Flotsam and Jetsam
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:63: start 12498.573000, end 12648.556000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]       title           : Chapter 64 Farewell to Faramir
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Chapter #0:64: start 12648.556000, end 12748.114000
DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2]     Metadata:

to this(starts a short while before DC happens):

Code: Select all

DEBUG 2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2] Press [q] to stop, [?] for help
DEBUG 2017-10-07 16:22:20.389 [ffmpeg64.exe-6-2] frame=    1 fps=0.0 q=1.6 Lsize=N/A time=00:00:00.04 bitrate=N/A speed=0.894x    
DEBUG 2017-10-07 16:22:20.389 [ffmpeg64.exe-6-2] video:1kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
DEBUG 2017-10-07 16:22:27.509 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:22:29.911 [FFmpeg Thumbnail Failsafe] Stopping process: ffmpeg64.exe-5
DEBUG 2017-10-07 16:22:30.248 [FFmpeg Thumbnail Failsafe] Stopping process: ffmpeg64.exe-6
DEBUG 2017-10-07 16:22:58.881 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:23:30.436 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:24:01.931 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:24:33.476 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:25:04.927 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:25:36.358 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:26:07.863 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:26:39.431 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:27:10.940 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:27:42.472 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:28:14.054 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:28:17.488 [HTTPv2 Request Worker 1] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:17.489 [HTTPv2 Request Worker 1] Starting transcode/remux of 01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4 with media info: Container: MP4, Size: 6494164478, Video Bitrate: 3793315, Video Tracks: 1, Video Codec: h264, Duration: 3:48:16.000, Video Resolution: 1920 x 800, Frame Rate: 23.976, Frame Rate Mode: VFR (VFR), Matrix Coefficients: BT.709, AVC Level: 5.1, File Title from Metadata: 01 The Lord Of The Rings The Fellowship Of The Ring Extended - Fantasy 2001 Eng Rus Multi-Subs 1080p [H264-mp4], Audio Tracks: 3 [Id: 0, Language Code: en, Audio Track Title From Metadata: English AAC, Audio Codec: AAC-LC, Bitrate: 127931, Channels: 2, Sample Frequency: 48000 Hz, Year: 2001, Genre: Fantasy], [Id: 1, Language Code: en, Audio Track Title From Metadata: English AC-3, Audio Codec: AC3, Bitrate: 640000, Channels: 6, Sample Frequency: 48000 Hz, Year: 2001, Genre: Fantasy], [Id: 2, Language Code: ru, Audio Track Title From Metadata: Russian AAC, Audio Codec: AAC-LC, Bitrate: 127930, Channels: 2, Sample Frequency: 48000 Hz, Year: 2001, Genre: Fantasy], Subtitle Tracks: 3 [id: 0, type: TX3G, lang: en], [id: 1, type: TX3G, lang: ru], [id: 102, type: SUBRIP, lang: sv, externalFile: E:\Damien\The Lord Of The Rings Trilogy Extended Edition - Action 2001-2003 Eng Rus Multi-Subs 1080p [H264-mp4]\The Lord Of The Rings Extended Trilogy\01 The Lord Of The Rings The Fellowship Of The Ring Extended.srt, external file character set: WINDOWS-1252], DLNAThumbnail: [Format = JPEG, Resolution = 320×133, Size = 6723, DLNA Profile = JPEG_RES_320_133], Mime Type: video/mp4
DEBUG 2017-10-07 16:28:17.490 [HTTPv2 Request Worker 1] Reading maximum_bitrate: "30" (default: "90")
DEBUG 2017-10-07 16:28:17.490 [HTTPv2 Request Worker 1] Reading x264_constant_rate_factor: "Automatic (Wireless)" (default: "Automatic (Wired)")
DEBUG 2017-10-07 16:28:17.491 [HTTPv2 Request Worker 1] Creating pipe \\.\pipe\ffmpegvideo_55_1507386497491
DEBUG 2017-10-07 16:28:17.493 [Thread-34] Waiting for Windows names pipe connection "\\.\pipe\ffmpegvideo_55_1507386497491"
DEBUG 2017-10-07 16:28:17.793 [ffmpeg64.exe-7] Starting "C:\Program Files (x86)\Universal Media Server\win32\ffmpeg64.exe" -y -loglevel fatal -i "E:\Damien\The Lord Of The Rings Trilogy Extended Edition - Action 2001-2003 Eng Rus Multi-Subs 1080p [H264-mp4]\The Lord Of The Rings Extended Trilogy\01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4" -filter_complex "subtitles=E\\:/Damien/The Lord Of The Rings Trilogy Extended Edition - Action 2001-2003 Eng Rus Multi-Subs 1080p \[H264-mp4\]/The Lord Of The Rings Extended Trilogy/01 The Lord Of The Rings The Fellowship Of The Ring Extended.srt:charenc=WINDOWS-1252" -map 0:v -map 0:a:0 -bufsize 15000k -maxrate 14000k -crf 23 -ab 448k -ar 48000 -c:a ac3 -c:v libx264 -tune zerolatency -preset ultrafast -level 31 -pix_fmt yuv420p -f mpegts \\.\pipe\ffmpegvideo_55_1507386497491
DEBUG 2017-10-07 16:28:17.799 [ffmpeg64.exe-7] Reading pipe: \\.\pipe\ffmpegvideo_55_1507386497491
DEBUG 2017-10-07 16:28:17.800 [ffmpeg64.exe-7] Attaching thread: ffmpeg64.exe-7
DEBUG 2017-10-07 16:28:17.801 [ffmpeg64.exe-7-Timer] Created playback timer for PlayStation 4
DEBUG 2017-10-07 16:28:17.898 [Thread-34] Result of \\.\pipe\ffmpegvideo_55_1507386497491: true
INFO  2017-10-07 16:28:20.497 [StartPlaying Event] Started playing 01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4 on your PlayStation 4
DEBUG 2017-10-07 16:28:20.498 [StartPlaying Event] The full filename of which is: E:\Damien\The Lord Of The Rings Trilogy Extended Edition - Action 2001-2003 Eng Rus Multi-Subs 1080p [H264-mp4]\The Lord Of The Rings Extended Trilogy\01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4 and the address of the renderer is: 192.168.1.11
DEBUG 2017-10-07 16:28:22.027 [HTTPv2 Request Worker 2] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:22.051 [HTTPv2 Request Worker 3] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:22.068 [HTTPv2 Request Worker 4] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:22.084 [HTTPv2 Request Worker 5] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:24.464 [HTTPv2 Request Worker 6] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:26.452 [HTTPv2 Request Worker 7] Recognized media renderer "PlayStation 4"
DEBUG 2017-10-07 16:28:45.586 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:29:17.025 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:29:48.563 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:30:20.085 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:30:21.068 [HTTPv2 Request Worker 7] Setting margin to 2Mb
DEBUG 2017-10-07 16:30:51.667 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:31:23.226 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:31:54.741 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:32:26.206 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:32:57.850 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:33:29.285 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:34:00.789 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:34:31.977 [HTTPv2 Request Worker 14] Finishing configuration for Unknown renderer
DEBUG 2017-10-07 16:34:31.977 [HTTPv2 Request Worker 14] Reading MediaInfo: true (default: false)
DEBUG 2017-10-07 16:34:31.977 [HTTPv2 Request Worker 14] Updating status button for Unknown renderer
DEBUG 2017-10-07 16:34:31.977 [HTTPv2 Request Worker 14] Using default media renderer "Unknown renderer"
DEBUG 2017-10-07 16:34:32.238 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:35:03.770 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:35:35.227 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:36:06.788 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:36:38.266 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:37:09.813 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:37:41.310 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:38:12.754 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:38:44.408 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:39:15.882 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:39:47.502 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:40:18.899 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:40:50.433 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:41:21.956 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:41:53.550 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:42:25.018 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:42:56.389 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:43:27.798 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:43:59.374 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:44:30.836 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:45:02.254 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:45:33.696 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:46:05.094 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:46:36.556 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:47:08.122 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:47:39.639 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:48:11.206 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:48:42.702 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:49:14.072 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:49:45.661 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:50:17.191 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:50:48.617 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2017-10-07 16:51:18.647 [ffmpeg64.exe-7-Cleanup] Stopping process: ffmpeg64.exe-7
DEBUG 2017-10-07 16:51:18.647 [Thread-34] Windows named pipe interrupted after writing 0 bytes, shutting down...
DEBUG 2017-10-07 16:51:20.045 [UPNP-AliveMessageSender] Sending ALIVE...
INFO  2017-10-07 16:51:21.176 [StopPlaying Event] Stopped playing 01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4 on your PlayStation 4
DEBUG 2017-10-07 16:51:21.176 [StopPlaying Event] The full filename of which is: E:\Damien\The Lord Of The Rings Trilogy Extended Edition - Action 2001-2003 Eng Rus Multi-Subs 1080p [H264-mp4]\The Lord Of The Rings Extended Trilogy\01 The Lord Of The Rings The Fellowship Of The Ring Extended.mp4 and the address of the renderer is: 192.168.1.11


the lines that seem weird to me are:
2017-10-07 16:22:20.342 [ffmpeg64.exe-6-2] Press [q] to stop, [?] for help
2017-10-07 16:22:20.389 [ffmpeg64.exe-6-2] frame= 1 fps=0.0 q=1.6 Lsize=N/A time=00:00:00.04 bitrate=N/A speed=0.894x
2017-10-07 16:22:20.389 [ffmpeg64.exe-6-2] video:1kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
2017-10-07 16:22:29.911 [FFmpeg Thumbnail Failsafe] Stopping process: ffmpeg64.exe-
2017-10-07 16:22:30.248 [FFmpeg Thumbnail Failsafe] Stopping process: ffmpeg64.exe-6
2017-10-07 16:28:17.491 [HTTPv2 Request Worker 1] Creating pipe \\.\pipe\ffmpegvideo_55_1507386497491
2017-10-07 16:28:17.493 [Thread-34] Waiting for Windows names pipe connection "\\.\pipe\ffmpegvideo_55_1507386497491"
2017-10-07 16:28:17.799 [ffmpeg64.exe-7] Reading pipe: \\.\pipe\ffmpegvideo_55_1507386497491
2017-10-07 16:51:18.647 [ffmpeg64.exe-7-Cleanup] Stopping process: ffmpeg64.exe-7
2017-10-07 16:51:18.647 [Thread-34] Windows named pipe interrupted after writing 0 bytes, shutting down...




PLEASE HELP! :( :( :(
jeffreydvp
Posts: 2
Joined: Thu May 28, 2020 2:32 pm

Re: PS4 disconnecting every 20 minutes

Post by jeffreydvp »

For people still running into this, there is a setting on the PS4 to automatically stop applications after 20 minutes. This was the issue for me. Simply increase the the time to stop applications to 2+ hours, or disable this functionality
Post Reply