The issue has broken my toolchain. That's the only reason I noticed it.
I am a software developer, so I know that user feedback is important.
Thanks a lot, especially to Thomas, for the quick reaction. I'm excited!
--
A list of frequently asked questions is available at:
On Fri, 04 Nov 2016 09:55:15 +1100, Gnome Nomad
wrote:
Oh, I agree that enblend 4.2 should support compression=none since 4.1
supported it. Sounds like a regression in enblend. Is there a bug report
on
it?
On Thu, Nov 3, 2016, 12:15 Stefan Peter
Oh, I agree that enblend 4.2 should support compression=none since 4.1
supported it. Sounds like a regression in enblend. Is there a bug report on
it?
On Thu, Nov 3, 2016, 12:15 Stefan Peter wrote:
On 03.11.2016 19:11, Gnome Nomad wrote:
> Hmm, TIFF uses lossless
On 03.11.2016 19:11, Gnome Nomad wrote:
> Hmm, TIFF uses lossless compression. So why are you wanting to use no
> compression?
This should not be the question. If an option is presented, this option
should be usable.
So, either enblend _can_ and _will_ do uncompressed tif output in this
case, or
True, it can use no compression or lossy; one of the benefits of TIFF IMHO.
Only reason I can think of for using no-compression TIFF is when some other
tool in the chain can't handle compressed TIFF. So wondered why OP needed
no compression specifically.
On Thu, Nov 3, 2016, 09:45 Frederic Da
2016-11-03 19:11 GMT+01:00 Gnome Nomad :
> Hmm, TIFF uses lossless compression. So why are you wanting to use no
> compression?
>
>>
AFAIK, TIFF can use no compression, lossless compression and lossy
compression.
--
Frederic Da Vitoria
(davitof)
Membre de l'April - «
Hmm, TIFF uses lossless compression. So why are you wanting to use no
compression?
On Thu, Nov 3, 2016, 06:04 Bernd D wrote:
> Hi,
> I found out, that the newest enblend.exe version 4.2 ignores the
> --compression=none parameter. The previous version 4.1.5 works