Closed GoogleCodeExporter closed 9 years ago
please attach logs from <home>/.Prismatik/Logs, and try described there
https://github.com/Atarity/Lightpack/issues/4 workaround, i'm working on the
issue.
Original comment by tim.hell...@gmail.com
on 17 Dec 2013 at 8:22
I ran into the same problem. Attached you find the logs and the crash report.
Original comment by sync4ph...@googlemail.com
on 17 Dec 2013 at 8:49
Attachments:
Help delete the whole .Prismatik folder, anyway its crash sometimes when you
change leds position. Here is crash reports before deleting folder with the
first startup crashes http://cl.ly/SyzO and here http://cl.ly/Sz7D is reports
of crashing while changing leds position.
Original comment by mic...@cerny.me
on 17 Dec 2013 at 8:51
Original comment by tim.hell...@gmail.com
on 18 Dec 2013 at 10:41
I have this same problem. It crashed while resizing the leds position (you must
disable the led then move it to avoid this causing a crash when moving it)
Now I can't even run prismatik. It crashes every time, even after a new clean
install of it. How do i fix this so I can run prismatik again????
OSX 10.9 Prismatik 5.10.4, crash report attached.
Original comment by joshjohn...@gmail.com
on 20 Jan 2014 at 10:23
Attachments:
I have found a small solution
Today when I turned on Prismatik, it worked (moodlamp mode), but switching to
ScreenGrab mode crashed it.
Still in ScreenGrab mode, it continued to immediately crash every time I opened
it.
Deleting
~/.Prismatik/Profiles/Lightpack.ini
allows it to launch (making a new profile), but then you lose your LED
positions. bit of a bother, right?
Ideally we would copy our old LED positions back into the new profile.
So before I deleted Lightpack.ini, I saved a backup.
Copying all LED positions in did NOT work (continued to crash).
But copying /some/ LEDs did work (LED position restored, without crash).
I decided that, when the profile 'breaks', it must be because one of the LEDs
in the profile has bad data.
In a binary-tree fashion, I narrowed down which LED in my broken profile was
causing the problem.
[LED_1] was the only LED I couldn't re-use from my old profile.
So my solution was:
Copy from backup ALL LEDs (except LED_1) into the new profile.
Prismatik launched fine, but I did have to figure out in the interface where
LED_1 was hiding and remake it.
For reference, this is what the broken LED_1 said (doesn't look particularly
evil):
[LED_1]
CoefBlue=1
CoefGreen=1
CoefRed=1
IsEnabled=true
Position=@Point(1345 923)
Size=@Size(575 157)
I remade LED_1 to say this:
[LED_1]
CoefBlue=1
CoefGreen=1
CoefRed=1
IsEnabled=true
Position=@Point(1440 920)
Size=@Size(480 160)
The default LED_1 also works without crashing, and says this:
[LED_1]
CoefBlue=1
CoefGreen=1
CoefRed=1
IsEnabled=true
Position=@Point(0 165)
Size=@Size(150 150)
My Lightpack monitor is 1920x1080
There exists also a secondary monitor, 1440x900. Probably that doesn't matter,
but certainly could believe the problems occurred when I reconnected my monitor.
Original comment by VENGEANC...@gmail.com
on 29 Jan 2014 at 1:18
fixed in 5.10.5
Original comment by tim.hell...@gmail.com
on 11 Feb 2014 at 9:31
Not fixed. The same is happening for me in 5.10.5 on Mac OS X 10.9.1.
Deleting the .Prismatik folder through terminal and trying to re-install
Prismatik gives the same result.
Original comment by Bar...@gmail.com
on 17 Feb 2014 at 9:44
Original issue reported on code.google.com by
mic...@cerny.me
on 16 Dec 2013 at 3:48