Thread: Vertical grey banding in viewfinder, camera inoperative - what to do?

Reply to Thread
Results 1 to 7 of 7
  1. #1 Vertical grey banding in viewfinder, camera inoperative - what to do? 
    Senior Member Mark Deeble's Avatar
    Join Date
    Aug 2010
    Location
    Kenya
    Posts
    142
    I booted up my Epic-M this morning in lightweight config (brain, side handle + redvolt, lcd and lens) and I got vertical grey banding in the viewfinder and the camera was inoperative. I have tried everything that I can think of and can't get it to work. I have:

    1. Switched power sources - redvolt, v-lock, mains adapter.
    2. Switched lcd cables ( x 4)
    3. Swapped the lcd for the evf
    4. Switched SSDs
    5. Reinstalled 2.0.5 beta and rebooted numerous times
    6. Tried rolling back to 1.7.9 - can't.
    7. I tried shooting with just the lens and side-handle - files ranged between 18KB and 880MB, but they just show coloured banding and I cannot recover the content I shot with REDundead.
    8. I have removed the SSD unit and tried restoring the system.

    I am remote and in Africa - so I really need to sort this myself if I can. I am in contact and getting help from Paul Jones and Alan Piper, REDeurope - but is there something I haven't tried or has anyone experienced anything like it?
    Attached Images
    Mark Deeble
    Wildlife Filmmaker
    cinematographer - director - writer
    www.deeblestone.com
    Reply With Quote  
     

  2. #2  
    Senior Member Curran Giddens's Avatar
    Join Date
    Jan 2007
    Location
    Berkshire County, Massachusetts
    Posts
    3,683
    Yikes!

    Maybe try re-downloading the firmware from Red.com again. Just in case the firmware installer is corrupt??? I have no idea what I'm talking about....


    http://www.SolarSystemStudio.com/

    EPIC-M #508, EPIC-X #124
    Reply With Quote  
     

  3. #3  
    Senior Member Mark Deeble's Avatar
    Join Date
    Aug 2010
    Location
    Kenya
    Posts
    142
    [COLOR=#FFFFFF !important]Curran - thanks, I'm trying - the problem is being in the bush with a verrry slow intermittent connection - speeds yesterday were .2 KB/sec so it took me over two hours to get a 2MB R3D out (!). I've been running 2.0.5 for a while without many issues.
    In addition i've tried:
    Removing all power, holding down the start for 30 secs then connected power and restarting.
    Booting up and then connecting the lcd/evf and tried to black-balance - won't.
    [/COLOR]
    Mark Deeble
    Wildlife Filmmaker
    cinematographer - director - writer
    www.deeblestone.com
    Reply With Quote  
     

  4. #4  
    Mark - you can roll back to 1.7.10 which is the last release build. I had similar problems on my last feature running 2.0.5 - went back to 1.7.10 and all was well. Good luck brother!
    watching budgets shrink since 2000

    www.adriancorreia.com
    Reply With Quote  
     

  5. #5  
    Senior Member Mike Lary's Avatar
    Join Date
    Mar 2011
    Location
    Seoul, South Korea
    Posts
    213
    Quote Originally Posted by Mark Deeble View Post
    Tried rolling back to 1.7.9 - can't.
    Mark,
    What happens when you try to force the 1.7.9 install?
    Mike Lary
    Director of Technology, DIGITAL FACTORY, Seoul
    Digital Revolution Since 2009
    Color Correction/Digital Workflow/Red Camera Rental
    www.DigitalFactory.kr
    Reply With Quote  
     

  6. #6  
    Senior Member Jacek Zakowicz's Avatar
    Join Date
    Jun 2008
    Posts
    1,752
    It turns out it may have been a fluke Prolock part that was involved.
    Investigating now on my end. All solved now it seems. No cameras we harmed in the process AFAIK- just a temporary error.
    Again- this prooves how bullet proof Epic are
    Big thanks to Mark, Jarred and the crew ....
    This is an isolated fluke but if you have any concerns what soever please contact me at the email below and I'll address your concerns.
    Jacek Zakowicz, Optitek-dot-org, jacek2@optitek.org
    Professional Broadcast and Digital Cinema Equipment
    Reply With Quote  
     

  7. #7  
    Senior Member
    Join Date
    Jul 2010
    Posts
    772
    Quote Originally Posted by OptiTek View Post
    It turns out it may have been a fluke Prolock part that was involved.
    Investigating now on my end. All solved now it seems. No cameras we harmed in the process AFAIK- just a temporary error.
    Again- this prooves how bullet proof Epic are
    Big thanks to Mark, Jarred and the crew ....
    This is an isolated fluke but if you have any concerns what soever please contact me at the email below and I'll address your concerns.
    wow. Nice of you to step up and take the Bullet for this!
    kudos

    Stu Aull
    Alaska
    Reply With Quote  
     

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts