Deploying to docs from @ Dusk-Labs/dim@3ca9667b5ca9460efb6b87c208f72d8f4860ab59 🚀

master/src/dim/scanner/mediafile.rs.html

@@ -263,10 +263,12 @@
 <span id="256">256</span>
 <span id="257">257</span>
 <span id="258">258</span>
+<span id="259">259</span>
 </pre><pre class="rust"><code><span class="doccomment">//! Module contains all the code that creates and inserts basic mediafiles into the database.</span>
 
 <span class="kw">use</span> <span class="ident"><span class="kw">crate</span>::external::filename::Metadata</span>;
 <span class="kw">use</span> <span class="ident"><span class="kw">crate</span>::streaming::ffprobe::FFProbeCtx</span>;
+<span class="kw">use</span> <span class="ident"><span class="kw">crate</span>::streaming::FFPROBE_BIN</span>;
 
 <span class="kw">use</span> <span class="ident">async_trait::async_trait</span>;
 
@@ -403,7 +405,7 @@
         <span class="comment">// and does its scheduling. If a user ever needs to obtain the metadata, we can request it</span>
         <span class="comment">// and patch it immediately. This would add a initial cost to the API call, but subsequent</span>
         <span class="comment">// API calls will be cheap.</span>
-        <span class="kw">let</span> <span class="ident">video_metadata</span> <span class="op">=</span> <span class="kw">match</span> <span class="ident">FFProbeCtx::new</span>(<span class="string">&quot;/usr/bin/ffprobe&quot;</span>)
+        <span class="kw">let</span> <span class="ident">video_metadata</span> <span class="op">=</span> <span class="kw">match</span> <span class="ident">FFProbeCtx::new</span>(<span class="kw-2">&amp;</span><span class="ident">FFPROBE_BIN</span>)
             .<span class="ident">get_meta</span>(<span class="kw-2">&amp;</span><span class="ident">target_file</span>)
             .<span class="kw">await</span>
         {