Atalasoft DotImage Photo Pro - Opiniones

Descripción | Precio y licencia | Evaluaciones y descargas | Compatibilidad | Datos del autor | Opiniones | Foro | Resumen

Opiniones de clientes

Opinión media:  basada en: 5 opiniones.

chris [USA] 04-Jun-2008Opinión: 

We have purchased the DotImage Photo Pro mainly because of its ability to deal with many Raw image formats. While most of the images are able to be read by DotImage Photo Pro, some of the image formats that they claim to support do not work well. When processing images from the same camera, not all images can be recognized: some of the images cannot be loaded at all, or have a funny color no matter what color table or rendering method is used, and some of the loaded images' meta information can not be read properly. Some of the Raw images we were trying to load even caused fatal exceptions when using their provided class to test for compatibility.

To make matters worse, their support does not response to trouble tickets well. I have submitted a support case for over 10 months, to this date there is still no resolution to the problem. They posted responses for my ticket in the beginning, but after 3 months my ticket has still not been resolved and the ticket just seems to be forgotten or ignored even though I have provided detail information describing the problem (including code samples and image samples). I have posted follow up notes on my ticket every month or so, till this date I am still waiting for their response. Maybe they are waiting for me to give up and pass down the problem to my end user to deal with, who knows. I can't see how they "take pride" in their level of support and quality of product as in one of the "Reviews" left by their staff below.

To be fair, I have only used their Raw image decoder and Exif processor. While both of them have problems, I can't comment on the quality of other components included in their suite. Maybe they provide better quality on their other components. If you are looking to process Raw images with their suite, please be aware - even though their Raw decoder supports many formats, your chances of success is hit or miss. Unfortunately this is the only royalty-free Raw image process component available as of now, otherwise we would probably be looking somewhere else for a solution.

tltaylor [USA] 21-Nov-2006Opinión: 

We are more than just users of .NET components, we are component developers ourselves. The number one thing I can say about Atalasoft is their desire to support and please their customers! We purchased DotImage, DotAnnotate, DotTwain, and the PDF Rasterizer. The DotTwain product made short work of our scanning needs and worked extremely well. We also had the need for PDF support within our imaging application and we tested a number of different products, all of which were much slower than Atalasoft's PDF Rasterizer. Additionally, there is seamless integration between the imaging controls and the PDF decoder making it very easy to display or create previews of a PDF document.

Aside from Atalasoft's desire to support their customers, the number one benefit of their imaging products is the royalty-free run-time. There were two deciding factors in our purchase of Atalasoft: Royalty-free licensing and the fact that their assemblies were 100% managed .NET. Many of their competitors just provide a .NET wrapper around unmanged DLLs.

If you are looking for an imaging tool, I definitely recommend Atalasoft.

tltaylor [USA] 19-Jul-2006Opinión: 

We are more than just users of .NET components, we are component developers ourselves. We have a medical product that had the need for imaging and scanning support. We did not want to take the time to develop these controls ourselves as we had no desire to get into this market. We evaluated many imaging products. I liked the fact that Atalasoft was all .NET. Moreover, I really liked the fact that they were run-time royalty free. This clinched my decision to go with Atalasoft. Immediately after purchasing a single license of the DotImage, DotAnnotate, DotTwain, and PDF Rasterizer I began having trouble. Their website stated that their PDF viewer was faster than Adobe, which was not the case (.5 to 1.5 seconds per page to load). The speed was nowhere close to Adobe's. In Atalasoft's defense though, the reader was much faster than many others that I downloaded and tried. They have many asychronous abilities, but none that work 100% properly with .NET 2.0. Since source code does not come with the product, another issue I have with the product, it is difficult to say exactly what is happening for sure. But I know for a fact that it has to do with improper use of delegates. Cross-thread violations will occur all over the place. So I created thread safe wrappers for the viewer and thumbnails which resolved most issues. Another problem occurred with the TextAnnotation (sticky note) annotation class in the DotAnnotate product. The nice thing about the DotAnnotate was that I could create a custom annotation class that allowed me to work around the problem. But once I did I had another issue with saving and loading the annotations. Since my custom annotation was in a class library, their code would not properly load the annotation even when specifing the AssemblyType. These are just a few of the irritations I ran into working through the project.

The DotTwain product was by far the best of the their products that I have used. I had few issues and it really did make relatively short work of interfacing with TWAIN devices.

In short, I have not been very pleased with the controls as a whole and I have spent a lot of time working around the shortcomings within the product. With that being said, I think I would still purchase the controls and go through the same process again since it would still take longer to write all of the pieces myself than it took to correct the problems with wrappers. Also, once I got the wrappers created things leveled out. Additionally, it is run-time royalty free which makes it worthwhile to me even if there were some frustrations along the way.

Bill [USA] 18-Aug-2005Opinión: 

We at Atalasoft take great pride in our level of support and quality of our products. This customer apparently wasn't happy with response times that averaged just a few hours, and a resolution to his reported problem about 3 months later. Many cases that this customer opened were extremely vague, and our response was to please provide more information. The customer never replied to some of these cases. The severety of the problem this customer is referring to was not deemed mission critical. The exact nature of the problem was that viewing an image in our thin-client image viewer control that was smaller than the viewport caused the image to be positioned in the upper left corner of the control instead of being centered. This issue required some rework to the code, which we did and implemented in the next version less than 3 months from the reported date. Other issues that were reported were resolved same business day, including at least in one case sending a javascript hotfix to resolve the problem.

After learning that this customer being disatisfied with our support, I personally called the customer, and had an amiable conversation with his supervisor. I encourage anyone who is evaluating our products to call us and talk to our support team, or send support requests via our web portal in order to rate our level of support which we take great pride in.

Bill Bither
President

waynesellars [USA] 24-Mar-2005Opinión: 

I honestly have to say that our company as a whole uses about 20 different .NET controls in our products. Some are expensive and some are free. None of them are perfect and of course some are worse than others. However, hands down the Atalasoft DotImage Pro component was the most expensive and the worst of all of our controls in all categories (bugs, value, and support). The problem is we needed the functional that only they (at this time) are attemptin to get to work and there are so many problems I don’t even know where to begin. Every time I tried to get support I just got an answer of either yeah we know about that or your code looks fine to me, no real assist there.