Page 1 of 1

Bandicut 3.5.0.577, bug report & suggestions

Posted: Sat Sep 28, 2019 2:40 pm
by gdgsdg123
[Bug Report] Problematic seeking to the 1st frame

When opening a file, it at times automatically seek to the 2nd frame rather than the 1st. (despite the timestamp being erroneously displayed as 00:00:00.00)

And attempting to manually seek to the 1st frame can be problematic at times. (capped at the 2nd frame)




[Bug Report] Maximized window obstruction on Windows 7

The maximized interface can be obstructed by the Taskbar. (not happening on Windows 10)




[Bug Report] Key combination: "Ctrl + C", interference

The shortcut for Capture (Ctrl + C) interferes with Windows' native shortcut for Copy.

Which can pose quite a nuisance when trying to copy the timestamp. (the "Right Click" context-menu method doesn't work in this case, neither)




[Bug Report] Joiner, temp file problem

viewtopic.php?f=22&t=8719

Yes, still the old problem. (without changing the "Cache folder", though I doubt changing it would make much difference)




[Suggestion] Frame as the unit

When cutting using time as the unit, the beginning/end of the output segment may be slightly off due to the accuracy problem.

Using frame as the unit can completely eliminate this problem.




[Suggestion] Seeking via directly entering the time/number

Key combination: "Ctrl + T"/"Ctrl + G", showing a pop-up textbox for the input.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Mon Sep 30, 2019 9:39 pm
by Bandicam Company
Hello,

We will forward your post to the development team and get back to you when we have got any feedback from them.

Thank you very much for your report.

Follow-Up

Posted: Fri Oct 18, 2019 7:23 am
by gdgsdg123
gdgsdg123 wrote:[Bug Report] Problematic seeking to the 1st frame

When opening a file, it at times automatically seek to the 2nd frame rather than the 1st. (despite the timestamp being erroneously displayed as 00:00:00.00)

And attempting to manually seek to the 1st frame can be problematic at times. (capped at the 2nd frame)

Part of the problem doesn't exist in Bandicut 3.1.5.511. (no incorrect seek upon opening)



gdgsdg123 wrote:[Bug Report] Maximized window obstruction on Windows 7

The maximized interface can be obstructed by the Taskbar. (not happening on Windows 10)

The problem doesn't exist in Bandicut 3.1.5.511.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Oct 18, 2019 2:15 pm
by Bandicam Company
Hi gdgsdg123,


Please try the latest Bandicut 3.5.0 beta from https://www.bandicam.com/bandicut-video ... /download/

We have fixed the maximized interface bug you reported.

Thank you very much!

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Mon Oct 21, 2019 3:37 pm
by gdgsdg123
Bandicam Company wrote:Please try the latest Bandicut 3.5.0 beta from https://www.bandicam.com/bandicut-video ... /download/

...I suggest reading the title.


And just linking this (Bandicut 3.5.0.577, problem handling high data rate videos).

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 7:44 am
by gdgsdg123
gdgsdg123 wrote:When cutting using time as the unit, the beginning/end of the output segment may be slightly off due to the accuracy problem.

True though, the app still acts in a WYSIWYG manner.

The real problem about the app's cutting accuracy is the misuse of ffmpeg's `-t` parameter over `-to`, which to some extent rendered the app's cutting accuracy near the last frame sort of unpredictable.


And the display/interaction accuracy of timestamps should be increased by 1 digit (HH:MM:SS.mmm), to maintain predictable cutting accuracy in most common cases.



Also, please allow me editing posts over an indefinite time. At times I might need to fix inaccuracies in them.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 11:50 am
by Bandicam Company
Hi gdgsdg123,

The real problem about the app's cutting accuracy is the misuse of ffmpeg's `-t` parameter over `-to`, which to some extent rendered the app's cutting accuracy near the last frame sort of unpredictable.

We will try to fix this issue in the future. Thank you for your report.

Also, please allow me editing posts over an indefinite time. At times I might need to fix inaccuracies in them.

Please send an email to bandicut@bandicam.com. We will update your old post manually.


Thank you!

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 1:04 pm
by gdgsdg123
Bandicam Company wrote:
gdgsdg123 wrote:Also, please allow me editing posts over an indefinite time. At times I might need to fix inaccuracies in them.

Please send an email to bandicut@bandicam.com. We will update your old post manually.

Well... it doesn't have to be this complicated.

I believe it can be done just by adjusting some forum settings.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 2:20 pm
by Bandicam Company
Sorry, we can't change our current settings because of spam posts.
Just for your information, you can't edit a post which is older than xx days.
If you send an email, we will definitely update your old post.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 11:51 pm
by gdgsdg123
Bandicam Company wrote:Sorry, we can't change our current settings because of spam posts.
Just for your information, you can't edit a post which is older than xx days.
If you send an email, we will definitely update your old post.

Spamming by editing old posts?.. Alright.

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Fri Nov 08, 2019 11:57 pm
by gdgsdg123
gdgsdg123 wrote:[Bug Report] Key combination: "Ctrl + C", interference

The shortcut for Capture (Ctrl + C) interferes with Windows' native shortcut for Copy.

Which can pose quite a nuisance when trying to copy the timestamp. (the "Right Click" context-menu method doesn't work in this case, neither)

The essence of the problem is the broken Copy & Paste support for timestamps. (pasting for timestamps also not working properly)

Append to the main post

Posted: Tue Nov 26, 2019 2:02 am
by gdgsdg123
[Suggestion] Seconds as the time unit

An option to allow using seconds as the time unit can be useful.

Also, the display/interaction accuracy of timestamps in this scheme can be increased to 6 digits (S+.mmmmmm). (for aesthetic purpose mainly... but might have other uses)

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Sat Jan 04, 2020 6:01 am
by gdgsdg123
How's the situation in Bandicut 3.5.0.594?..

Especially those:

Re: Bandicut 3.5.0.577, bug report & suggestions

Posted: Wed Jan 08, 2020 8:57 am
by gdgsdg123
gdgsdg123 wrote:The real problem about the app's cutting accuracy is the misuse of ffmpeg's `-t` parameter over `-to`, which to some extent rendered the app's cutting accuracy near the last frame sort of unpredictable.

Or it can be a FFmpeg issue if the app uses `concat` demuxer for the purpose...