Very good, thank you. As the average reader that I am (with no personal experience producing music for video or video), I have some questions. I’m happy to help improve the description with the answers.
Are all these formats really required, or all of them equally important? Can we define some priorities in case not all of them are feasible?
What is RTC? I think I understand grid cue markers
What is MTC?
Also, isn’t it a bit counterintuitive that we are proposing features to get rid of a second DAW but then here we ask for something to better sync with a second DAW? This feature request is already very beefy. Could this be removed?
These are Dolby formats. I wonder what is the business behind them, and whether shipping Bitwig with this support means a higher cost for Bitwig for every license sold to pay Dolby royalties or something.
Anyway, is this really required for a first release? This is related to the same point about this request being already very beefy.
This is a more open question. What kind of producers using Bitwig today can we expect to need this video support? What kind of producers would move to Bitwig if if this video support would exist? Is this about short videos, experimental stuff, film scoring…
I mean, if a video producer is using another DAW with well established video support, there must be a musical reason why they would switch to Bitwig, because the video support itself would be basically the same (best case scenario, unless Bitwig now decides to start innovating on video support).
(Also, should we change the owner for attribution? This software doesn’t allow to have multiple authors. Not very important but this came to mind as I was quopting these fragments from the description). 