You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is causing the audio to be cut off early on any wipes done via the Sting Producer.
This looks to be a bug in the version of FFmpeg we are currently using (a dev build from February), as it is happening with QT Animation and ProRes files rendered from After Effects CC2018, CC2017 and CC2015.
It appears to work for clips without audio.
One workaround is to render the clips from AE CC2018 on Windows, as they appear to play fine.
Another workaround could be to render the clips too long, so that we never intend to hit the ends of the clips. Not an ideal solution either though.
The same clips work fine in the official CasparCG Server 2.2, so this issue is just a way to document the problem that should be fixed once we transition to 2.2.
The text was updated successfully, but these errors were encountered:
The clips play to the end in both Server 2.2 and 2.0.
The problem is specific to the producer code in 2.1, as it is occuring with both the original version of FFmpeg included in 2.1, the version we updated to, as well as newer versions.
This is causing the audio to be cut off early on any wipes done via the Sting Producer.
This looks to be a bug in the version of FFmpeg we are currently using (a dev build from February), as it is happening with QT Animation and ProRes files rendered from After Effects CC2018, CC2017 and CC2015.
It appears to work for clips without audio.
One workaround is to render the clips from AE CC2018 on Windows, as they appear to play fine.
Another workaround could be to render the clips too long, so that we never intend to hit the ends of the clips. Not an ideal solution either though.
The same clips work fine in the official CasparCG Server 2.2, so this issue is just a way to document the problem that should be fixed once we transition to 2.2.
The text was updated successfully, but these errors were encountered: