hue inversion does not work on Mac OS X 10.9+ Mavericks

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Install Nocturne in Mac OS X 10.9+
2. Disable Monochrome and enable Invert Hue

Expect hues to be inverted. Instead, checkbox has no effect.

Using Nocturne 2.0.0 on Mac OS X 10.9

Original issue reported on code.google.com by al...@ali01.com on 5 Nov 2013 at 12:42

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

Ditto - this is primarily why I use Nocturne (otherwise, I just use 
Cmd-Opt-Ctrl 8)... What are the chances of this getting fixed?  Thanks! :)

Original comment by r...@warproof.com on 16 Nov 2013 at 12:21

GoogleCodeExporter commented 8 years ago

confirmed. good report.

Original comment by ericd...@gmail.com on 3 Dec 2013 at 2:12

GoogleCodeExporter commented 8 years ago

For what it’s worth, I was able to find a modified, working version of 
Nocturne here:

https://inbeta.org/2012/08/28/blacktrees-nocturne-updated-for-mac-os-x-10-8-moun
tain-lion/

Original comment by n...@natesilva.com on 3 Dec 2013 at 10:27

GoogleCodeExporter commented 8 years ago

Thanks for the update, I tried the modified version and it still isn't 
activating the "invert hue" function. The flickering problem seems to be 
solved, so that's a plus. 

I use this app all the time when annotating journal articles (I'm in grad 
school), and it really helps my studying. If anyone has a fix I'd really 
appreciate it.

Best,

~Ben

Original comment by benjamin...@gmail.com on 6 Dec 2013 at 1:13

GoogleCodeExporter commented 8 years ago

Any update on this? :)

Original comment by ricosu...@gmail.com on 8 Jan 2014 at 7:03

GoogleCodeExporter commented 8 years ago

Added a $15 bounty on 
https://www.bountysource.com/issues/1430592-hue-inversion-does-not-work-on-mac-o
s-x-10-9-mavericks

I <3 Nocturne, so until this is fixed, i'm stuck in Mountain Lion :(

Original comment by j...@benet.ai on 2 Mar 2014 at 1:22

GoogleCodeExporter commented 8 years ago

I'll match that ^

Original comment by benjamin...@gmail.com on 4 Mar 2014 at 4:32

GoogleCodeExporter commented 8 years ago

I believe I have solved this issue.  How can I commit a patch to Nocturne?

Original comment by And...@hunt.li on 28 Jul 2014 at 12:58

GoogleCodeExporter commented 8 years ago

I'll be very happy if you did!
Please, email one of these people as soon as you can: 
https://code.google.com/p/blacktree-nocturne/people/list

Original comment by ejwes...@gmail.com on 28 Jul 2014 at 6:50

GoogleCodeExporter commented 8 years ago

I think the negative hue stuff should behave like this Windows program does it: 
http://arcanesanctum.net/negativescreen/

You configure a set of color transformation matrixes which can be bound to the 
F1 keys.

Original comment by abazh...@gmail.com on 29 Jul 2014 at 12:00

GoogleCodeExporter commented 8 years ago

I completely agree. That's how it used to work with regard to the 'smart 
inversion', but it stopped working a while ago and since hasn't been fixed.

If And...@hunt.li believes he has fixed it so that it is now "smart inversion" 
I would greatly like to see this feature reimplemented as it was why I was 
using nocturne.

Original comment by ejwes...@gmail.com on 29 Jul 2014 at 12:10

GoogleCodeExporter commented 8 years ago

Well, first I have to find a way to contact the owners of this project.  Unless 
they see my request here, I can't find a way to see their full email addresses.

I was trying to test my fixes today, and may have run into an issue with 2 
external displays.

Once I have a working version of the code patched (and I'll want them to review 
and approve it if they're active), then maybe we can look at smart inversion.

Original comment by And...@hunt.li on 29 Jul 2014 at 12:45

GoogleCodeExporter commented 8 years ago

It's displaying tint correctly when displays are not mirrored.  When displays 
are mirrored, only the first display is tinted.  Out of curiosity, is that 
existing behavior?

Original comment by And...@hunt.li on 29 Jul 2014 at 1:26

GoogleCodeExporter commented 8 years ago

Also, j...@gmail.com, is there a way that I can commit my patch to source, once 
it's been reviewed?

Original comment by And...@hunt.li on 29 Jul 2014 at 1:27

GoogleCodeExporter commented 8 years ago

re comment #14, I found a way to tint them all, so it doesn't matter.

Original comment by And...@hunt.li on 29 Jul 2014 at 1:37

GoogleCodeExporter commented 8 years ago

Not hearing back from any of the owner / committer people.  If it goes another 
day or two, I'll fork it and put the source up on Github, with a binary.  I 
think that's ok with an apache 2 license.  I'll read over it a bit more 
carefully in the meantime.  Incidentally, if an owner would prefer I didn't do 
this for some reason... please let me know.

Original comment by And...@hunt.li on 31 Jul 2014 at 1:01

GoogleCodeExporter commented 8 years ago

!!! oh man, please, project owners, merge this!

And...@hunt.li -- you might want to release it through github so you can get 
some people to test it while the project owners get back.

Original comment by j...@benet.ai on 31 Jul 2014 at 10:34

GoogleCodeExporter commented 8 years ago

While we're waiting for the owners/committers to get to this issue:
https://github.com/kzsh/nocturne-fork

Thanks.

Original comment by And...@hunt.li on 1 Aug 2014 at 12:33

GoogleCodeExporter commented 8 years ago

Has anyone had a chance to try my changes?  I'm curious if there were any 
issues.   There's a binary available (.app) on the repo as well, if you don't 
compile for yourself.

Original comment by And...@hunt.li on 3 Aug 2014 at 2:01

GoogleCodeExporter commented 8 years ago

I tried running it. The Invert Hue option had no effect. I'm running OSX 10.9.2 
on late 2011 macbook pro 17"

Original comment by abazh...@gmail.com on 3 Aug 2014 at 6:17

GoogleCodeExporter commented 8 years ago

Yeah, I just realized that I got my defects mixed up.  I think I've solved for 
64 not 63.

Original comment by And...@hunt.li on 3 Aug 2014 at 6:44

GoogleCodeExporter commented 8 years ago

After a little investigation, it looks like the hue inversion was relying on a 
private API that may have changed.  If it did change, that might explain why it 
doesn't work anymore.

Original comment by And...@hunt.li on 3 Aug 2014 at 7:58

GoogleCodeExporter commented 8 years ago

@hunt.li
This is a great observation. May I ask how you determined this?
Perhaps we should start looking into another tool that can allow such 
functionality?

Original comment by ejwes...@gmail.com on 3 Sep 2014 at 4:12

GoogleCodeExporter commented 8 years ago

Honestly I don't really care if hue inversion doesn't work because then I can't 
watch movies/videos with the color inverted. I always have invert screen on, 
and I have VLC with colors inverted playing.. so that wouldn't work.

Original comment by abazh...@gmail.com on 3 Sep 2014 at 4:25

GoogleCodeExporter commented 8 years ago

Well I believe some of us want the hue inversion to work, keeps some of the 
color and prevents it from looking ugly(imo).
It's an option with in the menu and not a permanent fix, so it can be turned 
off =)

Original comment by ejwes...@gmail.com on 3 Sep 2014 at 4:36

GoogleCodeExporter commented 8 years ago

Andrew, did you get hue inversion working? (I accidentally updated to Yosemite, 
forgetting the awful "no hue inversion" disaster)

Original comment by j...@benet.ai on 29 Oct 2014 at 12:06

GoogleCodeExporter commented 8 years ago

Unfortunately, I have not had time to  get hue inversion working.  looking at 
the code a while back, it seem that hue inversion pre-Mavericks relied on 
accessing an API that is no longer exposed.  That's why it broke and was not 
quickly fixed.  The solution to the problem right now would involve a lot more 
work, so far as I recall.

Original comment by And...@hunt.li on 29 Oct 2014 at 12:10

Cyruslgroves / blacktree-nocturne

hue inversion does not work on Mac OS X 10.9+ Mavericks #63