Is Cinelerra10bit (Cinx) based on 10-bit x264 or 10-bit x265? It is based on x265 BUT there is a enable flag in the build scripts for anyone doing there own build to use x264 instead. Thank you for clarifying and confirming that, which was what I initially thought. The confusion and uncorrected manual resulted in falsely believing that the maintainers of x264 included the possibility of having both 8/10 bit working without having to make a special compile. We were fooled for a month or so and I had updated the manual and did not correct it Yes, I remember that (refer your previous mail 07.06.2018). But as Cinelerra (Cin) then is based on x264, I wonder if the following reference below is something that has been incorporated later in x264 and possibly yet change that "Cin" has the opportunity to work with both 8-bit and 10-bit x264? x264 supports both 8-bit and 10-bit outputs, and you don't have to do anything special. ffmpeg -h encoder=libx264 ...... Previously you had to compile x264 with --bit-depth=10, and then link your ffmpeg to either an 8-bit or 10-bit libx264, but that is now unnecessary. See Unify 8-bit and 10-bit CLI and libraries for more info. https://video.stackexchange.com/questions/13164/encoding-422-in-10-bit-with-... See Unify 8-bit and 10-bit CLI and libraries for more info. https://git.videolan.org/?p=x264.git;a=commit;h=71ed44c7312438fac7c5c5301e45... Very interesting and promising signals regarding better help and documentation, if this succeed to make things easier for new users to start with and next continue with Cinelerra. It is known this has been an Achilles heel and has caused the impression of a steep learning curve. Terje Den 02.01.2019 18:02, skrev Phyllis Smith: Is Cinelerra10bit (Cinx) based on 10-bit x264 or 10-bit x265? It is based on x265 BUT there is a enable flag in the build scripts for anyone doing there own build to use x264 instead. The confusion and uncorrected manual resulted in falsely believing that the maintainers of x264 included the possibility of having both 8/10 bit working without having to make a special compile. We were fooled for a month or so and I had updated the manual and did not correct it GG is doing a Leap15 cinx experiment right now so I can get the wording correct in the manual since we have not re-tested it in quite some time. And I will try to be consistent in the terminology as you suggested too. A single, updated manual for "Cinelerra-GG Infinity" sounds to be to the 'right time', and yes, I will report typos/faults/RFEs on areas I see the demand for more detailed explanations or procedures. In general a 'single manual' needs to fill the demand for a combined "Users Guide" beside a "Reference or Feature Guide", maybe also as a online html and pdf print. And especially the new "gui ease of use" with the new "Cinfinity plugins icon set" compared with the original default icons or KB shortcuts as a reference. Issue #77 in MantisBT is planned to be used to get reviewers help on the manual. Maybe this is a possibility to create a more integrated Help-system for Cinelerra-GG Infinity? I.e a "Help" menu with - link to the online manual - context sensitive Help? - the "About" button Believe it or not we actually have 2 shortcut single letters left in the english alphabet for use on the main window. One of these is "h" and we are saving it for Help ! The other letter is "p" which I think should be saved for "p-hyllis". P.S. gg's experiment was done faster than I could finish this email due to interruptions. With CINX, you can ONLY create 10-bit output when you render. gg/phyllis