search for: th_encode_ctl

...st the ones that I could take my time to dissecate). I found that the tables are listed as TH_VP31_HUFF_CODES in the file huffenc.c. I tried to investigate a little bit more to see who was setting the bitstream to those tables, but I ended in the fact that this is dependent whether the function th_encode_ctl is called with TH_ENCCTL_SET_HUFFMAN_CODES or TH_ENCCTL_SET_VP3_COMPATIBLE, but I could figure myself who is calling it using what parameter. Is that true that libtheora will always set the huffman codes to the same ones? Isn't this approach a little bit inefficient since the distribution o...

Hi, I recently had to encode few hours of desktop stream with Theora and I noticed it used only one core for encoding. Was I missing something? I did not find any "thread" options. As I dig, I found there was a multithread patch back in 2007, and some ffmpeg2theora-multithread commits, but it looks like all this was dropped. Am I right? If the multithreading encoding was dropped out,

...finished so that it can start its motion search. This is generally much more effective than threading within a frame, but a) requires additional delay (the API supports this in theory, but software using that API might not expect it, so it would have to be enabled manually through some sort of th_encode_ctl call) and b) requires changes to the rate control to deal with the fact that statistics from the previous frame are not immediately available. b) was the real blocker here. In every encoder I know of (for any format), the second approach is much more effective than the first.

...n daylight scenes, have no noticeable artifacts at all. But it seems that red surfaces are too much compressed; blocking artifacts are clearly visible on them. Also, white people have slightly smeared faces, especially in scenes with low motion. I guess I could pass a custom quantization matrix to th_encode_ctl<file:///home/wojownik/Pulpit/libtheora-1.1.1/doc/libtheora/html/group__encfuncs.html#g3a427f6514dfdc01ea72172c469d51d9>() but I got no idea how to affect only the red plane while leaving the rest of encoding as it is. So please tell me how to deal with it. -------------- next part -----------...

...t it can start its motion search. This > is generally much more effective than threading within a frame, but a) > requires additional delay (the API supports this in theory, but software > using that API might not expect it, so it would have to be enabled manually > through some sort of th_encode_ctl call) and b) requires changes to the > rate control to deal with the fact that statistics from the previous frame > are not immediately available. b) was the real blocker here. > > I have read Theora Specification (from March 2011) and I have some more ideas. 1. Each thread deals with...