616 Reply by joan

(8 replies, posted in Bug reports)

I committed a fix, it should respect the original proportion of the tool now.

Note that the scaling reference is hard coded at the moment. There is a virtual 800x600 canvas that the custom tool is assumed to be drawn on to, and when adding the tool it will be upscaled or down-scaled depending on the size of the target video. So for example if the initial point list covers half of this virtual canvas, they will also cover half of the image when the tool is added. This should probably be something controlled directly within the tool XML.

Go to forum: Bug reports

617 Reply by joan

(8 replies, posted in Bug reports)

It could be related to how the points coordinates are rescaled when the object is loaded into a video, to match the target image size.

Edit: there are several issues, this will need further investigation. First the textDistance wasn't properly scaled when adding the tool the first time. Secondly, the scaled values for the angles weren't taken into account anyway. These don't exactly match your symptom though. Then there is an issue that when saving the tool in KVA, it only saves the points and it looses the scaling information.

Go to forum: Bug reports

618 Reply by joan

(8 replies, posted in Bug reports)

Yes you are right, the format was updated, although the old format should still work for the most part.
It was indeed not possible for an object to be controlled by multiple options.

For documentation, the old page was painful to maintain. What I would like to do instead is have a "sample" tool with a collection of everything possible and many comments in the XML. This tool would be available in the menu as any other so you could experiment with it directly to find the appropriate object and mechanism, and then copy-paste the relevant parts.

For text distance, it is the distance to the center of the label, in pixels. The rectangular area covered by the text is first measured, based on the text itself and font size, and then the center of that rectangle is placed at the textDistance value, along the bisector of the angle.

Go to forum: Bug reports

619 Reply by joan

(1 replies, posted in Bug reports)

Thanks for the heads up! I added a fix.

While checking this I realized I have multiple microphones that all return the default "product ID", so selecting most of them is impossible, it always revert to the last one. VoiceMeeter virtual input/output cables and the Oculus Rift mic all have the same ID…

Go to forum: Bug reports

620 Reply by joan

(8 replies, posted in General)

Yes if you subtract the points (end - start) then you should be able to use the atan2 function to get an angle relative to the x-axis. I think Excel has such a function.

Go to forum: General

621 Reply by joan

(8 replies, posted in General)

Hi,
Unfortunately at the moment there is no way to get the angle between two disconnected segments. And there is also no way to get the angle-to-horizontal axis in the perspective calibration case.
For this second case it could be added to the line tool without too much effort. I think this could also help in another specific scenario with the goniometer tool that has been causing an issue.

Go to forum: General

622 Reply by joan

(2 replies, posted in General)

Hi,
This will be fixed in the next version with support for rotation directly in the capture screen. Recorded videos will then be saved with the corresponding rotation flag, so when opening them on the playback side they will be automatically oriented correctly.

Go to forum: General

623 Reply by joan

(38 replies, posted in General)

Thanks.

By "the dialog box that opens has a "Quick Access" section", you mean when doing menu File > Open video file? I'm not sure how the Quick Access feature of these system dialog work to be honest, we just setup the dialog title, initial directory and file type filter. The rest is handled by Windows. It seems weird that a user could have access to the files of another.

You could also try with the .zip version instead of the installer, it is self-contained in whichever folder you extract the zip to, so if the problem is coming from the application data folder (which has the preferences, shortcuts, history and is normally stored under the user files), maybe it won't have the same issue.

Go to forum: General

624 Reply by joan

(1 replies, posted in General)

There is an auto-rotate based on the metadata of the video file. At the moment the files captured from the capture screen don't have this flag because rotation wasn't supported there but in the next version the procedure will be to orient the image in the capture screen to make it upright (using the same Image > Image rotation menu), and this will make it store the correct rotation flag in the captured videos.

Go to forum: General

625 Reply by joan

(2 replies, posted in Ideas and feature requests)

This should be fixed in the next version with support for rotation in the capture screen.

Go to forum: Ideas and feature requests

626 Reply by joan

(5 replies, posted in Bug reports)

Hi,
The automatic slow down happens when the program can't playback the video at the expected framerate because it's too much processing.
What version is this with? On recent versions (after ~0.8.20 or something) there is an optimization that should help a lot with this. Please test with 0.9.1 and let me know if you reproduce the issue.

Going all the way to 0% is strange though, I imagine the original is at 240 fps and the program detects it's missing a ton of frames repeatedly.

Regarding memory allocation: if you reduce the working zone enough that it fits in the allocated memory it will decompress the frames in advance and you shouldn't have the problem.

Go to forum: Bug reports

627 Reply by joan

(3 replies, posted in Bug reports)

You're right, at the moment it's not really possible to do this.

You can use start/stop tracking to prevent objects from being tracked after the section you are interested in.
When you start tracking, it automatically changes the visibility option from the default fading to "Always visible". (You can change it back but it might become invisible before the tracking section is over.).

In the next version there will be more control over each drawing's visibility/fading. In theory it will allow you to do this as you can keep a drawing visible for a set number of frames but it will be tedious to match duration manually. I'll check how to support such an option in a more friendly way.

Go to forum: Bug reports

628 Reply by joan

(1 replies, posted in Bug reports)

This sounds awesome! Thank you for looking into this.

edit: Tested with various alphabets and it seems to work beautifully. Thanks!

Go to forum: Bug reports

629 Reply by joan

(2 replies, posted in General)

Hi,
You are right, the documentation is obsolete on this point, the capture system was rewritten for performance reasons and this particular feature, in the way it was written, wasn't compatible with the changes.
I'm looking at supporting this again for the next version with a different approach to keep the recording performance intact.

You can design your own grid. There is no "designer" application though, it has to be created manually in an XML file.

Go to forum: General

630 Reply by joan

(3 replies, posted in Bug reports)

It's a bug. For some reason there was an explicit test capping the output framerate to 100 fps. I traced it to a specific commit in 0.8.22 but I don't remember why I put it there in the first place. I can't think of any adverse effects of removing this limit at the moment. Should be fixed in the next version.

Go to forum: Bug reports