Archive for the 'Graphics' Category

Page 2 of 10

Screencasting

As far as I can tell, the best way to deal with inability to do good public presentations (yes, I do mean my darktable talk at last LGM) is to tame and reprogram it. For you it means a series of truly horrible screencasts with voiceovers :) The first one is out along with usual textual review to do some promo for Gpick — a real kick-ass color exploration tool for Linux and Windows.

And I think it’s time to have another look at RecordItNow in case it can unscrew screencasting on Linux just a little.

Why GIMP and Inkscape are not funded by Linux vendors

Martin wrote few days ago about why GIMP 2.8 is delayed. Apart from some annoying yet predictable mini-hatefests an interesting comment was provided by Alexander Hunziker:

One thing I wonder about is why none of the big Linux distributors steps forward and funds development. Both Gimp and also Inkscape I feel are very close to being useful also for professional designers, so just a handful of full-time developers could make a big difference. Surely, this would be an interesting market to enter into?

It’s a very valid question, and it is actually easy to answer. There are, in short, several reasons why it hasn’t happened yet.

1. Canonical already tried that back in 2004. The full story is here. TL;DR: money doesn’t magically solve everything.

2. The Linux vendors that have commercial interests (i.e. RedHat, Novell) make money on enterprise clients and governments, and their few attempts at non-enterprise desktop software (Banshee for Novell, GNOME Color Manager for RedHat) are rather personal hobbies of developers than paid projects. Entering a market means doing business with people. I’d love to see a business model around GIMP that would work for someone like RedHat.

The rest? Mandriva recently had a very instable finanical situation, followed by separation of the core team into a new project. As for Canonical, they still have problems making money and anyway they are now more focused on cloud computing which doesn’t have much place for heavy desktop apps such as GIMP and Inkscape. (As a matter of fact, three of the former active Inkscape developers work for Canonical.)

3. The teams themselves have diverse opinions on paid development. Inkscape committee is 3/4 (or 4/5?) dead against it. The GIMP team doesn’t seem to be sure: a year ago they didn’t mind, fairly recently they did mind (or so it seemed to me).

The way I see it, the future of these projects is in the hands of people who care about it so much that they are willing to work on it come hell or high water. So unless you can come up with a business model that doesn’t rely on donations, and the teams suddenly stop minding paid development, the state of affairs won’t change drastically.

Is it waving goodbye to GIMP and Inkscape? Not really. Relying on volunteers is what these projects have been doing for years, and despite the will of some people they are still around and about. A great many thanks for some of the new stuff (up to 50% in case of Inkscape) we see in the new releases of both of them goes to Google for its Google Summer of Code program.

Finally, can we get Linux vendors do at least something for the projects? Sure. They already do something actually: both RedHat and Novell are rather open about how their designers use free software: Mairin does Inkscape classes, and the whole Fedora design team uses both GIMP and Inkscape all around; Jimmac used almost complete free toolbox (GIMP, Inkscape, Blender, Fontforge) in Novell which he now does for RedHat, and now Andy Fitzsimon is in his place at Novell doing the same. It’s much less so in case of Canonical for some reason or another. Also, both RedHat (Fedora) and Novell used to publish short tutorials on using free design tools, both don’t do it much these days, so maybe they could give the initiative another go.

The important thing to understand here is that since we do eat our own dog food, we shouldn’t be shy about it. After all, not using Adobe products isn’t a mortal sin. If we don’t share excitement of using free tools, then who will?

What’s up with darktable

In case you’ve been living under a rock for last several days, darktable 0.8 is out with some important changes. There’s quite a bit of work done on the next version already, including blending modes + opacity for every darkroom mode (currently in blendops branch) and an on-canvas vignetting editor:

On-canvas vignetting editing

It’s the second darkroom mode that goes on-canvas, the first one being crop/rotation. The next one hopefully will be graduated filter.

In other words, darktable development continues in its best traditions: providing a working UI for a new feature first to get people something to use, then improving it at the next stage.

Inkscape FAQ taken to extremes

The first FAQ-like article on Inkscape I did was back in May last year and explained how to create layer effects. It looks like I missed the demand for them all this time. This is now changing. Most recent two ones published within last two weeks explain in details:

Some GIMP related things are coming too. If you feel like you want some particular stuff explained, be it GIMP, Inkscape or Scribus related, just say the word :)

Listening to users and drawing conclusions

This posting somehow complements the previous one where I quoted a couple of Audacity’s users both having diametrically opposed opninions on the tool’s usability.

Several days ago Harrison Consoles released new version of Mixbus — their Ardour-based digital audio workstation. The thread at Create Digital Music progressed quite a bit since I looked at it first, and I’ve just discovered that Paul Davis, Ardour’s lead developer, joined in and, probably not realizing it, provided the best explanation why software projects need design architects who listen to all opinions, but think about big picture first:

“Background: in the 10 years I’ve worked on Ardour, it has been my experience that listening too carefully to any one person’s experience with a given piece of technology always tends to be misleading. We have heard from people who tried Ardour and found it mostly unusable. We have others who have had years of experience with Logic or PT who find Ardour much more functional for them. Both these points of view are right, and its taken me a long time to realize that once a tool becomes even remotely complex (possibly at the point where there is any user choice at all), there’s no way to make that tool be the choice of all possible users. So these days, while I try to listen very carefully to the reports I get from people who have issues when using the software, I’ve learnt to not take anyone’s verdict (e.g. “its much harder to use than Logic”, “its ugly”, “its not mature yet”) as a comment about their specific working style and the way that Ardour fits into it rather than anything more general.”

If you take any big free software project, especially one that you bend your production workflow around, you’ll immediately stumble into X vs. Y battles. This is inevitable, but one needs to understand that any software developer who tries to please everyone usually ends up pleasing nobody, because complex software is always about vision, and visions are never shared by all of the human race, HIG or no HIG.

On intuition and habits

One of the most amusing misconceptions about software is that it can be intuitive or non-intutitive, with gradations between them. Being part of Audacity team, I’ve been receiving all sorts of feedback to our feedback email adress that we share for years. The nonsense of intuition as a notion regarding software can be easily illustrated with these two mails received with a gap of just an hour:

“Forward: Audacity is AWESOME! Absolutely love how intuitive it is and the price tag!”

“I tried the program and need to say that it is very un-intuitive. So I do not use it. Even simple tasks, like splitting a large file into several small ones (with lost cue sheet) is impossible to figure.”

C’mon people, software isn’t about intuition, software is about habits :) And speaking of habits here is another (translated) quote I can share:

“I use Inkscape. The migration from Corel [DRAW] was long and painful, I sat at nights and yelled. A month later I was thinking “OK, I think it’s usable after all, but Corel is still much better”. Two months after that I was thinking in the lines of “Yeah, it’s usable, but Corel is still better”. Then half a year later: “Well, Corel is a good vector graphics editor too.”

Parsing and viewing OLE containers

Our new reverse-engineering project, started end of last year, is progressing. We already know quite a bit about Microsoft Publisher file format, and to make this useful for Scribus team to get cracking with PUB importer, we’ll start writing the spec soon.

For ransacking .pub files Valek wrote a small tool called oletoy which is, simply put, a specialized HEX viewer with tabbed UI that reads OLE container based files and simplifies browsing chunks:

OLE toy 0.5

I’ve just pushed to Git an update from Valek that merges bits of his old(er) vsdviewer app. So oletoy is now a more universal reader of the OLE container. Right now we are not planning to work on reverse-egnineering VSD and VSS much, possible improvements are currently a middle-term goal. OTOH we do see a way to make oletoy a generalized parsing and visualization tool suited not just for OLE containers.

If you happen to have .pub files of any version (2000, 2003 and 2007 preferably) that have really crazy use of various eldritch features, we’d love to have them. Send them to alexandre.prokoudine-WE-LOVE-SPAMMERS-gmail.com.

Catching up on reading

Packt Publishing released three libre graphics related books in a row in December: “Inkscape 0.48 Essentials for Web Designers” by Bethany Hiitola, “Scribus 1.3.5 beginner’s guide” by Cedric Gemy and “Blender 2.5 Lighting and Rendering” by Aaron W. Powell. I had the first one almost immediately after release (but utterly lacked time to read) and got the second just now. Since all Cedric’s previous books were in French which I don’t speak, I’m really curious what Cedric came up with, so the Scribus book gets priority :)

Scribus 1.3.5 beginner's guide

Now, one question is how many GIMP books we’ll see this year. I know just one so far.

The more the better

As an appendix to the recent rant, the hilarious “Creative Suite for Linux” thread on omgubuntu brought this gem a couple of days ago:

“It [migration from Windows to Linux] will solve many issues. In free software community more users = more contributors. More contributors = better software. Better software = more users.”

Sounds like a dream, eh? Surely at least some of those people using free software want to contribute?

Let’s have look at download stats of Windows build of GIMP. The SourceForge page defaults to a week, and for the current timeframe (Dec 13 2010 to Dec 20 2010) it shows 379,681 downloads. That’s 380K downloads a week, boys and girls.

How about a year? 15,902,245.

So, how many new committed developers appeared in that timeframe? I mean, out of those very nearly 16 millions? 10? 20? 50? Um, no. It’s actually zero. Oh wait, I’m wrong! It’s actually -1, ’cause Martin is rather busy since last spring. The usual amount of people who occasionally do something hasn’t changed.

Now you might argue this is because typical Windows users are this and that, but seriously, there is no direct connection between amount of users and amount of contributors. You can have a very small, yet very focused community like the amazing gis-lab.info guys (sorry, it’s mostly in Russian) who work their ass off to make free GIS tools Just Work™ (and they use different OSes). And you can have a large project that doesn’t gain committed contributors at all despite of being well-known, popular, yadda-yadda… Amount of user base simply doesn’t affect anything directly.

NLE on Linux and more

I’ve been diving into screencasting and video editing lately. Sadly none of currently existing tools quite worked for me.

PiTiVi. Simple and almost all I wanted (I really am not into effects, just fades would do), but latest stable version doesn’t properly render videos that have still images. You need version from Git and most recent GStreamer.

OpenShot. Doesn’t read OGV files from recordMyDesktop, snapping is broken, overall sluggish feeling.

Kdenlive. That’s where my hope was. Doesn’t read OGV as well, but xvidcap sort of worked. Unfortunately the version I have renders heavily unsynced audio and video. In fact, depending on a codec it will render different incorrect versions of original clip.

I’ve seen some other editors and I was genuinely unimpressed.

The solution? Blender’s video sequencer. Even now I can’t believe I’m saying that. I’ve been neglecting Blender as a production tool for quite a long time. I used to say that all this soon-blender-will-do-it-all is just childish. But hey, this morning it took me about 20 minutes to twist my head around some basics concepts and then I just sat down and compiled a short clip and it all rendered like a charm.

The video in question? Oh, it’s just an early experiment :)

This page has more info on the tool, and here is wiki page on the GSoC project.