Enables video support in ardour by default.
I do a lot of sound design using ardour and in turn have it enabled in
my configuration. However, seeing as hydra only builds the default
configuration, the build I need is never cached, and I always end up
needing to build ardour from scratch which takes over an hour on my
small laptop. The `videoSupport` flag itself just ensures that xjadeo
and harvid (both required for video support to work in ardour) are
accessible via the PATH.
This adds a `bool` option that, when set to `true`, enables video
timeline support for the Ardour DAW. This is commonly useful for
soundtrack composition, sound design for film, etc.
When enabled, `videoSupport` ensures that both `harvid` and `xjadeo` are
available to the `ardour6` exe via the PATH. `harvid` decodes the video
stream in real-time to produce still images (I think for thumbnail
support for the timeline?). `xjadeo` acts as a video monitoring window
that whose playback position is synchronised to the Ardour playhead.
`videoSupport` remains disabled by default, preserving the original
behaviour.
Video support can be added to ardour in your system or home
configuration package list with:
```
(ardour.override { videoSupport = true; })
```
After making `ffmpeg` point to the latest `ffmpeg_4`, all packages that
used `ffmpeg` without requiring a specific version now use ffmpeg_3
explicitly so they shouldn't change.
We leave Ardour 5 in, since Ardour 6 has a new latency compensation
algorithm, so your mixes might end up sounding different in the new version.
Co-Authored-By: Pavol Rusnak <pavol@rusnak.io>
* Remove unneeded dependencies
* Stop vendoring other dependencies (fluidsynth, hidapi, libltc, qm-dsp)
* Fix using incorrect libusb version (libusb package is just a legacy compat layer)
* Move build-time dependencies to nativeBuildInputs
* Install freedesktop files & man page
* Drop libintl replacement that no longer applies
This avoids the potential conflict between autoconf flags and the waf
flags. There is some overlap between the two but waf errors when it
doesn’t recognize the flag.
The most complex problems were from dealing with switches reverted in
the meantime (gcc5, gmp6, ncurses6).
It's likely that darwin is (still) broken nontrivially.
