x266 VVC Encoder

[rwill]

Originally Posted by kurkosdr

You could've said "this person made a mistake". People make honest mistakes, you know. Nobody needs a jerk who treats another person's mistake as an opportunity to be a rude twat.

I see this somewhat differently.

In my opinion, if there is something we do not need, its people that pretend they contribute facts but have themself no idea what they are talking/writing about and are thus generating unfounded rumors. And Indeed when I look around the Internet there are a lot of these people. There are people lurking this forum looking for information regarding video compression. They shouldn't have to fact check everything that is stated here - but with the amount of half-knowledged people posting here I guess they have to anyway. Here I would like to take moment to applaud oibaf for asking for a source for that statement from you above. There is also a difference between a mistake and a made up fact. Some would even argue that making up facts is a form of lying.

Now regarding calling a person out I think it does not matter how it is done foremost, but that it is done. There is nothing worse than leaving misinformation uncontested. How this is done is secondary and comes down to personal preference. I, for example, am a fanboy of clear and direct communication. I even have problems understanding what someone wants when sugar coating and gift wrapping is applied to objection.

I am sorry that you are upset about the way I brushed your statement - that Google and Mozilla don't want EVC because of EVCs Design and that it is possible to decode a Main Profile stream with a Baseline decoder - off, but that you then quote Wikipedia, come to the false conclusions based on that quote and then more or less admit that you have no knowledge about the matter at all is pretty disappointing regarding further discussion.

I am somewhat at a loss.

[kurkosdr]

Originally Posted by rwill

Now regarding calling a person out I think it does not matter how it is done foremost, but that it is done. There is nothing worse than leaving misinformation uncontested. How this is done is secondary and comes down to personal preference. I, for example, am a fanboy of clear and direct communication. I even have problems understanding what someone wants when sugar coating and gift wrapping is applied to objection.

Nobody asked you to "sugarcoat" anything. You can be clear and direct and not be a rude twat at the same time. If you had said "made it up" instead of "pulled that one out of his rear" I wouldn't mind. Basic politeness should be a given and shouldn't take any effort on your part to achieve it.

This is more true in fuzzy subjects. For example, care to explain what do you mean by "decode"? Can an EVC Baseline decoder decode EVC Main in any capacity? Even with artifacts and dropped frames and such? Because that's "decodable". Also, that's what the whole "individually switchable coding tools" is supposed to mean, that you can skip stuff and still be able to decode the bitstream to some capacity. If ISO redefined the term you can see how it can be confusing.

[rwill]

Originally Posted by kurkosdr

This is more true in fuzzy subjects. For example, care to explain what do you mean by "decode"? Can an EVC Baseline decoder decode EVC Main in any capacity? Even with artifacts and dropped frames and such? Because that's "decodable". Also, that's what the whole "individually switchable coding tools" is supposed to mean, that you can skip stuff and still be able to decode the bitstream to some capacity. If ISO redefined the term you can see how it can be confusing.

This is getting better and better with each post. Have a nice day.

[kurkosdr]

Originally Posted by rwill

This is getting better and better with each post. Have a nice day.

Look man, if you are trying to pull of the "grumpy video engineer" vibe, let me tell you it's not working. You just come off as rude.

Anyway, I'll ask someone else in some other thread what that "individually switchable coding tools" thing actually means. We are off-topic anyway.

[ksec]

Any news on x266?

[birdie]

Originally Posted by ksec

Any news on x266?

Nothing. It's extremely delayed.

[FranceBB]

Nothing from my side either... One of my colleagues even tagged the actual guys working on it on a post on LinkedIn but they never replied...

[LigH]

No, this is the wrong thread. The x266 VVC encoder will be a specific encoder, and any other encoder is not the topic here. A general thread for all VVC development would be over here.
In your case, even creating a new thread would be suitable, as I believe you want to discuss an issue specific to this encoder you are using.

Regarding double backslashes: This may happen in programming languages like Python because a backslash is both a path separator in Windows and an escape character for special characters (C printf).

[TDS]

Originally Posted by LigH

No, this is the wrong thread. The x266 VVC encoder will be a specific encoder, and any other encoder is not the topic here. A general thread for all VVC development would be over here.
In your case, even creating a new thread would be suitable, as I believe you want to discuss an issue specific to this encoder you are using.

Regarding double backslashes: This may happen in programming languages like Python because a backslash is both a path separator in Windows and an escape character for special characters (C printf).

OK, thanks LigH, I will post it there, and see what happens, if that fails then I might consider starting a specific thread.

But the double backslash, would that be an error in how the app was written, or Windows...or even the version of Python.

Are there any usable VCC encoder GUI's available, yet ??

I will delete the below post.

[LigH]

The problem is not the double backslash, but rather that the converter expects a JPEG file in the Windows\system32 directory. No files should be created there by any application. It might miss a proper path to the temp.jpg file and look in default directories alternatively because it did not find it where it should have looked instead, which might be okay for required DLLs but not for data files.

Not many VVC encoders exist yet. Most are still in a testing phase and not well optimized. So there is not much incentive yet in creating a GUI for an encoder which may change rather much in the future. But searching Google for "VVC encoder GUI", I did find a few projects. And I would recommend to search the VideoHelp software archive for "VVC" too, now and then, pretty sure new ones will appear there sooner or later.

[birdie]

All GUI encoding applications suck by definition. If the OP is really interested in video encoding, they must learn to use console. It's not so difficult, children at the age of 9 do it in a few days.

[benwaggoner]

Originally Posted by birdie

All GUI encoding applications suck by definition. If the OP is really interested in video encoding, they must learn to use console. It's not so difficult, children at the age of 9 do it in a few days.

That is probably one of the biggest changes over my career. From 1995-2010 or so, the GUI tools offered as much or more control as command line. The decline of the workstation software market and the transition to cloud-based adaptive streaming really hurt us there. The last commercial GUI tool that offered pretty much complete parameter access while offering the kind of live preview and parameter rationalization features only GUI can do well was Expression Encoder.

One could do a lot with a commercial-grade GUI to the various open and closed source libraries out there with say $5M of developer, product, UX design, and test resources. But who would collectively spend >>$5M on such a product anymore?

I tried to kick off an effort to do something like this back in 2002-2003, but my second kid was born and spending 80 hours a week to roll the dice on a startup didn't seem like a wise or practical option.