Open GoogleCodeExporter opened 9 years ago
Also, just to note, the first few times I ran Prismatik it worked for me. The
initial crash was caused by moving the leds.
Original comment by joshjohn...@gmail.com
on 23 Jan 2014 at 8:04
will be fixed in next release. Meanwhile please delete <home>/.Prismatik or run
Prismatik with "--wizard" key, it will allow you to redistribute capturing
zones and workaround the bug.
Original comment by tim.hell...@gmail.com
on 23 Jan 2014 at 9:20
Thanks for the info. What do you mean by delete <home>/ and run it with
"--wizard" key? Do I do that in terminal?
Original comment by joshjohn...@gmail.com
on 24 Jan 2014 at 12:52
delete "<home>/.Prismatik" not "<home>/" OR run Prismatik with '--wizard' key!
Yes do it from command line of any kind.
Original comment by tim.hell...@gmail.com
on 24 Jan 2014 at 10:13
have same problem. sorry but dont use command like much could you be more
descriptive on what and how to delete and what is meant by "wizard key"
I am on OSX thanks
Original comment by mr.john....@gmail.com
on 25 Jan 2014 at 9:43
I do not follow either. Can you just tell me what I need to paste into terminal
or how to delete home...
Original comment by joshjohn...@gmail.com
on 26 Jan 2014 at 4:12
you need to:
1. open: terminal
2. type: defaults write com.apple.finder AppleShowAllFiles -boolean true
3. type: killall Finder
4. navigate to <user>/.Prismatik
5. delete: Profiles
6. return to: terminal
7. type: defaults write com.apple.finder AppleShowAllFiles
8. type: killall Finder
this will allow you to view hidden files on your mac so you can navigate to the
Profiles folder and delete it. This will allow you re-open Prismatik and you
will need to reset up your LED's screen location.
Original comment by theactiv...@gmail.com
on 27 Jan 2014 at 4:19
Have also tried this with no luck, deleted directly through terminal. When the
app is opened it doesn't seem to create the .Prismatik in the home folder,
maybe a permissions issue. Have been able to get it to run through terminal,
but looks as if it is unable to find the device. (ledDeviceOpenSuccess(bool)
false).
Am still looking for a solution but at the moment am not having any luck.
Original comment by danobro...@gmail.com
on 27 Jan 2014 at 9:46
When lightpack.tv is back up I will try version 5.10.4 as suggested here,
https://code.google.com/p/light-pack/issues/detail?id=65
Original comment by danobro...@gmail.com
on 27 Jan 2014 at 10:02
Managed to solve my issues, had to run Prismatik from terminal using sudo (sudo
/Applications/Prismatik.app/Contents/MacOS/Prismatik or sudo
/Applications/Prismatik.app/Contents/MacOS/Prismatik --wizard).
I then quit the prismatik app and from terminal changed the permissions of
~/.Prismatik (chmod -R <Username> ~/.Prismatik. At one point I did remove any
profiles, using rm -r ~/.Prismatik/Profiles.
Hope this helps, version 5.10.4 fixed the device not found issue.
Original comment by danobro...@gmail.com
on 28 Jan 2014 at 8:22
does 5.10.5 fix your problem?
Original comment by tim.hell...@gmail.com
on 10 Feb 2014 at 7:27
I also am having this problem, terminal does not seem to help at all. OSX 10.9
Original comment by willma...@gmail.com
on 17 Feb 2014 at 2:35
5.10.5 does not fix this problem for me. Even running Prismatik through the
terminal with --wizard crashes (although the .Prismatik folder and it's
contents get remade).
Original comment by Bar...@gmail.com
on 17 Feb 2014 at 9:50
Same problem happening with 5.10.6
Original comment by Bar...@gmail.com
on 19 Feb 2014 at 6:23
Same in 5.10.6. Does anyone know where is the official support for this product?
Original comment by Bar...@gmail.com
on 19 Feb 2014 at 6:30
couldn't reproduce the problem.( could you attach log files please?
Original comment by tim.hell...@gmail.com
on 19 Feb 2014 at 8:42
I removed the .Prismatik folder and re-ran Prismatik. It crashed straight away
(see Lightpack_crash_report).
Prismatik.0.log is the log file for that first run.
I reran Prismatik and the lights come on (all white). But, as previously
reported, trying to change anything in the app (even just going to the 'About'
tab, causes the app to crash (see Prismatik.1.log).
Thanks.
Original comment by Bar...@gmail.com
on 20 Feb 2014 at 3:34
Attachments:
Interestingly, just before the app crashed, I could see that it was saying
firmware 0.0 in the 'about tab' even though I updated the firmware to 7.5 on my
PC today (under Windows 8).
So, there is certainly a problem communicating with the device on Mac OS X 10.9.
Original comment by Bar...@gmail.com
on 20 Feb 2014 at 3:58
Count me in. Just got my Lightpack and the prismatik app crashes when I try to
click on a tab.
I use 5.10.6 and an iMac with Mavericks 10.9.1 the log says "segmentation
fault".
Original comment by mcr...@gmail.com
on 22 Feb 2014 at 5:02
Another impatient customer complain attached
Original comment by buivichc...@gmail.com
on 23 Feb 2014 at 11:46
Attachments:
Same for me. The software seams to work (I get colorful output with the
LED-stripes), but it crashes when I try to configure something.
I am able to open the setting, but when I click anywhere in the window, the
software crashes directly (and reproducible).
Prismatik version is 5.10.6
Original comment by B.Endem...@gmail.com
on 23 Feb 2014 at 2:59
Attachments:
Same problem :
Process: Prismatik [464]
Path: /Applications/Prismatik.app/Contents/MacOS/Prismatik
Identifier: @BUNDLEIDENTIFIER@
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [157]
Responsible: Prismatik [464]
User ID: 501
Date/Time: 2014-02-23 21:18:59.531 -0500
OS Version: Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 6DCE77F7-5D43-922E-42E6-236A60D0830A
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000115f48000
VM Regions Near 0x115f48000:
VM_ALLOCATE 0000000115ed0000-0000000115f48000 [ 480K] rw-/rwx SM=PRV .....
Original comment by Clarenne...@gmail.com
on 24 Feb 2014 at 2:19
Guys, please try this:
https://docs.google.com/uc?export=download&id=0ByyS4RhCQ3EHN2Zqei1STDFZZFU
Qt updated and it seems everything should be ok with this version, since some
related bugs were fixed there:
https://qt.gitorious.org/qt/qtbase/source/08cbbde61778276ccdda73d89fd64d02c62377
9f:dist/changes-5.2.1
Sorry for delay.
Original comment by tim.hell...@gmail.com
on 24 Feb 2014 at 12:42
Tim,
that fixed it! Awesome!
I can see a separate (unrelated) issue where trying to show pure blue is coming
out white (R G and B are active) but at least I can configure and play now.
Thanks for the Prismatik update. :)
Original comment by Bar...@gmail.com
on 24 Feb 2014 at 3:55
It is also working (aka not crashing) for me now. Thanks!
Original comment by B.Endem...@gmail.com
on 27 Feb 2014 at 9:04
[deleted comment]
Figured out how to do it.
Here, I will write what to do in the simplest way.
1. Open "Terminal" application
2. Type: defaults write com.apple.finder AppleShowAllFiles -boolean true
3. Press Enter
4. Type: killall Finder
5. Press Enter
6. Open “Finder” application
7. At the top bar, click “Go”
8. Click “Home”
9. Now you will see a folder named “.Prismatik”. Delete it
10. Go back to "Terminal" application.
11. type: defaults write com.apple.finder AppleShowAllFiles
12. Press Enter
13. type: killall Finder
14. Press Enter
15. Go to “Applications” folder.
16. Delete “Prismatik” application.
17. Download and install this program:
https://docs.google.com/uc?export=download&id=0ByyS4RhCQ3EHN2Zqei1STDFZZFU
Original comment by jigole...@gmail.com
on 1 Mar 2014 at 4:36
Hi jigole...@gmail.com,
Can you update your link ? I'have the same issue on MacOSX ! :(
Original comment by Clarenne...@gmail.com
on 18 May 2014 at 11:41
Hi Clarenne,
are you using the latest version of the software from
http://lightpack.tv/downloads (there is a version 5.11.0 now for Mac OS X)?
This issue has been fixed (for me at least) since version 5.10.7.
Original comment by Bar...@gmail.com
on 19 May 2014 at 8:41
Original issue reported on code.google.com by
joshjohn...@gmail.com
on 23 Jan 2014 at 8:02Attachments: