Messages

1

Chronos User Discussion / Savingdirectory & Triggerdelay (segmented)

« on: April 15, 2025, 12:59:13 AM »

Hi,

is there a parameter for the API to change the directory of saving, while having an nfs-device?
Furthermore is there a parameter to change the trigger delay? All my frames of each segment have to be captured after the triggersignal or isn't it necessary to change anything to achieve my goal?

Thanks!
 

2

Chronos User Discussion / Re: Is this a known issue and if so is there a workaround?

« on: April 02, 2025, 04:40:29 AM »

Hi,

do I understand correctly that you trigger each segment "by hand" (marked ######) because you don't have an external trigger, so that I can ignore this part of the code if I have one?

Also do I have to manually start the the recording?

And finally if I disable the looping of the ring buffer the recording will stop when the buffer is full. Is it correct, that it'll also stop if the defined number of segments is reached, even if the segments aren't "full"?
For better understanding, I want to capture an repetitive, very short event so it's not possible to save between events. That's why I want to use the segmented record mode. But I don't know how long such an event lasts till it's re-triggered and starts from the beginning, therefore my idea was to define 10 segments to capture 10 events after one another just try. My fear is that there will be a problem if the segment is defined for 2000 frames but the trigger for the next event hits every 1500 frames.

Thanks in advance for your help!

Code: [Select]

#!/usr/bin/python3
import time
import requests

ipAddress = '192.168.12.1'
totalFrames = 20000
totalSegments = 50
segmentInterval = 5

print(f'Flushing any previously recorded data for Chronos at {ipAddress}')
requests.post(f'http://{ipAddress}/control/flushRecording', json = {})

print(f'Setting recording frames quantity to {totalFrames}')
requests.post(f'http://{ipAddress}/control/set', json = {'recMaxFrames': totalFrames})

print('Setting recording mode to segmented')
requests.post(f'http://{ipAddress}/control/set', json = {'recMode': 'segmented'})

print(f'Setting recording segments quantity to {totalSegments}, each with a duration of {totalFrames // totalSegments} frames')
requests.post(f'http://{ipAddress}/control/set', json = {'recSegments': totalSegments})

print('Starting first segment recording')
requests.post(f'http://{ipAddress}/control/startRecording', json = {})

##########
for i in range(totalSegments):
    # Wait segment interval
    time.sleep(segmentInterval)

    # Trigger next recording segment
    requests.post(f'http://{ipAddress}/control/set', json = {"ioMappingTrigger": {"source": "alwaysHigh", "invert": True }})
    requests.post(f'http://{ipAddress}/control/set', json = {"ioMappingTrigger": {"source": "alwaysHigh", "invert": False }})
   
    print(f'Recorded segment {i + 1} of {totalSegments}')
##########
# Wait segment interval
time.sleep(segmentInterval)

print('Stopping recording')
requests.post(f'http://{ipAddress}/control/stopRecording', json = {})


3

Chronos User Discussion / Re: Speeding up the saving process

« on: March 27, 2025, 03:26:51 AM »

Thanks for the quick reply and the tip with the API and the segmented mode. I will definitely try this!

The automation of the web interface is done via Selenium, so that a web driver is generated and the program simply clicks through the interface like a user. It's also possible to do this in the background

Are you already finished with your program for splitting the videos? It looks like I'm heading for the same problem if I try your tip.

4

Chronos User Discussion / Speeding up the saving process

« on: March 26, 2025, 01:41:06 AM »

Hello,

for a project, I need to set up the camera to start recording according to a repetitive TTL triggersignal. I'm doing this with a code that accesses the web interface and configures all settings there. Unfortunally the saving process takes for a 1s video (1770frames, H.264 formate) more ore less a minute and but the trigger signal to start the next recording is a lot faster.

Is there a way to speed things up?
Would it be faster/simpler to use the REST API?