Search options (Page 51 of 134)

The function is called "Overview" in the English locale.

If you scroll with the mouse it will change the number of panels. Since the original aspect ratio is maintained it will only use perfect squares: 2x2, 3x3, 4x4, 5x5, 6x6, etc. The max is 10x10.

It's not currently possible to zoom or pan inside the images, get rid of the number, add analysis drawings or select the exact set of images you want to showcase. I agree it would be nice to have more options and be able to create a presentation using exactly the content you want. The main problem may be that the entire feature is only available when the player is in the special mode where the current section images are all cached in memory.

This should be fixed in the next version.

Thanks for the report. The parsing of the camera URL was indeed eating the "query" part. I just fixed it and should work again in the next version.

Just to clarify, I'm not currently actively working on this. The top priority for 0.8.26 is to be able to export angle tracking timelines and update the Basler module to work with Pylon 5.

Hi,
Thanks for the report.
Could you make a quick test to see if version 0.8.25 has the same issue?
The auto slow down is when there is not enough resources to handle the video(s) at the nominal speed.
Did you have superposition enabled? Does it cause trouble specifically with that function enabled or all the time?

Thanks for the feedback!

The delay feature is alive and well and has been expanded in the latest version (see mosaic button that allow you to split the capture screen and get multiple streams from the same camera at different delay values).

What has changed is that when recording video, we previously recorded whatever was displayed in the capture screen, so if you had a 10-second delay and recorded 5 seconds of video, at the end of the recording you have on file an action that happened before you hit the record button.

The new behavior (since 0.8.24, March 2015) is to record the stream as it comes from the camera, independently of what is shown on screen. So if you have a 10-second delay and record 5 seconds of video, at the end of the recording you have the  action following your hitting the record button.

This was done to improve the recording performance and avoid dropped frames. Dropped frames cause mismatches between real time and video framerate and break time and speed measurements when analyzing the videos, so it's very important to get this right.

I understand that there is now a missing feature of being able to record action in "pre-roll" fashion and considering various options.

Another feature that is often requested is to be able to increase the size of the delay buffer. This is currently limited by memory. It should be possible to increase it on 64-bit versions, but the real solution would be to allow the delay buffer to be stored on disk. I feel these two features are interlinked because if we have the delay buffer in a temporary file on disk, it should be a small step to being able to save the part of the delay buffer between the start and stop record commands to be converted to a regular video file.

There is slow motion on a live feed indeed. It was actually the challenge that sparkled the development of this multi-view feature. In the mosaic configuration dialog the third option is Slow motion.

Obviously continuous slow motion is not sustainable per se, if you are at 0.5x speed for example, during the time you are watching the slowed down feed, twice as much data needs to be cached for later display. This can't be going on forever. The way it works is using the multiple views, each view starts at a different point in time and slowly drifts, until it jumps back to live and start drifting again. Any given action should be displayed in slow motion somewhere in one the sub-feed or maybe start in one and end in another.

Yeah record/replay scenarios would be very interesting. I'm starting to think that the way to keep it completely open to the myriad of use-cases would be to make it fully "programmable", and have a bunch of standard scripts built-in for ease of use. Then for niche use-cases people can write their own script or have someone write it for them.