Activity for woodpeko
-
woodpeko modified a comment on discussion Open Discussion
Hello. From that time I tried it. However, it seems that only encoding to MP4 is like 30.1fps. Using Aviutl seems to result in this kind of result. I do not think this kind of thing has happened with x264vfw although the codec is different. Because making and structure are different, we can not simply compare. Is it quite a difficult problem? And seems that v2.8 of x265 was released. Thanks. EDIT: Updated and Changed.
-
Hello. From that time I tried it. However, it seems that only encoding to MP4 is like 30.1fps. Using Aviutl seems to result in this kind of result. I do not think this kind of thing has happened with x264vfw although the codec is different. Because making and structure are different, we can not simply compare. Is it quite a difficult problem? And seems that v2.8 of x265 was released. Thanks. EDIT: Updated and Changed.
-
Hi. Are you planning to release new revision of x264vfw or is there a possibility? If it is Yes you can do it? It seems that x264 r2901 was released. When will new revision of x264vfw release? We are waiting to be released near soon. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary EDIT: Updated and Changed.
-
Hello. From that time I tried it. However, it seems that only encoding to MP4 is like 30.1fps. Using Aviutl seems to result in this kind of result. I do not think this kind of thing has happened with x264vfw although the codec is different. Because making and structure are different, we can not simply compare. Is it quite a difficult problem? And seems that v2.7 of x265 was released. Thanks.
-
Hello. From that time I tried it. However, it seems that only encoding to MP4 is like 30.1fps. Using Aviutl seems to result in this kind of result. I do not think this kind of thing has happened with x264vfw although the codec is different. Because making and structure are different, we can not simply compare. Is it quite a difficult problem? It seems that v2.7 of x265 was released. Thanks.
-
Hi. Are you planning to release new revision of x264vfw or is there a possibility? If it is Yes you can do it? It seems that x264 r2901 was released by videolan. When will new revision of x264vfw release? We are waiting to be released near soon. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary EDIT: Updated and Changed.
-
Hi. Are you planning to release x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2018-01-06 Remove compatibility workarounds commit df90bdd7e931b498ae48f24b51284f62ef31d54a...
-
Hi. Are you planning to build x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2018-01-02 Remove compatibility workarounds commit de58a0decb29250525711bb75d920f3da59ab8d4...
-
Hi. Are you planning to build x264vfw with the latest commit on main or sandbox, or is there a possibility? If it is Yes you can do it? commit is below. x264 Main Development tree: http://git.videolan.org/?p=x264.git;a=summary latest commit: 2017-12-24 Cosmetics commit b00bcafe53a166b63a179a2f41470cd13b59f927 x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-12-24 Remove compatibility workarounds commit 794d351c523393c8de29daed03d63b5f2042c1b5...
-
Hi. nice works thank you. It is a good thing if the problem is fixed. I will test it later when I have time. I think it is a good thing to have a lot of other people test it. I think that it will be easier to find problems because it is various environments. thanks.
-
Hello again. works thank you. It seems that v2.6 of x265 has been released. Here it is. http://x265.readthedocs.io/en/default/releasenotes.html http://msystem.waw.pl/x265/ default: 2.6+22-ff02513 https://bitbucket.org/multicoreware/x265/commits/branch/default stable: 2.6+4-f7498ac https://bitbucket.org/multicoreware/x265/commits/branch/stable There was a problem that it would be like 30.4fps when encoded to MP4 in the current x265vfw, so I think that it is better to fix this. thanks. PS: Depending...
-
Hi. Are you planning to rebuild x264vfw with the latest commit on sandbox, or is there a possibility? If it is Yes you can do it? commit is below. main commit: http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-10-26 Remove compatibility workarounds commit de281381ceed2c9f5e8756aa59349f6af5828e44
-
Hi. Are you planning to rebuild x264vfw with the latest commit on sandbox, or is there a possibility? If it is Yes you can do it? commit is below. http://git.videolan.org/?p=x264.git;a=summary x264 Sandbox Developement tree: http://git.videolan.org/?p=x264/x264-sandbox.git;a=summary latest commit: 2017-10-26 Remove compatibility workarounds commit de281381ceed2c9f5e8756aa59349f6af5828e44
-
Hello again. works thank you. It seems that v2.6 of x265 has been released. Here it is. http://x265.readthedocs.io/en/default/releasenotes.html http://msystem.waw.pl/x265/ default: 2.6+14-f09f3b4 https://bitbucket.org/multicoreware/x265/commits/branch/default stable: 2.6+4-f7498ac https://bitbucket.org/multicoreware/x265/commits/branch/stable There was a problem that it would be like 30.4fps when encoded to MP4 in the current x265vfw, so I think that it is better to fix this. thanks. PS: Depending...
-
Hello again. works thank you. It seems that v2.6 of x265 has been released. Here it is. http://x265.readthedocs.io/en/default/releasenotes.html http://msystem.waw.pl/x265/ default: 2.6+14-f09f3b4 https://bitbucket.org/multicoreware/x265/commits/branch/default stable: 2.6+4-f7498ac https://bitbucket.org/multicoreware/x265/commits/branch/stable There was a problem that it would be like 30.4fps when encoded to MP4 in the current x265vfw, so I think that it is better to fix this. thanks.
-
Hello again. works thank you. It seems that v2.6 of x265 has been released. Here it is. http://x265.readthedocs.io/en/default/releasenotes.html http://msystem.waw.pl/x265/ default: 2.6+14-f09f3b4 https://bitbucket.org/multicoreware/x265/commits/branch/default stable: 2.6+4-f7498ac https://bitbucket.org/multicoreware/x265/commits/branch/stable There was a problem that it would be like 30.4 fps when encoded to MP4 in the current x265 vfw, so I think that it is better to fix this. thanks.
-
I tested this this time as well. And there is a good report. There were also minor problems. Thank you and your efforts so far. Used software: Aviutl 1.00 and VirtualDub 1.10.5 test7 - Incomplete decoding can be seen with only some encodings. (It is the case when encoded in avi, the same as previously reported. Generation was confirmed in 2pass encoding this time as well. Symptoms may be badly vfw encoded. However, the number of frames of the encoded file is the same as the source. They encoded with...
-
I tested this this time as well. And there is a good report. There were also minor problems. Thank you and your efforts so far. Used software: Aviutl 1.00 and VirtualDub 1.10.5 test7 - Incomplete decoding can be seen with only some encodings. (It is the case when encoded in avi, the same as previously reported. Generation was confirmed in 2pass encoding this time as well. Symptoms may be badly vfw encoded. However, the number of frames of the encoded file is the same as the source. They encoded with...
-
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
-
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
-
Thank you for your reply. Indeed it seems that it seems that way. I think that there is no choice but to give up if it is behavior on x264 specifications. There is this in the log of the commit of x264. LZCNT implies SSE2 AVX2 implies BMI2 It seems that these two are involved in my environment. If this is the way it is probably LZCNT is actually used or I think that the same process is being done. And it also becomes as follows. Skip printing LZCNT under CPU capabilities when BMI1 or BMI2 is available,...
-
I tried using this revision, but I have a doubt so I will report it. When using the previous revision 43_2694bm_43159_fix, use of LZCNT and BMI2 was observed when checking with info log. It seems that use of LZCNT and BMI2 can no longer be seen in info log using this revision. Although I do not know if LZCNT and BMI2 were actually running in the previous revision, though. Of course, there was no problem with the previous revision. It becomes as follows. 43_2694bm_43159_fix: MMX2 SSE2Fast SSSE3 SSE4.2...
-
Hi. works thank you. I test this revision and report on some things I found. Used software: Aviutl 1.00 and VirtualDub 1.10.5 test7 - It seems that decode is incomplete. (For example, content display starts from around 38 or 39 frames after encoding. This is with vfw encoding. For file output function encoding this is around 9 or 10 frames. It will open with VirtualDub.) - The number of frames of the encoded file is different from the source. (If it is vfw encoding it seems to have the same number...
-
Hi. works thank you. I test this revision and report on some things I found. Used software: Aviutl 1.00 and VirtualDub 1.10.5 test7 - It seems that decode is incomplete. (For example, content display starts from around 38 or 39 frames after encoding. This is with vfw encoding. For file output function encoding this is around 9 or 10 frames. It will open with VirtualDub.) - The number of frames of the encoded file is different from the source. (If it is vfw encoding it seems to have the same number...
-
Hi. works thank you. I test this revision and report on some things I found. It seems that decode is incomplete. (For example, content display starts from around 38 or 39 frames after encoding. This is with vfw encoding. For file output function encoding this is around 9 or 10 frames. It will open with VirtualDub.) The number of frames of the encoded file is different from the source. (If it is vfw encoding it seems to have the same number of frames as the source. But if it is file output function...
-
Hi. works thank you. I test this revision and report on some things I found. It seems that decode is incomplete. (For example, content display starts from around 30 frames after encoding. It will open with VirtualDub.) 2pass encoding can not be performed normally. An error occurs in the second pass and encoding can not be performed. (I think that the encoding of the first pass has been completed. 1pass encoding can be completed.) I output it to avi with file output function but the size of height...
-
oh! god apps... thank you very much. thank you your works. I will report if there is a problem.
-
thank you great works. i think add support file output function support is very important. If you can do this. -> approaching completion.
-
works thank you. can you add support x265vfw file output function support of avi and mp4 and etc? not vfw file output.
-
x265vfw file output function support
-
When will new revision of x264vfw release? current x264 is revision 2851.
-
When will new revision of x264vfw release? now revision 2851.
1