[With apologies for X-posting]
Hi all,
Recently I had posted on my blog ("Making change happen - the case of the IOTA job ad" - http://indradg.randomink.org/blog/archives/150) how the Institute for Open Technology and Applications (IOTA - the autonomous society setup by Dept of IT, Govt of WB) had originally posted a job ad asking for multimedia developers for CBT development with work experience on proprietary tools. Upon the intervention of the Minister-In-Charge IT (Prof Debesh Das) this changed asking for expertise in FOSS tools alone.
Today I received an email which puts an interesting twist and probably runs the risk of jeopardising the above decision to move to FOSS for CBT development.
A multimedia expert who's highly proficient in proprietary software for multimedia authoring was asked to create a feasibility plan for development of the CBT using FOSS tools, and his report is as follows. I figured it would be interesting reading for a lot of people, so I’ve shared it below.
=== THE REPORT ===
I have gone through the most recommended open source software in Linux, to be used as substitutes of the commonly known graphics related software. On basis of the requirement for CBT development project, I have performed dry-run of some test cases. The results from those trials can be stated below.
GIMP (as a substitute of Photoshop)
- No option for true resembling of bi-cubic to bilinear conversion
- Many of the layer comp option cannot be found
- Antialising is poor
- Many of the color correction tools are absent
- Cannot share GIMP comp with INKSCAPE comp and UIRA comp layer wise
- Smart object facility is not available
(There are several other problems are there in GIMP, but those are not mentioned here, only some of the points very much linked with the work procedure of CBT development are mentioned here)
INKSCAPE (as a substitute of Illustrator)
- EPS quality and standard of vector is not up to standard
- Cannot share INKSCAPE comp with GIMP maintaining vector property
- INKSCAPE drawing cannot be used properly to animate with UIRA
- Vector layers cannot be managed with UIRA
- Rasterization of Vector , maintaining transparency and smooth edges cannot be done
(There are several other problems are there in INKSCAPE, but those are not mentioned here, only some of the points very much linked with the work procedure of CBT development are mentioned here)
F4L (as a substitute of Flash)
- F4L is no more
- It is now converted into UIRA with a blend of QFlash
- Both of them are not so professional
- Crashes anytime and almost every time
- Smart clip and nested movie clip system is unstable
- Symbol definition is not OK
- Action script is full of bugs
- File compatibility is not even good
- Authoring property is very bad
- Compatibility with running text in local language is very bad
(There are several other problems are there in F4L, but those are not mentioned here, only some of the points very much linked with the work procedure of CBT development are mentioned here)
KINO (as a substitute of Premiere)
- Codecs are very poor
- Conforming process frequently crashes
- Lightweight screen captured video cannot be edited properly
- Unsafe rendering
- Unwanted loss of project data in time of save and reopen
- Voice-over cannot be taken in form of dubbing
- A little bit long timeline often crashes
(There are several other problems are there in KINO, but those are not mentioned here, only some of the points very much linked with the work procedure of CBT development are mentioned here)
Audacity (as a substitute of Audition)
- Codecs are very poor
- Conforming process frequently crashes
- MP3 cannot be edited properly
- Unsafe rendering
- Cannot be converted into MP3 properly
- Too few tools to operate
- Recording in full duplex cannot done properly
- Dubbing facility is not available
(There are several other problems are there in Audacity, but those are not mentioned here, only some of the points very much linked with the work procedure of CBT development are mentioned here)
=== END OF REPORT ===