WebP is pretty much equal to JPEGs via jpegli (for lossy compression). AVIF is better than WebP and jpegli JPEGs for lossy compression and supported pretty much everywhere now. AVIF is worse than WebP for lossless compression.
jpegli JPEGs will convert to lossy JPEG XL without generation loss when JPEG XL is more well supported.
IANAL, but that's not quite true right? As per your own citation, återgivningsrätten gives the right to use any piece of art (not in digital form) in conjunction with a piece of critical text.
In my experience, what you call vision-based systems don't even come close to Gyroflow. After I started using Gyroflow I haven't touched the Ronin gimbal many times.
In the guide videos they show you just have to sync it up by pressing the record button and end record button on both the gyroscope and the camera at the same time and this is apparently enough to calculate the time difference between the two clocks.
I think mikae1 refers to the lens/sensor stabilization, as it can be problematic if you combine it with other stabilization systems. My camera already embeds gyro information automatically in the video files without intervention (I didn't even know about it).
I use this for near 100% of my video projects at work (with Sony cameras) and it's absolutely amazing. Sony is not exactly class leading when it comes to stabilization (like Panasonic). There's a Premiere and Resolve plugin-in these days.
Fast guide:
* Be sure to turn off any in camera stabilization in Sony cameras.
* Be sure to take the added crop into account when composing.
* The faster shutter speed, the better. Forget about 1/50 for 25p. There will be the most horrible artifacts. For 25p, use 1/100 or preferably use 1/200. For 50p, use 1/200 or preferably 1/400 etc.
Normally you double the shutter speed compared to the frame rate to include a motion blur that looks good. But if you then apply stabilisation post processing, you end up with a shot that has motion blur yet isn’t moving. So you want to set a very fast shutter speed, and then you might introduce fake motion blur in post processing later that matches the movement of the stabilised video.
Interesting—and makes sense. (Perhaps motion blue becomes a post-process as well then, ha ha.)
Kind of a tangent: One of the remarkable things to me about the "Dykstra flex" cameras developed for Star Wars was that the dolly/stepper-motors moved the camera while the shutter was open giving those fly-by shots full motion blur. Freeze any frame where there is a space battle and it is obvious.
That small detail was not small at all in selling the effects of the film.
But one of the effects guys joked that some team had borrowed the camera for some effects they were doing for a TV show or film—and they used Dykstra-flex in sort of a "stop motion" manner. He was dumbfounded why someone would move the camera, pause to expose a frame, move again to the next location, pause to expose. Just walking away, leaving motion-blur on the table…
This is one of those things that pops up on fixed aperture cameras where the only way to control the exposure is with shutter speed. We used this when using GoPros in the early days of live action VR. We'd also run at 60fps. Any kind of motion blur would just become problematic when trying to stitch the footage together especially since the cameras were catching objects in different parts of the wide angle lenses.
ND filers slow down the shutter speed which will only increase the motion blur. When shooting in the sunny outdoors, you're going to be using the lowest ISO. The only thing left to control the exposure is the shutter speed. So with a fast shutter and 60fps also decreasing the exposure time the motion blur is going to be reduced as much as one can get.
If you're on the lowest iso you could use an ND filter and bump the ISO a little higher giving some room to move up and down the ISO values to match the conditions while keeping the shutter speed fixed. That's kind of the primary function of an ND filter.
For video ideally you want both the shutter speed and aperture fixed since having the depth of field fluctuate in the video isn't ideal either.
Sounds like someone that is used to running a single camera looking in a specific direction. Try running 6 cameras with one pointing in each direction so that every thing is seen. That's a small rig. Do the same thing 22 cameras running at the same time to make one image. You'll be just fine with allowing the camera to adjust the ISO for you.
I once thought similarly to you are thinking now. I quickly gave that up for the specific type of shooting discussed. You quickly realize that the software in post for stitching is really good at what it does.
Yes. It's confusing, which is why this is often discussed in terms of shutter angle, which makes this a litter easier to understand: https://www.youtube.com/watch?v=ehpdzt0JHUc
>> This project requires a special entitlement from Apple. I’ve requested it, and heard they may be open to granting it, but I have not yet heard back, and I’m told that the wait time could be months.
> I have been bothering the VM team for years for VM GPU pass through.
Good luck. I'm sure they're keen on giving people access to this so that people can spend their money on NVIDIA GPUs instead of buying more expensive Macs. :)
Would of course be awesome, but I'd be very surprised if it happened.
There isn't a more expensive Mac option to buy if what you're after is a gaming GPU. It's more likely that the VM team sees this as a very low benefit ticket to pursue given the tiny segment of Mac gamers hoping to improve their options with a Linux VM for gaming.
(Meanwhile, I'm recompiling Wine to see if I can patch it to address an issue that was hotfixed in Proton two weeks ago but isn't in a CrossOver build yet, so yeah, there's maybe some arguments to be made here that I'd be a potential beneficiary. If I weren't too cheap to spring for an eGPU in today's market, anyway.)
The entitlement in question is the standard `com.apple.developer.driverkit.transport.pci` [0], required for anything that touches the PCIe bus [1]. Apple is generally restrictive with how much third-party applications can do on machines with SIP/"full security", so I'm not exactly surprised. It's not an Apple-private entitlement, however.
The VFIO-style driver made by the author of this also appears generic enough to support all kinds of PCIe, not just GPUs. Apple might find a way to weasel out of this ("hey, this is for hardware companies and you don't seem to be affiliated with one", "your driver requests too broad access", etc.) if there really is a conflict of interest, but so far, there's a chance it will just get rubber-stamped.
I can see them rejecting it for legitimate reasons, though, at least as far as "legitimate" with Apple goes. This driver is essentially a thin layer over PCIDriverKit, exposing all functionality that's supposed to be behind the entitlement to arbitrary applications, in similar fashion to WinRing0. They probably didn't come up with all this bureaucracy only to sign something like that in the end. We'll see what happens.
Microsoft Design also released 4K renders of nostalgic wallpapers (including bliss) a few years ago. I can't find the original link but here's the reddit post with the pictures.
I like kde connect, but find it randomly breaks every month or so and for the life of me cannot figure out why. A week or so later it starts working again.
reply