if you navigate to NeonBoombox/contents/resources/modules and delete the radio module it should finish launching. the only reasons I can think that would be crashing are that either you aren't using the latest download (available only in the update thread, not on the site) or you have either an XM radio attached or another USB serial device that the radio module has mistaken for a radio
That works. Good job. Quick response. YEAH!!!!!
Been using NBB daily for a month now and I want to thank you for some great work. I'm really pleased with the software and especially your progress. I continue to have the problem with the control buttons disappearing with this release. Now it is the reverse control that is missing (previously the pause/play and then the forward). As previously, the the touch target still works properly, so function is not impaired, the control image just does not show up in the bottom bar. I'll check the log when I get a chance, but that's the only functional bug I have right now.
Once again, awesome job, keep up the good work.
well thank you for your support.
I definitely need to figure that out but you are the only one that I have heard having that problem... farther more if it is not always the same ones missing that doesn't point to a damaged bundle like I had previously suggested. I think Ill tweak the NIB today and put up a minor release with that and some apple remote fixes.
Edit: think I have the problem figured out. it is probably the same problem I am having with the main screen dial. it is core animation related and I don't yet know how to fix it. I have however disabled the core animation layer on the track details screen which will prevent the problem. obviously when I do actually need to use core animation on that screen (which I will, I have some sweet things planned) I will have to re-enable it. hopefully by then I will know how to fix it.
I do want to know why you are the only one reporting it.... What computer do you use? maybe it is related to the chronic Macbook and macbook pro graphical glitches.
Command: Neon Boombox
Path: /Users/Crzunch/Desktop/Neon Boombox.app/Contents/MacOS/Neon Boombox
Parent: WindowServer 
Version: ??? (PublicRelease7)
Link (dyld) error:
Library not loaded: /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
Referenced from: /Users/Crzunch/Desktop/Neon Boombox.app/Contents/MacOS/../Frameworks/NeonBoomboxSDK.framework/Versions/A/NeonBoomboxSDK
Reason: image not found
THIS IS MY CRASH ERROR LOG
NBB is crashing because the quicklook framework isn't loaded. I suspect that you are running mac os x 10.4 or earlier. NBB requires 10.5. If you are in fact running 10.5 you have something seriously wrong with your install and will likely need to reinstall your system
no i have 10.4 lol where i can i get 10.5 ive looked all night is that one i need to buy
yeah I recommend ebay. you can nab a copy for less than $100
NeonBoomBox 1.0RC 3
-OS X 10.5.4
-2.0ghz Core2 Duo
#1 NBB doesn't seem to save Volume state between launches. It will always restart with Volume at Full. (Update: Yes it does. Sometimes. Seems sporadic..?)
#2 If playing a video, pause video, return to pane view.
Restart video. Screen will go black. Right click -> "Play" will start video, but audio only. Still black screen.
Normal CMD-Q will exit app normally, otherwise it's "stuck".
#3 (minor) Track info does not appear at the top of Modules, Date/Time only
#4 On Screen Keyboard - Keys are cropped along top edge, close button is compressed/overlapped
This is reproducible on my end, however it may be linked to the way I am using NBB.
Steps to Reproduce:
Launch NBB, play any music, stop music, then attempt to play Video. NBB crashes.
If no music has been played, video will play without issue.
I am operating my Mac Mini via "Screen Sharing" or "Apple Remote Desktop". This occurs in both instances (not certain, but I believe both use VNC for access, so it's the exact same).
My set up is not such that I can dedicate a monitor/mouse/keyboard to the Mini (yet).
Info.plist reports it as 1.0 RC 1 (overlooked internal update, or is the server linked to wrong version?)