Mikael Berglund
Active member
- Joined
- May 20, 2012
- Messages
- 31
- Reaction score
- 0
- Points
- 6
Asking for a friend, he's new on Reduser and can't post a tread for some reason.
"Hi guys, I have a very weird problem, maybe someone had encountered this before?
I just Upgraded my Scarlet-X to the latest firmware and now there is something strange going on in the image, regardless of resolution or compression I have this strange artefacts running on the right side vertically. It runs from top to bottom. Of course I have tried to downgrade the FW (several times and to several different versions) but the problem now remains, I even did a hard reset, nothing.... it is stuck…
Googled this and it seems like it has happened to some users before in some degree, but not exactly like my pattern. And I have found no good answer to it....
I see it both in playback in camera as well as in premiere pro.
What can cause this? A bad debayer? A shortcut? processor problem? Codec? I don’t get it. I don’t think it's the sensor since it is not fixed to the pixels,. It's almost as there is some kind of bad code programed into the data going out???...
Anyone seen this before? Would appreciate feedback, thanks!"
I know he got it working again for a short time, when he started a mic during a recording and when he pulled the power plug and reattached it. But later it was the same thing again.
Anybody else encountered something similar?
"Hi guys, I have a very weird problem, maybe someone had encountered this before?
I just Upgraded my Scarlet-X to the latest firmware and now there is something strange going on in the image, regardless of resolution or compression I have this strange artefacts running on the right side vertically. It runs from top to bottom. Of course I have tried to downgrade the FW (several times and to several different versions) but the problem now remains, I even did a hard reset, nothing.... it is stuck…
Googled this and it seems like it has happened to some users before in some degree, but not exactly like my pattern. And I have found no good answer to it....
I see it both in playback in camera as well as in premiere pro.
What can cause this? A bad debayer? A shortcut? processor problem? Codec? I don’t get it. I don’t think it's the sensor since it is not fixed to the pixels,. It's almost as there is some kind of bad code programed into the data going out???...
Anyone seen this before? Would appreciate feedback, thanks!"
I know he got it working again for a short time, when he started a mic during a recording and when he pulled the power plug and reattached it. But later it was the same thing again.
Anybody else encountered something similar?