
KnightsFan
Members-
Posts
1,334 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Everything posted by KnightsFan
-
Testing Danne's new EOS-M ML Build (7/29/2020)
KnightsFan replied to SoFloCineFile's topic in Cameras
I played at 1440p and I have to agree, it's very noisy and not sharp. When you watch the version on YouTube, how does it compare to your H265 intermediates? How about to your original MLV files, if you have a way to play those back? I haven't watch any other EOS M footage so I can't say whether this is typical of that camera, but I checked against the XT-3 footage I'm editing right now (which is on a 1080p timeline) and it's night and day the clarity and noise level--not to force a comparison but just to make sure I wasn't going in without an immediate reference. In any case, you've got some great stuff to film and practice on at that museum! Tinkering with ML was always fun. -
Those new capsules look fairly interesting. It would be neat if Zoom transitioned to a modular recorder system, without compromising quality, durability and form factor. Being able to just add 4 more XLR's with phantom power, or an ambisonic capsule, is actually pretty cool. They're in a position to make a Zoom F1 sequal that is small enough to be a beltpack recorder, has remote triggering from bluetooth, but can also turn into a recorder with 4-5 XLR inputs when needed. That would be great for people at my budget/skill level who need a swiss army knife for lots of different uses. Since their new capsule can do 4 tracks apparently, it would be nice to see some capsules with, say, two XLRs plus stereo mics, though I don't know how many people would ever use those. I wonder if it's bi-directional? Could they make an output module for live mixing? It seems like they've put some effort into improving their OS as well. Touchscreen control is... not ideal, but moving towards a modern UI with more functionality is a good direction. When they say it's app based, I assume there are no 3rd party apps--but it would be REALLY interesting if they could get a Tentacle Sync app.
-
@dgvro Resolve can't use AMD hardware acceleration at all on Windows. It just isn't implemented, according to blackmagic forum posts from 2019. So you're stuck with CPU decoding if you're on a Windows system.
-
The other part of HEVC decoding is that it's not a simple question of whether your GPU supports it. Last year I upgraded my CPU from an i7 4770 to a Ryzen 3600. My GPU remained the same, and yet my HEVC decoding performance in Resolve jumped from barely usable to really smooth. This was editing the same exact project with the same exact files on the same version of Resolve studio. I don't know if it was the CPU, the new motherboard/chipset, whether Resolve just doesn't like 7-year-old systems, or what--but it's certainly false that the GPU is the only factor, even on GPU accelerated performance in Resolve.
-
I think Intel supports 10 bit 4:2:2 decoding, but I have AMD so I'm not sure. @gt3rs was the one who started our attempts at smooth playback with 4:2:2 files, and I'm not sure if they found anything else about CPU decoding. Fwiw, I don't see any options in Resolve for CPU decoding on my Ryzen 3600, so if it has any they aren't implemented in Resolve. Edit: actually, I did try 1Dx3 4:2:2 files on an 8th gen Intel i7 processor. With QuickSync enabled, the files didn't even show up, and with QuickSync disabled they played at ~10fps. So either Intel doesn't support 4:2:2 on that processor, or Resolve doesn't implement it.
-
It is true for Nvidia cards, yes.
-
The pocket is keeping the highlights better, yes. That doesn't necessarily equate to DR because we don't know the distribution, and I do think that the Ursa is better in the underexposure strictly in terms of amount of noise, not that you would use it because the fixed pattern is very unpleasant. But Ursa is also keeping the sharpness in the underexposure just slightly better--though that could be a slightly sharper lens. But of course that's splitting hairs as you wouldn't use either one at that point. If you do any more tests, what I would do is get a gradient of light and ensure that they clip at the same point, and then check the shadows. That would avoid any variables with them distributing DR differently around middle grey, or any discrepancies between what the two cameras use as middle grey to begin with. Maybe I'll do a similar test with my cameras just for fun.
-
Back when I did a ProRes vs H265 comparison, the only person to actually take a guess pointed out that the ProRes version had significant artifacts compared to H265. So in terms of plain quality, H265 can do very well with most scenes. It broke down a little bit more vs. ProRes HQ on a scene with extreme artifacting--even at very high bitrates, H265 couldn't get to ProRes HQ levels, though it did look favorable compared to ProRes 422 to me. Of course, actual camera footage will vary, so looking forward to your tests. Another test of just the codecs can be done on a Z Cam, which shoots 10 bit H265 and and flavor or Prores, internally. While H265 is harder on the PC, I actually have very little trouble editing it. I'm editing 4K IPB Fuji H265 in a project at the moment. I'm even doing motion tracking and VFX in Fusion, directly on the timeline, plus color grading. I'm not really having any issues with a GTX 1080, Ryzen 3600, 32GB ram. It's not buttery smooth, but it's not holding me back at all for the edit or VFX. The color page is very slow if I have clip thumbnails enabled and am using groups, I guess because every change re-renders all the thumbnails for each clip in the group. Seems like a place Blackmagic could optimize Resolve with some simple tweaks. So I just turn off clip thumbnails and then it's fast again. So yeah, while ProRes is easier to work with and definitely has better compatibility when working with others, H265 isn't bad at all.
-
@thebrothersthre3 Thanks for the files. I've played around with them a little bit. It's so close, I can't definitively say one looks to have more DR than the other. I do think that, although the FPN is subjectively displeasing in motion, the actual amount of noise looks slightly less on the Ursa... though it's obviously hard to say. One really interesting thing is just how different the colors are. The Ursa is very magenta. I can definitively say that from these images, I like the P6K version better. Just to go back against the other measurement, C5D puts the P6K at 11.8 in 6k at ISO 400, and the Ursa 4.6K at 12.5 when the 4.6k is downscaled to UHD in ISO 800. That's gotta be really close if you also downscale the P6K to UHD. Also worth noting that they measured at 400 instead of 800. I don't know which way that would change things--you'd expect worse DR in a non-native ISO, but it could also have different noise reduction. So overall I'd caution against saying this disproves the other measurement, but it is evidence against the Ursa having more DR than the P6K at any given setting. The other thing I will say about latitude is that while latitude does not equal DR, its is true that if Camera A has both more over- and under-exposure latitude than Camera B, then Camera A also has more dynamic range (discounting subjective opinions on one having a "nicer" noise pattern).
-
Thanks for the info. I look forward to the DNG's.So you only used one camera setting total, and the only difference between the over- and under-exposure tests is that one has a 300W light and the other does not? Is that correct?
-
@thebrothersthre3 Raw files would be great, along with some information about your test. What ISO? How much over/under are these? What did you use as a base line for "correct" exposure? How are you measuring stops (aperture or shutter speed)? How did you process the images? Did you process the images differently? Because on the under exposure images that the P6K clips more outside the window than the Ursa. Not trying to say you're wrong here, just trying to understand what I'm looking at.
-
I'd love to see tests! So just to clarify, you didn't test them both at native ISO, which I believe is 800 for the Ursa Mini, but 400 for the P6K?
-
You can get a 3rd party cable for stereo XLR on the E2. I have not tried it, but I have heard that there are audio issues such as possible clipping at -3 db or something like that. Definitely something to research first if you need reliable XLRs. V mount batteries are quite easy to attach, though personally I prefer using NP batteries for size and simplicity. I use an old iPhone SE as a monitor, which is charged over the USB cable, so it's still a single battery solution. Can't you keep your right hand on the handle and use your left to press buttons? Or vice versa if you have a left handed grip. But yeah, the menu sucks, and on the original E2 the buttons are... not great. It's certainly not designed for handheld at all. A proper handle would go a long way, particularly one that can navigate the menus. I get the impression that their original design was for people to use the app, which is what I use. So IF your camera is rigged with an iphone, then it has great touchscreen controls. The other thing that is really annoying on the original E2 is the CFast slot is essentially underneath my handle, and is hard to open to begin with. I wrapped a piece of tape around it with a tab to open, so it's not terrible, but the card slot should have been on the left from the beginning (as it is on the new bodies).
-
I've been working on this. It's pretty tough. I have mounted an Oculus controller onto my camera and tried to simply record the movement and rotation. I think that it will take some sitting down and doing some math to figure out the exact X, Y, and Z axes of the controller because it doesn't line up quite right "out of the box". I think those "puck" things from the HTC Vive would be better suited, but the Rift is what I have so I'm trying to get it to work with that. I'm not even sure the tracking is accurate enough anyway. The Rift only samples movement at 30 FPS.
-
There's definitely some hefty CA in the trailer I just watched, example: Speaking of which, that's a pretty awesome shot. I haven't paid any attention to Mulan based on the quality of the other live action remakes, but that is a great shot, both for content and the optical quality. It reminds me of showdown with the Wild Bunch at the end of My Name is Nobody. It also shows the impact that vintage styling can make.
-
I love the light CA from some of my older lenses, sort of a light touch of surrealism in my opinion. Sometimes even video games add CA to make it more artsy, gritty, vintage, visceral or something along those lines. (Personally I don't like it as much in video games, but at least someone thought it was a good idea.)
-
@FranciscoB x264 is a specific set of libraries that encodes h.264 files, it's not an either or. I'm not sure what library Resolve uses under the hood to encode h.264 if you use the internal encoder. You can also use Nvidia's NVENC. To clarify, NVENC and x264 are different algorithms that both end up with an H.264 video. I haven't compared them myself. In the past, I have seen better results from ffmpeg compared to Resolve when exporting to h.264 and h.265. One thing that I have noticed is that Resolve does much better if you give it a quality preset rather than a max bitrate. Use the dropdown instead of a number and you'll have fewer artifacts even at comparable bitrates. Yes, you can still get better quality up upscaling to 4k and uploading that instead of HD--but only if the user watches in 4k. I never watch YouTube in 4k so if I was your target audience then it wouldn't make any difference. My phone doesn't even stream 1080p most of the time, and honestly I watch as much on my phone as a PC.
-
You can read YouTube's upload guidelines here. YouTube reencodes everything to a very low bitrate (~8mbps for HD). So while you do want to maximize the quality that you upload, keep in mind that viewers watching on YouTube will see worse quality than the file you created. So for example, if you are worried about a quality difference between 50 mbps and 25 mbps on your HD file before uploading, well, that's a moot point since the actual stream will be much lower than either of them. I always upload in H.265. I haven't uploaded much to YouTube in the past year or two, but when I did I couldn't see any benefit or downside between H.264, H.265, and DNxHD uploads. So I picked the one that was easiest for me, which is a high quality H.265 file.
-
I use the NX1 with an external monitor all the time and all buttons continue to function. At one time I had a hack installed and didn't have any issues there, I don't remember which one it was and I uninstalled it long ago. Have you tried with other field monitors? TVs or PC monitors? Is the USB actually connected to anything while you're trying this? I previously found issues with HDMI and USB having issues when using both at the same time. I'd try without a USB cable attached, if you haven't already.
-
One option is to use hashing to determine whether a digital file has been altered or not. The one technology I saw about it was that the user is directed to make certain camera movements, which are hashed with the content of the video. That makes it virtually impossible to edit the video without anyone being able to immediately tell it's been altered, since the hash would change. So that technique won't help you immediately determine if a video you see on YouTube is real or not, but it would be possible for the filmmmaker to provide source clips to prove that they are real, if necessary.
-
Roadmaps for Meike S35 and FF cine lenses
KnightsFan replied to photographer-at-large's topic in Cameras
Locking your focus while vlogging can be useful, but I have yet to see anyone vlog with a follow focus. -
I find the F4 relatively easy to use on the go. I think that audio equipment in general has UI/UX issues since the general convention is to use a little knob to twiddle your way through expansive menus. You kinda have to memorize where things are, but it's not worse than other recorders. (I think the DSLR convention of a wheel built on top of 4 directional buttons is simply easier to use). But the main UI of being able to toggle channels on/off with 1 click, adjusting gain directly on a knob, and soloing a channel with 1 click are nice. I like having all the controls on the front panel so that it's easy to see when hanging from a neck strap. The one thing I miss from the DR60 Mk2 is that little Mic/Line/Phantom switch. You have to enter the menu on the F4 to get to that. But you can press a button on the F4 to immediately access a channel's options, so day-to-day I don't have to hunt around. It's things like switching from 48kHz to 96, or changing the routing matrix, that are a pain because I only do them once every few months and forget where the options are. The biggest issue F4 has for me is that battery life is quite bad using 8 AA batteries. I affixed a large 12V battery on top, but it's an ugly, heavy solution. However, most recorders have pretty bad battery life in my experience, especially older ones. The F6 is very attractive to me for the simple reason of having a built in NPF battery sled and (supposedly) really good battery life, along with 32 bit recording of course.
-
Roadmaps for Meike S35 and FF cine lenses
KnightsFan replied to photographer-at-large's topic in Cameras
My EF and F lenses follow me from camera to camera, so it will be a long time before I buy anything other than EF. I'd love to see Rokinon get some competition for affordable EF cine style lenses. It's great that they also have mirrorless mounts as well. Gotta love the #vlogger on Meike's tweet about manual focus cinema lenses though. -
It's definitely worth differentiating opinion vs. fact. But I'll second the opinion in this case: be wary of old pro audio equipment, modern engineering has done marvels at a low price. I tried out an FR2 back when I owned a DR-60D mk2. The FR2 was noisier using the same mic in a sound proofed studio. Granted, @independent 's numbers are for the FR2LE (which is supposed to have better preamps) and the DR-60D (which has worse preamps than the Mk2). also keep in mind that if your problem is too much wind, then you are certainly not going to be hearing the noise floor of the recorder. The difference between self noise in any of those recorders is negligible in any normal outdoor recording. And, to bring it back to the original suggestion, I've had a Zoom F4 for a few years now. It is superior audio quality to either the FR2 or the DR60 Mk2 by a significant margin. Even more importantly, it has better ergonomics than the FR2. The headphone preamp is much cleaner than Tascam's rather terrible one, and the construction is another league from the DR60.