Quantcast
Channel: magick Issue Tracker Rss Feed
Viewing all 1011 articles
Browse latest View live
↧

Closed Unassigned: Error when converting from jp2 format [1415]

October 17, 2016, 12:57 pm
$
0
0
I tried to upgrade from version 7.0.0.103 but got an error while trying to convert from jp2 to jpg formats. The version 7.0.0.103 works fine but does not after upgrading.

Just tested and it is working in 7.0.3.1 Sorry for the post
↧
Search

Closed Unassigned: Cannot write proper progressive JPEG [1410]

October 19, 2016, 2:07 am
$
0
0
Using Magick.NET-7.0.3.1-Q8-AnyCPU.zip I'm attempting to take an image and make it a progressive JPEG, however this isn't working as expected.

```
public static void ProcessJpegImageProgressive(Bitmap image, ref MemoryStream stream)
{
using (MagickImage mImage = new MagickImage(image))
{
mImage.Strip();
mImage.Format = MagickFormat.Pjpeg;
mImage.Interlace = Interlace.Plane;
mImage.Quality = 80;
mImage.Depth = 8;
mImage.Settings.SetDefine(MagickFormat.Jpeg, "sampling-factor", "4:2:0");

//mImage.Format = MagickFormat.Pjpeg;
//mImage.CompressionMethod = CompressionMethod.JPEG;
//mImage.SetOption(MagickFormat.Jpeg, "sampling-factor", "4x1,2x1,2x1");

mImage.Write(stream);
}
}
```
Comments: Closed due to lack of response.
↧
↧

Commented Unassigned: Mono support is missing [1359]

November 5, 2016, 12:16 am
$
0
0
If I understand well, because of the nature of accessing embedded dlls it is impossible to use the mono dllmap feature to use the library on mono.

If there would be a version which would ship the dlls as non-embedded files, it would be simple to map to the apropriate .so files on Linux.
Comments: Hello, what about Xamarin support ? would you need help with that ?
↧

Created Unassigned: Xamarin Support [1416]

November 5, 2016, 2:40 am
$
0
0
Hello, my question is whether or not the new Magick.NET for .NET Core also support Xamarin ?
↧

Commented Unassigned: Xamarin Support [1416]

November 5, 2016, 10:49 am
$
0
0
Hello, my question is whether or not the new Magick.NET for .NET Core also support Xamarin ?
Comments: Magick.NET for .NET Core does not support Xamarin at the moment. But if you are planning to help me add support for it you will only need to focus on getting the ImageMagick library compiled.
↧
↧

Closed Unassigned: Xamarin Support [1416]

November 5, 2016, 10:49 am
$
0
0
Hello, my question is whether or not the new Magick.NET for .NET Core also support Xamarin ?
↧

Created Unassigned: 'TIFFWriteDirectoryTagData' @ error/tiff.c/TIFFErrors/565` [1417]

November 28, 2016, 5:36 am
$
0
0
Hi,

I'm using magick net library to convert image from jpg/png image into tif. Besides conversion I need apply some transformation for image (Trim, SetColorProfile, Resize, etc.).
For most of images it works just well, but for some of them it throws error like:
`IO error writing tag data. 'TIFFWriteDirectoryTagData' @ error/tiff.c/TIFFErrors/565`.

This error not happens if during conversion skipped SetColorProfile step. Before similar error was for Trim, but we updated library from version "Magick.NET.Core-Q8 7.0.2.400", to "Magick.NET.Core-Q8 7.0.3.300", and it fixed problem, but now it happens for another operations. Stack trace does not told me reason of error:
`
"at ImageMagick.MagickImage.NativeMagickImage.WriteBlob(MagickSettings settings, UIntPtr& length)\r\n
at ImageMagick.MagickImage.Write(Stream stream)\r\n
at ImageMagick.MagickImage.ToByteArray()\r\n "
`
NOTE: Console tool of ImageMagick works for problematin image.

I prepared sample to reproduce the problem. https://github.com/inteno/ImageMagickTifError
↧

Closed Unassigned: 'TIFFWriteDirectoryTagData' @ error/tiff.c/TIFFErrors/565` [1417]

November 28, 2016, 5:47 am
$
0
0
Hi,

I'm using magick net library to convert image from jpg/png image into tif. Besides conversion I need apply some transformation for image (Trim, SetColorProfile, Resize, etc.).
For most of images it works just well, but for some of them it throws error like:
`IO error writing tag data. 'TIFFWriteDirectoryTagData' @ error/tiff.c/TIFFErrors/565`.

This error not happens if during conversion skipped SetColorProfile step. Before similar error was for Trim, but we updated library from version "Magick.NET.Core-Q8 7.0.2.400", to "Magick.NET.Core-Q8 7.0.3.300", and it fixed problem, but now it happens for another operations. Stack trace does not told me reason of error:
`
"at ImageMagick.MagickImage.NativeMagickImage.WriteBlob(MagickSettings settings, UIntPtr& length)\r\n
at ImageMagick.MagickImage.Write(Stream stream)\r\n
at ImageMagick.MagickImage.ToByteArray()\r\n "
`
NOTE: Console tool of ImageMagick works for problematin image.

I prepared sample to reproduce the problem. https://github.com/inteno/ImageMagickTifError
Comments: See github: https://github.com/dlemstra/Magick.NET/issues/26
↧
Search

Created Unassigned: MagickImage Write Webp error [1418]

November 29, 2016, 4:08 am
$
0
0
```
using (MagickImage image = new MagickImage(filepath))
{
image.Format = MagickFormat.WebP;
image.Write(Response.OutputStream);
image.Dispose();
}
```

Width or height exceeds limit `' @ error/webp.c/WriteWEBPImage/541

image size is 800x29856. very height...
↧
↧

Commented Unassigned: MagickImage Write Webp error [1418]

November 29, 2016, 4:38 am
$
0
0
```
using (MagickImage image = new MagickImage(filepath))
{
image.Format = MagickFormat.WebP;
image.Write(Response.OutputStream);
image.Dispose();
}
```

Width or height exceeds limit `' @ error/webp.c/WriteWEBPImage/541

image size is 800x29856. very height...
Comments: The WebP format has a limit of 16383 x 16383 (https://developers.google.com/speed/webp/faq#what_is_the_maximum_size_a_webp_image_can_be) and that is why this exception is thrown.
↧

Closed Unassigned: MagickImage Write Webp error [1418]

November 29, 2016, 4:38 am
$
0
0
```
using (MagickImage image = new MagickImage(filepath))
{
image.Format = MagickFormat.WebP;
image.Write(Response.OutputStream);
image.Dispose();
}
```

Width or height exceeds limit `' @ error/webp.c/WriteWEBPImage/541

image size is 800x29856. very height...
↧

Created Unassigned: Magick.NET-Q16-x86.Native.dll staying locked till app pool recycle [1419]

November 30, 2016, 7:05 am
$
0
0
One of the magick.net assembly is staying locked until we manually recycle app pool. I have tried all versions above 7.0.0.22 and it happens in every one of them. This is causing deployment errors.

VS 2015 Build warning
4>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(4604,5): warning MSB3061: Unable to delete file "C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll". Access to the path 'C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll' is denied.

Octopus error
Remove-Item : Cannot remove item
11:39:05Error
C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll:
11:39:05Error
Access to the path
11:39:05Error
'C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll' is
11:39:05Error
denied.

↧

Commented Unassigned: Magick.NET-Q16-x86.Native.dll staying locked till app pool recycle [1419]

December 7, 2016, 5:01 am
$
0
0
One of the magick.net assembly is staying locked until we manually recycle app pool. I have tried all versions above 7.0.0.22 and it happens in every one of them. This is causing deployment errors.

VS 2015 Build warning
4>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(4604,5): warning MSB3061: Unable to delete file "C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll". Access to the path 'C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll' is denied.

Octopus error
Remove-Item : Cannot remove item
11:39:05Error
C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll:
11:39:05Error
Access to the path
11:39:05Error
'C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll' is
11:39:05Error
denied.

Comments: The DLL is locked due to a DllImport. I have tried to see if I could somehow prevent the locking of the dll but I could not find an example for that. I would advise you to tell octopus to stop the application pool before you upgrade the app and then start it again afterwards.
↧
↧

Closed Unassigned: Magick.NET-Q16-x86.Native.dll staying locked till app pool recycle [1419]

December 9, 2016, 4:37 am
$
0
0
One of the magick.net assembly is staying locked until we manually recycle app pool. I have tried all versions above 7.0.0.22 and it happens in every one of them. This is causing deployment errors.

VS 2015 Build warning
4>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(4604,5): warning MSB3061: Unable to delete file "C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll". Access to the path 'C:\Workspace\Dev\App\bin\Magick.NET-Q16-x86.Native.dll' is denied.

Octopus error
Remove-Item : Cannot remove item
11:39:05Error
C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll:
11:39:05Error
Access to the path
11:39:05Error
'C:\inetpub\wwwroot\App\bin\Magick.NET-Q16-x86.Native.dll' is
11:39:05Error
denied.

↧

Created Unassigned: Unable to create 8-bit grayscale JPEG-2000 images [1420]

December 21, 2016, 12:37 pm
$
0
0
As I discuss in [this post](https://magick.codeplex.com/discussions/660276) and these ImageMagick forum posts (the ["Users" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=31094); as well as the ["Magick.NET" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=27&t=31095)), I am unable to successfully create 8-bit grayscale JPEG-2000 images in Magick.NET.

I __am__ able to successfully create 8-bit grayscale images via the command line in ImageMagick, so I believe the problem is not a deeper issue with ImageMagick. Rather, Magick.NET does not respect commands to change the Color.

With certain commands (see my discussion linked above in the Magick.NET forum), the JPEG-2000 metadata changes, but the file size does not change appreciably, suggesting that the actual imagery data being written is not changing. With other commands, neither the metadata nor the file size change.
↧
Search

Commented Unassigned: Unable to create 8-bit grayscale JPEG-2000 images [1420]

December 22, 2016, 8:59 am
$
0
0
As I discuss in [this post](https://magick.codeplex.com/discussions/660276) and these ImageMagick forum posts (the ["Users" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=31094); as well as the ["Magick.NET" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=27&t=31095)), I am unable to successfully create 8-bit grayscale JPEG-2000 images in Magick.NET.

I __am__ able to successfully create 8-bit grayscale images via the command line in ImageMagick, so I believe the problem is not a deeper issue with ImageMagick. Rather, Magick.NET does not respect commands to change the Color.

With certain commands (see my discussion linked above in the Magick.NET forum), the JPEG-2000 metadata changes, but the file size does not change appreciably, suggesting that the actual imagery data being written is not changing. With other commands, neither the metadata nor the file size change.
Comments: As requested [here](https://magick.codeplex.com/discussions/660276), I've uploaded a test 8-bit grayscale bitmap that reproduces the issue. It's not the same file that I've been using, but it still illustrates the discrepancy. [Here is a Google Drive link.](https://drive.google.com/open?id=0B2YsHp3KHrDrbUxCNFJFOVUyU28) When I use Magick.NET (version 7.0.3.500-Q8-x86), without setting to Grayscale, the jp2 file size is 698 KB. When I set m.ColorSpace to ColorSpace.Gray, the jp2 file size actually increases to 702 KB. When I use the ImageMagick command-line "convert" tool on Linux Mint (version 6.7.7-10), without setting to Grayscale, the jp2 file size is 698 KB (the same as from Magick.NET). When I pass the "-colorspace gray" argument, the file size decreases to 665 KB. Not as dramatic of a decrease in file size as I saw with my other file, but it still illustrates a discrepancy in the behavior of the command line vs. Magick.NET. Could it be related to the version numbers of the two libraries? Has anything changed in the JPEG-2000 encoder between ImageMagick 6.7.7-10 and Magick.NET 7.0.3.500?
↧

Commented Unassigned: Unable to create 8-bit grayscale JPEG-2000 images [1420]

December 26, 2016, 7:37 am
$
0
0
As I discuss in [this post](https://magick.codeplex.com/discussions/660276) and these ImageMagick forum posts (the ["Users" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=31094); as well as the ["Magick.NET" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=27&t=31095)), I am unable to successfully create 8-bit grayscale JPEG-2000 images in Magick.NET.

I __am__ able to successfully create 8-bit grayscale images via the command line in ImageMagick, so I believe the problem is not a deeper issue with ImageMagick. Rather, Magick.NET does not respect commands to change the Color.

With certain commands (see my discussion linked above in the Magick.NET forum), the JPEG-2000 metadata changes, but the file size does not change appreciably, suggesting that the actual imagery data being written is not changing. With other commands, neither the metadata nor the file size change.
Comments: I think this has to do that we switched from JasPer to OpenJPEG. I saw that I could reduce the size of the file if I specified the compression rate: ```C# image.Write(jpeg2000FullPath, new Jp2WriteDefines() { // Not sure what is a good value Rate = new float[] { 5 } }); ```
↧
↧

Commented Unassigned: Unable to create 8-bit grayscale JPEG-2000 images [1420]

January 3, 2017, 7:11 am
$
0
0
As I discuss in [this post](https://magick.codeplex.com/discussions/660276) and these ImageMagick forum posts (the ["Users" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=31094); as well as the ["Magick.NET" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=27&t=31095)), I am unable to successfully create 8-bit grayscale JPEG-2000 images in Magick.NET.

I __am__ able to successfully create 8-bit grayscale images via the command line in ImageMagick, so I believe the problem is not a deeper issue with ImageMagick. Rather, Magick.NET does not respect commands to change the Color.

With certain commands (see my discussion linked above in the Magick.NET forum), the JPEG-2000 metadata changes, but the file size does not change appreciably, suggesting that the actual imagery data being written is not changing. With other commands, neither the metadata nor the file size change.
Comments: That code that you provided doesn't work on my machine. I get an error message: "_The type or namespace name 'Jp2WriteDefines' could not be found (are you missing a using directive or an assembly reference?)_" Again, my Magick.NET version is 7.0.3.500-Q8-x86. I also attempted to insert the following code (hoping that it would be equivalent) immediately before the Write command. This gives no errors, but the output jp2 file appears to be unchanged. ``` m.Settings.SetDefine(MagickFormat.Jp2, "Rate", "5.0"); ```
↧

Commented Unassigned: Unable to create 8-bit grayscale JPEG-2000 images [1420]

January 3, 2017, 8:46 am
$
0
0
As I discuss in [this post](https://magick.codeplex.com/discussions/660276) and these ImageMagick forum posts (the ["Users" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=31094); as well as the ["Magick.NET" forum](https://www.imagemagick.org/discourse-server/viewtopic.php?f=27&t=31095)), I am unable to successfully create 8-bit grayscale JPEG-2000 images in Magick.NET.

I __am__ able to successfully create 8-bit grayscale images via the command line in ImageMagick, so I believe the problem is not a deeper issue with ImageMagick. Rather, Magick.NET does not respect commands to change the Color.

With certain commands (see my discussion linked above in the Magick.NET forum), the JPEG-2000 metadata changes, but the file size does not change appreciably, suggesting that the actual imagery data being written is not changing. With other commands, neither the metadata nor the file size change.
Comments: You will need to upgrade Magick.NET to get that new feature. I added the Jp2WriteDefines because of this issue that you created. If you want to stay with the old version you should use `rate` instead of `Rate` in the define. The defines are case sensitive.
↧

Created Unassigned: Insufficient memory (case 4) [1421]

January 6, 2017, 6:43 am
$
0
0
Hi,

I'm using Magick.net in a very high volume multi threaded photo processing application. I see random errors like below. This usually on photos that are larger, I have to deal with JPG files that are sometimes up to 40 megabytes in file size. But, i can see errors like this even on 5 megabyte files. The servers have plenty of memory. Is there anything i can do to avoid this other than forcing the application to only process one photo at a time?

I am using Magick.Net-Q16-AnyCPU version 7.0.3.902


ImageMagick.MagickCorruptImageErrorException\",\"Message\":\"Insufficient memory (case 4)
at ImageMagick.MagickImage.NativeMagickImage.WriteBlob(MagickSettings settings, UIntPtr& length)
at ImageMagick.MagickImage.Write(Stream stream)
↧
Viewing all 1011 articles
Browse latest View live
Search