Posted by: sphinx
« on: November 08, 2025, 08:08:55 pm »It was a faulty sound card, even if everything appeared to be functional.
Card replaced, problem solved.
Card replaced, problem solved.
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Posted by: sphinx
« on: July 31, 2024, 08:36:40 am »The Test button does not return meaningful time value. The value is set only upon the event, otherwise it's undefined.I guess so, but not the Test button functionality is my problem.
Posted by: Jan
« on: July 30, 2024, 11:21:22 pm »The Test button does not return meaningful time value. The value is set only upon the event, otherwise it's undefined.
Posted by: sphinx
« on: July 30, 2024, 08:35:56 pm »Let me bring more details.
I have running 2 instances of Silence Detector on the same PC (Windows 10), each in its own folder.
Both instances send HTTP queries with %date and %time variables.
One instance runs with no problem, the values assciated with those variables are correct.
The second instance, the one I am complaining about, send %date and %time with wrong values.
That means that if the date and time of an event is, let's say, 2024-03-22 17-44-10, the values of date and time sent by the second instance is like 2024-03-21 13-22-19.
It makes no sense for me.
More over, what I noticed is that when I test the query by pressing the Test button from the Alarm Tasks and Return Tasks, the values of associated with %date and %time are those from DateTime within priraside.ini file, which seems to be the date and time when Silence Detector was installed (or started).
I have running 2 instances of Silence Detector on the same PC (Windows 10), each in its own folder.
Both instances send HTTP queries with %date and %time variables.
One instance runs with no problem, the values assciated with those variables are correct.
The second instance, the one I am complaining about, send %date and %time with wrong values.
That means that if the date and time of an event is, let's say, 2024-03-22 17-44-10, the values of date and time sent by the second instance is like 2024-03-21 13-22-19.
It makes no sense for me.
More over, what I noticed is that when I test the query by pressing the Test button from the Alarm Tasks and Return Tasks, the values of associated with %date and %time are those from DateTime within priraside.ini file, which seems to be the date and time when Silence Detector was installed (or started).
Posted by: Jan
« on: July 30, 2024, 06:51:03 pm »What does it mean "wrong" in this context?
The %time value is associated with the most recent event (alarm or return). It may not show current time.
The %time value is associated with the most recent event (alarm or return). It may not show current time.
Posted by: sphinx
« on: July 30, 2024, 06:36:08 pm »I am using the latest version of Silence Detector.
I am sending an HTTP query with %time variable in Alarm Tasks and Return Tasks.
The problem is that the value of the %time variable is wrong.
Any ideea why?
I am sending an HTTP query with %time variable in Alarm Tasks and Return Tasks.
The problem is that the value of the %time variable is wrong.
Any ideea why?