Nicke Manarin
Nicke Manarin
I did this on purpose to prevent a recording with different sizes. To enable this, first I'll need to enable some flexibility on my code, I believe it can be...
Strange, that's not happening here. I run the installed version (msi) and debug via VS. Apparently, this is an issue with .NET 6: https://github.com/dotnet/wpf/issues/6289
@majkinetor Hi, sorry for taking so long. I would like to push this forward, at least with FFmpeg. With Gifski and SharpDX, it's a little bit different. I think that...
Strange, it's not working on my tests in here: I added these lines to the nuspec: ``` [...] ``` And I'm trying to test with this command: `choco install -fdv...
Forget it, it's working now with this command, running the same folder as the package: `choco install -s "'.;https://chocolatey.org/api/v2/'" -fdv screentogif`
Now for the Gifski and SharpDX, I think that I could simply ship my own MSI file. But I'm not sure how existent "choco" installations of ScreenToGif would work. Because...
I'll try to embedd both Gifski.dll and SharpDX.dll.
@lucastheisen Yes, it can be. Thanks.
I'm glad that you love it :) Without encoding the file in the background, I don't see a way to predict the file size.
By annotation, @infreespace means text or drawings? During recording or afterwards? Both are available afterwards, and at least drawings will be available during recording in a near future version.