# [CD-2194](https://ownzones.atlassian.net/browse/CD-2194) **Input Clipping on Mediawarp screen**

**Issues**:

- [x] input clipping start timecode: 00:00:00:00; Input clipping end timecode: 00:00:20:00 -> resulted video track duration: 00:00:20:01. For end timecode 00:00:15:00 -> resulted video track duration: 00:00:15:00
> probably it's the same issue as [CD-3067](https://ownzones.atlassian.net/browse/CD-3067)
> https://connect.three.ownzones.dev/three/files/ed7127a7-056e-411f-b4b5-578bafc7511a/
> this file sometimes has 20s and 1 frame and sometimes just 20s in player
- [x] sync button not working, also tooltip needed?
> the sync is done between the tracks from the same file. try the feature on a file with multiple audio tracks
> tooltip in progress
- [x] input clipping clear button (“x”) does not seem to be working
> there is no clear button. it a design "feature" - talking about that 'x' inside input's borders

- [x] same validation: *“There was a problem submitting the data. GraphQL error: The input clipping start timecode '00:00:00:00' must be less than the input clipping end timecode '00:00:00:00’”* must be present in mediawarp screen as well, otherwise *“00:00:00:00 / 00:00:00:00  (0 / 0)”* clip will be created
- [x] also for validations, don't know if it's really a problem, you can only set the end timecode and leave start timecode empty, the resulted demux for that track will have full length, so only end timecode, is not taken into consideration
> not an issue
- [x] `Timecode() constructor expects a number, timecode string, or Date()` - this happens when you put input start timecode bigger than end timecode - i guess this will be solved when the validations are done
- [x] i guess this was what Thor was talking about in the daily, about having different durations for video and audio
- [x]` Error: Demux activity failed (activity id: b7dc50d9-6b57-4bbc-90a1-10865d6dcc7c, workflowId: 46157bc7-8d4e-44ec-9557-1d8326d3835b): streamsClipping has different sizes of interval` - **audio/video tracks not having the same clipping**
- [x] `Error: Demux activity failed (activity id: f937e29a-d4f9-4277-a7a2-6b6f85d37ad4, workflowId: a7dcb610-4ded-4c00-8a8d-0f0f20ed529a): Cannot read property 'end' of undefined` - **audio not having input clipping at all**
- [x] `Error: Demux activity failed (activity id: f1d34811-ddea-40d9-9aef-568cc6e09a5e, workflowId: 101982d7-2b7b-4754-a3eb-e530ae941386): Task Expired` - **caused by a demux profile after all**
- [x] profile: https://connect.three.ownzones.dev/three/demux-profiles/18a8e6ee-431d-4f0c-8f48-939093a47df7
- [x] file: https://connect.three.ownzones.dev/three/files/0352ab9a-1930-45ba-8c1b-4f0a8a1f173e?tab=workbench
- [x] Error: Demux activity failed (activity id: 23fec3e5-7640-483a-a55f-2514da8364b4, workflowId: e8440368-d072-4331-a4f0-7c0d3dae9a58): ffmpeg exited with code 1:
- [x] wav: https://connect.three.ownzones.dev/three/files/7c27571f-2573-4b67-bc17-13dbb1e81bce?tab=workbench
- [x] 12 mono tracks: https://connect.three.ownzones.dev/three/files/23277e1b-14cc-412a-be9e-cfe5f9c46644?tab=workbench
- [x] video + audio input clipping demux - [CD-4520](https://ownzones.atlassian.net/browse/CD-4520)

---
# [CD-4134](https://ownzones.atlassian.net/browse/CD-4134) Add color space settings to media warp screen

- [x] when trying to demux only audio track error occurs: GraphQL error: Cannot read property 'colorSpace' of undefined - [CD-4400](https://ownzones.atlassian.net/browse/CD-4400)
- [x] apparently there are some movies that don't have color properties filled in and until now that was not necessary, but now the file can't be demuxed without filling in those properties, which seems to be tricky, demux will fail with the following error: `Error: Demux activity failed (activity id: 39462e38-9671-40f5-b8ce-7f5d8a07278e, workflowId: c8869bdf-32bf-48e9-a7c0-df3f305eea28): Unable to detect the colorimetry system`
* file example: https://connect.three.ownzones.dev/three/files/bf7cccb8-a49d-4f78-b6ce-df0ee0485662?tab=workbench - [CD-4404](https://ownzones.atlassian.net/browse/CD-4404)
> This is not related to this ticket, it's an older issue caused by a bad Demux profile