вт, 5 нояб. 2024 г., 18:16 Terje J. Hanssen <[email protected]>:
> Continued and extracted from previous threads_ > https://lists.cinelerra-gg.org/pipermail/cin/2024-October/008967.html > > Den 27.10.2024 21:11, skrev Terje J. Hanssen: > > ........snip > > For me it looks like nothing has changed: > > localhost:/Cin # git am 0001-Experimental-try-10bit-vaapi-encoding.patch > fatal: previous rebase directory .git/rebase-apply still exists but mbox > given. > > > remove it again? > > >> By the way,testing >> >> bin/cin >> compression: hevc_vaapi.mp4 >> Pixels: vaapi (no other options) >> cin_hw_dev=vaapi >> >> Renders >> >> Color space : YUV >> Chroma subsampling : 4:2:0 >> Bit depth : 8 bits >> >> >> The same with >> CIN_10BIT_ENC=1 bin/cin >> > > > yeah, it does not exist in normal cin, only after you add patch. > > > may be just take a break from all this, I do not think we will solve this > problem in few remaining days until end of October. So ... do not rush > > Ok for me. > > > Den 04.11.2024 21:49, skrev Andrew Randrianasulu: > > > Terje, I think if you are ok with this idea we can return to testing > 10bit-vaapi patch ... > Hopefully in its final form it will just allow same format= string in > encoding profiles as supported by per-file decoding opts files now ,,, > > I'm not sure I understood the last line yet, but I should be ready to > continue vaapi-testing to-morrow. > > ==================== > > Yeah, here we are. > The problem as I understood lastly, was to apply the > 10bit-vaapi-encoding.patch? > yes ... basically git's internal help messages usually helpful, so try to follow them? > > > > > > > >
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
