View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001260 | DCP-o-matic | Bugs | public | 2018-03-29 22:50 | 2019-11-10 19:34 |
Reporter | Carsten | Assigned To | carl | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | reopened | ||
Platform | Mac | OS | OS X | OS Version | 10.11 |
Product Version | 2.12.x | ||||
Target Version | 2.12.x | ||||
Summary | 0001260: Catch 'no output filename specified' condition during export | ||||
Description | It is possible to click 'OK' on the export dialog even when there is no output filename specified. In that case, export starts, but immediately stops with 'Error: (could not allocate FFmpeg format context)' - which is Klingon for 'Where the heck should I write this stuff to?' a.) catch this condition and output a better warning message 'You need to specify an output filename!' For GUI simplicity, I prefer option c.)
| ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Unknown | ||||
|
1d5ea1b139942bad5500ae40f0646da3fd29dc7f in master. aa97e44d334f3e2a1924059e10407aae85519eba in v2.12.x |
|
Thanks, I went for (b) as I think it's a marginally nicer user experience... |
|
Yup. Grants user another second of rest to think about their final choice. |
|
Export now automatically uses the set ISDCF/DCNC name. However (at least in OS X), it now automatically uses the DCP-o-matic application directory as the export file location (and overwrites preexisting files there without asking). That means, after opening the export dialog and hitting 'OK/Return', the exported file is immediately written 'somewhere' (and it may actually fail on some systems due to write permission issues for the program folder?). Maybe still show 'Choose file/location' in that dialog, but then just prepopulate the 'Save To' dialog with the DCNC name? Or maybe better, show the DCNC name immediately, but when hitting 'OK', offer the Save To dialog for the user to change the location (and remember last location). I also think (debatable, of course) that the default MP4 export quality setting '23' is too high. I creates very large files for shorts and full length features - I regularly see data rates in the range of DCPs - e.g. 50-100 MBit/s (twice as much as typical Bluray data rates). I think they should be lower. I would opt for '35' as installation default. But remember the setting in the config, so it's reused for all exports. From my experience, '35' creates data rates that are common for DVDs and internet streams (3-8MBit/s). I think that makes more sense for MP4. And, while there, maybe make MP4 the export default (but, again, remember in config)? Some systems do not have Prores codecs installed, but all systems now can play MP4. I think defaults should be targeted at the 'regular' user, while it can be expected that advanced users are able to make deliberate decisions.
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-03-29 22:50 | Carsten | New Bug | |
2018-03-29 22:50 | Carsten | Status | new => assigned |
2018-03-29 22:50 | Carsten | Assigned To | => carl |
2018-03-29 22:55 | Carsten | Description Updated | |
2018-04-12 22:58 | carl | Note Added: 0002363 | |
2018-04-12 22:58 | carl | Status | assigned => resolved |
2018-04-12 22:58 | carl | Resolution | open => fixed |
2018-04-12 22:58 | carl | Note Added: 0002364 | |
2018-04-13 04:28 | Carsten | Note Added: 0002367 | |
2018-10-17 20:16 | carl | Status | resolved => closed |
2019-11-10 19:07 | Carsten | Status | closed => feedback |
2019-11-10 19:07 | Carsten | Resolution | fixed => reopened |
2019-11-10 19:07 | Carsten | Note Added: 0003577 | |
2019-11-10 19:07 | Carsten | Note Edited: 0003577 | |
2019-11-10 19:08 | Carsten | Note Edited: 0003577 | |
2019-11-10 19:10 | Carsten | Note Edited: 0003577 | |
2019-11-10 19:34 | Carsten | Note Edited: 0003577 |