I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
When uploading a clip to the atem, all the frames must be presented to the library at once. While this is optimal for upload speed, it will require very large amounts of memory when doing long clips (filling a constellation in 1080p will take 12gb of ram)
Julusian
commented
2 years ago
I'm submitting a ... [ ] bug report [x] feature request [ ] question about the decisions made in the repository [ ] question about how to use this project
Summary When uploading a clip to the atem, all the frames must be presented to the library at once. While this is optimal for upload speed, it will require very large amounts of memory when doing long clips (filling a constellation in 1080p will take 12gb of ram)
Other information
https://github.com/nrkno/tv-automation-atem-connection/blob/abcff0c74a51b3ffb4880106b87109a7fc72b9ec/src/dataTransfer/dataTransferClip.ts#L12 Instead this should be able to take an
Array<Promise<DataTransferFrame>>There could be a strategy in place to preload x frames to keep the uploader running smoothly.
What should happen if a frame promise rejects? Should the whole clip be invalidated and aborted?