 |
@PhyllisSmith, i think libaom-v3.1.0.patch1 really should be named libaom-v3.1.1.patch1 becuse this isvwhat we use and buildsystem assumes name of source trabal before. tar. * part and patch name is the same. also, if ffmpeg/libaom/x264 update works ok may be you can delete old tarballs? |
 |
@Andrew-R Tested and checked into GIT, the defaults for mxf format. (Also tested and checked in randrik18/0008-libaom-3.1.0-and-libwebp-1.1.0-patches-for-thirdpart.patch - PLEASE VERIFY) |
|
|
@MatN - re: ffv1 in mxf I think according to those links it still not done/under discussion https://mediaarea.net/ollistd/MXF_FFV1 https://kws.smpte.org/higherlogic/ws/public/projects/645/details |
|
|
@MatN, ah, ffv1-in-mxf... I do not think ffmpeg's mxf muxer support this... not even sure if such combination allowed by mxf spec.. / |
 |
@Andrew-R, I think the defaults are a good idea, I applied the patch here. But it does not solve the problem of unchecked boxes. Like Phyllis wrote, if you call the render menu, I think audio/video boxes should be checked by default if audio/video tracks are present in the current project. I am not sure these settings are part of the project (and saved in the .xml project file)? @PhyllisSmith, good idea, a chapter about exchanging files with other NLEs could be helpful. @Andrew-R, ffv1 works for avi and mov, but it is not in the list of video compression for mxf. For avi and mov, the same input as for my previous test generates file size of 166 MB. Smaller than OpenMpeg anyway, and VLC plays it fine. |
|
|
I tried to make mxf.dfl (defaults) for audio and video, still you might need to re-select ffmpeg/mxf _WITH BOTH AUDIO AND VIDEO CHECKBOXES CHECKED/ENABLED_ for those defaults to have effect..
0001-defaults-for-mxf-ffmpeg-profiles.patch (894 bytes) |
|
|
@PhyllisSmith, I think this little automatization at least prevent erroneously trying to set audo codec for image-only containers/formats? but for mxf may be renaming audio profiles to have same name as video ones might help? or some new mxf.mxf profile with new most compatible combination (like dnxhr/24 bit pcm)? |
|
|
@Andrea_Paz Once verified, perhaps the information MatN uncovered about "exchanging media" should be mentioned as a note in the manual? @MatN I agree we should leave this open until someone figures out why the boxes are unchecked. There are other casees. For example: 1) choose 'png' instead of ffmpeg. The audio checkbox automatically is unchecked and ghosted out AND "one frame" checkbox is automatically checked. 2) choosing 'dpx" under ffmpeg, also unchecks boxes and is a recently added one by Andrea. 3) it seems that once the boxes are unchecked, they usually stay unchecked -- so if you choose 'dpx' and then switch to "mp4", they stay unchecked. (Maybe the above is a hint of where to look in the code?) |
|
|
@MatN in theory ffv1 profiles are installed: --- $ less bin/ffmpeg/video/ffv1.<tab> ffv1.avi ffv1.mkv ffv1.mov |
|
|
Well, I got the result back from importing the 5 different encoded mxf files into Adobe Premiere Pro (APP) en DaVinci Resolve (DVR). The encoding was 5 seconds of a HD movie with 2 audio channels. Encoding avcintra, size 5.2 MB. APP - jittery playback. DVR - does not play. dnxhr_proxy, size 48 MB. APP - OK. DVR - OK h264_b, size 6.3 MB, APP - does not import. DVR - OK mpeg2, size 5.5MB. APP - OK. DVR - OK openjpeg2000, size 510 MB. APP - imports but no picture. DVR - OK So, for now the safest bet for exchanging media as mxf files between CinGG, APP and DVR seems to be dnxhr. There is probably a quality difference between mpeg2 and dnxhr. CinGG does not support ffv1? |
|
|
@Andrew-R @PhyllisSmith, You are right. The problem was that the audio format was not selected. As soon as I selected it (16 bit pcm) the rendering went OK for 5 out of 6 formats. I could not render the DV format because apparently it does not support the 1920x1080 format. I missed the bit in the manual that Phyllis mentioned, my bad. I don't remember ever having to set the audio format before. May I suggest to keep this open until we find out why the boxes/setting are not automatically filled in? |
|
|
@MatN Not much help here but the manual does say this: "The Render window will sometimes automatically update the Render Audio Tracks or Render Video Tracks checkbox as allowed by the chosen file format, but you should always check." It must be something in the code !! |
|
|
@MatN This puzzles me too and I have no recollection why this occurs but will see if I can find some explanation -- "4. Select file format ffmpeg.mxf . Already both video and audio render boxes become unchecked! Why?" However, as soon as I check both the audio and the video boxes, the first available mxf format for both the audio and video comes up when I check the "wrench" and the render works. |
|
|
well, in theory there should be two audio choices in ffmpeg/audio folder: mxf_pcm16.mxf mxf_pcm24.mxf try to select one of them manually? |
- Anonymous
