On Saturday, June 19, 2021, Phyllis Smith via Cin < [email protected]> wrote:
> Andrew / Andrea, > > Either this computer is crazy or I am. > Using "Proxy" at 1/2 with format set to 72 or 144, the proxy file is > created for me using mpeg. > Even though there is an error message in the terminal window, it still > worked. > Does this work for you also? > > No, it fails reliably for me at 144 fps media.. (no proxy file appear on disk or in Resources/proxies window). Be sure to delete *proxy*.mpeg from previous run? > > > I am still hesitant to change the default from mpeg to mov, but it may > be wise to do so. > > On Mon, Jun 14, 2021 at 11:36 AM Andrew Randrianasulu via Cin < > [email protected]> wrote: > >> Hm, I think I added few more framerates, still can't say why >> ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. / >> >> I also changed default proxy codec to mov (mpeg4/xvid) due to this - >> while my real 25 fps clip does not hit this limitation if i just change >> project settings to 144 fps... >> >> I returned some logic in ffmpeg.C patch back to initial state, because I >> still do not understand how this homebrew conversion/check work.. :/ >> >> Will post updated patch in its own thread >> >> On Monday, June 14, 2021, Andrew Randrianasulu <[email protected]> >> wrote: >> >>> Because typing from virtual kbd is hard and i have bad nemory.. >> >> -- >> 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
