Beiträge von kalamazandy

    Thank you. That worked, sort of. Voukoder still won't let me export video with my graphics card if the footage is wider than 4096. That seems to be true in ffmpeg for h.264, but not for h.265 with hevc_nvenc

    But also, it didn't fix the issue I'm having with Premiere. But this is likely an ffmpeg question at this point.

    Something about the export, premiere just doesn't like. It Works, but it doesn't scrub smoothly. I'll let you know if I figure that one out eventually. With XAVC S-I becoming a more popular edit format, I think we'll see more and more professionals preferring it since it Significantly reduces our storage issues.

    Well, I've had to move back to just regular media encoder for now, but I'd still like to figure this out. AME was rendering the 5:30 footage in about 22 minutes, where voukoder was taking much longer.

    I've got timelapse footage that is 5568x4176. Already, ffmpeg won't let you use Cuda for that, so neither will Voukoder right? But my graphics card, nvidia 3080 Ti, can output and encode at least 6k. But maybe not in h.264.

    I ended up using AME, using Main 10, High Tier, and a key frame distance of 1, H.265. After importing that footage into a NLE, it feels just as smooth as ProRes. I thought H.265 was more demanding, so I was surprised that footage was so smooth.

    That being said, even with the "Render at Maximum Depth" checkbox, the footage is limited to 4.2.0, but the original is 4.2.2

    For Voukoder, I looked at all of the H.264 codecs, but found that the (x264) codec had the most options. I know many options only show up if you have another option selected, but I hadn't been able to get a key frame interval to appear.

    But ideally, I'd want to use GPU to render, so now I'm looking at HEVC (NVIDIA NVENC).

    From seeing what is available in Voukoder 12.2, if I want YUV422, I'll actually have to use YUV444. Is that correct?

    But I still can't figure out how to get all i-frames. I've done that in ffmpeg, using H.265, which doesn't limit me to 4096 width, but I have to use yuv444 there as well. But also, there's something else to making the video smooth in Premiere because I Did get all i-frames, and the correct bit depth, and I'm not losing to yuv420, but it's still not smooth when moving the playhead around, and that's the goal...to keep a decent the color info in tact, and just control the compression quality and resolution to control the size. This way, it would work really well for ProRes alternatives in terms of Actual editability, and also for scrubbing with smaller proxies.

    I'm not a huge fan of the idea of costs based on total employees of a company, or even total revenue, because that creates huge limitations for people who work at a large place who's primary business isn't related to the software they are doing. For instance, the company I work for is a manufacturing company. I do 3D animations, renderings, and videos. There are two of us. The revenue from that barely covers our salaries, and some years not. So asking for software outside of what we usually use can be difficult. And if it's something like this, that's only suggested to give money, not going to happen.

    But what you Could do is say that any commercial use Must used a paid license. And then give guidelines for how much you have to pay, but not actually tie that to what is mentioned in the paid license. So if someone pays $50 for it, and it was recommended to pay $300, then legally they wouldn't have reprocussions or anything, but it would read ambiguous enough that they would likely Try to get the $300 for you.

    If the licensing said I Must pay in order to use it commercially, then I would say, "hey, I'm using an unlicensed version of this software and it's making projects 20 minutes faster. It costs $100 per year." Then it's likely I could get that sent. But if it isn't required, the best I've done is just send developers like you $5 here and there if I happen to have some money in my Paypal account personally. Not sure my wife would be too keen on me sending folks money just to be nice, so I do it that way. I mean, $5 is just a beer.

    Anyway, that's my thought on it. And assuming I can get it to work well (having some troubles so far but only Just started) then I'll definitely send some beers as I get some paypal funds.

    The Sony a7siii uses the "XAVC I-S" format, which is just an h.264 intra format with their own special XAVC name, from what I understand. It's a great balance of quality and editability while keeping file sizes Much smaller than ProRes.

    This is what the video portion of the format looks like with ffprobe.

    Stream #0:0[0x1](und): Video: h264 (High 4:2:2 Intra) (avc1 / 0x31637661), yuv422p10le(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 229419 kb/s, 23.98 fps, 23.98 tbr, 24k tbn (default)

    Metadata:

    creation_time : 2023-02-09T20:24:19.000000Z

    handler_name : Video Media Handler

    vendor_id : [0][0][0][0]

    encoder : AVC Coding

    Ideally, I'd like to render things fairly quickly. The camera is obviously doing this in real-time. Of course, it's also doing this using 230MB/s. I assume I could achieve something a Bit smaller if it doesn't have to encode in real-time.

    Many of these settings are a bit daunting to me. From my understanding, intra formats are only i-frames?

    I see the 444 general purpose 10bit prores alternative, but there are quite a few settings being used that I was surprised to see in use like Noise Reduction. But I don't know, maybe ProRes Does that?

    So how do I get Intra frame? Can I just change the I-P ratio to 1.0? Is that forcing only i-frames?

    If I'm being dumb, no need to point that out. I'm aware :rolleyes:

    I'm just trying to store some time lapse image sequences into a single format to save a bit of space, but keep editing nice and easy. The images are 37.7GB. ProRes LT is 37.7GB. I'd Like to get that between 4-16GB and still have something that I can scrub the timeline in Premiere without hanging. Also, the frames are 5568x4176. ProRes and the images scrub fine, like butter. The computer is sufficient. I often edit RED 8k raw footage, just because that's what I'm given (we don't have that camera). So the sponginess from the footage is definitely coming from the compression format. That sony footage slides around incredibly smooth as well, and from what I'm reading, Intra formats are the way to go if you want to edit h.264 footage.

    Ideally, I'd use CUDA to render also. It seems to be Quite a bit faster. But it also looks to be much more limited in the options available.