KeithM At Home.

on the web since 2010.not retro.just old-fashioned

monoVeon: monochrome Foveon X3F Convertor for Sigma ( and Polaroid ) Digital Cameras.

Overview.

• By summing the raw RGB pixel values, monoVeon effectively creates a monochrome sensor.
• Pixel values are not multiplied to apply above-base ISO settings, giving access to increased highlight headroom.

• No 'multiple pixel' processing is carried out on the raw data ( no luminance or colour noise reduction ).
• No processing of colour images to standard colour spaces.
• Colour images in single file or split into separate RGB files.

Due to the stacked design of the Foveon X3F sensor, summing the RGB unprocessed raw values at each pixel effectively creates a monochrome sensor. Colour output is also available. This is intended mainly for those who are curious to see what the digitised sensor output actually looks like, but it may also be used as a somewhat desaturated colour source for creating images.

Workflow.

• Batch processing with no user input required during conversion.
• Output images can have consistent output range.

monoVeon was written to provide an easy link between raw Foveon X3F files and 16bit image editing. Like many, I started by using Sigma Photo Pro where you can batch process images but not with individual settings. In my workflow, I like to start with a consistent image ( 16bit monochrome with image values placed between known black and white values ). Working each image individually in SPP to create a consistent output is a mechanical, repetitive task which computers are very good at doing on their own!

monoVeon is a program which performs that repetitive task as quickly as possible. You are then free to spend more time doing the creative work in the image editor of your choice.

History, download and future thoughts.

The application was designed with the aim of providing a means of quickly converting a number of image files, with no user input required during the conversion process. The interface is a simple application window. X3F files to be converted are assembled into a list and an optional output target directory specified. The files are then batch converted using the options set in the Options Dialog.

This version of the application is written using the Microsoft .Net 1.1 Framework. This Framework has to be present before installing and running monoVeon. If you do not have the Framework installed, you will need to download it from Microsoft. As of February 2010, it could be found with this Microsoft Search. After installing the Framework, it would be advisable to run a Windows Update to ensure it is patched up to date.

The installation files, along with a ReadMe First file are contained in a single Zip file. To install - download the zip, unzip to a suitable location and run setup.exe. During installation, you are asked to agree to a EULA. It would be impossible to enforce the EULA, but please treat it as an expression of my wishes concerning the use of monoVeon. monoVeon is being offered as Freeware in that no payment is required for it's use, there is no limit to how long you can use it and there are no nag screens. You are also free to re-distribute it as long as the EULA remains intact and the files are un-modified.

Changes made to first release:

• Bug fixes:
  • Previous errors now cleared in Error reporting
  • Will now open read-only source files.
• Modifications:
  • Destination Folder can now be left blank - each output file will be saved to the same folder as the source file.
  • Selectable behaviour if output filename already exists. If set to not overwrite existing files, the output filename is incremented until an unused name is found.
  • Preemptive checking that the Destination folder is writeable.
  • The conversion settings used can be saved to a text file for reference. If combined with the option to not overwrite existing files, this maintains all conversions in the order they were created.
  • Added link to this website in Help menu.

• Second Release 9th March 2010

Changes made to second release:

• Bug fixes:
  • Corrected version checking for SD9 cameras.
• Modifications:
  • Variable Black and White points for limited output value range.
  • Auto-Start Conversion with options for selecting which Add Files method triggers an auto-start conversion.
  • Date/Time of exposure and camera model name optional in output filenames.
  • Added support for Polaroid x530 ( test image kindly made available by Arvo Jägel ).
  • Improved conversion speed when scaling image values.
  • Installer now removes previous version. I hope this works OK... we are at the mercy of Microsoft on this one !

Latest release:

• Download monoVeon for Windows ( 238KB )

Current ToDo list:

• Recompile application under .Net 3.5.
• Embed Exif data from Property Block into output Tiffs.
• Optional graphical interface for viewing and selecting source files by thumbnail.

monoVeon is only currently available as a Windows application. I am, however, currently learning Cocoa/ObjectiveC programming with the intention of producing an OS X version. This may take me a little while though.

Tested cameras and Operating Systems.

The table below summarises how many images have been converted from a particular camera under which Operating System. I plan to add a Feedback page soon, one purpose of which, if any users would be kind enough to do so, will be to report success or failure with cameras and Operating Systems.

I would like to thank the members of the Sigma SLR Talk forum on dpReview for providing feedback on monoVeon. This has expanded the number of tested combinations of cameras and operating systems.

Source Code.

Parts of the source code for monoVeon will be published with the doumentation of monoVeon, for those who are interested or engaged in similar projects. The documentation also includes a breakdown of the decompression used for the Sigma series of cameras:

• Inside monoVeon

The program was written in Microsoft Visual Basic .Net 2003. I make no claim to be an elegant programmer or that my code makes full use of the Visual Basic environment. The code has developed as I wrote the application from the top down and early decisions may not have been the best. If nothing else, the code should allow you to see the detailed program flow which may be re-written far more succinctly.

Page Last Updated: 20th April 2010, Maintained by KeithM.