This is and has been a issue for quite a while now. I thought and hoped it was fixed in the latest build, but it does not seem to be a priority at the Developer...
This is probably not the correct place to create this topic, but could you please add the Tapatalk plugin to your forum, that way it would be a lot easier for us who travels alot, to keep up with forum threads.
It's just a plugin and does not take much of an effort to install/enable.
My apologies in advance for a long post. I installed ICamSource 2.1.6 on my Windows 7 laptop. I bought and installed ICam on my IPhone 4. It worked immediately and perfectly. I went to work where my phone connects to the company wifi network. I showed my coworkers the app on my phone. Still working fine. I installed ICamSource on my laptop in my vacation home and tried to get 2 cameras attached to my laptop there(Windows Vista) to work. I had issues and was advised to move back to an older version of ICamSource. It worked when I was on my home network but crashed using 3G. I gave up on the vacation home pc. Now my original home setup will work on my home network and on 3G but not when I connect to my work wifi. I tried changing the username and password but I still can't connect from my work wifi. Several other coworkers can connect to their cameras so I know it is not being blocked by something at work. I don't know what to check now. It used to work from my work wifi, it still works for other people on my work wifi but it won't work for me on my work wifi. Any thoughts, ideas, suggestions as to what I should do?
I have the exact same problem. If I connect from my home wifi or use 3G, it works fine. If I connect to the job wifi or wifi anywhere else than my home wifi, it does not work...
For some time now, iCAM uses 80-90% CPU power... WHY and how can I fix this so it don't? (it did not do that earlier and it SHOULD NOT NEED TO if it's programmed correctly)
Oh and... : It says in the gui that it is connecting..., But I can connect from both iPhone and iPad just fine. There seem to have been a lot of trouble with 2.1.3, so when will there be a 2.1.4 without all these bugs....?
Correction: I stopped it and started it again and it now says "Connected", but still uses A LOT of CPU...
And I might add, I have two Panasonic ip cams connected...
That will erase the current iCamSource settings in your registry. You will need to re-enter all of your settings, but hopefully the problem will be resolved if it's due to a problem in the registry.
Well... After resetting password and trying with different usr/pwd, I finally got it working, but there seem to be a problem with the passwords. I think it has to do with the length of the passwords used....
Oh well... I'm in
Could you please make an option for 24H clock for us in europe as we do not use AM/PM....