<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/imgseqscan/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 20 Dec 2018 15:45:09 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/imgseqscan/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>check for image depth / alpha</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/26/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
Very good tool. Very good (and unique) to find continuity problems in image sequence.&lt;/p&gt;
&lt;p&gt;I have sometimes a specific problem :&lt;br/&gt;
image sequence with no continuity in alpha (and/or bit depth).&lt;br/&gt;
exemple : some PNG with alpha switch from 24 bit to 32 bit. And avid don't like that !&lt;/p&gt;
&lt;p&gt;Do you think possible to add in "check for corrupt" the bit depth count of files like for resolution (and or the alpha yes/no) ?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br/&gt;
Diego&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Diego from Paris</dc:creator><pubDate>Thu, 20 Dec 2018 15:45:09 -0000</pubDate><guid>https://sourceforge.netd230b1984f408090ae6070155f4bcd1465c83c7d</guid></item><item><title>add desktop icon</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/25/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Sun, 05 May 2013 16:46:58 -0000</pubDate><guid>https://sourceforge.netc1730f0c63d8a1c948e5f7155a346990ac3a4601</guid></item><item><title>option to use different date/times?</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/24/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;not sure if this is necessary..... but DateTime is used in many places. It is first attempted to use some Exif DateTime tag - if unable to find then it uses CreationDate from FileInfo struct. Perhaps the user wants to use CreationDate because Exif value is less accurate?&lt;/p&gt;
&lt;p&gt;If Exif data is available, usually there are multiple date/time tags that could be used (digitized, original, etc). Also available is the Windows CreationTime which may be more interesting/useful to the user, assuming it's even correct. Anyways it's theoretically possible that either of these could be wrong, so giving the user an option to use either/or (or even one of the multiple exif values) might be beneficial?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Wed, 19 Jan 2011 09:25:47 -0000</pubDate><guid>https://sourceforge.netdcee8285a54692b30aee77bd344295c1ae3912e2</guid></item><item><title>group exif info into groups</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/23/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;e.g. Exif, Maker Notes, Canon Info, etc.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Tue, 18 Jan 2011 13:44:10 -0000</pubDate><guid>https://sourceforge.net9c15aff3dae3014d28367eb19baacbf243b96f18</guid></item><item><title>add status icons to corrupt files list</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/22/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Would be very helpful to quickly discern which files are maybe/really corrupt, and further an indicator of what's wrong. Also allow sorting on this column i.e. make it it's own column (if possible).&lt;/p&gt;
&lt;p&gt;Just ideas:&lt;br /&gt;
? = potentially corrupt&lt;br /&gt;
H = header is corrupt&lt;br /&gt;
x = file is dead&lt;br /&gt;
0 = file-size is zero&lt;br /&gt;
Z = exception caught processing this file&lt;br /&gt;
etc.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Wed, 05 Jan 2011 08:54:02 -0000</pubDate><guid>https://sourceforge.net072690b570e8a7faf996c1d81b889d0fdccfec41</guid></item><item><title>parse exif maker notes</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/21/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This is a gold-mine of information, though it needs to be decrypted first...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Thu, 09 Dec 2010 02:54:23 -0000</pubDate><guid>https://sourceforge.netc11feec852b9e01b7026879a6c4f09762a3c871c</guid></item><item><title>ignore last characters</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/20/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently the sequence number can not have characters following it e.g. blah00 copy.jpg (after windows copy). Otherwise yet another tool is needed to rename the files to a format that is compatible.&lt;/p&gt;
&lt;p&gt;IDEA: add an "ignore last # characters" option underneath the "ignore first # characters" option.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Sat, 04 Dec 2010 14:59:12 -0000</pubDate><guid>https://sourceforge.netfbb7806202129338f0897c31e691b8ebf6a102fc</guid></item><item><title>time estimate for corrupt file checking</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Put a text label somewhere with estimated time til exif statistic collection is finished.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Tue, 30 Nov 2010 02:01:44 -0000</pubDate><guid>https://sourceforge.netc4c36eda262450b1d873d331df486e051c5c1830</guid></item><item><title>build graphical representation of selected exif data</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;see: &lt;a href="http://timescapes.org/phpBB3/viewtopic.php?f=8&amp;amp;t=3087" rel="nofollow"&gt;http://timescapes.org/phpBB3/viewtopic.php?f=8&amp;amp;t=3087&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Mon, 29 Nov 2010 13:32:05 -0000</pubDate><guid>https://sourceforge.net2ebbaedb22d5d5b6dbb0e37790a3491054ba9390</guid></item><item><title>warning if files found with different case</title><link>https://sourceforge.net/p/imgseqscan/feature-requests/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This might prove problematic if, for some odd reason, files from multiple sets/exports/cameras come together with different extensions.&lt;/p&gt;
&lt;p&gt;Somehow show a list of files with different cases? Or at least warn the user and give them a list of all the variations.&lt;/p&gt;
&lt;p&gt;If rename feature is ever added, possibly offer the option to auto-rename to all lower/uppercase for convenience.&lt;/p&gt;
&lt;p&gt;Note: currently extensions are converted to upper-case for making an extension search.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Bristol</dc:creator><pubDate>Sat, 27 Nov 2010 17:09:49 -0000</pubDate><guid>https://sourceforge.netd4f6e1d509f732cc7b88f3cba6f6289b18dfc217</guid></item></channel></rss>