PS4 + Destiny + Odyssey 7Q (2.11.110) Freezes - "Recording Unexpectedly Suspended"

Draco

Draco

New member
PS4 + Destiny + Odyssey 7Q (2.11.110) Freezes - "Recording Unexpectedly Suspended"

(Edit: ...on second thought, I have no idea why I posted in this specific forum, being that it isn't FS700-related. I just know that Mitch commonly swings by here, so he might be interested in it perhaps. I'll have to hunt for a more appropriate place for this most likely, unless a mod has a better idea on where to throw this. Sorry!)

I have an Odyssey 7Q using F/W 2.11.110 (with 2x512GB) freezing in a very weird fashion. Recording with 4:2:2 HD -> PRORES HD (.MOV)

When attempting to record Destiny from my PS4 with an HDMI-to-SDI converter (to achieve 1080p59 input) it seems to lock up during the opening video sequence at the same spot (of that video) and displays "Recording Unexpectedly Suspended". Touch functions cease to work and the unit requires a hard reboot as it never progresses past the flashing "Check last clip" and "Closing files, please wait". I cannot seem to recreate this issue with any other game yet, but I can replicate the issue every time in Destiny.

Any idea's why this might be happening? Can anyone else with a 7Q +PS4 + Destiny possibly test the same configuration? It has me a little worried that there might be something that could trigger this in the 7Q.

Here's a quick recording on YT showing off the issue at hand. Sorry for the poor focus in the recording and my blabbering.

http://youtu.be/DaDC2WzR0OQ

01:56 to fast-forward to the freeze: https://www.youtube.com/watch?v=DaDC2WzR0OQ#t=115
 
Last edited:
I've also had touch-response issues. VERY often will I turn on my O7Q and have no touch control of the unit and will have to power cycle the unit.

This has come up since latest firmware update.
 
Touch response not working is a glitch of the latest firmware. Convergent is aware of it. I had it on it a shoot and had to un-plug the battery like.. 15 times in one day, and it was super frustrating. Apparently, the current solution is to hit the F1 button on the side which re-calibrates the screen. Hopefully this gets fixed soon.
 
Another possibility, and I have not retried with the latest, I'd tested an earlier firmware, is the 7q does not support hdcp.

i tried reading output from a teradek clip designed to go to an ipad. Unless I used a hdcp stripping device, it wouldn't take it.

actually, just did a search and since April this year you can turn it off on the ps4 which I presume you've done?
 
Mitch Gross said:
Sounds to me like the HDCP theory is correct. We have to put this in our devices or we could suffer serious legal ramifications.

http://en.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection
Click to expand...
If this theory is correct, then how come this completely flips out the 7Q requiring a reset? Shouldn't the unit stop recording and alert that it synced with a signal that enabled it while losing a lock to the video feed? Last I remember, if HDCP is sent, it would display green or not acquire a lock at all.

Additionally, as timmy mentioned above for me to re-check, the PS4 should not be sending any HDCP signals as it's disabled in its own settings. Typcally, when something may require it, you would be prompted (eg. launching Netflix) and be booted from the application/game. Also keep in mind that this is additionally split to *another* capture device that does not support HDCP (and does not report EDID)... and this device (Datapath VisionRGB E1s) does not show any issue capturing it. Not even a blip.

I will try it with a HDCP stripper to rule out the PS4 going rogue and sending signals it shouldn't be first and report back.
 
Last edited:
Tested with the HDCP stripper without much luck. Same issues cropped up but on a different frame in the video, which I found odd.

Disabling Full Range RGB ("RGB Range: Limited" on the PS4) fixed the issue compl--... no, wait. As I was typing this post (and was still recording the PS4's dashboard) it happened again, only this time at a different FR point (26,258). I also had this occur when the PS4 wasn't doing much at all at its own dashboard. I tested 1080p, 720p, full and limited range, with the SDI converter (1080/720) and without it with direct HDMI (720 only).

I'm completely confused. Is there any way to diagnose why it might be doing this at all?

---------

New test - PS4 HDMI output is set to Automatic, hooked direct to the Odyssey (no splitters), signal negotiates @ 1080PSF 29.97 (I'm assuming the PS4 is sending out 1080i here), recording goes uninterrupted for well over 11 minutes now. While still connected direct, I attempted to set 720p and now it refuses to lock a signal, with the input reporting 1080PSF 30.00. I had to re-seat the HDMI connector in order to lock the new signal (now detecting 720p 59.94). I tested the same sequence again and we're back to the original freezing issue (2:41 into recording).

So I'm not sure *what* to blame here but I ruled out any of my splitters/converters/cables. It has nothing to do with HDCP from the looks of it. Very very frustrating.
 
Last edited:
The 7q is only on it's first firmware detecting the difference between I, p, psf. I've not found it to be reliable. In trying to get a signal out of the a7s in 50/60p the detection on the 7q flip flops, loops and makes the 7q unusable. I've found this using a hdmi to sdi converter that also puts test patterns at various I/p frame rates into sdi on 7q. So it's not limited to hdmi input. Mitch has said their engineers were going to test a bunch of cameras and converters a few months back. I did not hear back further.

there is a 7q submenu under video I think, where you manually force what it's expecting. Progressive or interlaced. I think I've seen this menu in prores as well as dpx. So maybe try that for more stability.

from reading its seems turning hdcp off on the ps4 is for games only not movies. But it sounds like you've tested all hdcp related bits. Have you tried another mode other than prores? And what's your input signal set to expect on the 7q?

and which sdi converter are you using? (I tried 3)
 
Try also setting the ps4 output to 1080i only, and 7q input the same. I've had no issues recording a fixed interlaced signal (not what I wanted, but stable in recording and detection using the hdmi to sdi converter)
 
If you have a PS4 devkit and not retail unit you can disable HDCP on the PS4. PM me if you need info as its under NDA.

I also noticed the crash happened during a lot of cuts, which would mean a bitrate spike in ProRes. Have you tried uncompressed capture? It could be an issue with not enough processing power on the unit to compress a video with a lot of changing pixels.
 
Last edited:
At this point I would suggest contacting cdsupport@convergent-design.com for more direct assistance.

As for the converter, I did ask our engineers again and they got back to me with one unit that so far has successfully handled every 1080 signal they could throw at it for converting HDMI to SDI. Best of all it's also one of the lowest cost units out there. $59 and they found it very reliable with a clean & robust signal. Powers off 5-12vdc as well.

http://www.amazon.com/Excelvan®-MIN...sr=8-8&keywords=hdmi+to+sdi+converter+1080p60
 
Mitch, thanks for that. They don't seen to be available to ship outside USA. Found one eBayer in Australia who claims to have one. Ordered. If it turns up looking forward to finally getting a7s working with 7q at 50/60p
 
Demistate said:
If you have a PS4 devkit and not retail unit you can disable HDCP on the PS4. PM me if you need info as its under NDA.

I also noticed the crash happened during a lot of cuts, which would mean a bitrate spike in ProRes. Have you tried uncompressed capture? It could be an issue with not enough processing power on the unit to compress a video with a lot of changing pixels.
Click to expand...

Regarding the HDCP portion: I was under the impression (and have this option applied) that as of a few months ago, a PS4 update provided the option to disable HDCP completely. So if an application required it, it would prompt you to change this option *BACK* to being enabled to use that specific application only (eg. Netflix). A dev kit or modified firmware is unnecessary... unless it's a PS3, of course.

Thanks for letting us know of your experiences with the Prores crashes though! I'm curious as well if these bitrate spikes, if that's what they are, can cause the Odyssey to flip out the same way from a FS700 (of which I own w/ the 4k upgrade). If this is the case... well.. that's no good. I will try uncompressed this morning to see what results I get.



Mitch Gross said:
At this point I would suggest contacting cdsupport@convergent-design.com for more direct assistance.

As for the converter, I did ask our engineers again and they got back to me with one unit that so far has successfully handled every 1080 signal they could throw at it for converting HDMI to SDI. Best of all it's also one of the lowest cost units out there. $59 and they found it very reliable with a clean & robust signal. Powers off 5-12vdc as well.

http://www.amazon.com/Excelvan®-MIN...sr=8-8&keywords=hdmi+to+sdi+converter+1080p60
Click to expand...

Thanks Mitch, I will contact cdsupport referencing this thread to help investigate further. And thanks for the converter suggestion as well. Unfortunately I already picked up this Oupree one off eBay for about $75. Difference with mine is mostly that I get 2 HD-SDI's out of it. But again, keep in mind that this crash happens with straight 720p HDMI and not through the converter, so I don't believe it might be that causing the problem.

oupree_hdmi2sdi.jpg


I also hope you guys have a PS4 in-house somewhere to relieve any of that stress! (and that you can test/replicate this issue with) ;)
 
Mitch,

your suggested converter worked. First one out of 3-4 much more expensive ones I've tested. And after starting and contributing to 3-4 threads over the last 9months or so asking if anyone on this board got hdmi > sdi 50/60p working with the 7q (as well as asking cd) I believe this is first time it's worked.

i still cannot get it to work in multistream. A single 50/60p feed flicks every two seconds or so, and two feeds (one from fs700) just renders the 7q inoperable with detection issues. Works fine in 1080i, so might be able to do some matching there.

anyway, it works. Now if only the a7s 50/60 signal was better (and 10-bit would be nice). I think the hdmi 2 output of the a7s is still 8bit? Maybe the moire and aliasing is gone though which would be ace :)

Draco, that converter and a cd sdi cable are cheap and worth a go. Zero detection issues for me now in 50/60p prores.
 
You must log in or register to reply here.
Back
Top