Jump to content

Search the Community

Showing results for tags 'format'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cinematography Forums
    • General Discussion
    • News & Press Releases
    • Lighting
    • Camera Operating
    • AC's & DIT's
    • Grip & Rigging
    • Visual Effects Cinematography
    • Grading, DI and Telecine
    • Students and New Filmmakers
    • Cameras Systems and Formats
    • Lenses & Lens Accessories
    • Camera Accessories & Tools
    • Film Stocks & Processing
    • Books for the Cinematographer
    • Cinematographers
    • In Production
    • On Screen
    • Cine Marketplace
    • Business Practices
    • Jobs, Resumes, and Reels
    • Please Critique My Work
    • Regional Cinematography Groups
  • Not Cinematography
    • Producing
    • Directing
    • Sound
    • Editing
    • Off-Topic
    • Forum Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Location


My Gear


Specialties

Found 4 results

  1. I wanted to share a problem I recently encountered on a feature I shot in May/June of 2017. This website is a great resource to search for solutions to film specific problems and I feel my experience with G Drives, partition maps, formatting, and Red Undead can help others who may end up in the same situation. I will go in depth on what I learned and end with a simple tutorial on how to fix the problem. Detailed Story The production I was shooting decided to have post-production be a Windows OS based workflow. Per usual, I checked in with the post-team to figure out their OS and together advised the production on which types of hard drives to get. Remember, a FAT32 file system is largely unsuitable for video production because of the file size limitations. The production was opening formatting all of the hard drives FAT32 so they can work on either a Windows or Mac OS, but I advised against it for the above reason. I haven't had much experience with ExFat, which holds larger file sizes and is cross platform. We decided a conservative approach and felt formatting the hard drives for Windows was our best solution. The film was low budget and slightly inexperienced, so we received our hard drives on the first day of production. We used G-Drive branded hard drives with 3TB each. Our camera system was the RED Epic with normal SSD magazines. The first night after shooting we started to format hard drives and discovered that G-Drive is specifically designed for Mac. It can work on Windows, but G-Drive's workflow for formatting hard drives on and for a Windows environment is convoluted. Instead of having the hard drive in a FAT32 format that both systems can recognize for initial formatting, the drives came pre-configured for Mac. To format them, we had to use disk utility and command prompt (see instructions here: https://support.g-technology.com/KnowledgeBase/answer.aspx?ID=14080) A key thing to note about this process: command prompt uses the clean command that erases the information that tells the computer the layout of the file structure of the hard drive. In a nutshell, every hard drive has a file that is a roadmap of all the data it stores; where each physical gate is, what row, how it's fragmented, etc. Windows and Mac have very specific structures, hence why Mac hard drives are largely unreadable by Windows and vice versa. [TANGET] Software exists that allows the OS's to read hard drives for opposing OS's [TANGENT] The clean command erases that file, but nothing else. When you're in a Windows environment, a Mac formatted hard drive will not even be recognized by the OS. The only way a user can see it is through the Disk Utility program; at that point a user can only see that a hard drive is connected, but nothing else (because Windows sees nothing else either!). When you use clean in command prompt on the Mac hard drive, it creates the drive as an "unallocated" or unused hard drive. You can then create a new volume out of this unallocated hard drive and format it to a Windows structure. From there you have a hard drive that Windows can read/write to. What if you accidentally use a clean command? What if that command was used on a Red SSD that has undownloaded footage? That happened to my production. There is no way to undo a clean command; the partition file that describes to the OS what the structure is becomes completely unique once content is written to the hard drive because the partition file is updated to reflect where that new information is written. It's like a dynamic rosetta stone; without it, there's no way to decipher the data written. It is better described as a partition map. With the partition map erased, the SSD had undownloaded footage with no way to find it. This became extremely stressful for me. However, I did find a solution. Red Undead is a Mac based program developed by Red. It's designed for recovering data from accidental formatting of SSD's. Essentially, when an SSD is formatted in camera, the partition is re-written to display the structure and all of the data is made available for re-writing. But, none of that data is changed; physically the bits are still in the position they were last in (either a 1 or 0). Red Undead takes advantage of these "old states" and reads the data. From there, based on how Red's own R3D files are constructed, Red Undead can re-create the lost footage. To recap, we had accidentally erased the partition map of a Red SSD. There's undownloaded footage sitting on the magazine, but there's no map available to tell the computer a) that a hard drive exsists and B) what and where each file is. So, we decided to try Red Undead. We formatted the Red SSD in camera (to write the Red partition file) and then brought it into Red Undead. The program then spent an hour or so reading every gate, eventually spitting out nearly all of the lost footage. We only lost a portion of the first clip, which is a lot better than losing the entire card. NOTE: do not perform a secure format of the SSD in camera. A secure format rewrites the partition file and writes 0's across the entire SSD. A secure format truly erases footage. There are a few things to learn from my experience: Hard Drives must be delivered during prep. Be adamant about it as a DP and DIT. Erasing a partition map is part of the formatting process; the damage is done. An unsecured or simple format doesn't erase the already written data, but makes it available to be written over A secured format erases the partition map and writes 0's across the entire card/hard-drive, fully erasing footage. Red Undead reads old written data that hasn't been written over yet Red Undead is only available for the Mac OS. (we should keep pestering them for a Windows port) The obvious one: DO NOT FORMAT HARD DRIVES WITH CAMERA MEDIA CONNECTED AT THE SAME TIME Of course, this technology may change over the years, but the concepts should hold. Tutorial: How to fix a Red SSD Mag that has its partition map erased If the partition map has been erased, do nothing else to the SSD mag if it's still connected to a computer. Insert the SSD mag and do an unsecure format in camera. Reconnect the SSD mag to a Mac computer. Run Red Undead in the computer. Verify which clips were saved and which were not. Ensure recovered clips are backed up before formatting the card again. --- I hope my experience can help others! I'm in no way an engineer (software or hardware), so please correct me if my terminology or concepts are wrong. Has anyone else had experiences similar to this? Does ARRI, Canon, or Panasonic offer data recovery software like Red Undead?
  2. Hi I am a Cinematographer on a feature film that we're going to start filming in September on the ARRI Alexa EV camera. We have the SXS cards and can max film in ProRes 4444. My question is, is it worth trying to find faster cards and then film in ARRI raw? Or do I get almost the same quality out of the ProRes 4444. The film is properly going to end up on a DCP 2K or 4K. We are setting the camera up fro 16:9 full and then use a 1:2:35 mask to frame after. Thank you, Henrik A. Meyer www.henrikameyer.com
  3. Hello, I've bought a used Arri Sr3 Highspeed. It is adjusted to super 16. I haven't used it in a while and I have an anamorphic shoot coming up where I will be using 2x anamorphics. I want to shoot in Normal16 to get the 2,66:1 aspect ratio. Do I have to get through the adjustment of changing the camera's lens alignment, the opening in the universal film gate and the viewfinder alignment in order to convert it to normal16? I lack the tools and the experience to do so. I get that I definately need to do this when adjusting from normal 16 to super 16, but isn't it sufficient to just change the Fibre Optic Viewing Screen in my case? In post I would just have to crop the sides because the Super16 just uses a larger portion of the negative. I won't lose any resolution by going down this road in comparison to adjusting all the mentioned parts of the camera and just have the additional portion of the super 16 frame covered and unexposed in normal16 "mode", right? Thank you so much for the answers! Best Walter
  4. I read that the Panasonic AG-DVX200 features a 4/3-type, large formate image sensor. Doesn't the AF101 has a MFT sensor? So shouldn't it be a large format as well though the crop factor is around 1.7x to S35mm and 2x to full frame? or 4/3 and MFT are much different in size and format? thank you for any clarifications :)
×
×
  • Create New...