![]() Facility maps with thumbnail links for cameras, embedded layouts, and embedded facility maps. Select recorded video files or motion events for a specific day, month, or year range. Quick access to recorded video through a list of files, by entering a date and time, or by selecting motion events point PTZ enabled cameras to preselected positions View camera information such as frame size, frame rate, last read and write times, network bandwidth, codec, and camera model. Maintain aspect ratio of high resolution images Synchronized playback available for multi-camera views (requires server version 7.0.0.45 or newer) Timeline available on multi-camera views Save a video snapshot to as an email attachment, as a file on your system, or export it directly to iPhoto. View live cameras in layouts of up to 36 cameras. Access live and recorded video from any Video Insight server Reload all servers or one particular server at the touch of a button. View current connection and server version for all your servers at a glance. View server statistics such as CPU and memory utilization, used disk space, available cameras, serial number, and unique ID. Option to use unique login credentials for each server providing federated login Support for private and public IP addresses. Import a server's cameras, maps, and layouts with just one IP address. User access is controlled by the Video Insight Server with robust integration with Active Directory/LDAP users and groups. View facility maps with the location of your cameras, embedded views, and embedded maps. View recorded video by selecting a video file, a specific time, or a motion event. Users can save, email snapshots, or export the snapshot into iPhoto. The app imports all settings from a single address providing users access to individual cameras or in groups of cameras in pre-defined views. Users can view and control PTZ cameras, view full resolution and high frame rates with H.264. VI Monitor is a video management system app that allows authorized users to access live and recorded video from any camera on any server. Price: Free, Version: 2.0 -> 2.1 ( iTunes) CSV export of your transactions (e.g to Dropbox) Administration of transactions, categories, accounts Data filtering, sorting, grouping and aggregation Evaluation of your expenses, income and budget Storage of your expense and income data ![]() Simplified usage by voice input and output SayMoney is an innovative solution for administration and evaluation of your personal finances. I will be checking to see how stable this fix remains.Price: Free, Version: 1.3.15 -> 1.3.22 ( iTunes) The proper grid color remained on the map.Īt this point, then, I’m assuming that somehow (the “why” is above my pay grade and better left for the programming experts) the link between LOTW and GT was not being made or had been lost, with an old lotw.adi file getting in the way (?). I did a couple of simple tests thereafter: 1) quit GT: the clublog.adi file remained in the GT folder but the lotw.adi file was gone 2) restart GT: the clublog.adi file was updated (new timestamp) and a new lotw.adi file was generated. And suddenly, all the grids were properly colored again. After a minute or so, a new lotw.adi file also showed up. After starting GT, though, the ClubLog.adi file appeared almost immediately. Before startup, only the GridTracker_QSO.adi file appears. You can actually watch the results in real time if you have the GridTracker folder that holds the. Assuming that LOTW is the only source that can provide QSL verification (and hence, give me a properly colored grid), I cleared those files (using the “clear log” button in the QSO status window) and restarted GT. adi file for each logging program to which it’s connected. However, the GT Wiki indicates that when GT starts, it will create a temporary. adi files from LOTW, ClubLog, or GT 2) testing on an older version of GT 3) systematically turning off logging programs one at a time and then turning them back on. Initial attempts at a fix that did not solve the issue: 1) reloading all. Setup: Icom-7610, MacOS 10.15.7 running GT, WSJT-X, JTBridge, and RUMlogNG. ![]() My apologies in advance if this is a Captain Obvious type of solution: I think I found the fix and thought I’d post the results in case anyone else runs across this issue. All connections in the Settings/Logging window gave a “passed” result when tested. Recently (1/27/22) I posted about an issue in which the set QSL color (green) had disappeared after working perfectly for a couple of weeks and reverted to the QSO color (yellow), with no apparent intervention on my part.
0 Comments
Leave a Reply. |