Shutter encoder windows 101/31/2024 In any case, this is all kind of beside the point. It is most likely showing the general CPU state, which would include applications and processes that are unrelated to Hybrid. I've written applications like this (gui front end to command line tools) and have seen similar behavior on the CPU meters. I seriously doubt that's showing only the CPU usage of the app that's running, especially if this is just a front end to ffmpeg and is calling these other applications in the background. That could be from other tasks Hybrid is running at the same time, or that other unrelated OS-level (or other application) background tasks are doing. ![]() Just because there are multiple CPU bars showing doesn't mean something is multithreaded. And until there's commercial support, this will remain a marginal format that's difficult to deal with.Ĭlick to expand.Granted, perhaps it's different on the mac, somehow? I don't doubt that it's faster than v1, but it appears to still be single threaded. It's post production that's going to drive manufacturers to support a format, not libraries and archives. Which is good on paper, but in fact it's a hugely clunky workflow and I don't see that ever changing because there's really no interest in it on the Post side of things. Basically it's a format that an archive can request that doesn't lock them into anything proprietary. The fact that it's containerized and that you can have per-frame checksums is a plus too.īut it's a completely impractical format in almost every way - there's little to no commercial support for it, it's not really a format you can play back, it's single-threaded so it's slow to encode and decode. They like that it's open source and that it employs lossless compression, though that's probably not very useful with film scans. which is fine, but I mean, i hate ffmpeg.Ĭlick to expand.The main "advantage" i hear from archivists is that it's supposed to be "one format to rule them all" but of course, I would say this is more wishful thinking than anything. I suspect ffmpeg is going to be our best bet here. The deliverables sheet we have for a current client has their ffv1 set up differently than the master scan, so I'm trying to find a way to avoid having to make multiple mezzanine files (some RGB, some YUV, etc), and instead doing those conversions in the ffv1 encoder. Are there any other tools out there that do export ffv1 (other than ffmpeg) and allow you to control things like color subsampling, whether it's RGB or yuv, etc. In any case, I know Premiere Pro can do ffv1 now, but we don't generally use it in house. But I think that's a problem with ffv1 not being multithreaded, and not ffmpeg (or maybe ffmpeg is the only encoder out there, and is not multithreaded for this codec). Last time I played with ffv1 it was just with ffmpeg and was painfully slow. ![]() But more archival clients are asking for it now despite the fact that almost no commercial software tools support it. We have done some experimentation with this format and determined it's a waste of time.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |