TheUberOverLord

Nonsense. The ISO always supported dual boot. The ISO has NOTHING TO DO with the dual boot sparky. Pray tell how the new ISO supports dual boot and the old one didnt. Furthermore even if the ISO had block letters that said it supports dual boot, that has no bearing on proper licensing. You have NO clue. Nice try though. Not with auto-activation of Windows 10 using the key from Win7, Win8, Win8.1 using a USB memory boot stick with the Windows installation taking place from it, while maintaining the activation for the older Operating System. Liar-Liar pants on fire! You're a hopeless case. I will wait for someone else to confirm what I say is true. Your only end-goal is to attempt to destroy any thread I create. You lost, as usual. Once again. Don

Your referenced link was published on March 21, 2015. 11 months ago and has NEVER been updated since new Windows 10 ISO releases have been released: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/free-upgrade-from-windows-7-to-windows-10-dual/29b232b2-ac67-45d6-be88-ac14b0c7bf8e?auth=1 That's how far behind the times you are. The Microsoft Windows 10 ISO's at the time did NOT support dual booting Windows 10 alongside Win7, Win8 and Win8.1 and auto activating the Windows 10 while still maintaining the activation for the other Operating Systems. Using a USB memory boot stick with the Windows installation taking place from it. Now they do, because the newest Microsoft Windows 10 ISO's now support that feature! Compare your archaic and stale link to another Microsoft.com answer that HAS been updated here: viewtopic.php?p=284846#p284846 What part of that, continues to confuse you? GET IT SPARKY? Don

Booogiieee.... I am confused? In your opinion what is He saying or doing wrong? sound OK for me Thanks, I can assure you at least for my specific Laptop which in a prior post here I define, in detail. It works. Maintaining the activation with Windows 8.1 while automatically activating Windows 10. I have shown that in detail. Boogieman, jayson, Sammy dah Boy and Sparky is speculating and using conjecture based on prior installs of Windows 10 using older ISO releases. That's the issue. His false statements and allegations are based on using older Windows 10 ISO versions. Not the current ISO versions for Windows 10 now available directly from Microsoft. One can easily do a search about "Windows 10 ISO dual boot" using the search engine of your choice and if the information is/was posted recently. As in the last month. It's easy to see that Boogieman, jayson, Sammy dah Boy and Sparky is totally incorrect. I avoided using links to those 3rd party websites. Because IMHO it's a waste of time. Boogieman, jayson, Sammy dah Boy and Sparky would simply try to destroy this thread for other reasons. So, why waste the time? Since I have proven that, beyond any doubt here: viewtopic.php?p=284846#p284846 After all. I provided instructions from Microsoft and pictures of my Laptops results using those instructions. It did not satisfy Boogieman, jayson, Sammy dah Boy and Sparky. Because his intent is nothing less than to destroy any thread I create with silly banter. So, why feed that, lol. So, I won't help Boogieman, jayson, Sammy dah Boy and Sparky by responding to his craziness. As others use these instructions. My statements will be validated vs. Boogieman, jayson, Sammy dah Boy and Sparky trying to destroy virtually any thread I create. I am more than confident. This will be the case. Don

Please be aware that despite what Donny says, using your free windows 10 upgrade to dual boot into windows 7/8 is not sanctioned by Microsoft and you may be committing software piracy. Donny will post a bunch of random links that simply discuss the upgrade process, that have NOTHING to do with whether or not you can dual boot as "evidence". Please take the time to read those links and note that they DO NOT state that dual booting is allowed. In general, when software is upgrade to a new version the original licences is invalidated. Despite his rants (and they will be long winding rants ) to the contrary. Donny has no evidence that Microsoft has changed this policy. Boogieman, jayson, Sammy dah Boy, fenderman and Sparky. You're following me from Forum to Forum, and posting the same false statements and false allegations, where I state this. You should take your "Feet" out of your mouth because you are totally incorrect in your false statements and false allegations. You should do more research. But I know that's above you! You are SO ill-informed on this subject matter, that it's beyond comprehension on why you need to scream FUD about subject matter that you obviously don't understand and are not up to date on! I have nothing more to comment here to any responses you make in this thread. Others here who use these instructions and the links provided by me that go to Microsoft.com. Will, once again prove that you are a "fool" when it comes to this subject matter. I'm more than willing to respond to anyone but you in this thread. But not you. So, please get over that! I stand by my statements and instructions here. That using the latest Windows 10 ISO provided by Microsoft and the tool that converts that ISO to a USB memory stick also provided by Microsoft. Works and is legal and allows one to continue to use Win7, Win8 and Win 8.1 while activating Windows 10 using a dual-boot by using the original key from those Windows Operating systems that are eligible for the FREE Windows 10 upgrade. Which is sanctioned and approved by Microsoft. It works, it's legal and it's sanctioned by Microsoft. Get a secretary to do proper research for you. Because I tire of your false allegations and false statements. One can even download the terms of using the Windows 10 ISO. It's legal and sanctioned from Microsoft.com: https://www.microsoft.com/en-us/software-download/techbench Secondly. The tool used to convert the ISO to a USB memory stick. Once again, is provided by Microsoft: https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool So. As stated earlier. You're false allegations and statements. Are you simply acting as the "Nut Job" you have been known to be! I don't have the training to help people with reading comprehension issues and/or medical issues. I have tried to be helpful here with you. But your classless comments have made me decide. I'm wasting my time. Because you are acting like such a fool. I leave you with one more link. Again from Microsoft.com about installing Windows 10 via a USB memory stick. Which references the EXACT tool I include in my posts and instructions here. Which is again. Provided by Microsoft. Please see what's stated under "Prepare Windows 10 ISO file". The same MICROSOFT.COM instructions, further down the page also reference the EXACT Microsoft.com web page my instructions and posts say to use to download the Windows 10 ISO. Under "Alternative methods if all the above fails": I quote. From the Microsoft.com link below: "WARNING: If you are still using Build 10240, do not use the Windows 10 ISO to format your PC. Upgrade first from an activated Windows 7, Windows 8, Windows 8.1, ensure the Windows 10 installation is activated, then you can perform a clean install. If you are using build 10586 or what is known as the November Update (1511), this rule does not apply, read below. UPDATE: Previously, Windows 7, Windows 8.0 and Windows 8.1 users needed to have either of those versions of Windows installed and activated in order to qualify for the free upgrade offer. For persons who needed to perform a clean install of Windows 10 from the outset, it was a two step process of first validating the machine through the upgrade routine, ensure the Windows 10 Upgrade was activated, then proceed to perform a Reset. With the latest November Update (1511), users no longer have to go through this process." http://answers.microsoft.com/en-us/windows/wiki/windows_10-windows_install/how-to-download-official-windows-10-iso-files/35cde7ec-5b6f-481c-a02d-dadf465df326 The answer above, by Microsoft. Was updated due to the new Windows 10 ISO's, which I reference here. More details: https://www.microsoft.com/en-us/software-download/techbench The FAQ ("After confirming the Windows 10 ISO you want") from the above link: http://www.microsoft.com/en-us/software-download/faq Even the tool used to convert the Microsoft ISO provided by Microsoft to use in a USB Memory stick for Windows 10. Which I reference here. Is produced and provided by Microsoft. It's also suggested in the FAQ above under "I've download an ISO file, now what?": https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool Which is EXACTLY as my instructions and links in my posts state. To do. Nothing nefarious was done. All accomplished, by using and following only explicit Microsoft instructions from Microsoft.com. Using a unmodified Microsoft ISO and their Tool. BOTH directly downloaded from Microsoft.com. No editing or changes of any kind, were done. No commands were used, of any kind. No deviations, of any kind for the Windows 10 Installation instructions provided by Microsoft, took place. As in EVER. The Windows 10 installation was activated automatically while maintaining the activation for Windows 8.1 ("As shown below"). As stated and confirmed above. All sanctioned by Microsoft using their latest Windows 10 ISO: Click on image for larger view of same Click on image for larger view of same Click on image for larger view of same It should also be noted. That the tool which is from Microsoft and suggested at the link above by Microsoft to use for converting a Windows 10 ISO. Which I use in my posts here and instructions here as well. To create a USB memory stick from a Windows 10 ISO. Works with BOTH UEFI based computers using UEFI Disks as well as MBR based computers using MBR based disks AUTOMATICALLY! So, Once again you have shown how foolish you are with your false allegations and false statements. Because of that. I will no longer be responding to you, in this thread. I will however, respond to others. The more you post, people get to learn and see who you REALLY are and aren't. Which in the end. Is a good thing. For everybody. Note: Your classless comments. Don't justify any individual response. Truly I'm ashamed for you and how your carry yourself online, which I guess is why you have a need to use some many different aliases and never expose your real name. No joke! Fortunately, that's your problem not mine. Hint: If you can't take the time to do research before making false allegations and false statements. Don't post comments about those false allegations. Because doing so, only continues to make you look foolish. If you have a reading comprehension problem, that's nothing to be ashamed of. Simply have someone else read the above and they can take the time to explain it, as needed. Don

I run Ubuntu 15.10 on a Laptop that is a triple boot system for Windows 8.1, Windows 10.1 and Ubuntu 15.10. Using this Windows 7 VM from within Ubuntu 15.10, also allows me besides accessing the IP Cameras interface. To now have access to four different Operating Systems on the same system. For testing. For the curious. The laptop is a Dell 3541 Inspiron running Windows 8.1 and guaranteed to be upgradeable to Windows 10 ("Which it was") , 4GB ram, 500GB drive, 8X DVD +/- RW Drive, 4 CPU cores clocked at 1.8 - 2.4 GHz (With turbo boost) with a touch screen and 15.60 screen size. Which I was able to purchase from the Dell Outlet on Jan 24, 2016 as a "Scratch and Dent" refurbished laptop from Dell that includes a 1 year warranty ("Which I could have paid extra to extend") for $212.68 U.S. Which included tax and shipping. Original price was $199.00 U.S. Which included shipping, but did not include tax. It was delivered on Jan 29, 2016. Five days after ordering it. Interesting enough, I could find no "Scratches or Dents". I checked the Dell outlet laptops being sold daily for 2 weeks before finding this deal. It works well and being a developer which includes developing applications for IP Cameras. I now use this laptop as my primary system yet I have 4 other systems which I was using that each had individually and standalone Operating systems of Vista, Win 7, Win 8.1 and a Win 10 with Ubuntu 12.04 LTS as a dual boot. I can upgrade to 8GB ram max and may in the future, but my highest ram usage currently is in the high 60 percentiles. Even while running Ubuntu 15.10 with a Win 7 VM running along side it, at the same time. While I have the 500GB disk partitioned to support each Operating System. I have plenty of free disk space. For each disk partition. I partitioned the 500GB disk: Win 8.1 300GB Win 10 75GB Ubuntu 15.10 50GB - The Win7 VM uses disk space from here. I can reallocate disk space as needed in the future as well. I installed each Operating System using the same 8GB USB memory card/stick. Reformatting it after each install. Making sure that all my Windows versions were installed first. Using a Microsoft Utility called "Windows USB/DVD Download Tool" for converting the latest Microsoft ISO for the Windows 10 version. Then finally, converting the ISO for Ubuntu 15.10 with "Rufus" to install Ubuntu 15.10. Most people don't realize that because Win 7, Win 8 and Win 8.1 can upgrade to Windows 10 for FREE. That if one chooses. One can install Windows 10 and it will activate using the Key for the prior Operating System while running as a dual boot and not replacing that Operating System. Allowing you to run what you have and also use Windows 10. One simply needs to choose the "Custom Install" option and choose a disk or a disk area on the same disk of where Windows 10 should be installed, during the USB memory card boot. Everything was taken care of automatically. I did not need to edit any Windows boot-loader options or change any Ubuntu GRUB configuration. My Bios allows me to choose which boot loader to use. Ubuntu or Windows. I chose Windows. Because I can use F12 during boot to select Ubuntu to boot from at any time and when using the Windows boot-loader, there is an option to boot from Ubuntu. By selecting the choice to boot from another device. The Ubuntu boot-loader also has an option to go to the Bios F12 boot selector as well. So, I have many different options to get to any Operating System. Don

While Hikvision and Dahua IP Cameras are good brands. There are other choices as well. I would avoid any Gray Market Hikvision products that are Chinese region codes and were kludged with custom firmware to "Act" like they can support English firmware in the future. Otherwise you might not be able to update/upgrade firmware when/if you choose. This includes both IP Cameras and NVR/DVR products. Anyone that says it's a good idea as in "Ever" to do otherwise, has no idea of the new features and fixes that Hikvision is going to release in future firmware releases soon. Misery loves company, so don't join them. You can check reviews in many places by many people to see what equipment which is within your budget that was purchased by others that have high ratings. The more places you look for reviews by others, the more likely you are going to see a better reflection of what the average rating for that equipment is. Don

Your response to the person mentioning the reasons why they won't purchase a specific brand of IP Camera devices ("Their choice") stated that the person "Did not have a clue". Your words, not mine. I decided to show you and others, that they in fact did have a clue. As noted in my prior post here. In some cases, only a firmware upgrade will "Prevent" these issues. The manufacturer states so themselves. While you should be proud of your less than 3 years experience with IP Cameras. Please don't take it personally that myself and others may choose to follow the manufacturers advice vs. yours in cases like this. IMHO. Insulting others does not help make your points stonger in your responses. I will let the Moderators and Administrators here, deal with your incessant insults to others here in your responses. I'm not going to argue with you on this. I show here, that even the manufacturer disagrees with you. That's enough proof, by me. On this subject matter. Don

You have no clue....next time properly secure your device. The person in fact making this statement indeed has "a clue" and in some cases without also doing a firmware upgrade properly securing your devices ("As you call it") won't help fix those issues: http://overseas.hikvision.com/europe/Press-Release-details_435_i4987.html http://overseas.hikvision.com/europe/list01_435.html Any suggestion that nobody should expose their NVR/DVR/IP Camera to the outside world is also not a solution in cases where only a firmware upgrade can truly fix an issue. Which would be like telling someone who is afraid of falling while walking outside. That the solution for them, is that they should never go outside and then their problem would be solved. I hope that someday, you can respectfully respond to others here in this forum. Without the need to insult them, while responding. Don

The Axis Q6044 live IP Camera demo below even allows you to to start a train and includes Axis IP Camera controls such as PTZ ("Pan/Tilt/Zoom"), Presets and infinite zoom as well as the IP Cameras zoom lens controls. The live demo below works with any Internet browser capable devices which are using any browser and never requires any plug-ins or media player. It works instantly and does not by default require a login. Although that is also a supported option: http://107.170.59.150/Axis/SecureImageDisplayControl.htm Note: The Interface does and will work with any IP Camera brand and models that allows pulling snapshots using HTTP or HTTPS URL's. The Interface is free ("Without IP Camera controls") and can be downloaded here: http://107.170.59.150/V40/SecureImageDisplayV40.zip Don

Thank you for confirming what I have stated here. Yes. It truly depends on ("How") the Gray Market Hikvision IP Camera was Kludged by the seller. Before it was sold and shipped. As you may also know. The "Downgrader" that did work in the past. Was for an extremely limited number of total Hikvision models being sold and cannot even be tried for those other Hikvision models anyway. Don

There are solutions to your issue. Ignore others who say otherwise. Google "hikvision 5.25". I clearly stated that what you are calling a solution is a downgrade. I also clearly stated that what you are saying also, will not work in all cases. Secondly. That downgrader solution is compatible with an extremely limited number of the total Hikvision IP Camera models and NVR/DVR models available and being used today. So what I said is correct and factual. I'm sure that as time moves forward more people will also state and confirm that here. That said. I have already seen that stated in other forums. Where some have already tried your suggestion and failed and they were using Hikvision models that the "Downgrader" worked with and supported ("In the past"). Not one, but many have already confirmed that your suggested solution, did not work for them. There is no personal attack in the above statements toward you. I have not asked anyone to "Ignore you" like you have asked others to do here. That may or do disagree with "Your Point Of View". There are no issue with stating facts and will I no longer constantly respond to your posts using other posts here. I'm not going to get into anymore argument post chains with you in forum threads here. Those days are over. So I have respectfully respond instead to you in one post here. Don

Have you ever heard the term: There is no honor among thieves Please think about why no Hikvision Gray Market seller would easily give up whatever Kludged firmware they use, as a download? If they did? Then any other seller could use that firmware to sell their own Gray Market Hikvision products. The "Secret Sauce" to selling Hikvision Grey Market products is the firmware required to do that. Generally even Hikvision Gray Market sellers pay a fee for the firmware they need to a 3rd party. It's not free. Anyone living or having connections to purchase China Hikvision IP Cameras intended to be sold only in China can easily purchase them. The hard part, is converting them to run English firmware. So that can you then turn-around and sell them worldwide and make a profit. The more sellers that have the "Secret Sauce" the more chance you lose sales to them. Because they decide to sell at lower prices than you currently do. Not a good idea to "Give Away" that "Secret Sauce" to anyone. I can assure you that Hikvision Gray Market sellers won't do anything that could cause them to lose money. Which includes handing out download links to the Kludged firmware that runs in their Gray Market products. It might be worth a try to contact your Gray Market seller to see what they suggest. Good luck on that quest as well. Points being: 1. Anyone that is Kludging Hikvision firmware simply for fun and bragging rights. Has yet to figure this latest new strategy out being used by Hikvision that will always work in all cases. In the very recent past. They could not do much anyway. Besides downgrade to very old firmware versions and for an extremely small subset of the total of Hikvision IP Camera models and NVR/DVR models. Even when/if they do figure this New Hikvision strategy out. Hikvision is constantly changing and adding strategies that will need to continue to be defeated in newer firmware releases. 2. No Hikvision Gray Market seller has yet to figure this latest new strategy out being used by Hikvision and when/if they do, they will never "give it away". 3. In the past Hikvision Gray Market sellers thought that simply adding details to their sales pages like "Do Not update the firmware in this device and you won't have any issues" worked to help their sales. Hikvision as you have personally experienced. Has come back with "Wanna Bet!". Most likely, this won't be the last time they do this. Don

Unfortunately the "Hooky 'Engrish' v5.2.5 firmware" firmware won't help with your problem because of the NVR most likely depending on how your Gray Market Hikvision IP Camera was Kludged to run English firmware. I go into some detail on why that is here: viewtopic.php?p=281853#p281853 Note: If anyone else says otherwise. Please make sure they substantiate and validate with trusted sources any of their claims. Such as links to others they claim "Did x" and it worked and it worked recently with a Hikvision NVR/DVR that was rejecting the connection from a Gray Market Chinese Hikvision IP Camera with "Language Mismatch". I can say that in this situation. In many cases ("It depends on how your Gray Market Hikvision IP Camera was Kludged to run English firmware"). It's possible to run a valid Chinese firmware version produced by Hikvision in a Gray Market Chinese Hikvision IP Camera and the NVR/DVR will once again be happy. If you can't read Chinese or choose not to read Chinese. That's not much of a real solution. Don

As part of Hikvision's continued and constantly changing methods to deal with their Gray Market issues. The last firmware version which was released for Hikvision NVR/DVR's now includes checking the Region Code ("Langauge(s)") that Hikvision IP Camera was intended to support against that Hikvision's IP Cameras Serial Number. If that check fails now? The Hikvision NVR/DVR will not connect to that Hikvision IP Camera due to a "Language Mismatch". It's important to note that a similar new firmware version is going to be released for Hikvision IP Cameras. Sometime this month, that will do the same when a Hikvision IP Camera is looking at any Hikvision NVR/DVR they will try to connect with. Upfront and first. I know this because I develop 3rd Party applications that interface to Hikvision devices and have access to pre-released firmware versions prior to those firmware releases being released to the general public. Additionally. Many others also, are now posting in IP Camera forums about these same issues. It's also important to note that Hikvision is also implementing the new checks for their applications such as Ezviz, iVMS and others. Some of which new versions may already include these similar checks and others will soon have new releases that do. If they don't now. Don

Another point to be aware of is that you can copy the folders that contain the scripts and edit their Global script so that you can even have different folders for the same IP Camera. As an example. You may want a folder that is setup to run FFmpeg using that IP cameras LAN IP Address, another using that same IP Camera via your ISP IP Address and another using that same IP Camera using a DDNS. So that you can compare FPS rates, dropped packets or bandwidth issues using all the access methods for your IP Cameras. Of course you can also copy the same folder for the same IP Camera brands and use the copies of each folder for multiple IP Cameras of the same brand. For each of those different IP Cameras, as needed as well. I the event that your brand of IP Camera model is not a Hikvision, Foscam or Top-201 IP Camera model you can edit the scripts and use the URL for your MJPEG or RTSP video/audio streams. I suggest using the Foscam Script download link from the link below. Because they contain folders which support both MJPEG and RTSP video and audio streams: viewtopic.php?p=281549#p281549 To see the command line options for FFmpeg. Please see the link below: https://ffmpeg.org/ffmpeg-all.html If you need any help with your brand of IP Camera model. Please post here and I will help you get the scripts working for your IP Camera. Don

FFmpeg is a very well known and free media multimedia framework and player that has great logging abilities and is easy to use. I have put together some free Windows .bat file scripts that use FFmpeg and FFplay which are also free ("Both of which are included in each .zip file") for Foscam, Hikvision and Top-201 ("Very bare bones and cheap +- $18.00 U.S. including shipping") IP Cameras. The goals in creating these FFmpeg and FFplay Window scripts were the following: a. Quick setup. b. Make sure all media players can also use any recording files produced, not requiring exclusively FFplay for playback. c. Allow copying the script folder on a per IP Camera basis for quick use/access at anytime for multiple IP Camera support. d. Provide real-time detailed logging and save log output as well. So that any issues with a IP Camera can be seen and/or reviewed easily. e. Limit file clutter and re-use log and recording files vs. creating new files every time the same script is used. f. Include all files required so that nothing else is needed and no formal Windows installation is required. g. Grab snapshots from main or sub video stream to show how easily that can be done when needed. h. Make the scripts parameter driven using a global script so that multiple scripts don't require editing to allow easy copying of the folder for other IP Cameras. Only requiring the global parameter file to be modified for those other IP Cameras. I will add more IP Camera brands in the future, but these are the current brands supported by these free scripts and their download links: Once the global parameter script file is modified for a IP Camera. The scripts for the IP Camera brands below. All support using a double left click to instantly: 1. Record video only or audio only and video with audio for main and sub video stream. 2. Record all video or audio only, video with audio streams for your configured amount of seconds. Then automatically stop. 3. Playback of all recording files saved using FFplay. You can also use the media player(s) of your choice as well. 4. Real-Time playing of your IP Cameras audio only, video only and video with audio for main and sub streams. Using FFplay. 5. Grabbing a single snapshot from main and sub video streams. 6. View the detailed log which was saved while also being displayed in real-time, for each script run. Download Link For All Foscam IP Camera Models http://107.170.59.150/FFmpegTools/ffmpegForFoscamCameras.zip Download Link For All Hikvision IP Camera, NVR/DVR Models and iVMS http://107.170.59.150/FFmpegTools/ffmpegForHikvisionCamerasAndNvrsDvrsV11.zip Download Link For All TOP-201 IP Camera and NVR/DVR Models http://107.170.59.150/FFmpegTools/ffmpegForTop-201CamerasAndNvrsDvrsV11.zip Caveats: You may need to allow firewall access to both FFmpeg and FFplay to access your IP Cameras, NVR/DVR or iVMS from your Windows system. Depending on any firewall(s) you use on that Windows system. You may need to right click on each .bat file ("After initial download and unzipping, once") and choose security and click an allow button. It depends on your version of Windows and its security settings. Log file lines can sometimes be truncated when using Windows Notepad to view the detailed logs. Other text viewers like Windows Wordpad and others display the detailed logs properly. I would create a Operator/User level Id that is not an admin level User Id for these scripts if you intend to use them on a non-secure LAN or remotely via WAN. Because the scripts run in the clear. While making sure that User Id is allowed to have access to the NVR/DVR, iVMS or IP Cameras, audio and/or video stream(s). If a IP Camera, DVR/NVR or iVMS is not configured to access video sub streams then the video sub stream related scripts will fail because of that. If a IP Camera does not support audio. Then the audio only stream related scripts will fail because of that. All RTSP recording and real-time playing using RTSP streams by the scripts. Force TCP to be used vs. defaulting to trying UDP first. To minimize delay. Of course this does not apply to Foscam MJPEG based IP Cameras which are also supported by these scripts and use MJPEG streams as are Foscam H.264 based IP Cameras which do use RTSP streams. The default recording time is set to 60 seconds. You can set that lower or higher. You can set the recording time to a very small amount of seconds, such as 10 seconds. If you are trying to get a true and accurate measurement of how many bytes per second of real-time bandwidth and/or a recording file will need on a stream by stream basis. For a specific IP Camera. With video or audio only or with video and audio. For both main and video sub streams with and without audio and audio only. This also allows you to view real-time bandwidth usage for a specific IP Camera. By viewing recording bandwidth differences with audio only, video only and video and audio. Because the log detail is also displayed in real-time during all recordings as well as saved to a log file which is re-used anytime that specific script is re-run as well as the recording file created by any specific script is also re-used. As you change IP Camera resolution, FPS rates, Bit rates, numbers of key frames and other IP Camera settings. You can see instant cause and effects for both MJPEG or RTSP based real-time bandwidth utilization as well as changes in MJPEG or RTSP recording file sizes of fewer or more bytes required for the same recording time. You can also see any data packet issues like re-transmissions, slow response times and other issues when using these scripts as well. The scripts also support saving video only and video with audio recordings as .avi or .asf formats. So you can see the differences in recording file sizes between the two formats as well. All audio recording only recording files are saved in .wav formats. Don

Example 10 second FFmpeg recording of RTSP Main video stream: http://107.170.59.150/FFmpegTools/h264_MainStreamAudioVideo.avi Example of FFmpeg snapshot grabbed from RTSP Main video stream: http://107.170.59.150/FFmpegTools/MainSnapShot.jpg Example 10 second FFmpeg recording of RTSP Sub video stream: http://107.170.59.150/FFmpegTools/h264_SubStreamAudioVideo.avi Example of FFmpeg snapshot grabbed from RTSP Sub video stream: http://107.170.59.150/FFmpegTools/SubSnapShot.jpg Example 10 second FFmpeg recording of MJPEG video stream: http://107.170.59.150/FFmpegTools/MJPEG_VideoOnly.avi Example of FFmpeg snapshot grabbed from MJPEG video stream: http://107.170.59.150/FFmpegTools/MJPEGSnapShot.jpg Example FFmpeg Detail Log Output: ffmpeg started on 2015-12-01 at 23:11:59 Report written to "H264RecordMainStreamAudioVideoAvi.log" Command line: "..\\ffmpeg.exe" -rtsp_transport tcp -i rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/ -acodec copy -vcodec copy -force_key_frames "expr:gte(t,n_forced*5)" -t 10 -report -y h264_MainStreamAudioVideo.avi ffmpeg version N-76860-g72eaf72 Copyright (c) 2000-2015 the FFmpeg developers built with gcc 5.2.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 9.100 / 55. 9.100 libavcodec 57. 16.100 / 57. 16.100 libavformat 57. 19.100 / 57. 19.100 libavdevice 57. 0.100 / 57. 0.100 libavfilter 6. 15.100 / 6. 15.100 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Splitting the commandline. Reading option '-rtsp_transport' ... matched as AVOption 'rtsp_transport' with argument 'tcp'. Reading option '-i' ... matched as input file with argument 'rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/'. Reading option '-acodec' ... matched as option 'acodec' (force audio codec ('copy' to copy stream)) with argument 'copy'. Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'copy'. Reading option '-force_key_frames' ... matched as option 'force_key_frames' (force key frames at specified timestamps) with argument 'expr:gte(t,n_forced*5)'. Reading option '-t' ... matched as option 't' (record or transcode "duration" seconds of audio/video) with argument '10'. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'. Reading option 'h264_MainStreamAudioVideo.avi' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option report (generate a report) with argument 1. Applying option y (overwrite output files) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/. Successfully parsed a group of options. Opening an input file: rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/. [rtsp @ 0116ab80] SDP: v=0 o=- 1109162014219182 0 IN IP4 0.0.0.0 s=HIK Media Server V3.3.4 i=HIK Media Server Session Description : standard e=NONE c=IN IP4 0.0.0.0 t=0 0 a=control:* b=AS:3082 a=range:npt=now- m=video 0 RTP/AVP 96 i=Video Media a=rtpmap:96 H264/90000 a=fmtp:96 profile-level-id=4D0014;packetization-mode=0;sprop-parameter-sets=Z2QAKKwXKgHgCJ+WEAABX5AAFfkIQA==,aP44sA== a=control:trackID=video b=AS:3072 a=Media_header:MEDIAINFO=494D4B48010100000400000100000000000000000000000000000000000000000000000000000000; a=appversion:1.0 [rtsp @ 0116ab80] video codec set to: h264 [rtsp @ 0116ab80] RTP Profile IDC: 4d Profile IOP: 0 Level: 14 [rtsp @ 0116ab80] RTP Packetization Mode: 0 [rtsp @ 0116ab80] Extradata set to 0116d220 (size: 34) [NULL @ 0116cd80] setting jitter buffer size to 0 [rtsp @ 0116ab80] hello state=0 [h264 @ 0116cd80] Frame num gap 21 19 [rtsp @ 0116ab80] All info found [rtsp @ 0116ab80] rfps: 7.833333 0.019018 [rtsp @ 0116ab80] rfps: 7.916667 0.009901 [rtsp @ 0116ab80] rfps: 8.000000 0.008035 [rtsp @ 0116ab80] rfps: 8.000000 0.008035 [rtsp @ 0116ab80] rfps: 8.083333 0.013419 [rtsp @ 0116ab80] rfps: 21.916667 0.013522 [rtsp @ 0116ab80] rfps: 22.000000 0.008116 [rtsp @ 0116ab80] rfps: 22.000000 0.008116 [rtsp @ 0116ab80] rfps: 22.083333 0.009962 [rtsp @ 0116ab80] rfps: 22.166667 0.019057 [rtsp @ 0116ab80] rfps: 29.833333 0.014604 [rtsp @ 0116ab80] rfps: 29.916667 0.003707 [rtsp @ 0116ab80] rfps: 29.916667 0.003707 [rtsp @ 0116ab80] rfps: 30.000000 0.000061 [rtsp @ 0116ab80] rfps: 60.000000 0.000244 [rtsp @ 0116ab80] rfps: 120.000000 0.000976 [rtsp @ 0116ab80] rfps: 240.000000 0.003904 [rtsp @ 0116ab80] rfps: 29.970030 0.000537 [rtsp @ 0116ab80] rfps: 29.970030 0.000537 [rtsp @ 0116ab80] rfps: 59.940060 0.002150 [rtsp @ 0116ab80] rfps: 59.940060 0.002150 Input #0, rtsp, from 'rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/': Metadata: title : HIK Media Server V3.3.4 comment : HIK Media Server Session Description : standard Duration: N/A, start: 0.842000, bitrate: N/A Stream #0:0, 29, 1/90000: Video: h264 (High), yuv420p, 1920x1080, 8 fps, 30 tbr, 90k tbn, 16 tbc Successfully opened the file. Parsing a group of options: output file h264_MainStreamAudioVideo.avi. Applying option acodec (force audio codec ('copy' to copy stream)) with argument copy. Applying option vcodec (force video codec ('copy' to copy stream)) with argument copy. Applying option force_key_frames (force key frames at specified timestamps) with argument expr:gte(t,n_forced*5). Applying option t (record or transcode "duration" seconds of audio/video) with argument 10. Successfully parsed a group of options. Opening an output file: h264_MainStreamAudioVideo.avi. Successfully opened the file. Output #0, avi, to 'h264_MainStreamAudioVideo.avi': Metadata: INAM : HIK Media Server V3.3.4 ICMT : HIK Media Server Session Description : standard ISFT : Lavf57.19.100 Stream #0:0, 0, 1/16: Video: h264 (H264 / 0x34363248), yuv420p, 1920x1080, q=2-31, 8 fps, 30 tbr, 16 tbn, 16 tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help frame= 34 fps=0.0 q=-1.0 size= 143kB time=00:00:03.43 bitrate= 341.2kbits/s frame= 39 fps= 33 q=-1.0 size= 154kB time=00:00:04.06 bitrate= 310.5kbits/s frame= 43 fps= 25 q=-1.0 size= 162kB time=00:00:04.56 bitrate= 290.6kbits/s frame= 47 fps= 21 q=-1.0 size= 170kB time=00:00:05.06 bitrate= 274.7kbits/s frame= 51 fps= 19 q=-1.0 size= 230kB time=00:00:05.56 bitrate= 338.4kbits/s frame= 55 fps= 17 q=-1.0 size= 239kB time=00:00:06.06 bitrate= 322.6kbits/s frame= 60 fps= 16 q=-1.0 size= 247kB time=00:00:06.68 bitrate= 302.7kbits/s frame= 64 fps= 15 q=-1.0 size= 253kB time=00:00:07.18 bitrate= 288.5kbits/s frame= 68 fps= 14 q=-1.0 size= 260kB time=00:00:07.68 bitrate= 277.3kbits/s frame= 73 fps= 13 q=-1.0 size= 269kB time=00:00:08.31 bitrate= 265.1kbits/s frame= 77 fps= 13 q=-1.0 size= 275kB time=00:00:08.81 bitrate= 255.7kbits/s frame= 82 fps= 13 q=-1.0 size= 284kB time=00:00:09.43 bitrate= 246.3kbits/s frame= 87 fps= 12 q=-1.0 size= 295kB time=00:00:10.06 bitrate= 239.8kbits/s No more output streams to write to, finishing. frame= 87 fps= 12 q=-1.0 Lsize= 297kB time=00:00:10.06 bitrate= 242.0kbits/s video:288kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 3.391166% Input file #0 (rtsp://User:Password@IPorDDNS:RTSPport/PSIA/Streaming/Channels/ChannelNumber/): Input stream #0:0 (video): 89 packets read (298284 bytes); Total: 89 packets (298284 bytes) demuxed Output file #0 (h264_MainStreamAudioVideo.avi): Output stream #0:0 (video): 87 packets muxed (294412 bytes); Total: 87 packets (294412 bytes) muxed 0 frames successfully decoded, 0 decoding errors [AVIOContext @ 06011320] Statistics: 10 seeks, 98 writeouts Don

You are very welcome. Just want to make sure you get facts. It will save you many headaches in the future, by doing a little upfront research. Everything you have said here that you would like to do or may do. Is doable. Don

You were wrong and are wrong about this subject matter. Own that! Note that I said "Generally Speaking" when I stated that IP Cameras use the same switching circuitry for their IR-CUT filters and IR light controls. I never made any blanket statement that all IP Cameras did same. The above statement is an example of an inaccurate, misleading and false statement. Because it's ALL inclusive and excludes NO IP Cameras of any kind. Please provide any scientific facts provided by trusted sources, that only Foscam IP Cameras use Electromechanical IR-CUT filters in their IP Cameras which use the same internal switching circuitry for their IR-CUT filters and IR light controls. Which has already been proven to be wrong here by your own admission as well as another link I provided for a non Foscam IP Camera and a non Foscam clone. Please stop babbling and read and study more. Because you are only continuing to make yourself look more silly than what you already appeared to be. Don Wow, you are completely wrong and cannot admit it. A cameras night vision capability with IR OFF is NOT in anyway related to whether or not it has IR lights or not.. Whats with you and scientific facts. Look up any hikvision, vivotek, axis manual and you will see that they all have the ability to disable IR light while staying in night mode allowing the use of external IR. That is FACT!!!! You are simply lying trying to cover up your tracks as is your MO. So now how are you going to disprove the owners manual. Hmmmm, guess the companies are wrong...you are right..they dont know their own product. Fool. Your babbling doesn't change the facts and your personal conjecture never has or will change those facts. Which prove your statements are wrong. So own it. Because your 2+ years of IP Camera experience is limited to few brands and models of IP Cameras of the total IP Cameras available. Please re-read my posts if you continue to be confused. Because at no time did I ever make any blanket claim, that all IP Cameras could not control IR-CUT filters and IR lights separately. Saying that I did is lying. Because I never have said such a thing. On the other hand. You have made blanket statements about all IP Cameras, saying that no IP Camera of any kind, has any issues with IR-CUT filters and IR lights. So, please get the facts straight. I find it humorous at best that your above statement is all inclusive and excludes no IP Cameras of any kind. Yet you wish to not claim ownership of it. LOL The facts are. That if a IP Camera is using the same internal switching circuitry to control both the IR-CUT filter and the IR lights. That it does have a bearing on its low light viewing capability with that IP Cameras IR lights being off. Because the IR-CUT filter would remain over the camera sensor filtering IR light at night. For those IP Cameras. Defeating any purpose of using even external IR lighting effectively for a IP Camera looking through a window, that required its own IR lights to remain off to avoid reflection. Which is what I originally clearly stated as fact. This link below alone. Proves that your above statement is blatantly incorrect, misleading and false. Which is already along side of your own late admission here. That even Foscam IP Camera are doing the same thing as the link below shows other brands and models of IP Cameras are: https://community.ubnt.com/t5/UniFi-Video/UVC-ir-cut-without-LED/m-p/1280873#M41015 The simple fact is that you are wrong and have been wrong about this subject matter yet continue to refuse to own it. I don't owe you links to every IP Camera that is doing the same. After all, your statement above does not exclude any IP Cameras whatsoever. Your statement quoted above, has clearly already been invalidated as blatantly false, misleading and incorrect. You don't need my help to continue to look silly with your statements about this subject matter. Your doing just fine doing that by yourself. Don

You were wrong and are wrong about this subject matter. Own that! Note that I said "Generally Speaking" when I stated that IP Cameras use the same switching circuitry for their IR-CUT filters and IR light controls. I never made any blanket statement that all IP Cameras did same. The above statement is an example of an inaccurate, misleading and false statement. Because it's ALL inclusive and excludes NO IP Cameras of any kind. Please provide any scientific facts provided by trusted sources, that only Foscam IP Cameras use Electromechanical IR-CUT filters in their IP Cameras which use the same internal switching circuitry for their IR-CUT filters and IR light controls. Otherwise, please stop babbling and read and study more. Because you are only continuing to make yourself look more silly than what you already appeared to be. Don

This is absolutely incorrect. Whether or not a camera has an ir cut filter has ZERO bearing on its low light viewing capability with the IR off. You need to stop with your misleading advice to end users. Your statement, is once again a very misinformed one. Many IP Cameras have a Electromechanical IR-CUT filter which slides back and forth over the IP Camera sensor, when IR Lights are enabled/disabled for a IP Camera. Since the IR-CUT filter in those IP Cameras is over the camera sensor when it's in day mode. IR light is filtered from reaching the camera sensor. As long as the IR lights are off in those IP Cameras. The IR filter will remain over the camera sensor filtering IR light. This means that even external IR lighting will not be picked up well until the IP Cameras IR lights are enabled and that IR-CUT filter is slid away from the camera sensor. Generally speaking. IP Cameras that have this feature, do not have the ability to separately move the IR-CUT filter over or away from their camera sensor. Without also simultaneously enabling/disabling their IR lights. Meaning that those functions are on the same internal switching circuitry, of those IP Cameras. Google is your friend about this as well: "The perfect night guard: Cameras with infrared lighting The challenge when doing surveillance with infrared: Infrared light leads to colour distortion during the day. This is why day/night cameras feature an IR-cut filter which keeps the disturbing infrared light out of the image sensor during the day. When the light falls below a certain level, in contrast, the filter automatically swivels out of the way so that the infrared light does hit the image sensor. At the same time, the camera switches to black/white mode, in which it can use the infrared light optimally." From: http://www.abus.com/eng/Commercial-Security/Video-Surveillance/IP-HD-SDI-analog-HD-or-analog/IR-cut-filter "About Mechanical IR Cut Filters IR light is filtered out so that it does not distort the colours of images as the human eye sees them. When the camera is in night (black and white) mode, the IR-cut filter is removed, allowing the camera's light sensitivity to reach down to 0.001 lux or lower." From: http://www.camsecure.co.uk/IRCutFilter.html Please try and do more reading and studying about subjects you have no experience with. Because you are looking very silly as you attack others using false, misleading and incorrect statements. For sure, as you continue to make these misleading, false and unsubstantiated statements. It's not making you look any smarter. I commend you for trying to use your 2+ years of IP Camera experience to try to sometimes help others with IP Camera issues. But you have not reached the supreme level of "Expert of All Things For All IP Cameras". This is NOT a video game. So please continue to learn and study before acting like you won some video game. Which you have not. I am personally not aware of any single person who is a "Expert of All Things For All IP Cameras". So better to continue to read and study, than always claiming that you have already reached, an unobtainable goal. Don

You are very welcome. Just want to make sure that you don't get sucked into anything because of any bias or lack of experience with this or that. Some may claim to have knowledge that they can't substantiate. Minus their words alone. So without also seeing any of those claims validated and confirmed by other trusted sources and/or many reviews in many different places by those that actually purchased specific equipment that substantiate those claims. I would be very leery of any of those types of claims. I think you mean IP Camera vs. webcam since generally a webcam has a USB connection to a computer vs. an IP Camera which has a hard wired Ethernet or WiFi connection to a LAN. Depends on your goals and how close the IP Camera is to the window and if you also wish to monitor motion detection going on the outside from the inside. The other thing is direct sunlight during the day. In many if not most cases since the IP Camera would be at a 45 degree angle looking down you would be ok. But only you know that specific view. So best you decide if that's true for you, in this case. Note: If your outdoor lighting is bright enough at night outside. You would not even need any External IR light outside. If that light by itself covered the complete area outside you wished to cover from inside. You would still want to keep the IP Cameras IR lights off to avoid creating any reflections. That said. Depending on how far you wish to see outside at night if you're set on using a indoor IP Camera to be viewing the outside through a window from the inside. You may want to at least place some external IR light outside to get better night distance while keeping any IR lights in the indoor IP Camera off. This will minimize any possible IR reflection as well as potentially allow you to see a longer distance from the inside looking outside, at night. There are many online stores like ebay and Amazon and others that you can find external IR lights that will turn on and off automatically that can handle any reasonable distances you may need. In some areas you might even be able to find them in brick and mortar home improvement stores. Although they maybe priced higher there then you can get them online. Again, even with something like this. It's best to look for many reviews in as many different places as possible about external IR lights where people say what distances the IR lights really do go vs. any specifications their seller may claim they reach. Some are better than others. So better to be safe that sorry. Two very important points not to lose sight of when using an indoor IP Camera to view outside is: Avoid any IP Camera that uses what's known as a "IR-CUT" filter if you intend to use IR light to see outside at night from the inside looking through a window. This is because these cameras do very poor in low light night conditions when their IR lights are turned off. Because they use a special filter specifically for IR light. Which won't be used when IR lights are disabled in the IP Camera itself. So even with IR external lights outside. Those IP Cameras won't do well at night with their IR lights turned off. While some IP Cameras can control the IR-CUT filter separately from the IR lights. Some cannot. So it's important to distinguish if a IP Camera can control both features separately. If it can't, then don't use that IP Camera with external IR lighting while trying to disable the IP Cameras IR lights. Some IP Camera use built in PIR ("Passive infrared") sensors in some IP Camera models to detect motion. A PIR sensor does not do well behind glass. So if you need to detect outside motion from the inside. Then you would want to avoid those IP Camera models if they also can't do image motion detection separately. Unless you are going to be using some hosted software on a computer, to provide image based motion detection. So, while using a indoor IP Camera to view outside is not the ideal solution when compared to using an outdoor IP Camera. It is done often and can be done successfully in most cases, with a little upfront planning. Don

I will not furnish you with anything. There is no statistical data and you know it. The reason is explained in my earlier post. No sane installer will touch this garbage until its proven. Foolish as usual. Its ok, I understand why you cannot grasp this. Its not your fault. Its simply because you have never installed an ip camera. Also stop editing your post after the fact its misleading and you do it intentionally. LOL from the man who has no documented experience anywhere on the Internet worldwide older than 2+ years that has anything to do with IP cameras. Well said for that limited experience. Nice try. Your claims would be confirmed and validated by trusted sources by now. If your claims were valid. Nobody could hide those facts. Must be a "Conspiracy Theory" you believe in where a group of people are hiding the "Real Truth" from IP Camera owners. LOL. Do you know of any other secrets being held from us? None of us seem to have "Your connections" including trusted sources. So, please share any other secrets being held from us. Don

LOL now your going to once again make things up and say that good ones need to mostly be expensive. Again, where's your scientific facts by a trusted source to back this garbage up now? Don Quality brands like axis, Avigilon, vivotek are simply more expensive. Hikvsiion and dahua also both have more expensive lines. I have tested enough "new" promising cameras to know they have HIGH failure rates. The led's are overdriven and fail, in 6-12 months, the ir cut filters fail, and on the zoom cameras the focus mechanism fails. You can rant and rave all you want...no one has statistical data because installers who install many cameras will not risk their reputation on a startup. I owe you nothing and will provide nothing to you. Show me data that says that startup brands are just as reliable as established brands...you cant. I know reliability is a hard concept to grasp since you deal with foscams...its important to installers and their customers. Again, where's your scientific facts by a trusted source to back this garbage up now? So far, all you have done is fear monger using your personal opinions. Your overdue for providing some facts that backup your claims, from a trusted source. Don

LOL Now your going to once again make things up and say that good ones need to mostly be expensive. Again, where's your scientific facts by a trusted source to back this garbage up now? Don't worry I won't wait, because I know you have none. Don