Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Paralinx Arrow caused HDMI-Board crash in Epic - had to send it "home" for repair

Last time my HDMI was used was on an octocopter setup - the guy had an arrow and had trouble getting it to work.

Just tried HDMI out on several monitors - no go. That sucks. Looks like mine is hosed as well.
 
Christian.

Same exact thing happened to me.

Brand spanking new Epic. HDMI port died after working for maybe 5 mins. Was using an Arrow.

Very strange.

Sent the camera back to RED and it's worked flawlessly ever since.


On another weird but interesting side note, I've also noticed problems with the Arrow when a walkie is used near the camera.
 
Interesting is that
the Arrow that Christian used is my Arrow 1:3 AND I use it with both of my EPICs all the time and I never had any problems.

I don't see the problem with the Arrow, I use it with my MacBooc Pro and my two EPICs all the time.
 
I had the same issue using a Nyrius HDMI transmitter (similar to the parallinx) with the Red Scarlet. The HDMI from my Red Scarlet stopped working after a couple of uses. I then used a cheap 75$ HD-SDI to HDMI converter, to connect the Scarlet HD-SDI OUT to the Nyrius. Guess what, the HDMI output of the converter died too after a couple of days.
 
Something must be up with some of the the epics hdmi, I wonder if this only affects a certain serial range. Red? I haven't used hdmi yet for transmitting, I'll probably wait to see how this all shakes out before trying...
 
I had dropped frame glitches when my Arrow was connected to the hdmi but unpowered. Red looked at it and alleged that there were hdmi connect messages spamming. This may be something specific to my Epic's hdmi board - upgrading to Arrow+ did not change the behavior. Works fine when the Arrow is powered though, so this is different from what's being described in this thread, and I don't mean to point a finger at Red or Paralinx... I've just learned to be VERY careful about unplugging the hdmi if I'm not powering the Arrow.
 
Is it possible what Red told you was that there was a spanning of HDMI connections? This does sound like a short, particularly with the overheating comments. HDMI blows.

Tim Morten said:
I had dropped frame glitches when my Arrow was connected to the hdmi but unpowered. Red looked at it and alleged that there were hdmi connect messages spamming. This may be something specific to my Epic's hdmi board - upgrading to Arrow+ did not change the behavior. Works fine when the Arrow is powered though, so this is different from what's being described in this thread, and I don't mean to point a finger at Red or Paralinx... I've just learned to be VERY careful about unplugging the hdmi if I'm not powering the Arrow.
Click to expand...
 
I took that to mean that hdmi was essentially packet based, and that connect messages were being spammed which the camera was trying to react to, interrupting its digestion of frames from the sensor. I didn't do any research to understand that more deeply though. :)

Edit: Quick search confirms that hdmi is indeed packet based, so I'm more confident that my understanding was correct.
 
Oh, OK. Over my head then. :-)

Tim Morten said:
I took that to mean that hdmi was essentially packet based, and that connect messages were being spammed which the camera was trying to react to, interrupting its digestion of frames from the sensor. I didn't do any research to understand that more deeply though. :)

Edit: Quick search confirms that hdmi is indeed packet based, so I'm more confident that my understanding was correct.
Click to expand...
 
Has anyone gotten to the bottom of this issue?

Mike
 
Same thing happened to my Scarlet using the Nyrus. After I got the HDMI replaced the Nyrus has been working great.
 
This really makes me nervous using the epic with the paralinx. I hope Dan and Red are in talk with each other to try to figure this out. There now three threads about similar issues...
 
Indeed - this is of course a sensitive issue.

Of the thousands of Arrow and Arrow+ out in the world, no HDMI port on any other device or Camera has ever stopped functioning while in use with our product.

I use the Arrow+ on a weekly basis with my personal Epic.

If you are having an issue, please be sure to file a support ticket with support@paralinx.net

If you are worried that you may have a sensitive HDMI port (many Many people don't have a bad HDMI port and have never had an issue) then one solution would be to use the Crossbow

http://www.paralinx.net/store/paralinx-crossbow

It is not only our product that has been in use when an Epic or Scarlet (or Red One) HDMI port has stopped working - it is monitors and recorders on HDMI as well.

My belief is that you are in good hands if any port stops working on your Red Digital Cinema Product, and if your Arrow stops working for some reason, you are of course 100% covered if under our warranty terms.

Best Regards,

Dan
 
Hi Dan,

Are you bringing out an all SDI solution, BTW?

Thank you very much

Fury
 
Using a cheap sdi-hdmi converter seems to be the safest way to use the Paralinx and Nyrius then, right? Worst case scenario you'd fry the converter not the camera's hdmi port.



Pedro Faerstein said:
Had the exact same problem after using the paralinx without issue for 3 months. One day the port simply stopped working. Bought a cheapo amazon sdi-hdmi converter and was able to keep using the paralinx on the epic. Didn't really think the trouble was related to the paralinx, as it wept working well. But after listening to similar reports, I don't know.

Cristian, did Red tell you it was a problem with the paralinx that caused it? Did they charge you for replacing the hdmi board?
Click to expand...
 
I really don't believe that the frying of the port is device related. It can happen using any piece of hardware. I had my SDI fail on a Scarlet that I had, and I connected converters, monitors, but obviously not my Arrow to the SDI port.
 
It is definitely device related- although not necessarily Paralinx. The most common reason for the video ports taken out is improper grounding of the device.
If there is no bullet proof protection (balun comes to mind) a nasty ground loop will take out the port eventually...
 
You must log in or register to reply here.
Back
Top