| Age | Commit message (Collapse) | Author |
|
instead, assume it should be at timestamp 0.
Backported-from-commit: d7a3d94ec307a03ebe3fcf239ba991e9a3c1b8b8
Backported-from-branch: v2.15.x
|
|
hang around. Part of the fix for #1857.
Backported-from-commit: 9a3df0a97b7962c00726447a75599e34c632cb2b
Backported-from-branch: v2.15.x
|
|
|
|
|
|
|
|
|
|
|
|
to write metadata to the "create in folder" directory, which throws
an uncaught exception if the specified directory is unwriteable.
If we have a name then DoM tries to create the directory with that name,
which fails more elegantly and with a nicer error.
Backported-from-commit: 50aaa3789864c7330ee92e7e89ad5b6cc2155a82
Backported-from-branch: 2.15.x
|
|
|
|
from Dolby.
Backported-from-commit: 746e298e214a65ca9151867b2948560e76b45546
Backported-from-branch: v2.15.x
|
|
Backported-from-commit: 5f1fdbafc6eef37523250e0b8542a8939a038823
Backported-from-branch: v2.15.x
|
|
Backported-from-commit: d461077cf4f2c1470d2d0d6dbc4f5708411bec65
Backported-from-branch: v2.15.x
|
|
Cherry-picked from 591c73b472f0eb74225dbc1b08885f552b8814c4 in v2.15.x.
|
|
so that they can be displayed.
Cherry-picked from 09860271bb6d03b3937c08bffb4c672697f6d711 in v2.15.x.
|
|
Cherry-picked from d902160e3c89a9f65f58a2463fac0b1de1d940b1 in v2.15.x.
|
|
DVD rips from NTSC DVDs are sometimes (always?) encoded using
soft 2:3 pulldown. The video frames are actually 23.976 but
FFmpeg detects them as 29.97. With the current approach of the video
decoder ignoring most PTSs and assuming a constant frame rate
it is vital that the file contains the number of frames per second
that the detected frame rate predicts.
This fixes large sync errors with NTSC DVD rips (#1790).
Cherry-picked from af680761cf7c3e97660e8e55c68f42e90b026bf9
in v2.15.x.
|
|
is running as clicking the higher ones will cause an assertion
failure.
Cherry-picked from 4b5e05b9845d609524328a88a81011b364e03a8a in
v2.15.x.
|
|
analysis window while the analysis is running.
Cherry-picked from 6b1d9adcf6e75fc8e441b61108a2169bda6a6094 in
v2.15.x.
|
|
inclusive fails, at least for AAC. There's probably a way around
this with some FFmpeg-cleverness but for now let's just export any
project with more than 8 channels as 16.
You could argue that we should offer choices to, for example
export 7.1/HI/VN as 7.1 but that sounds fiddly.
Fixes #1786.
|
|
|
|
|
|
|
|
Backported from 2c844e57ed5c54e65a2b4484f02907122a03361e in v2.15.x.
|
|
Backported from 8c7ad603cf0a534abe1a920b70b0daa095257d3a in v2.15.x
|
|
|
|
|
|
so that the thread is gone before the object is torn down.
|
|
|
|
the same time (github #7).
Back-ported from c403e757cf0b029954fe18dc969314bfb179412f in v2.15.x.
|
|
more than one piece of content at once (e.g. trim start).
Back-ported from 746aa7337ac2d51a4fa09039c1d5d7717cc880fa in v2.15.x.
|
|
|
|
|
|
|
|
|
|
Required because of the change to the way video frame timing
is done.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
then convert it back to resampled content frames using the DCP
rate rather than the resampled content rate, which seems wrong.
If we want to go from metric time to frames we surely have to use
the frame rate of the thing we are working with (not the frame rate
which that thing will be played back at).
Backported from 26c62598730d1d32333bfab0d5f463b90d26ee4d in v2.15.x.
|
|
Before this fix, the following situation could happen in threads
A and B:
A: Some DONE signal happens; this triggers setup_pieces which
takes a lock on the player mutex.
B: FFmpegContent::examine takes a lock on the content mutex.
B: FFmpegContent::examine adds a stream
B: That causes STREAMS PENDING to be emitted.
B: This tries to take a lock on the player mutex so it can update _suspended
A: setup_pieces tries to access some content information, hence
tries to take a lock on the content mutex.
Now B is holding the CL and awaiting the PL and A is holding
the PL and awaiting the CL.
It feels like the root cause of this is that while setup_pieces
is happening another change (which would itself cause setup_pieces)
is announced, and this isn't dealt with properly.
There are two steps here; _suspended is protected with an atomic
rather than using _mutex, and also it can cope with being updated
recursively.
Backported from df48c75c38dd788835a93540aea243a2dac4bb10 in v2.15.x
|
|
Back-ported from 98342fb53eae4d32440fc69c279f2ca0fef785b5 in v2.15.x.
|
|
Back-ported from dec5ae11238495c64fffdab37f189d96aed7d636 in v2.15.x.
|
|
|
|
|
|
|