Sorry, you need to enable JavaScript to visit this website.

Guidelines for contributors

First, make sure you read our mission statement.

Type of content

Our main interest for new content is Articles and Tutorials.

Articles: An article deals with a specific subject and describes for example the technology, inner workings, artistic decisions etc.

Tutorials: A tutorial describes HOW to do something, for example, you start at point A and show steps to get to point B.

For other details about contribution content, please read - How to contribute to Libre Music Production.

Text

The text should start with a short introduction where you describe what the article/tutorial is about and what the user will accomplish by following it.

Content must be written in English, Make sure you run it through a spell checker before submittting. If English is not your first language, we can proofread any text if you feel you need help in polishing it off.

We use a maximum of two levels of headings (which are translated into "Heading 2" and "Heading 3" in HTML). So, don't use too many sub-headings or the stuff will be difficult to read.

A rough rule of thumb for articles and tutorials is that they should aim to be between 2000 and 2500 words.

Where relevent, content should link to terms and technical mumbo-jumbo in our Jargon Buster/FAQ sections. This only needs to be done once per page and links should be created the first time a term is used. If you mention software that is included in the Tools section, you should also create a link to this.

Please scan these sections and makes notes in your text of possible links:

Images

Both articles and tutorials should be illustrated with images.

Use the PNG format for graphics and screen dumps.

Photos can be submitted as JPGs.

All images should be 600 pixels wide. Height is dependent on the image content itself but where possible, images should be approx 400 pixels high.

If you are making graphics to explain things (and we like that), please use the following resources:

Large files

If you have large files (movies) that you want to include, please contact us.

Movies/screen casting

  1. Record your screen and audio using SimpleScreenRecorder.
  2. Put your various recordings into the KDENLive template. Arrange and edit accordingly. Add explanatory titles and text.
  3. If necessary, export the video uncompressed, load it in Ardour, and process the sound to your liking.
  4. Export the video with these settings: Full HD, 1080p (1920x1024), 25fps.

Putting it all together in Kdenlive

  1. Install Kdenlive. Check out the tutorials at http://userbase.kde.org/Kdenlive/Manual if you are a beginner.
  2. Create a project folder for the videos. Let's call it "lmp_videos".
  3. Download the Kdenlive template but do not extract it.
  4. Also download the Titles template and extract it into "lmp_videos".
  5. Fire up Kdenlive. Open the Kdenlive template ("lmp_video_template.tar.gz"). Kdenlive will ask you where to extract it -- chose "lmp_videos". While extracting, you will probably get a question about paths; adjust them using the "Search recursively" button. (http://userbase.kde.org/Kdenlive/Manual/Projects_and_Files/Archiving)
  6. "Install" the title template by chosing Project > Add Title Clip. In the dialog, click the "Open Document" icon and select the document in the folder extracted in step 4 ("text.kdenlivetitle"). (http://userbase.kde.org/Kdenlive/Manual/Titles#Template_Titles)

The template contains 7 tracks:

  • title (video) - for the title of the video. Edit the "Title - intro" clip at about 5 seconds to change the title of the video.
  • intro video (video) - the intro animation. Do not edit.
  • intro music (audio) - the intro music. Do not edit.
  • text (video) - here goes your text boxes (see below)
  • video (video) - here goes your screen capture
  • music (audio) - here goes any music featuring in the video
  • voice (audio) - here goes the voice of the video

Adding text boxes:

  1. In the Project Tree, right-click and select Add Template Title.
  2. Select template "text.kdenlivetitle" template. Press OK button
  3. In the project tree you now have a new clip, "Template title clip".
  4. Double click the name ("Template title clip") and rename it to our standard "text - xxxx".
  5. Right-click the clip and select Clip Properties. Enter the text that should go into the text clip. As the template doesn't handle word wrapping you have to do that yourself with the Enter key.
  6. Drag the clip to the correct place on the "text" track.

Rendering

Rendering means making a movie of it all.

  1. Menu: Project > Rendering.
  2. Select the tab Render Project.
  3. Settings: MP4, video: 12000, audio: 128.
  4. Set Output File and press Render to File.

Creating custom youtube thumbnail

  1. Take a screenshot of your video. Crop your final image to a 16:9 ratio. Zoom in if necessary, eg. if you are demonstrating a plugin, crop in on the plugin.
  2. Download and extract the Inkscape template
  3. Open up youtube-thumbnail.svg in Inkscape, then import your screenshot (File > Import). Resize your screenshot to 1280x720 if necessary. 
  4. Select your screenshot image and make sure that it is set to the bottom layer (Layer > Layer to bottom)
  5. Go to Layer > Align and Distribute. In this dialog, select page from the 'Relative to' drop down menu. Making sure your screenshot image is selected, use the 'align left edges' and 'align bottoms edges' buttons. This will make sure it is centred on the canvas. 
  6. Double click on the text and highlight it. The text can then be edited. Try to keep the description brief and don't change the font size. Also, use caps for this description. The template uses the OSP-DIN font. Make sure this is installed on your system.
  7. Go to File > Export PNG Image. Make sure the export area is set to 'Page' and that the image size is set to 1280x720. Set your export location and press export. 

Upload

See "Large files" above.

Philosophy of LMP

Any material submitted to LMP must reflect the aims and objectives of the website, and so must respect the following -

  1. Has to relate to, or demonstrate FLOSS software
  2. Can't promote proprietary software

LMP specifically caters towards FLOSS audio software, something which we feel is under-represented in the audio field. We are trying to fill this niche and feel that mentioning anything other than the FLOSS software, and it's related philosophies, which we are trying to promote would dilute our intended goals.

License

All content on LMP is published under a Creative Commons Attribution-ShareAlike 4.0 International License.