Jump to content

ajay

Members
  • Content Count

    262
  • Joined

  • Last visited

Everything posted by ajay

  1. I've never understood Canon's logic. I once owned the 1DX2 and they never put Clog of any kind on that camera...their flagship camera. They did put it on the 5D Mark IV, but never on the 1DX2. That's about the time I switched to Sony and have been with Sony ever since. I had plans to switch back to Canon (since I still own expensive Canon lenses) with the R5 but what kept me from switching were record limits, overheating and the hard to edit codecs. I spend too much time already putting videos together and then to add transcoding to the workflow was just too much for me. I was hoping the
  2. Being 4:2:2 h.265, I assume that the new codecs are still a PITA to edit? Still need to transcode or use proxies?
  3. I assume these lighter codecs for 4k still are 4:2:2 and not 4:2:0? I was hoping the 1.3 firmware would give 4:2:0 as an option. I prefer 4:2:0 as it is much easier to edit. Especially interested in this for 4k 120p.
  4. ajay

    Sony A7S III

    The "gyro magic" is nice but it requires added steps, crops in quite a bit and makes my face fatter. I might use it occasionally.
  5. ajay

    Sony A7S III

    Can Catalyst Browse be used as a transcoder for ProRes Raw? This might be a solution for those using Davinci Resolve. Can someone try that has the Ninja? Thanks!
  6. I think it might now be the other way around.
  7. This has been a complaint with Resolve for two years now. I've given up hope. I will say however that Atomos is kicking butt with so many new cameras using their product that maybe it will force them to finally include it.
  8. I have the Sony 20mm 1.8 and I LOVE this lens. It's about the right focal length for vlogging and light weight and SHARP! I can't think of one negative with this lens.
  9. Yes, A7SIII. I'll do some checking on that as well. Thank you.
  10. I understand about the competition between the two companies. I'm not holding my breath for Resolve to accept the format. What I'm looking for is some kind of workflow and tool to convert ProRes Raw to something else that is lossless or close to it that Resolve can work with. I need a method and some kind of conversion software.
  11. Since more and more cameras are now using the Atomos Ninja V to record ProRes Raw I am curious as to what is the best way to bring the footage into Davinci Resolve since it does not natively edit Pro Res Raw. How painful or painless of a process is it? I really don't want to switch NLE's. I've put way too many man hours into learning Resolve and like what I've got. Thanks for any input.
  12. ajay

    Sony A7S III

    Here's an example of what's happening at higher ISO's. The ISO threshold for the star-eating NR happens at different levels based on the picture profile. For S-Log2 it's between 80,000 and 102,400.
  13. ajay

    Sony A7S III

    I think you should be okay with stills. It's the video side that eats stars. There could also be some NR going on with raw stills but it's looks really good with time exposures and time lapses should look outstanding as well. Attached is a shot I took the other night with the Sony 20mm 1.8. It's a 10 sec exposure at ISO 3,200. You should be able to test the "star eating feature" even with skies that aren't the best. As long as the stars look sharp, the dimmer ones disappear. That would really be helpful if you could determine if recording externally will resolve this. Thanks!
  14. ajay

    Sony A7S III

    That would be great if you could give it a try. The stars have to be in focus for them to disappear @ ISO 102,400 in Slog 2. Hopefully the weather will cooperate. Yet another hurricane in the Gulf! Crazy. Thanks!
  15. ajay

    Sony A7S III

    Anyone with the A7SIII and a Ninja want to do a test for me? I have the A7SIII and I'm having difficulties with the camera shooting the night sky. It appears that at certain ISO levels, it eats stars. They will disappear from view. For example using pp7 (Slog2) between ISO 80,000 and 102,400 it appears that some NR kicks in and wipes out a bunch of stars from the night sky. I'd be curious to know if recording raw externally will prevent this from occurring. I might invest in a Ninja if this works. I just hate to order it and then find out it still looks like crap. It's a real shame s
  16. I also took ownership of the A7SIII last week. A few minor inconveniences but for the most part a solid camera. Here's a few things I have found on the negative side of things: No Clear Image Zoom in 120p, all other frame rates it works. No animal eye detect in video mode, only in stills. Human eye detect does work in video and stills mode. In video mode, tracking only works by using touch on the display to activate. No way to assign a button to start tracking when using the viewfinder. Strange and frustrating if you plan to use the EVF instead of the display. Another
  17. No EVF? I guess I could rig it with an external EVF but then it's even bigger and clunkier. Doing primarily wildlife work, I use EVF's most of the time. I think I'll pass.
  18. Not at present. 4k 60p is the max. There's been rumors that maybe Atomos may build an adapter/interface/modual for the V that allow this but at present the max you can record is 60p.
  19. I am just as sad. Did the same thing and I'm also a PRO Support member. Let's hope they get more than one or I'll have to fight you for it!
  20. I wonder if All-I is really better for most video recording? Will you be able to tell video quality wise? I can see using it if you are grabbing frame grabs and converting them into images, but otherwise I have never seen a real difference between All-I and long-gop. I guess easier editing too?
  21. Heat dissipation. Heat-sinked sensor probably. Same as all other cinema cameras that won't overheat.
  22. When I mean viable, I mean in a real-world professional use setting. I just couldn't phantom a wedding videographer, preformatting their chips in FAT32 using Linux or some 3rd party software, then record x-amount of footage, then making sure they record enough extra footage so that what they want to keep makes it to a recorded block of data before pulling the battery. That's not viable IMHO. And for myself personally, I do mostly wildlife shooting and use 4k120P quite often. I also leave cameras running to catch a particular moment when the subject does something of interest. But, that is
  23. So getting back to the camera...I don't think there is any viable workaround and Canon's not going to give you much. I stated earlier today, I've given up hope to make this into a decent video camera. Here's why: Pulling the battery, segmenting clips using FAT32 is useful for confirming that the camera really can work for extended periods w/o overheating but it's not a viable workaround. Doesn't seem to work with CFast either. Magic Lantern - Canon has changed things up making it more difficult to boot the added firmware, let alone decode. Probably not impossible, but a lot of wo
  24. Ummm... Although I do like Chris and Jordan, their very first review DID NOT mention overheating at all. I reached out to Jordan about this and he stated that they hadn't encountered the overheating during their initial testing and stated they would do a more thorough test of the camera once they had a production unit. This was on July 10th that I wrote to him. (The video from Chris and Jordon on July 9th about the camera did not mention overheating.)
×
×
  • Create New...