free
/
freedombonee
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Advice on file format

This commit is contained in:
Bob Mottram 2016-12-26 10:54:13 +00:00
parent 24bee4265c
commit a85ffc6c81
2 changed files with 45 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/EN/app_mediagoblin.org
View File

@ -45,3 +45,17 @@ If you have just obtained a Lets Encrypt certificate as above then go to *About*
Create an account and verify it by returning to the *user control panel* opening the email client and looking for the Mediagoblin verification email. It will contain a link that you should follow to activate the account. Create an account and verify it by returning to the *user control panel* opening the email client and looking for the Mediagoblin verification email. It will contain a link that you should follow to activate the account.
You should repeat that for however many accounts you want on the system and then go back to the *administrator control panel*, select *App Settings* then *mediagoblin* and turn off new registrations. This will prevent millions of spam accounts from being created by internet bots. You should repeat that for however many accounts you want on the system and then go back to the *administrator control panel*, select *App Settings* then *mediagoblin* and turn off new registrations. This will prevent millions of spam accounts from being created by internet bots.
* File formats
It's a good idea to upload videos in /webm/ format. In that case Mediagoblin will skip the transcoding step (which can take hours for videos of non-trivial length) and the whole process will be quicker. Transcoding just converts whatever file format you submit into a standard resolution and file type. On your local system you can convert a video to webm with:
#+begin_src bash
ffmpeg -i myvideo.mp4 myvideo.webm
#+end_src
Or if you are moving a video from YouTube to your own site:
#+begin_src bash
youtube-dl -f webm [my_video_url]
#+end_src

38
website/EN/app_mediagoblin.html
View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head> <head>
<!-- 2016-12-25 Sun 11:54 --> <!-- 2016-12-26 Mon 10:53 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title> <title></title>
@ -255,9 +255,9 @@ With Mediagoblin you can host video and audio content in a similar manner to the
When hosting media files you should take into consideration that since anyone on the internet can view your content then this could significantly increase your bandwidth usage and overall strain on the server. If you are hosting anything which might become popular then it's a good idea to set up the Freedombone system on an old laptop rather than something like a Beaglebone Black. However, as small single board computers become more powerful with more RAM and CPU cores being able to stream media to many clients should be far less of a problem. When hosting media files you should take into consideration that since anyone on the internet can view your content then this could significantly increase your bandwidth usage and overall strain on the server. If you are hosting anything which might become popular then it's a good idea to set up the Freedombone system on an old laptop rather than something like a Beaglebone Black. However, as small single board computers become more powerful with more RAM and CPU cores being able to stream media to many clients should be far less of a problem.
</p> </p>
<div id="outline-container-org8d1d522" class="outline-2"> <div id="outline-container-org11c3839" class="outline-2">
<h2 id="org8d1d522">Installation</h2> <h2 id="org11c3839">Installation</h2>
<div class="outline-text-2" id="text-org8d1d522"> <div class="outline-text-2" id="text-org11c3839">
<p> <p>
Log into your system with: Log into your system with:
</p> </p>
@ -282,9 +282,9 @@ After the install has completed go to <b>Security settings</b> and select <b>Cre
</div> </div>
<div id="outline-container-orga30e9ca" class="outline-2"> <div id="outline-container-org6c142c0" class="outline-2">
<h2 id="orga30e9ca">Initial setup</h2> <h2 id="org6c142c0">Initial setup</h2>
<div class="outline-text-2" id="text-orga30e9ca"> <div class="outline-text-2" id="text-org6c142c0">
<div class="org-center"> <div class="org-center">
<div class="figure"> <div class="figure">
@ -306,6 +306,30 @@ You should repeat that for however many accounts you want on the system and then
</p> </p>
</div> </div>
</div> </div>
<div id="outline-container-orgadacbc6" class="outline-2">
<h2 id="orgadacbc6">File formats</h2>
<div class="outline-text-2" id="text-orgadacbc6">
<p>
It's a good idea to upload videos in <i>webm</i> format. In that case Mediagoblin will skip the transcoding step (which can take hours for videos of non-trivial length) and the whole process will be quicker. Transcoding just converts whatever file format you submit into a standard resolution and file type. On your local system you can convert a video to webm with:
</p>
<div class="org-src-container">
<pre class="src src-bash">ffmpeg -i myvideo.mp4 myvideo.webm
</pre>
</div>
<p>
Or if you are moving a video from YouTube to your own site:
</p>
<div class="org-src-container">
<pre class="src src-bash">youtube-dl -f webm [my_video_url]
</pre>
</div>
</div>
</div>
</div> </div>
<div id="postamble" class="status"> <div id="postamble" class="status">