пт, 8 нояб. 2024 г., 22:33 Terje J. Hanssen <[email protected]>:
> > > > Den 08.11.2024 20:15, skrev Andrew Randrianasulu: > > > > пт, 8 нояб. 2024 г., 22:04 Terje J. Hanssen <[email protected]>: > >> >> >> >> Den 08.11.2024 19:01, skrev Andrew Randrianasulu: >> >> >> >> пт, 8 нояб. 2024 г., 18:56 Terje J. Hanssen via Cin < >> [email protected]>: >> >>> During render testing to and fro, I have had a suspect that now and then >>> the content of ffmpeg compression type has changed or could not be >>> picked up again. >>> But I have thought it was me that had confused or forgot something. Or >>> may this occur by other reasons? >>> >>> Seemingly this happened recently during render switching between >>> hevc_vaapi,mp4 and hevc_qsv.mp4 . >>> hevc_qsv.mp4 has several more pixel options than hevc_vaapi.mp4 which >>> has only the single "vaapi" option. >>> And in one occasion I got more pixel options for hevc_vaapi.mp4(?) - or >>> was it still on hevc_qsv,mp4? >>> >>> So to find out, I have tried to edit the hevc_vaapi.mp4 file, but have >>> not got the edited content loaded in the video wrench compression window. >>> So I wonder where is the preset file used by Cingg located? >>> >>> I have >>> >>> # ls -l /Cin >>> lrwxrwxrwx 1 root root 29 Oct 22 20:23 /Cin -> >>> /home/cinelerra/cinelerra-5.1 >>> >>> and the hevc_vaapi.mp4 preset file with the same content located in both >>> >>> /Cin/bin/ffmpeg/video >>> /Cin/ffmpeg/video >>> >>> But the edited content isn't visible in Cingg? >>> >> >> I think cingg (or OS?) caches things >> >> I usually switch to another profile from lisr and back to see my changes. >> >> >> What is "lisr" ? >> > > > list - typo! > > >> You are right ;) >> >> I tried again now, and it isn't enough to quit and cold start Cingg >> again. >> For better or for worse Cingg seemingly remember the last used profile. >> I had to switch one (or two times) to another profile before the profile >> content was updated. >> >> But why is there two similar locations for profiles and which one is used >> by Cingg? >> >> /Cin/bin/ffmpeg/video >> /Cin/ffmpeg/video >> >> > one in ffmpeg/video is distributed file > > > So when installed from downloaded Appimage or rpm, ffmpeg/video is used > no .... appimage is compressed directory, with its own copy of ffmpeg directory. (and it not easy to change those, but you can unpack appimage and edit/run cingg from unpacked directory) rpm installs into /usr so in this case profiles live in /usr/share/cin/ffmpeg/ > one in bin/ffmpeg/video installed by make install command. This one > actually looked up and loaded (because source part of cinelerra usually not > present on user machine) > > And Cingg locally built, use bin/ffmpeg/video > and bin/ffmpeg/audio .... > > >> Another thing, though off-topic here: the file menu has many useful >> shortcuts like Shift-R for rendering, but none for Load recent file ;) >> > > one of many? there might be whole list of them ... > > > Shift+o is freely available for Load recent ;) > may be "Load most recent"? Because we load one file, and this probably should be most recent in Recent files submenu ... I'll look into it. > > you can run bin/cin mediafile.m2ts directly from console. > > Thanks for that tip. > However during repeated testing I often use warm Load recent file after > finishing one rendering before to the next, without closing Cingg. > > > > > >> >> >> >> . >> >> >> >> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Cin mailing list >>> [email protected] >>> https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> >> >> >
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
