View Bug Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001880 | DCP-o-matic | Features | public | 2020-11-23 23:12 | 2024-01-06 22:49 |
| Reporter | carl | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Summary | 0001880: Support ATMOS IAB MXFs | ||||
| Description | For ATMOS we have both "DCP IAB" and "IMF IAB" types; it seems that present we support only DCP. The free conversion tool only writes IMF. It looks like IMF support was added to asdcplib, so it should just be a question of rebasing our asdcplib fork and using the IMF reader in DoM. I have squashed and tidied the Some example files in | ||||
| Tags | No tags attached. | ||||
| Branch | |||||
| Estimated weeks required | |||||
| Estimated work required | Undecided | ||||
|
|
Any news? Is there an option to import IMF IAB file now to use for "generic IAB" DCP mastering? |
|
|
No immediate news but I'll try and look at it soon. |
|
|
In case it is of any use: If understand correctly, IAB, Atmos, DTS:X, all should be basically the same and compatible in DCP. Differences are in playback implementations. What I don't really understand is if IMF IAB and DCP IAB have to be different, are they technically different, or they just need to be mixed in different environments. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-11-23 23:12 | carl | New Bug | |
| 2020-11-23 23:13 | carl | Description Updated | |
| 2020-11-23 23:13 | carl | Estimated work required | => Undecided |
| 2020-11-23 23:13 | carl | Status | new => acknowledged |
| 2024-01-06 14:57 | cloud06 | Note Added: 0006200 | |
| 2024-01-06 22:16 | carl | Priority | normal => high |
| 2024-01-06 22:16 | carl | Note Added: 0006201 | |
| 2024-01-06 22:49 | cloud06 | Note Added: 0006202 |
