Forum Replies Created

Page 11 of 37
  • You are wrong.
    Apple is great, Apple is great, Apple is great.

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 19, 2019 at 5:15 pm in reply to: 29 and 59.9 footage

    Did you try to see what happens if you do one or the other?

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 19, 2019 at 9:34 am in reply to: Very strange: clip has 2 video tracks?

    How do the tracks look? Identical?
    It is very well possible the clip has a thumbnail baked in, and that is displayed as a track, but omitted in playback.
    There are two mono audio tracks, but they probably belong to the ‘good’ video.

    You could use FFmpeg to strip the second track, or perhaps turn off one of the tracks in QT7 pro.
    (Or delete it, and do a ‘save as’ to flatten it without the track.)

    If it plays in the viewer, it can be rescued without any quality loss.

    Bouke
    http://www.videotoolshed.com

  • No, I mean, open up your aperature as far as you dare, so you have the highlights a tiny bit clipping or just below.
    Do so on ANY shot you take, and bring it back in Resolve to your liking.

    An 8 bit codec has (in theory) 256 values for each color.
    Now, a typical nice shot of a sunset has red values from 200 in a gradient to 0
    That is just 200 different colors of red. Your image is 1920 pixels wide. So worst case each color is repeated
    1920 / 200 = about 10 times.
    That is noticable. (AKA banding)
    But, since you shoot your nice log, the number of color values are reduced, and poor Resolve has to calculate what ‘should’ be there.
    Then it amplifies the compression artefacts…

    a 10 bits codec can store 4 times more colors. (Each bit extra doubles the amount of values possible to store.)
    Hence you definitely want that for this way of shooting.

    I have no clue how that is called in your cam, or if it is even possible. look it up in the manual.
    (I have had my fair share of footage this way in 8 bits, and I can tell you for sure, it sucks big time.)

    Long story short, shoot both in log and normal, compare, see what you like best.

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 14, 2019 at 10:00 am in reply to: Which bit depth does DaVinci Resolve grade in?

    Try to totallly crash a shot, (crush all blacks, flatten out all hightlights)
    Then add a node, and bring it back. Normally, this would be impossible, but in Resolve this is no problem at all.

    Bouke
    http://www.videotoolshed.com

  • Yes, this is how it is.
    You need to exposure right (meaning, all the way open, no matter what end result you want.)
    And you need a 10 bit codec, or it will definitely suck.

    I totally fail to see why shooting this way is a good idea.

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 10, 2019 at 11:19 am in reply to: Images glitches on Premiere exports

    Your images are very sharp, what you are seeing are the differences in subpixel remapping while scaling.
    First to try is re-do them in After Effects, hope it has a better scaler. (AE is subpixel accurate, but the sharpness might still be an issuse. Motion blur might help a bit, but I’m afraid it’s not good enough in this case.)

    If that does not work also, try a small (gaussian) blur on the image.
    Blur them in PSD first, make some variations, see if that helps.
    Another try is to do a blur on an adjustment layer (so the blur itself does not get scaled) on top of your effect.

    Do note, also keep the original. Stack the original, and do a cross dissolve from original to blurred on the start/stop of the zoom. This way you have a crisp image on still, and less annoying jitter on movement.

    I’m sorry, but you have to do a lot of experimenting / trial and error work. Luckily you have instant feedback in Premiere, so it won’t take you more than an hour or so.

    On a personal note, loose the box on your subtitle. Subs are NOT captions, and the only reason captions have boxes is the state of the technology when they were introduced.
    It looks way better to use a white (well, not top white, some RGB 220 220 220) font with a small black outline.

    Bouke (Who is a subtitle freak.)

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 9, 2019 at 8:37 am in reply to: Premiere importing XML/EDL from Davinci incorrectly

    I can’t help with the actual problem, but you can still use ReCut (available from my site.)

    But, if you have mismatched cams, why not do the job in Resolve itself?

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 7, 2019 at 9:40 am in reply to: CSV with linebreaks for source text

    Ah, good.
    But, out of curiosity, how does the script handles a comma in your regular text, if you have a comma separated input?
    (I would think that could cause mayhem…)

    Bouke
    http://www.videotoolshed.com

  • Bouke Vahl

    January 6, 2019 at 3:19 pm in reply to: Why Video quality on my canon 70d look very bad

    Not sure where you’re from and if the Internet over there is steam powered, but 1080 / 720 isn’t that bandwidth intensive anymore, especially with this kind of content where there is very little motion.
    I don’t think you can do anything else but having your talent use wider felt-tips / whiteboard markers, and write a big bigger on the board.
    Of course upload a high quality version, and do note that not all compression software is the same, eg if you use old Quicktime to make a H264, it may be 5 times bigger than a better quality version from modern encoders.

    (And, it does not look that bad over here, so I would not worry about it.)

    Bouke
    http://www.videotoolshed.com

Page 11 of 37

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy