36-image converter and large images


As most 36IC users already know, 36-image converter can’t edit images bigger than the screen resolution minus 20 pixels, eg. 1.400×830 = max. size of 1.380×810 pixels. Many people have been wanting a fix for this problem, but there isn’t any except for 36-image express which allows conversion of bigger images, but isn’t as advanced as 36IC. So when will it be fixed?

In our next version (4.7) coming in the fall of this year, we will include tools to batch convert/resize/rename images of any size. This will be the first step. In version 5.0 this issue will be resolved completely and you will also be able to edit/convert and save images in the default editor. But this won’t happen anytime soon.

The current editor of 36-image converter is too complicated to support images bigger than the screen resolution, the entire application has to be rewritten. That’s why we created 36-image express, 36Ix is build to support large images and to be much lighter. But at the moment 36Ix is still lacking a lot of features and is actually a development version of 36-image converter 5.0 which is publicly being tested and incrementally being improved.

So first we have to complete 36IC 4.7, then we have to update 36Ix with the new CIPU conversion engine from 36IC and make it more stable, then we can begin improving 36Ix step by step to support all functions of the current 36-image converter and to support advanced image editing features like editable layers. Then 36-image converter 5.0 will be build on top of 36-image express. So we can proceed the 36IC development with the same care we used for developing 36Ix.

So in a while 36-image converter will support large surfaces, but it will not be for 2009. Even we are waiting for a stable core to continue the development of 36-image converter. But as always when we fix the size issue, the 36IC users will find something new to rant about on CNET, that’s why all coming versions of 36-image converter and 36-image express will have the Reasonable Feedback Agreement in the EULA, like 36Ix does. In this way we can at least protect all future version of 36IC against idiotic comments and even sue the people who do.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s