Documentation/manual questions
Hi! I looked into pdf WIP document Andrea posted few days ago: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0 on page 315 I can see reference to configure switch --with-findobject, but as far as I can see this switch was removed in latest git code? at p. 390 1 mov prores 2 preset medium 3 pix_fmt yuv422p10le shouldn't be pix_fmt changed to cin_pix_fmt, according to our recent discussion with Phyllis?
Andrew:
on page 315 I can see reference to configure switch --with-findobject, but as far as I can see this switch was removed in latest git code?
Yes, that was removed from the build. The above section is being looked at today and I will try to get it fixed to pass along to Andrea for inclusion.
Andrea: could you change on p. 190 (typo, not 390) the pix_fmt to cin_pix_fmt as you see below? Thank you.
at p. 190
1 mov prores 2 preset medium 3 pix_fmt yuv422p10le
Andrew:
shouldn't be pix_fmt changed to cin_pix_fmt, according to our recent discussion
I am correcting the ffmpeg/video opts files that mistakenly use pix_fmt and they will be checked into GIT in a day or 2.
В сообщении от Saturday 02 November 2019 22:22:40 Phyllis Smith написал(а):
Andrew:
on page 315 I can see reference to configure switch --with-findobject, but as far as I can see this switch was removed in latest git code?
Yes, that was removed from the build. The above section is being looked at today and I will try to get it fixed to pass along to Andrea for inclusion.
Andrea: could you change on p. 190 (typo, not 390) the pix_fmt to cin_pix_fmt as you see below? Thank you.
at p. 190
1 mov prores 2 preset medium 3 pix_fmt yuv422p10le
Andrew:
shouldn't be pix_fmt changed to cin_pix_fmt, according to our recent discussion
I am correcting the ffmpeg/video opts files that mistakenly use pix_fmt and they will be checked into GIT in a day or 2.
Thanks! I also subscribed to http://ffmpeg.org/pipermail/libav-user and can bring up there two points made in documentation p. 193: Outstanding Issues with ffmpeg: There are some problems that need to be ad- dressed by the ffmpeg developer group that adversely affect Cinelerra. These are stated below with the hopes that that group will fix them as time permits. • Make all the default parameters operational. When they are not, the Cinelerra plugins can’t be initialized since the initial state of the filter is not operational. If that is not possible, then provide a set of nominal parameters for each plugin, so that they can be used as the plugins initial default state. • Make the filter config function project the new parameter data into the filter function at any point during filter operation. This is so that continuous updates can be done as the plugin operates. • Improve seek codec restarts. The past predictor must be reset or recon- structed after a seek. The only documented way to seek is open/seek/- play. Reopening the format layer is very expensive. I think I can also link in https://www.cinelerra-gg.org/bugtracker/view.php?id=330 because IMO it shows how wild timestamp can ruin synchro If GG OK with this formulation I will send email to libav-users and CC this list too.
Andrew, I just re-read this to GG to make sure it was stated correctly (sometimes I do not state it quite right or things change). A few years ago he did send the ffmpeg group an email but there was no response at that time. Yes, please feel free to pass it along as it could not hurt and may actually help. On Sat, Nov 2, 2019 at 2:38 PM Andrew Randrianasulu <[email protected]> wrote:
В сообщении от Saturday 02 November 2019 22:22:40 Phyllis Smith написал(а):
Andrew:
on page 315 I can see reference to configure switch --with-findobject, but as far as I can see this switch was removed in latest git code?
Yes, that was removed from the build. The above section is being looked at today and I will try to get it fixed to pass along to Andrea for inclusion.
Andrea: could you change on p. 190 (typo, not 390) the pix_fmt to cin_pix_fmt as you see below? Thank you.
at p. 190
1 mov prores 2 preset medium 3 pix_fmt yuv422p10le
Andrew:
shouldn't be pix_fmt changed to cin_pix_fmt, according to our recent discussion
I am correcting the ffmpeg/video opts files that mistakenly use pix_fmt and they will be checked into GIT in a day or 2.
Thanks!
I also subscribed to http://ffmpeg.org/pipermail/libav-user and can bring up there two points made in documentation
p. 193:
Outstanding Issues with ffmpeg: There are some problems that need to be ad- dressed by the ffmpeg developer group that adversely affect Cinelerra. These are stated below with the hopes that that group will fix them as time permits.
• Make all the default parameters operational. When they are not, the Cinelerra plugins can’t be initialized since the initial state of the filter is not operational. If that is not possible, then provide a set of nominal parameters for each plugin, so that they can be used as the plugins initial default state. • Make the filter config function project the new parameter data into the filter function at any point during filter operation. This is so that continuous updates can be done as the plugin operates. • Improve seek codec restarts. The past predictor must be reset or recon- structed after a seek. The only documented way to seek is open/seek/- play. Reopening the format layer is very expensive.
I think I can also link in https://www.cinelerra-gg.org/bugtracker/view.php?id=330 because IMO it shows how wild timestamp can ruin synchro
If GG OK with this formulation I will send email to libav-users and CC this list too.
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Andrew, BUT, gg says the BT 330 link should not be included. He believes that the device that created the media is the one in error, NOT ffmpeg. As you showed, ffmpeg handles the media just fine in whatever method it uses. It is just CinGG that does not use that method to do so.
I think I can also link in https://www.cinelerra-gg.org/bugtracker/view.php?id=330 because IMO it shows how wild timestamp can ruin synchro
В сообщении от Sunday 03 November 2019 01:01:44 Phyllis Smith написал(а):
Andrew, BUT, gg says the BT 330 link should not be included. He believes that the device that created the media is the one in error, NOT ffmpeg. As you showed, ffmpeg handles the media just fine in whatever method it uses. It is just CinGG that does not use that method to do so.
OPS, already send :/ But I'll stand corrected if there will be any response. (if you look into avi demuxer in libavformat you will see it has some workarounds...for 'slightly broken files'. so, this is not something unheard about.) static void avi_read_nikon() for example ... I think I even saw workaround for quicktime 3 (!!!) but can't find it off-head .....
I think I can also link in https://www.cinelerra-gg.org/bugtracker/view.php?id=330 because IMO it shows how wild timestamp can ruin synchro
participants (2)
-
Andrew Randrianasulu -
Phyllis Smith