Multimedia Workflow on GNU Linux

Whilst you wait for the dependencies to compile and install, you may as well read about workflows on open source.

Slackermedia is a blank canvas. There is not one “right” way to create and use your Slackermedia system. While Slackermedia does divide packages into broad sets, there is no pre-set that says “install this if you want to make music” or “install this if you want to make videos” and so on. The quandry that a new user faces is knowing what major applications to install to meet their artistic needs.

In other words, this chapter contains a bunch of advice, which, as the cliché goes, is the one free thing in this world that no one really wants. You don't really want to read this chapter; you want to get on with using Slackermedia. However, unless you've got experience as a production co-ordinator, this chapter will probably do you some good. Think of it as the green vegetables of Slackermedia and give it a read not because it's all that good, but because it's good for you.

Different disciplines have different methods of creating content, and different people work in unique ways. However, there are common elements from any production to another, and the basic methodology of getting a production from idea to finished product is called the “workflow”.

The term “workflow” refers to the entire process of production, not just what happens in the computer system being used on the project. However, since so much of modern production happens on a computer, the computer workflow is a often a determining factor in how the rest of the production will happen. It is important, therefore, to understand certain unique aspects of the Free Software workflow.

Much of the GNU workflow is defined by its inherent modularity. This is very different than the popular tendency to consolidate broad functionality into one “one-stop shop” application. They are two different philosophies that are not really exclusive of one another; it makes sense to keep different tasks confined to specialized applications because this divides work among many applications and makes troubleshooting much easier, but it also makes sense to have an application designed to a specific goal to also include capabilities to complete all the steps required to achieve that goal.

For instance, why include video ingestion and conversion components in a non-linear video editing application when it would make more sense to offer specific importing applications for each different kind of video that an editor might need to import?

On the other hand, including basic video effects in a non-linear editor makes sense, because basic effects are common, and they can require frequent adjustment, and their inclusion saves the need for a round-trip out to another application.

Same goes for photographic applications; if a photographer works in realistic photos, then watercolour emulation and fancy effects are just so much bloat.

As you can see, there are many times when the modular approach makes more sense than the monolithic. There is an immediate convenience sometimes with the monolithic; depending on how well-structured your workflow is, you may find yourself confounded when you suddenly have to find a new application to do a task that you'd never had to do before. While in a monolithic application, the solution to that may be found in a sub-menu of the sub-menu of a menu, in the modular approach you may be faced with no hint or indication of where to turn.

However, these are mere growing pains that are eliminated once you've found the solution; they tend to happen only once: the first time you are faced with the issue that requires a new solution. And in the mean time, you have no need to deal with bloated software with more menus and features than you can ever hope to either understand or use.

It's important that you approach your workflow carefully and deliberately when setting up your multimedia studio. Simply throwing together a collection of applications that are tagged as “multimedia” or “graphics” or “audio” is not the correct solution in GNU Linux any more than it is on blackbox vendor software. The artists knows best what they need from a computer, so the artist should determine what should be on the computer in order to get the work done.

If you have never served as a producer (or in software terms, “project manager”) before, then this concept may be new to you, so we will review it here.

1. List all of the major tasks you are expecting to do on the computer system. Use general, broad terms here, such as “edit video”, “retouch photos”, “motion graphics”, “clean up audio”, and so on.
2. Do a second pass of this list for the specific steps involved in each major task you wrote down for the first step. For example, a video editor might list: log footage, review all footage with video player with variable speed control and spreadsheet for notes, organize, organize by scene number and take number, edit, sync sound and color correction tools, print to full quality, re-edit, rinse and repeat. A separate list might expand this to include motion graphics: acquire specs fom director, create assets, animate, basic render for approval,beauty render for delivery, integration into final edit. A third list might detail the audio needs, a fourth the visual effects, and so on.
3. Do a third pass of your list(s) and assign known software applications to each task, at least prospectively.
4. Do some research to learn what application will address each list item.
5. Make sure that everything you need to do can effectively be achieved with what is available to you. Be prepared for many different applications to surface in the Free Software world; due to the modular nature of its design, it's only natural that there will be a software application just capture video from a deck, or a separate application from your graphic design application just to change color space and compression settings, and so on.
6. Take the time to learn the new software. Switching to a new OS (Linux or otherwise) in mid-production or when there are deadlines on the horizon is a bad idea. You are changing the tools and the operating system underneath those tools; you need time to spend in the new applications in order to learn them.
7. With the help of Slackermedia, build your Slackware GNU Linux system according to the requirements you have specified in your list.

Habits are notoriously hard to break. If ever that was true, it's true in computing. Computer history is rife with deprecated technology being forcibly prolonged well past their natural life spans. As users, we tend to cling to not just the application that we know best, but even the way we do specific tasks. After all, why would anyone willfully use a new application where it takes them a minute to complete a task when their old familiar application could do it in ten seconds?

Of course, the answer is that new technology is an investment. At first, learning even the landscape of multimedia on Linux will slow your productivity, to say nothing of learning each new application that you adopt. However, to use it is to learn it, and once you have learnt the applications, your productivity does not just reach the same level as before, but skyrockets past anything you thought possible, and in many new directions.

That said, the initial steps are confusing, since even if you know what applications are available for you to use, you probably don't know which ones will actually work for you.

While Slackermedia itself will help you find many great multimedia applications, and the very contents of http://slackbuilds.org and http://studioware.org will suggest applications to try, there are also package lists for multimedia distributions like Ubuntu Studio, which will at least give you ideas of applications that you should investigate and try for yourself.

Certainly. the ultimate answer to “what applications should I use?” is best answered by using applications. Try the ones that appeal to you, whether from recommendations and reviews, or by screenshots, or from examples of works completed within those applications.

The harder question to answer is how it all fits together.

As with building Slackermedia itself, there's no right way to use the applications within your studio. However, having no idea of what is possible is a lot different than having a clear picture and choosing to modify it; before you can get creative with how applications fit together to help you create great art, you need to know how they're meant to fit together.

To this end, there are sample workflow ideas available at http://slackermedia.info/workflows.

foobaz Some vendors bundle their closed source applications along with gigabytes of extra content for their customers to use. While many of these kinds of assets you should be able to continue to use (after all, a font is a font, and a graphic is a graphic), if you don't have them then you aren't going to get them with an operating system and application set with no budget to bundle such things. However, the internet is hard at work to solve this .

Free Software lacks the luxury of having gigabytes of licensed content to
ship along with their software. Again, this is a double-edged sword that
has the benefits of cutting download size by orders of magnitude, and also
fights the pre-fabricated feel of art produced on Free Software as opposed
to the off-the-shelf solutions, but means that when you do need some extra
raw materials, you must go out and find the content yourself.

Sites like flickr.com , freesound.org , and openclipart.org are veritable
bastions of free culture, offering Creative Commons content for easy
download.

To further address this need, the Slackermedia project itself gathered
supporters from around the globe to do an initial crawl of the Internet to
find free raw materials for artistic endeavor (such as fonts, clip art,
sound banks, and so on). The content can be found as a torrent file on the
Slackermedia.info website.