+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Talk, Talk, Talk (https://forum.selur.net/forum-5.html)
+--- Forum: Small Talk (https://forum.selur.net/forum-7.html)
+--- Thread: Esxi running macos For selur (/thread-1495.html)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
RE: Esxi running macos For selur - Selur - 30.03.2021
The 'experimental'-option combines some otherwise disabled options.
There are a bunch of undocumented (and a bunch of undocumented and not working) misc.ini options, but I'm not planning to change anything about those options.
Since I do not plan to support custom window sizing, I do not plan to add anything in that regard.
I was once planning to add a fullscreen-option, but dropped it for the time being.
-> I know that you want to freely resize the window size, but like I wrote before that is probably not happening.
Cu Selur
RE: Esxi running macos For selur - shijan - 30.03.2021
But why?
Current "experimental" window resize works very well. It is even better than window resize in legacy Hybrid versions because it don't change window size to default when i switch to upper row of tabs. Fullscreen also subjectively works very well. Very useful when used on secondary display.
By the way, do you think Hybrid_2021.03.30 stable enough? Is is worth to update installer package with it? Or don't hurry and wait for future releases?
RE: Esxi running macos For selur - Selur - 30.03.2021
a. There are still quite a few things broken with resizing and fullscreen, especially since quite a bit of it uses legacy code which, from what I read will not be usable in the next MacOS.
b. There are tons of problems with different themes under Linux, Windows and Mac.
-> not changing the default behavior any time soon.
Quote:By the way, do you think Hybrid_2021.03.30 stable enough? Is is worth to update installer package with it? Or don't hurry and wait for future releases?short: wait
longer: There are still a bunch of bugs in it which I haven't had time to fix or look deeper into.
Also I haven't looked into updating all the tools. (especially the encoders)
Currently I plan to get a new public release ready end of this week.
Cu Selur
RE: Esxi running macos For selur - shijan - 30.03.2021
Ok, got it.
Back to bug (or not a bug) with incorrect duration.
I done some tests with file "Test Patterns Resolve 422 HQ.mov" (original duration 600ms):
Rendered to ProRes mov - Incorrect duration.
Rendered to Cineform mov - Incorrect duration.
Rendered to x264 mov - no problem.
Rendered to x264 mp4 - no problem.
Rendered to ProRes mkv - no problem.
Rendered to Cineform avi - no problem.
So i guess there is a problem somewhere in FFmpeg or in Hybrid.
RE: Esxi running macos For selur - Selur - 30.03.2021
Can't reproduce this here.
None of the files from https://www.dropbox.com/sh/bak63hnr7mnpgbj/AAAf-rMK0LvHYTAFjPuQaaxFa?dl=0 are reported by mediainfo with Duration_Lastframe-info.
You didn't share any debug output so I don't even know what command lines are used.
No clue what's happening.
-> You are on your own on that one.
Quote:"Test Patterns Resolve 422 HQ.mov"I don't have that file. Only similar named file would be 'Test Patterns Resolve 422 HQ 10-bit.mov'
Quote:So i guess there is a problem somewhere in FFmpeg or in Hybrid.or your file is simply flagged in a wrong way
Cu Selur
RE: Esxi running macos For selur - Selur - 30.03.2021
Ahhh,... okay, reencoding 'Test Patterns Resolve 422 HQ 10-bit.mov' with ProRes created a file with the 'Druation_LastFrame' info.
The whole time I understood it that the input had this info not the output,...
ffmpeg -y -noautorotate -nostdin -threads 8 -ignore_editlist true -i "C:\Users\Selur\Desktop\ProRes Examples 10 12 bit\Test Patterns Resolve 422 HQ 10-bit.mov" -map 0:0 -an -sn -pix_fmt yuv422p10le -strict -1 -vsync 0 -vcodec prores_ks -profile:v 3 -vtag apch -metadata encoding_tool="Hybrid 2021.03.30.1" -f mov "E:\Output\Test Patterns Resolve 422 HQ 10-bit_2021-03-30@16_23_34_1710_01.mov"During the reencoding ffmpeg reports:
[mov @ 00000108f32800c0] Application provided duration: -9223372036854775808 / timestamp: -9223372036854775808 is out of range for mov/mp4 format
[mov @ 00000108f32800c0] pts has no value(when reencoding to a non ffmpeg based encoder, only the frames are used not the time codes)
There is probably an additional ffmpeg-option to fix this,..
Cu Selur
RE: Esxi running macos For selur - shijan - 30.03.2021
It is same as "Test Patterns Resolve 422 HQ 10-bit.mov" i just renamed it on computer.
It was no problem with old version of FFmpeg and Hybrid.
I will test different combinations of FFmpeg and Hybrid
Here is debug. Hybrid_dev_2021.03.30 + ffmpeg-101748-g797c2ecc8f 2021-03-28
RE: Esxi running macos For selur - Selur - 30.03.2021
Read my last post again.
Problem might be that ffmpeg keeps some sort of time code track.
Cu Selur
RE: Esxi running macos For selur - shijan - 30.03.2021
Ok, hope it will be some fix for this. I don't like when ffmpeg changes file duration like this under the hood
RE: Esxi running macos For selur - Selur - 30.03.2021
Problem seems to be the '-vsync 0' option:
Quote:-vsync parametersource: https://www.ffmpeg.org/ffmpeg-all.html
Video sync method. For compatibility reasons old values can be specified as numbers. Newly added values will have to be specified as strings always.
0, passthrough
Each frame is passed with its timestamp from the demuxer to the muxer.
1, cfr
Frames will be duplicated and dropped to achieve exactly the requested constant frame rate.
2, vfr
Frames are passed through with their timestamp or dropped so as to prevent 2 frames from having the same timestamp.
drop
As passthrough but destroys all timestamps, making the muxer generate fresh timestamps based on frame-rate.
-1, auto
Chooses between 1 and 2 depending on muxer capabilities. This is the default method.
Note that the timestamps may be further modified by the muxer, after this. For example, in the case that the format option avoid_negative_ts is enabled.
With -map you can select from which stream the timestamps should be taken. You can leave either video or audio unchanged and sync the remaining stream(s) to the unchanged one.
When removing the option (which then uses '-vsync -1') everything seems fine.
-> Seems like the way how ffmpeg reacts to broken time codes in the input has changed.
Cu Selur