TRichView.com

hi, Me again. Here is something new, please advice. I put some more logs of the information for all MJPEG cameras (CamAnyMJPEG) defined in MRVIPCamList.pas; Here are the information related with rvctSamsung in the log (as I mentioned, with the old component, we could see the URL and looks like it ...

Actually, I did some change to make the port work. so the port is should not the problem - we tested another 2 IP Cameras which have 80 as the port and 18082 as the port, both worked. I wonder instead of discuss this issue here, is there another way to contact you, like by email or arrange a meeting ...

I added logs to check VideoFormat, and it's MJPEG (the VideoFormat is 0 which is rvvfMJPEG; TRVVideoFormat = (rvvfMJPEG, rvvfH264, rvvfAVI_H264, rvvfMP4_H264, rvvfAVI_MPEG, rvvfMP4_MPEG)), and the URL is empty; What else I can check? Thanks, Below is the log details - the last several lines shows ...

I will check it.
Can you tell me where can I find the logic to identify the Videoformat before calling RVCamera.SearchCamera, so that I can put some log their to check why it's not MJPEG, or how the VideoFormat is determined ? (Is that because of multiple channel from the IP Camera?)

Yes, that's correct - one camera which was identified as Axis camera is an Web Camera which showed video correctly - the IP is 158.39.49.51. The one with 10.123.2.142 is the one which we want to make work, and but we could not see the video from this Camera. With the old component, it showed an URL ...

Looks like it retuned simular information when we tested with the old component; All four methods returns false; Enclosed is the log file - the file name is search_cam.txt, here are some comments of the contents: 1. the first part is log information when searching an online Web Camera, the IP is 158 ...

All four methods returns false, here is log of ExecuteStr: 174624281: CheckConnect After InternetConnect 174624281: CheckConnect InternetConnect success 174624609: IsFoscam_1 Start................ 174624609: IsPanasonic Start................ 174624625: IsAxis Start................ 174624640 ...

I just did a test with RVMedia 8, and compared the logic on my comoputer and the one you attached, they are same. But looks like the issue related with ParseURL2 is still there, here are the details when I debug : function TSearchCameraThread.SearchCameraToIP -> CheckConnect -> ParseURL2; and in ...

I cannot find MRVSearchCamThreads.pas, but I found the methods you listed in MRVCamera.pas; Actually, one thing I did not mention is that when I tested IP Camera with UserName and Password, I had to change the procedure ParseURL2 in MRVInetUtils.pas to make the PORT to be parsed correctly - looks ...

It's in our customer's site, with their restrict policy, they cannot open the video stream to us. We tested different IP Camera in their network, the new Executable works with others IP Camera in the same network; worked with Web IP Camera too. They had their IT guy checked the network and firewall ...

hi, After upgraded RVMedia from 5.0 to 7.5, the new compiled Windows Desktop Application could not find one of the IP Camera - it showed 'Could not find the Camera'; while the old executable with RVMedia 5.0 works fined. The IP Camera is 3XLOGIC, the port is 80; username and password are required ...