Jump to content

Matt Perks

  • Content Count

  • Joined

  • Last visited

About Matt Perks

  • Rank
    New member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am indeed! I meant to thank bloggers (including Andrew specifically) for bringing the issue of overheating up so much. The pressure about the timer nonsense forced Canon to change the way the camera monitors temperatures, which is the reason the mod works at all.
  2. It doesn't work like that - there's no license for you to use the music so you can't legally do it. YouTube just keeps them happy by giving them the ad money, but there's nothing in their terms of service that say that it's ok to use music without a license because they have some kind of agreement with the labels. Just doesn't work like that unfortunately sorry Andrew!
  3. Here's a video demonstrating the problem with LUTs (and yes, it renders them unusable). https://www.youtube.com/watch?v=j6EcowEtA9c
  4. It's not legal, as you're still infringing copyright. They might not 'care' as they'll have the streaming revenue, but still, it's not legal. You probably won't get in much trouble by it, but if you keep at it, depending on how hostile the label is, your account could get copyright strikes. If it as three... then your channel will be banned. Better go with some stock music instead. Lots out there, like artlist, and they've got some good stuff. Hope this helps - sorry the news isn't brighter.
  5. I've been doing more testing and have narrowed it down to problems with DNxHR. When recording in ProRes, any values outside of 16-235 aren't displayed on the Ninja's screen, but are indeed saved in the recording, so behave just like in-camera recordings so no detail is lost as it can all be recovered. When recording in DNxHR however, values outside of 16-235 are lost resulting in heavy clipping. I'm not sure why this is the case - whether it's a bug, or whether DNxHR doesn't actually support 0-255 ranges or something, but they need to provide a fix of some kind, even if that's a 'remap to 16-2
  6. I've tried everything I know of to recover the lost detail but I really think that it's been clipped out of existence. Here's the Ninja file: https://drive.google.com/file/d/1C1NxTfwSi-miqkEt16GLNUYIBdINEGD4/view?usp=sharing The detail lost is what's shown in the picture above, and as you can see the clip is way too contrasty and it's butchered the Fuji's otherwise pleasing colours and as far as I know there's nothing I can do to change that. Hopefully I've just missed something! Take a look at the sample clip above to see if you can recover both the highlights and the shadows so tha
  7. That sounds similar yes, which is a bit concerning as it's unlikely to get a fix! ? They might have been recoverable in that case because the dynamic range was so low in that shot. Unfortunately with mine, they're completely gone. Nothing to recover! Here's a picture, with some levels adjustments to show it up more clearly. Left is the internal camera recording, right is the ninja. So much lost shadow detail!
  8. Howdy! So, I've just received my Ninja V today and there's a big problem... it's clipping the input assuming that it's limited RGB (16-235) rather than full RGB (0-255), and the problem with that is that my XT-2 outputs the latter, so there's some awful butchering of the highlights and shadow areas. Does anyone have any suggestions? The input gamma has only one option: rec.709. I've confirmed this with a laptop also - it just throws away the shadow and highlight details of the image. Not good!
  • Create New...