AbelCam Forum
Download AbelCam buy Pro
 
 
 
Welcome Anonymous User
11/01/2024 - 12:49 AM
Quick Search:
Quick Jump:
 
Announcements
Latest Topics
 
Camera Offline
By: BriggsD
Rank: Newbie
Topics: 5
From: n/a
Added: 02/16/2007 - 04:37 AM

Don't get me started on the Logitech drivers (i've got a communicate stx) but Logisphere was working fine and then all of the sudden i get "camera offline". I haven't installed/removed anything and I can still get the camera to work fine from an explorer window. It just doesn't work within Logisphere. I've tried unplugging it and restarting to no avail. Any ideas?
By: MelvinG
Rank: Magna Cum Laude
Topics: 661
From: Los Angeles, USA
Added: 02/16/2007 - 06:41 AM

Hmmm. I'm not sure I have any answers but I do have a few ideas to try. Stuff that will help isolate what exactly is going on.

0.5) Are you *positive* some other running program is not attaching itself to your camera? LogiSphere wants exclusive use of the cam.

1) Try removing your camera from the Devices list on LogiSphere's main tab. Then try to re-add it. Will it even let you re-add it? If so, did it start working now?

2) More extreme version of #1. Remove the cam from the Devices list and then close LogiSphere. Look in your 'Documents and Settings\All Users\Seiz System Engineering\LogiSphere\' folder. There should be one or more sub-folders there with names that start with 'cam'. Delete all such sub-folders, but leave the one(s) with names that look like version numbers alone. Then start LogiSphere and try to re-add and re-config your camera. What happens?

3) Also, you could turn on Write Debug File (on the Web tab) and then restart LogiSphere. Try removing and adding your cam again. The resulting debug file ahould then contain some lines indicating what devices LogiSphere thinks are on your system. Examine the debug file or post it and I'll have a look.
By: BriggsD
Rank: Newbie
Topics: 5
From: n/a
Added: 02/17/2007 - 01:19 AM

I've tried all of that and it's still not working. In addition I re-installed Logisphere and went out and bought a Microsoft VX-3000 and I've got the same problem. Argh! I did notice a "Device in use already, skipping" line and I'd guess that's causing some problems.

19:16:36 Listing available sound devices:
Manufacturer | Name | PNPDeviceID | ProductName
Microsoft | Microsoft LifeCam VX-3000. | USB\VID_045E&PID_00F5&MI_01\6&10047DE4&0&0001 | Microsoft LifeCam VX-3000.
Realtek | Realtek AC'97 Audio for VIA (R) Audio Controller | PCI\VEN_1106&DEV_3059&SUBSYS_1416147B&REV_60\3&2411E6FE&0&8D | Realtek AC'97 Audio for VIA (R) Audio Controller

19:16:36 getDeviceList
19:16:36 devicelist: found device ATI AVStream Analog Capture-1
19:16:36 devicelist: found device Microsoft LifeCam VX-3000-1
19:16:36 getDeviceList summary:
19:16:36 0 ATI AVStream Analog Capture-1
19:16:36 1 Microsoft LifeCam VX-3000-1
19:16:36 2 TPZOnly
19:16:36 3 Web Video
19:16:36 4
19:16:36 Search for Tilt/Pan devices
19:16:36 InitializeComponent()
19:16:36 tray resizedNormal
19:16:36 previous line repeated 1 times
19:16:36 start myinit
19:16:36 caption properties
19:16:37 set_read_values completed
19:16:37 hidden: False
19:16:37 Init done, running form eventqueue
19:16:40 building 'add cam' list
19:16:40 add Device ATI AVStream Analog Capture-1 to selection
19:16:40 add Device Microsoft LifeCam VX-3000-1 to selection
19:16:40 add Device TPZOnly to selection
19:16:40 add Device Web Video to selection
19:16:40 Device in use already, skipping
19:16:41 frmvcx new generic
19:16:41 Reading Config C:\Documents and Settings\All Users\Application Data\Seiz System Engineering\LogiSphere\camMicrosoft LifeCam VX-3000-1\
19:16:41 Config not found
19:16:41 Microsoft LifeCam VX-3000-1 DevInit
19:16:42 vcxConnected invoked
19:16:42 previous line repeated 1 times
19:16:42 Microsoft LifeCam VX-3000-1 DevInit zoomer
19:16:42 Microsoft LifeCam VX-3000-1 DevInit mover
19:16:42 Microsoft LifeCam VX-3000-1 DevInit set confi
By: MelvinG
Rank: Magna Cum Laude
Topics: 661
From: Los Angeles, USA
Added: 02/17/2007 - 11:38 AM

Thanks for the debug log. Unfortunately I don't see anything that's obviously wrong there. I get the "skipping" entry on my system too; every time I open the Add Cam dialog. Pretty sure what it means is that some cam is already in your Devices list, so it "skips" putting that cam in the Add Cam list (eg. to prevent adding the same cam multiple times). When SSE reads this thread perhaps he can confirm or correct me on this.

But since I've got the same message on a setup that's working, I think we need to look a little farther. Next logical step would be to log some debug info while trying to start the cam. Start LogiSphere and wait for it to finish all its initialization work. Go into Config for you cam and make sure Use Cam is un-checked. Then turn on Write Debug File. Then go back to the cam Config and check Use Cam. Keep an eye on the "Server Events & Messages" in the main window - something interesting may turn up there as well as in the debug file.

My thinking here: since you can add the cam, it must be dying on Start. Doing the steps above should capture all the events surrounding the start attempt. Should be a clue in there somewhere as to what is killing the start.

Totally off-the-wall idea: I see you have the same audio chip that I have on one of my boxes. Both my LogiTech and Creative cam drivers had "startup death" issues that were related to that chipset (it's documented on the LogiTech and Creative web sites somewhere but I no longer have the links). Now why this would appear suddenly on a working system is beyond me... but just try this for the heck of it anyway. On the Start menu, under LogiSphere, you'll find a Tools selection. One of the Tools is "LogiSphere without Audio". What it does is start LogiSphere normally, except that LogiSphere will totally ignore your audio devices.
By: BriggsD
Rank: Newbie
Topics: 5
From: n/a
Added: 02/19/2007 - 10:54 AM

Sure enough by starting with the audio disabled it now works again. Thanks!
I never use the start menu in windows and didn't even see that option or otherwise I would have tried it earlier.