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
(19.08.2020, 19:04)Selur Wrote: I understood you the last time you posted about it.
The problem is that QuickLook is a crappy player, which like old Quicktime requires some additional adjustments which ffmpeg might not be able to do.
You can try if enabling/disabling one of the other options under 'Mp4 Settings' helps with the issue. (I doubt it, but it might be worth a try; especially try the 'Force HEVC tag')

This has nothing to do with Hybrid directly so I will look at it once the basic stuff works.

But why x264 no more produce jumping effect in new hybrid? Same FFmpeg 4.3.1 used.

Ok, i will not mix multiple problems in one Log report.
Reply
Because H.264 and H.265 are different standards.
-> Okay, I'll drop everything and stop trying to fix Hybrid and will now look into the incompatibilities of Quicktime/Quicklook.

Cu Selur
Reply
-> Problem is Quicklook can't handle B-frames when FFMpeg is enabled.
Disable B-frames and Quicklook should properly playback the file.
Reply
Yes, disabled B-frames fix jumping frames problem in QuickLook. So i will experiment with other options...

I agree, working VapourSynth is priority.
Reply
And? Did you try the Vapoursynth preview?
Reply
But nothing was chaged i see same 20200818_1 version in Google Drive. VS preview gives me same error. Should i record Log with VS preview error only?
[Image: CyAsUHI.jpg]

There is an alias file in /usr/local/bin/vspipe
vspipe alias goes to original file located in /Library/Frameworks/VapourSynth.framework/bin/vspipe

I can click vspipe alias and launch it manually. It gives me this:
[Image: 14iZxk0.jpg]
Reply
On Linux and Windows I usually do not put the libraries inside the autoload folder of Vapoursynth.
So now Vapoursynth is complaining that the script tries to load libraries it already has loaded.
-> I got it and fixed it locally, solution is to simply not load the libraries.

Not sure so far what broke the normal preview, but that will take some time to fix.
I'll probably have to rewrite the whole preview code to make it work with the latest changes in mac os :/

Signing out for today. Probably won't do anything tomorrow.
Looking at the preview over the weekend, but I don't expect it to be fixed at the end of the weekend.

Cu Selur
Reply
Just want to notice that it is not only VapourSynth Preview problem. Render to file don't works if i select any of VapourSynth filters. Here is log (open file, De-halo filter, render to ProRes).
Wish you good luck to make it work globally somehow in future.
Reply
Thank you selur
For your time and energy. You are very appreciated!
Reply
@shijian: the version I uploaded today should work,.. (does here)

Cu Selur
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)