This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Esxi running macos For selur
(updated dev version)
Converting 'Ramp Resolve ProRes 422 HQ 10-bit' to CineformHD works fine here on Windows and Mac.

The ffmpeg version you used does not support 'cfhd'.
"/Applications/Hybrid.app/Contents/MacOS/ffmpeg" -y -noautorotate -nostdin -threads 8 -ignore_editlist true -i "/Volumes/shph/install mac/Video/,Converters/VapourSynth + Hybrid/2020 development/Test Patterns Resolve 422 HQ.mov" -map 0:0 -an -sn -strict -1 -vsync 0 -vcodec cfhd -quality 0 -vf scale,format=yuv422p10le -pix_fmt yuv422p10le -metadata encoding_tool="Hybrid 2021.03.29.1" "/Volumes/temp/Hybrid Temp/Test Patterns Resolve 422 HQ_2021-03-29@19_44_31_0210_01.mov"
returned:
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay
  libavutil      56. 51.100 / 56. 51.100
  libavcodec    58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter    7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample  3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Volumes/shph/install mac/Video/,Converters/VapourSynth + Hybrid/2020 development/Test Patterns Resolve 422 HQ.mov':
  Metadata:
    major_brand    : qt 
    minor_version  : 0
    compatible_brands: qt 
    creation_time  : 2020-08-31T01:15:17.000000Z
  Duration: 00:00:00.60, start: 0.000000, bitrate: 5748 kb/s
    Stream #0:0(und): Video: prores (Standard) (apcn / 0x6E637061), yuv422p10le(tv, bt709, progressive), 720x576, 5728 kb/s, SAR 59:54 DAR 295:216, 25 fps, 25 tbr, 25 tbn, 25 tbc (default)
    Metadata:
      creation_time  : 2020-08-31T01:15:17.000000Z
      handler_name    : Core Media Video
      encoder        : Apple ProRes 422
      timecode        : 00:00:00:00
    Stream #0:1(und): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      creation_time  : 2020-08-31T01:15:17.000000Z
      handler_name    : Core Media Time Code
      timecode        : 00:00:00:00
Unknown encoder 'cfhd'

CineformHD encoding was added "Sun, 2 Aug 2020" any ffmpeg build before that date will not allow to encode to CineformHD. Wink
(see: https://git.ffmpeg.org/gitweb/ffmpeg.git...e99774a967)


Cu Selur
Reply
Interesting... ffmpeg 4.3.2 is fresh release (2021-02-20) but seems cineform is just not there there. Maybe they still consider cineform as experimental option available only in development snapshots yet?

...

If deinterlacer disabled - error on startup:
Couldn't set property(2): value in deinterlacer - FilteringModel to none, found: Yadif - fast


After restart no error.
Reply
Quote:Couldn't set property(2): value in deinterlacer - FilteringModel to none, found: Yadif - fast
thought I had that fixed,... -> will look at it again

Cu Selur
Reply
Can't reproduce the problem here.
Deleted the settings folder content, started Hybrid, loaded a source, no problem,...
To be sure we use the same version I packaged and uploaded the version again, but renamed the zip (added .1).

Quote: ffmpeg 4.3.2 is fresh release (2021-02-20) but seems cineform is just not there there.
Changelog for 4.3.2:
https://fossies.org/linux/ffmpeg/Changelog mentions avcodec/cfhd so it should be included,..
strange.

What does the version output for:
ffmpeg -codecs
if CineformHD is supported it should contain:
DEV.L. cfhd                 GoPro CineForm HD


Cu Selur
Reply
D.V.L. cfhd Cineform HD shown in list in Terminal in ffmpeg 4.3.2 So it looks really strange that Hybrid can't render to Cineform with ffmpeg 4.3.2 release version.

Maybe because different name used?
DEV.L. cfhd GoPro CineForm HD
D.V.L. cfhd Cineform HD

...

Here is how to reproduce that fancy error message:
- Delete Hybrid app support folder
- Start Hybrid
- Config -> Profiles -> Check "Autosave Defaults"
- Filtering -> Deinterlace -> Uncheck "Auto"
- Close Hybrid
- Start Hybrid again and here should be a message:
Couldn't set property(2): value in deinterlacer - FilteringModel to none, found: Yadif - fast
Reply
Quote:Maybe because different name used?
DEV.L. cfhd GoPro CineForm HD
D.V.L. cfhd Cineform HD
Not the name, the missing 'E' is the problem!
'E' stand for encoding support, so that version is missing the encoding support.

Will look at the 'Yadif - fast' error tomorrow, finished for today. Smile

Cu Selur
Reply
Did a fix for the deinterlacer issue, by removing 'none'. Wink
(updated dev; last for today, going to bed now)

Cu Selur
Reply
Removed some additional error messages and updated the dev version.

Cu Selur
Reply
Updated dev version, changed errors to simple notifications in the normal log.

Cu Selur
Reply
Nice. I like that new more human friendly checkbox "Use Deinterlacer" instead of legacy confusing "Auto".

I understand that probably current experimental=true options are designed like this or some reason or for some special test purposes, but i really hope things may be improved a little bit in future:

- Instant auto fullscreen on start is not a good idea. In most situations it only makes things too complicated. I guess it is better to add separate option for this in misc.ini or in UI settings.
- Back to default window size by clicking to main window toolbar it not a good idea as well. It is always better to let custom window size stay the same size in all situations if it was adjusted by user.
- Colored text on pressed tabs is near impossible to read on macOS. So i guess it is better to add separate option for colored tabs text in misc.ini or in UI settings.
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)