Error At Scanline
TiffAppendToStrip errors with uncompressed output [SOLVED] Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Jukka I downloaded and converted your test VRT file to a single Geotiff without any problems - on Linux... Conversion took a few minutes on a fast server. Just a guess, but in my opinion this problem is related to the limited memory handling capabilities of Windows. It does not seem to be a shortage of total memory but more a sort of memory "fragmentation". Windows is not able to provide a contiguous block of memory that is required by some software in some cases. Some time ago a colleague had this type of problem when working with IDL scripts, it worked fine on Linux or Mac OS, never on Windows with larger datasets. On Windows, working with large datasets and gdal (especially compressed and VRT) or allowing gdal_translate to use more memory via GDAL_CACHEMAX config, caused always problems for me. So I stopped trying this... On Linux I can easily work with VRT files that reference several 100's of GB. There on Linux however, higher settings for GDAL_CACHEMAX were speeding up conversions noticeably when working with lots of tiles, especially when they were compressed Tiffs. So I can just recommend, if feasible, to try out Linux or any type of Unix for your processing and see if the problem disappears. Greetings Armin On 08/05/2012 14:32, Jukka Rahkonen wrote: > Jukka Rahkonen
♦ ♦ Locked 6 messages Rahkonen Jukka (Tike) Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ [gdal-dev] TiffAppendToStrip errors with uncompressed output Hi, I have some LZW compressed paletted 8-bit tiff files which I look throuhg a .vrt file. I have been taking some timings with different gdal_translate parameters but for some reason the most common command fails always for me. The result is gdal_translate -of GTiff test.vrt http://lists.osgeo.org/pipermail/gdal-dev/2012-May/032714.html uncompressed.tif Input file size is 96000, 48000 0...10...20...30ERROR 1: TIFFAppendToStrip:Write error at scanline 14650 ERROR 1: TIFFAppendToStrip:Write error at scanline 14650 ERROR 1: An error occured while writing a dirty block ERROR 1: TIFFAppendToStrip:Write error at scanline 14664 ERROR 1: TIFFAppendToStrip:Write error at scanline 14664 The error is the same with tiled and untiled output. However, http://osgeo-org.1560.x6.nabble.com/gdal-dev-TiffAppendToStrip-errors-with-uncompressed-output-td4959969.html if I use -co tiled=yes the error occurs always at scanline 5888 and without tiling it occurs at scanline 14650. Changing GDAL_CACHEMAX value does not change anything. I use compressed output there are no troubles at all. I have verified it with LZW and packbits compression, with and without tiling and I get no errors ever. I can make a zip from the originals for downloading if someone is interested in having a look. I am on Windows XP and GDAL is from Gisinternals, downloaded in April 24. Program is listing the version as GDAL 1.9.0, released 2011/12/29 but I do not quite believe it. Aren't the Gisinternals builds coming from trunk? -Jukka Rahkonen- _______________________________________________ gdal-dev mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/gdal-dev Rahkonen Jukka (Tike) Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ [gdal-dev] Re: TiffAppendToStrip errors with uncompressed output Jukka Rahkonen
next » Print Pages: [1] Go Down Author Topic: TIFFAppendToStrip Error -- Serious Problem (Read 2884 times) 0 Members and 1 Guest are viewing this topic. Jon A. Bell Newbie Posts: 2 TIFFAppendToStrip Error -- https://forum.avast.com/index.php?topic=20940.0 Serious Problem « on: May 02, 2006, 07:23:16 PM » I’m a http://www.asmail.be/msg0055456195.html 3D graphics artist who uses Autodesk’s 3ds max software, and I’m encountering a problem that Autodesk believes may be related to my copy of Avast Personal Edition.When I attempt to network render a sequence of .tif images, I will sometimes get the following error message in my render Server program: "Task error at error: Tif Error: TIFFAppendToStrip - \My Workstation\Output Path\Test0000.tif" Tif Error (and occasionally, "Write error at scanline ??" after the filename.)The network render Server program on my main workstation will then have to re-start the rendering job. My other rendering nodes (which are not running Avast) are unaffected, and don’t have this error.According to Autodesk, it seems as if either Avast, or (maybe) an anti-spyware error at scanline program on my computer (Spybot Search and Destroy, Ad-Aware, and/or Spyware Blaster) is interfering with the .tif save/writing process, and causing these errors. (If I’m working in another program and trying to read or write .tif files at the same time the Server is rendering a .tif, I’ll most often get the error.)If anyone else has seen something like this, or can offer some advice, I’d really appreciate it, because this is seriously affecting my work. Thanks!-- Jon Logged igor Avast team Serious Graphoman Posts: 11518 Re: TIFFAppendToStrip Error -- Serious Problem « Reply #1 on: May 02, 2006, 08:59:16 PM » Well, the obvious question is: if you pause or stop avast! resident protection temporarily (or maybe only the Standard Shield provider), does the problem go away?How often does the .tif writing error occur? I mean, if you try to reproduce that (or decide whether stopping the provider worked), do you have to wait (=work) for days, or would it be clear within a few minutes?Additionally: what operating system do you use? What build of avast! do you have? Logged Jon A. Bell Newbie Posts: 2 Re: TIFFAppend
Date Next by Date Contact The TIFF Mailing List Homepage This list is run by Frank Warmerdam Archive maintained by AWare Systems Thread 2014.04.10 14:36 "TIFFAppendToStrip: Write error", by Irvanda Kurniadi 2014.04.11 01:40 "Re: TIFFAppendToStrip: Write error", by Bob Friesenhahn 2014.04.11 03:21 "Re: TIFFAppendToStrip: Write error", by Irvanda Kurniadi 2014.04.11 13:28 "Re: TIFFAppendToStrip: Write error", by Bob Friesenhahn 2014.04.11 13:53 "Re: TIFFAppendToStrip: Write error", by Irvanda Kurniadi 2014.04.11 17:58 "Re: TIFFAppendToStrip: Write error", by Bob Friesenhahn 2014.04.11 01:40 "Re: TIFFAppendToStrip: Write error", by Bob Friesenhahn On Thu, 10 Apr 2014, Irvanda Kurniadi wrote: > Hi, > I'm doing a project by involving libtiff. I got some error while running > my program shown by this error > message: > > TIFFAppendToStrip: Write error at scanline 3806. > Error: Could not copy the picture > > I run my program over Fiasco.OC microkernel. I test 2 kind of programs, > the first program can run properly > while the other program stuck in that error. I need to know what is the > meaning of this error analyze the > problem. Please let me know if you by any chance understand about this. This means that writing to the file failed for some reason using the parameters supplied in TIFFAppendToStrip(). The writer checks to see that the reported bytes written equals the number requested and if this fails, then an error is reported. There are many possible causes for the issue, many of which are outside of libtiff. What sort of C library does the Fiasco.OC microkernel use? What filesystem is being used? Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/