μGiffer [graphic capture utility]
Re: μGiffer [graphic capture utility]
0.9.7 is out, fixes a GDI handle leak in capture phase.
Re: μGiffer [graphic capture utility]
0.9.9 is out
F1 now starts the capture after a 3 second countdown.
Ctrl-F1 starts it immediately.
There's also now an option of not deleting captured BMP frames after GIF is created (and do that immediately before the next capture instead).
F1 now starts the capture after a 3 second countdown.
Ctrl-F1 starts it immediately.
There's also now an option of not deleting captured BMP frames after GIF is created (and do that immediately before the next capture instead).
Re: μGiffer [graphic capture utility]
Just tested μGiffer latest release and I'm really impressed by how efficient it runs.
A few niggles, though:
A few niggles, though:
∙ If 'uGiffer.ini' is present in the program folder, it isn't automatically picked up. I know it should be passed as a parameter with '-c' command option but it would make uGiffer simpler to operate if it did automatically.
∙ Even using the '-c' option, μGiffer doesn't seem to support relative paths and throws an error if you try to use them (see below). If changing that, please add environment variables as well.
∙ IMHO, even some sort of minimal command toolbar -- with buttons like Go, Pause and Stop -- would be a great usability improvement.
∙ I'm getting some artifacts with video capture that I don't know how to get rid of. Truth be told, I get them in most other giffing tools and μGiffer is the best in this particular aspect.
∙ The Github 'readme.txt' should be part of the download, which should also be packaged into some kind of archive format. Naked executable downloads from the Internet tend not to fare very well.
Re: μGiffer [graphic capture utility]
Hi Midas, thanks for the notes.
It is meant for rather specific type of use and it's trivial to learn how to use it that way. Aim, press F1, press F1 (or Esc), done. Once you know this, there's no need for a toolbar. It will be just an embellishment.
If you have a use case where a toolbar is a must, please describe it.
I'm not a big fan of keeping config data alongside with the binaries, but I can make the program check for .ini in the exe folder first (and if -c is not specified).∙ If 'uGiffer.ini' is present in the program folder, it isn't automatically picked up. I know it should be passed as a parameter with '-c' command option but it would make uGiffer simpler to operate if it did automatically.
Supporting relative paths is a road to (support) hell, because different people would assume different things about what it is relative to. The lack of support for relative paths is by design, basically. Supporting envvars is not a bad idea, but they will need to expand into an absolute path. Let me see what I can do.∙ Even using the '-c' option, μGiffer doesn't seem to support relative paths and throws an error if you try to use them (see below). If changing that, please add environment variables as well.
Strongly disagree.∙ IMHO, even some sort of minimal command toolbar -- with buttons like Go, Pause and Stop -- would be a great usability improvement.
It is meant for rather specific type of use and it's trivial to learn how to use it that way. Aim, press F1, press F1 (or Esc), done. Once you know this, there's no need for a toolbar. It will be just an embellishment.
If you have a use case where a toolbar is a must, please describe it.
Can you elaborate?∙ I'm getting some artifacts with video capture that I don't know how to get rid of. Truth be told, I get them in most other giffing tools and μGiffer is the best in this particular aspect.
The whole GH "page" is just a temporary hack. I've been meaning to put together a proper page, but haven't had time for that yet.∙ The Github 'readme.txt' should be part of the download, which should also be packaged into some kind of archive format. Naked executable downloads from the Internet tend not to fare too well.
Re: μGiffer [graphic capture utility]
You know better than we do about supporting a very popular software project, but keeping everything in the same folder is at the heart of portability. If you're running something off a removable drive, the absolute path is going to change and/or die as soon as you have another drive plugged in. This happened to me earlier today as I had to rename my backup process to point to E:\ after an attached SD card pushed my drive out of the D:\ slot. Relative paths in this way require less work/configuration. Storing these configuration changes to the local folder works similarly.
Many of the programs here on the site unsurprisingly disable those by default, but make them options either via config file or Preferences menu item. Of course, if your users aren't going to run things off an encrypted volume, cloud folder, or USB drive, you certainly don't need those tweaks.
Re: μGiffer [graphic capture utility]
0.9.10 is out
* Arrows, Ctrl-Arrows, Ctrl-Shift-Arrows now move window, bottom-right and top-left corners respectively. Useful for finer position/size adjustments.
* Window can no longer be resized to be less than 1 px tall.
* Both 32- and 64-bit binaries are now in a single zip file.
source
* Arrows, Ctrl-Arrows, Ctrl-Shift-Arrows now move window, bottom-right and top-left corners respectively. Useful for finer position/size adjustments.
* Window can no longer be resized to be less than 1 px tall.
* Both 32- and 64-bit binaries are now in a single zip file.
source
Re: μGiffer [graphic capture utility]
Oops, sorry for a late reply, this must have slipped by me...
Another time tested solution is to check for a 'portable' or 'conf' sub-folder, and place the INI there.
You could easily solve that by inserting YOUR definition of what a relative path is, in a comment in the INI, for instance...
Fair enough, it's your program after all.
It's just that, at my age, the hands are not that precise anymore; it gets easier to click a (preferably large) button to stop a process at a moments notice than to aim for a tiny key on your keyboard while keeping an eye on the screen...
I don't create GIFs all that often. When I do, I'll be sure to report back.
I was laboring under the impression that Github creates the packages on its own, if you place the files in the right location.
But then again, thanks for making your excellent programs available for the Internet at large.
vacherin wrote: ↑I'm not a big fan of keeping config data alongside with the binaries, but I can make the program check for .ini in the exe folder first (and if -c is not specified).
Another time tested solution is to check for a 'portable' or 'conf' sub-folder, and place the INI there.
vacherin wrote: ↑Supporting relative paths is a road to (support) hell, because different people would assume different things about what it is relative to. The lack of support for relative paths is by design, basically. Supporting envvars is not a bad idea, but they will need to expand into an absolute path. Let me see what I can do.
You could easily solve that by inserting YOUR definition of what a relative path is, in a comment in the INI, for instance...
vacherin wrote: ↑Strongly disagree.
It is meant for rather specific type of use and it's trivial to learn how to use it that way. Aim, press F1, press F1 (or Esc), done. Once you know this, there's no need for a toolbar. It will be just an embellishment.
If you have a use case where a toolbar is a must, please describe it.
Fair enough, it's your program after all.
It's just that, at my age, the hands are not that precise anymore; it gets easier to click a (preferably large) button to stop a process at a moments notice than to aim for a tiny key on your keyboard while keeping an eye on the screen...
vacherin wrote: ↑Can you elaborate?∙ I'm getting some artifacts with video capture that I don't know how to get rid of. Truth be told, I get them in most other giffing tools and μGiffer is the best in this particular aspect.
I don't create GIFs all that often. When I do, I'll be sure to report back.
vacherin wrote: ↑The whole GH "page" is just a temporary hack. I've been meaning to put together a proper page, but haven't had time for that yet.
I was laboring under the impression that Github creates the packages on its own, if you place the files in the right location.
But then again, thanks for making your excellent programs available for the Internet at large.
Re: μGiffer [graphic capture utility]
Update's out:
- F3 now takes a single screenshot - like Alt-PrtSc, but capturing the mouse cursor too
- Ctrl - ~ (that's tilda, top-left key in the keyboard's main section) now stops the recording even if μGiffer doesn't have the focus
- Few more key combos, documented in the brand new "User manual" accessible via window's system menu
- It's now also possible to pin it to a specific CPU if needed
- __philippe
- Posts: 687
- Joined: Wed Jun 26, 2013 2:09 am
Re: μGiffer [graphic capture utility]
Nice! I've seen so many screen recorders at this point it's almost reassuring that someone can still just keep upping the ante.__philippe wrote: ↑Sat Sep 11, 2021 3:50 am uGiffer v0.9.13.0 (link date 28-APR-21) handy right-click "User Manual" ...
Re: μGiffer [graphic capture utility]
0.9.14 is out - fixes an issue with capturing cursors that are not 32x32 px or another issue with cursors being changed mid-frame.
Previously, the former caused larger (or smaller) cursors to be scaled to 32x32 and the latter caused the cursor not be drawn in affected frames at all.
Homepage: https://iobureau.com/ugiffer
Download link: https://iobureau.com/ugiffer/uGiffer-0.9.14.zip
I should really add a change log to the homepage instead of using this thread as one.
Previously, the former caused larger (or smaller) cursors to be scaled to 32x32 and the latter caused the cursor not be drawn in affected frames at all.
Homepage: https://iobureau.com/ugiffer
Download link: https://iobureau.com/ugiffer/uGiffer-0.9.14.zip
I should really add a change log to the homepage instead of using this thread as one.
Re: μGiffer [graphic capture utility]
from virustotal..
Download link: https://iobureau.com/ugiffer/uGiffer-0.9.14.zip
...
https://www.virustotal.com/gui/file/3e7 ... /detection
[5/67]Popular threat label: trojan.
Download link: https://iobureau.com/ugiffer/uGiffer-0.9.14.zip
...
https://www.virustotal.com/gui/file/3e7 ... /detection
[5/67]Popular threat label: trojan.
- DeepInstinct: MALICIOUS
- Ikarus: PUA.CoinMiner
- Kaspersky: VHO:Trojan-PSW.Win32.Agent.gen
- Malwarebytes: MachineLearning/Anomalous.100%
- ZoneAlarm by Check Point: VHO:Trojan-PSW.Win32.Agent.gen
Re: μGiffer [graphic capture utility]
These are false positives for 32-bit binary being UPX compressed.
Here's 64-bit .exe (from the .zip) - https://www.virustotal.com/gui/file/43a ... c1303b98f8 (0 detections)
Here's 32-bit .exe (from the .zip) - https://www.virustotal.com/gui/file/690 ... 4fb15a517e (12 detections, none specific)
Here's the same 32-bit .exe, decompressed - https://www.virustotal.com/gui/file/c36 ... 54b7f7b1c9 (1 detection, "AI" variety)
You can reproduce this yourself by extracting 32-bit/uGiffer.exe and removing UPX compression with "upx.exe -d uGiffer.exe"
UPX binaries you can get from here - https://github.com/upx/upx/releases
Here's 64-bit .exe (from the .zip) - https://www.virustotal.com/gui/file/43a ... c1303b98f8 (0 detections)
Here's 32-bit .exe (from the .zip) - https://www.virustotal.com/gui/file/690 ... 4fb15a517e (12 detections, none specific)
Here's the same 32-bit .exe, decompressed - https://www.virustotal.com/gui/file/c36 ... 54b7f7b1c9 (1 detection, "AI" variety)
You can reproduce this yourself by extracting 32-bit/uGiffer.exe and removing UPX compression with "upx.exe -d uGiffer.exe"
UPX binaries you can get from here - https://github.com/upx/upx/releases