If you made it to a starting Resolve installation on your Linux system (congrats) and you don't actually use the Studio version, you may realize quickly that Resolve is unable to import your Video footage.

This is (as far as I read) because of licensing issues (lol) so only the Studio version can handle H.264 and AAC in Linux, so you may quickly run into the following issues:

Bildschirmfoto vom 2018-04-16 18-00-36.jpg
MTS files from a Sony RX100II, not even imported but already listed as "offline".

Bildschirmfoto vom 2018-04-18 19-44-35.png
MP4 from a Canon 750D, shown as audio file but not even with audio working

Okey it seems like there is only one (or two) solutions, you can use a tool like WinFF but I will show you one-line terminal commands to use.

For Intel based Systems:

cd /path/to/folder/with/footage
# MTS
for f in *.MTS;do ffmpeg -i "$f" "${f%mts}.wav";ffmpeg -i "$f" -i "${f%mts}.wav" -c:v dnxhd -profile:v dnxhr_hq -acodec pcm_s16le "${f%mts}.mov" ;done
# MP4
for f in *.MP4;do ffmpeg -i "$f" "${f%mp4}.wav";ffmpeg -i "$f" -i "${f%mp4}.wav" -c:v dnxhd -profile:v dnxhr_hq -acodec pcm_s16le "${f%mp4}.mov" ;done

For AMD based Systems:

cd /path/to/folder/with/footage
# MTS
for f in *.MTS;do ffmpeg -i "$f" "${f%mts}.wav";ffmpeg -i "$f" -i "${f%mts}.wav" -c:v prores -profile:v 3 -acodec pcm_s16le "${f%mts}.mov" ;done
# MP4
for f in *.MP4;do ffmpeg -i "$f" "${f%mp4}.wav";ffmpeg -i "$f" -i "${f%mp4}.wav" -c:v prores -profile:v 3 -acodec pcm_s16le "${f%mp4}.mov" ;done

Notice that you can vary quality with the -profile:v N flag:

Quote from ffmpeg.org

There are 4 profiles that exist within Prores: Proxy, LT, SQ and HQ (and then optionally 4444). In ffmpeg these profiles are assigned numbers (0 is Proxy and 3 is HQ). [...] For quick reference, the basic difference is the bitrates: (TODO).

find out more...

So what we do here is extracting the audio source from the footage and then convert the source footage with the wav audio source to a new file in the dnxhr_hq/prores format.
The reason why we have two formats for two systems is mainly because AMD processors don't work that nice with dnxhr_hq - Resolve would die as soon as you try to import the file on a system based on AMD. Also it takes less CPU time and memory when using prores for AMD (i only tested this with AMD but dnxhr_hq was initially recommended to me).

Okey, the good news is: you now can use your footage without issue.
The bad news is: these fileformats are way bigger than the original files.Bildschirmfoto vom 2018-04-19 10-48-34.png
But you can alter that as mentioned above.
...so keep this in mind before trying out this workaround. ;)

Okey, I hope this How-To helped somebody.
The formats we're using here are actually pretty common in professional video production, however it's still not a big benefit but a big storage use when coming from the regular mts or mp4 files.