[krita] [Bug 454716] New: Animation Timeline Docker: Frame Drag and Drop Hilariously Laggy

2022-06-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=454716

Bug ID: 454716
   Summary: Animation Timeline Docker: Frame Drag and Drop
Hilariously Laggy
   Product: krita
   Version: 5.0.6
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: junior-jobs
  Severity: minor
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

This is a very minor polish issue that's been around forever, but if you click
on a keyframe in the timeline docker and drag it around like crazy it will lag
behind, slowly following the whatever path you've taken with your mouse while
falling further and further behind. It's pretty cool. :)

We probably need to somehow optimize the way drag-and-drop works with timeline
frames. 
(We probably also need to make it so that it doesn't scrub the timeline while
drag-dropping. That may be part of the issue or a separate problem. I'm not
quite sure.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 455178] Animation timeline scroll wheel get stuck after going past end frame

2022-06-13 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=455178

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 455178] Animation timeline scroll wheel get stuck after going past end frame

2022-06-13 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=455178

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 455178] Animation timeline scroll wheel get stuck after going past end frame

2022-06-13 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=455178

Emmet O'Neill  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/2ab171c54
   ||5c1ece49b6a4b80f5e00f55e4b2
   ||eaa4
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Emmet O'Neill  ---
Git commit 2ab171c545c1ece49b6a4b80f5e00f55e4b2eaa4 by Emmet O'Neill.
Committed on 14/06/2022 at 00:02.
Pushed by emmetoneill into branch 'master'.

Animation Timeline: Fixed mousewheel scrubbing behavior.

The mouse wheel no longer gets stuck after scrolling beyond the end
frame of the animation range.

M  +7-8plugins/dockers/animation/KisAnimTimelineFramesView.cpp

https://invent.kde.org/graphics/krita/commit/2ab171c545c1ece49b6a4b80f5e00f55e4b2eaa4

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 459134] New: Animation Cache displays black frame when "limit cached frame size" is active.

2022-09-14 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=459134

Bug ID: 459134
   Summary: Animation Cache displays black frame when "limit
cached frame size" is active.
   Product: krita
   Version: 5.0.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY

On my system at least, my animation cache is displaying totally black frames
when the configuration setting "Performance > Animation > Limit Cached Frame
Size" is active. If that box is checked, and if the size of the current frame
is >= the setting's limit value, then the cached frame will appear completely
black rending the program functionally unusable.

I haven't yet determined whether this is a regression or simply a bug that is
difficult to find due to needing a specific configuration, but it's pretty bad.

For some reason this bug is consistently reproducible in my source build, as
well as in any appimage (including stable), but I cannot make it happen with
the flatpak binary via flathub. I thought that might hint at a driver issue,
since I recently updated my system, but the same behavior appears on both the
proprietary nvidia GPU driver as well as the open source nouveau driver...  

STEPS TO REPRODUCE
1. Go to "Configure Krita > Performance > Animation" and enable Limit Cached
Frame Size checkbox with a value that is <= the size of your current canvas.
("Display > Canvas Graphics Acceleration" must also be enabled to see results
of caching in general.)
2. Try to play back your animation and watch the cache markers appear at the
top of the timeline.

OBSERVED RESULT
After the cache generates the canvas will go pitch black, and it will stay that
way until the cache is cleared. While the canvas is dark there seems to be
nothing that can cause it to function properly.

EXPECTED RESULT
You should see the proper cached frame!!!

SOFTWARE/OS VERSIONS
Linux: Fedora 36
GPU: NVidia GTX 1060 3GB vram version. Tested with both `nvidia` and `nouveau`
drivers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 459134] Animation Cache displays black frame when "limit cached frame size" is active.

2022-09-14 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=459134

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 459134] Animation Cache displays black frame when "limit cached frame size" is active.

2022-09-14 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=459134

--- Comment #1 from Emmet O'Neill  ---
Edit: Ah, Eoin and I managed to find out the source of the bug, and it is now
100% reproducible in every version that we've tested on. It looks like this bug
occurs when "Configure Krita > Display > Canvas Graphics Acceleration > Scaling
Mode" is set to either "nearest neighbor" or "bilinear interpolation" modes.

Still important to fix soon, but bringing the importance level back down to
normal since it's not something that will happen without a specific
configuration.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 459134] Animation Cache displays black frame when "limit cached frame size" is active.

2022-09-14 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=459134

Emmet O'Neill  changed:

   What|Removed |Added

   Severity|major   |normal

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 459806] New: Timeline UX: Actions on unlocked layers are blocked when the active layer happens to be locked.

2022-09-28 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=459806

Bug ID: 459806
   Summary: Timeline UX: Actions on unlocked layers are blocked
when the active layer happens to be locked.
Classification: Applications
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Animation
  Assignee: emmetoneill@gmail.com
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY
If the active layer, LAYER_A, is locked and you select a frame on a different,
unlocked layer, LAYER_B, that frame will not be deleted when the delete
keyframe button is pushed. The same is true for adding frames.

More info:
https://invent.kde.org/graphics/krita/-/merge_requests/1597


STEPS TO REPRODUCE
1. Create a file with 2 layers.
2. Lock LAYER_A, Unlock LAYER_B
3. Make sure that the locked layer, LAYER_A, is active, and select a frame on
the unlocked layer, LAYER_B.
4. Click the `Create Blank Keyframe` button 

OBSERVED RESULT
Notice that a new frame will not be added on the unlocked LAYER_B, because the
active LAYER_A is locked.

EXPECTED RESULT
We should either (a) limit keyframe addition and deletion operations to the
active layer like most operations within Krita, or (b) we should make sure that
operations happen as expected on unlocked layers regardless of the locking
status of the active layer.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 469116] Cant launch through Steam but the .sh and .appimage work in steamapps folder

2023-04-28 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=469116

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 469116] Cant launch through Steam but the .sh and .appimage work in steamapps folder

2023-04-28 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=469116

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Emmet O'Neill  ---
Hi Thomas. Thanks very much for the report, and sorry that you've run into this
[really bad] bug.

I can confirm this behavior on my Fedora Silverblue (Gnome) laptop as well,
where Steam is also installed as a flatpak. 
I'll have to test to see if this is a problem with non-flatpak install of Steam
as well, and I'll post my findings here.

Emmet

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 469116] Cant launch through Steam but the .sh and .appimage work in steamapps folder

2023-04-28 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=469116

--- Comment #2 from Emmet O'Neill  ---
Ok, so yeah. I've been able to confirm that this seems to be a problem that is
relegated to Flatpak Steam installs. 

As you rightly pointed out, both the 'launch.sh' script and the AppImage itself
run without issue.
On top of that, I've installed the .deb version of Steam and Krita runs there
without issue as well.
So, it appears that mounting an appimage while Steam is contained in a flatpak
is either broken or impossible right now...
We might have to change our approach to distributing Linux binaries through
Steam.

The best workaround we have right now is to simply run the AppImage itself.
Creating a .desktop file, symlinking it elsewhere, or adding it to your PATH
may make that less of a hassle.
(Also, if you have recently bought Krita on Steam and are disappointed that
this bug has nullified the convenience of doing so... First, I'm sorry about
that, and second, consider asking for a refund through Steam.)

Anyway, sorry again for the nasty bug, and thanks a ton for letting us know and
supporting the project in general.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 489467] Release 5.2.3 update to paying customers

2024-07-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=489467

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com

--- Comment #2 from Emmet O'Neill  ---
Hey Markuss.

To clarify a bit, Krita 5.2.3 actually was released for Linux, Windows and Mac
on Steam last Tuesday (even before our release announcement post went up), but
has unfortunately since been rolled back to 5.2.2 due to the problem that
Dmitry mentioned causing users to experiences frequent assertion failures
(crashes).

As a paying customer I can understand how that's frustrating, so to make sure
you have some agency here too I have pushed Krita 5.2.3 to the "beta" branch
for Krita on Steam. (Access by right clicking on Krita -> Properties -> Betas
tab -> "beta" Branch. Steam may take a minute to switch back.) 

We've never had to roll back a release on Steam before, and I realize it's not
ideal, but it seemed to be the better option than continuing to ship an update
with frequent crashes to Steam customers. Providing timely updates to people
like you who choose to support us on Steam is not something that I take lightly
and in the ~6 years since I've been managing Krita on Steam, I can only think
of 1 time that we've been late to push an update there (which was due to me
being unavailable at the time). 

I give you my word that I'll push the Krita 5.2.3 update to Steam as soon as
humanly possible once we have a stable release build available.
Please give us a bit more time to work out this issue and thank you for your
support.

Emmet

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478134] New: Anim Audio: Timeline scrubbing pushing too much audio.

2023-12-05 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478134

Bug ID: 478134
   Summary: Anim Audio: Timeline scrubbing pushing too much audio.
Classification: Applications
   Product: krita
   Version: 5.2.1
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY

When animation with audio, scrubbing (changing frames quickly via the timeline
time ruler header) pushes multiple frames of audio which can block the program
until the audio is processed. 

This is usually a minor issue, but becomes worse with (a) lower playback
framerate and (b) lower playback speed.
Setting the animation to a low speed and framerate before scrubbing (with audio
attached) will push tens of seconds of audio, causing Krita to slow down until
it's all been played.

STEPS TO REPRODUCE
1. Open an animation
2. Attach some audio
3. Set low animation playback framerate.
4. Set low animation playback speed.
5. Scrub between frames on the timeline.

OBSERVED RESULT

Listen to a half minute of cow noises.

EXPECTED RESULT

We probably need to limit the rate of pushing audio based on the amount of time
a single frame of audio takes to play (considering both anim framerate and
speed).

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478185] Playback doesn't work after scrubbing.

2023-12-07 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478185

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478017] Krita crashes on opening an animation file

2023-12-20 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478017

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #2 from Emmet O'Neill  ---
@Aleksandr:

Hey there.

First, technically the only supported means of getting Krita is via the
official AppImages that we generate, or from the various "app stores" that we
officially distribute on (Steam, Windows Store, EGS, Android's App Store). So,
personally, I would recommend using the AppImage version of Krita for the most
consistent experience. (Of course Krita is FOSS and available in many other
formats and repositories, and we want it to be working correctly in those
places too, but much of that is going to be in the hands of the repository
maintainers.)

With that said, based on your backtrace it's possible that there's a problem
with how Krita is being packaged on Arch with regard to MLT. Right now we're
shipping a fork of MLT with a custom plugin for handling animation audio, and
so If I had to guess, I'd say that the wrong version of MLT is being used on
Arch. 

In other words, this is a bug for the Arch package maintainer(s), though to be
fair we haven't exactly made it easy on them. :(

I should also mention that I'm in the process of improving this (as much as
possible) so that our custom MLT plugin is shipping in our own source tree,
while other changes are upstreamed so that we can use the regular MLT instead
of maintaining our own fork. So, fwiw, we're working on improving and
simplifying things. (This work should be merged soon (tm)--taking into account
Christmas and New Years and all that.) 

@Alvin:

Yeah, we still have a KisPlaybackEngineQt, which should work just fine other
than it no longer supports audio. 
(Mainly so we could move away from also packaging GStreamer, which our old
QtMultimedia audio system depended on...)

IIRC MLT is an optional CMake dependency, so it should be possible to build
Krita without MLT as a workaround, at the cost of losing animation audio
support...

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 470109] Moving the timeline with the bar makes the zoom function on the timeline engage for some reason

2024-02-12 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=470109

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #5 from Emmet O'Neill  ---
You mentioned a video but I think you didn't attach it right because it's not
appearing in the attachments box. Please give it another try when you can.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 481184] Krita crashes on animation cache on a file without animation

2024-02-12 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=481184

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 481184] Krita crashes on animation cache on a file without animation

2024-02-12 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=481184

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #1 from Emmet O'Neill  ---
Hey Tiar, 

Can you consistently reproduce this bug? So far I'm not having luck... :(

I can see from your backtrace that it's might be failing an assertion, so it
could just be a flawed assertion that isn't accounting for some kind of edge
case. 

If you have more detailed repro steps or a specific document that it's
consistently crashing with, sharing those would help a ton.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 470109] Moving the timeline with the bar makes the zoom function on the timeline engage for some reason

2024-02-26 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=470109

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INTENTIONAL
 Status|NEEDSINFO   |RESOLVED

--- Comment #10 from Emmet O'Neill  ---
Thanks for the follow-up, nunya. 

I think you're right that we need to find a better way to show how these
zoomable scrollbars work, because although these kinds of scroll bars are
becoming somewhat more common it certainly isn't very intuitive to people who
are used to classic scroll bars. We'll consider that in future UI work for
sure.

Resolving this bug as intentional.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485666] Animation Renderer doesn't remember file type used last

2024-04-17 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485666

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||emmetoneill@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Emmet O'Neill  ---
You're right, and it should. Confirming this.

Thanks for the report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485582] Krita plays from wrong frame after setting playhead during playback.

2024-04-17 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485582

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|Krita plays from wrong  |Krita plays from wrong
   |frame after setting |frame after setting
   |playhead|playhead during playback.
 CC||emmetoneill@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #1 from Emmet O'Neill  ---
Hi Maarten, thanks for the bug report. 
I've been able to reproduce this bug on the latest master branch, so I'm
confirming it.

I think this is an edge case to do with changing the play head while the
animation is playing.
Because if I stop or pause the animation and *then* move the play head, it
seems to work as expected.

Just as a note to my future self, here are my slightly different STEPS TO
REPRODUCE:
1. Play an animation file.
2. Click the time header to change the play head position, while the animation
is still playing.
(Animation playback will stop after you change the playhead.)
3. Hit play again.

I'd imagine that this shouldn't be too hard to fix, so hopefully we can get to
it soon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 483526] Frames disappearing as I click through them with a pen

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=483526

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Severity|normal  |wishlist

--- Comment #12 from Emmet O'Neill  ---
Hey again Dynline, I want to let you know that I'm confirming this issue but
reclassifying it as a wishlist item since it seems to be less of a bug and more
of a potential usability improvement.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 483526] Usability: Improve precision of timeline frames view drag and drop controls.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=483526

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Frames disappearing as I|Usability: Improve
   |click through them with a   |precision of timeline
   |pen |frames view drag and drop
   ||controls.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480759] onion skin doesn't reappear after scrubbing

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480759

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|NEEDSINFO

--- Comment #6 from Emmet O'Neill  ---
Hi there Ben. 

I can't reproduce this on my end right now, and because it sounds like you
can't reproduce it anymore either I'm marking this as "worksforme" for the time
being. Doing this will help us keep the bug tracker clean. :)

With that said, if you do end up coming across the bug again in a reproducible
way please feel free to open this bug again and we can continue to investigate
it. 

Thanks for the report!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480759] Onion Skins don't immediately reappear after scrubbing.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480759

Emmet O'Neill  changed:

   What|Removed |Added

Summary|onion skin doesn't reappear |Onion Skins don't
   |after scrubbing |immediately reappear after
   ||scrubbing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484679] Animation Curves: Keyframes are added on a frame depending on where the caching is currently, not where the timeslider is at.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=484679

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
Summary|Keyframes are added on a|Animation Curves: Keyframes
   |frame depending on where|are added on a frame
   |the caching is currently,   |depending on where the
   |not where the timeslider is |caching is currently, not
   |at. |where the timeslider is at.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480468] The animation timeline is selecting a different frame from what is shown in the canvas

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480468

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Severity|normal  |major
 CC||emmetoneill@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Emmet O'Neill  ---
Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from
http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included
with the next stable version release of Krita. However, if you're still having
this issue in Krita Next or with Krita's master branch, please feel free to
reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478822] What I draw appear on the unselected keyframe.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478822

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #4 from Emmet O'Neill  ---
Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from
http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included
with the next stable version release of Krita. However, if you're still having
this issue in Krita Next or with Krita's master branch, please feel free to
reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 476203] Krita draws on the wrong frame after dragging the playhead

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=476203

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||emmetoneill@gmail.com

--- Comment #2 from Emmet O'Neill  ---
Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from
http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included
with the next stable version release of Krita. However, if you're still having
this issue in Krita Next or with Krita's master branch, please feel free to
reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485582] Animation plays from wrong frame after setting playhead during playback.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485582

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Krita plays from wrong  |Animation plays from wrong
   |frame after setting |frame after setting
   |playhead during playback.   |playhead during playback.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 473468] Layer's stroke effect appearing in wrong animation frames.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=473468

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||emmetoneill@gmail.com
 Resolution|--- |WORKSFORME

--- Comment #1 from Emmet O'Neill  ---
Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from
http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included
with the next stable version release of Krita. However, if you're still having
this issue in Krita Next or with Krita's master branch, please feel free to
reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 475438] Krita constantly select/insert/edit/delete frames at the wrong spots in the animation timeline

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=475438

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #3 from Emmet O'Neill  ---
Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from
http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included
with the next stable version release of Krita. However, if you're still having
this issue in Krita Next or with Krita's master branch, please feel free to
reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485582] Animation plays from wrong frame after setting playhead during playback.

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485582

Emmet O'Neill  changed:

   What|Removed |Added

 OS|Microsoft Windows   |All
   Severity|major   |normal
   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485666] Animation Renderer doesn't remember file type used last

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485666

Emmet O'Neill  changed:

   What|Removed |Added

   Severity|normal  |wishlist

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485666] Animation Renderer doesn't remember file type used last

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485666

Emmet O'Neill  changed:

   What|Removed |Added

   Severity|wishlist|normal

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485666] Animation Renderer doesn't remember file type used last

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485666

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 389015] Feature Req: Expand Selection of N frames

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=389015

Emmet O'Neill  changed:

   What|Removed |Added

Summary|expand selection of N   |Feature Req: Expand
   |frames  |Selection of N frames

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 369503] Render animation encode resume after error,by looking at folder

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=369503

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|saurabhk...@gmail.com   |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 437032] Timeline playback reset

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=437032

--- Comment #3 from Emmet O'Neill  ---
I think this has actually been improved quite a while ago now that the STOP
transport button has a dual-function:

1. If you hit STOP while PLAYING it should bring you back to whatever point the
playback started from. (For example, if you started playback from frame #24,
hitting stop while the animation is playing should bring you right back to
frame #24.)

2. If you hit STOP while the animation is already STOPPED, it should bring you
back to frame #0 or the start of the animation. 

(Note: there is currently 1 open edge case bug related to playback position
which will cause this to work incorrectly, but I should be able to fix it soon.
Generally it should be working as described above though.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 437032] Timeline playback reset

2024-04-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=437032

Emmet O'Neill  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Emmet O'Neill  ---
Resolving this for now. Please reopen if there is more we can do to make this
work better.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 486322] Export document dialogue doesn't have the original file name in Filename input field

2024-04-29 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=486322

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Keywords||triaged

--- Comment #1 from Emmet O'Neill  ---
Heya Tyson. Tested and confirming this for you.

Thanks as always for the report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485515] Recorder final preview doesn't show.

2024-05-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485515

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/40524a3
   ||39fc519cec62ed6e1fab663e923
   ||111635

--- Comment #1 from Emmet O'Neill  ---
Git commit 40524a339fc519cec62ed6e1fab663e923111635 by Emmet O'Neill, on behalf
of Ralek Kolemios.
Committed on 01/05/2024 at 22:07.
Pushed by emmetoneill into branch 'master'.

Reworked default FFmpeg profiles
Related: bug 455006, bug 450790, bug 429326, bug 485514

M  +2-0plugins/dockers/recorder/recorder_export.cpp
M  +166  -147  plugins/dockers/recorder/recorder_export_config.cpp
M  +1-0plugins/dockers/recorder/recorder_profile_settings.ui

https://invent.kde.org/graphics/krita/-/commit/40524a339fc519cec62ed6e1fab663e923111635

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 450790] Recorder not showing last frame properly

2024-05-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=450790

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/40524a3
   ||39fc519cec62ed6e1fab663e923
   ||111635
 Status|ASSIGNED|RESOLVED

--- Comment #7 from Emmet O'Neill  ---
Git commit 40524a339fc519cec62ed6e1fab663e923111635 by Emmet O'Neill, on behalf
of Ralek Kolemios.
Committed on 01/05/2024 at 22:07.
Pushed by emmetoneill into branch 'master'.

Reworked default FFmpeg profiles
Related: bug 455006, bug 429326, bug 485515, bug 485514

M  +2-0plugins/dockers/recorder/recorder_export.cpp
M  +166  -147  plugins/dockers/recorder/recorder_export_config.cpp
M  +1-0plugins/dockers/recorder/recorder_profile_settings.ui

https://invent.kde.org/graphics/krita/-/commit/40524a339fc519cec62ed6e1fab663e923111635

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 485514] Recorder starting preview overwrites timelapse

2024-05-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=485514

Emmet O'Neill  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/40524a3
   ||39fc519cec62ed6e1fab663e923
   ||111635
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Emmet O'Neill  ---
Git commit 40524a339fc519cec62ed6e1fab663e923111635 by Emmet O'Neill, on behalf
of Ralek Kolemios.
Committed on 01/05/2024 at 22:07.
Pushed by emmetoneill into branch 'master'.

Reworked default FFmpeg profiles
Related: bug 455006, bug 450790, bug 429326, bug 485515

M  +2-0plugins/dockers/recorder/recorder_export.cpp
M  +166  -147  plugins/dockers/recorder/recorder_export_config.cpp
M  +1-0plugins/dockers/recorder/recorder_profile_settings.ui

https://invent.kde.org/graphics/krita/-/commit/40524a339fc519cec62ed6e1fab663e923111635

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 429326] Recorder docker doesn't account for canvas size changes during drawing session.

2024-05-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=429326

Emmet O'Neill  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/40524a3
   ||39fc519cec62ed6e1fab663e923
   ||111635
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Emmet O'Neill  ---
Git commit 40524a339fc519cec62ed6e1fab663e923111635 by Emmet O'Neill, on behalf
of Ralek Kolemios.
Committed on 01/05/2024 at 22:07.
Pushed by emmetoneill into branch 'master'.

Reworked default FFmpeg profiles
Related: bug 455006, bug 450790, bug 485515, bug 485514

M  +2-0plugins/dockers/recorder/recorder_export.cpp
M  +166  -147  plugins/dockers/recorder/recorder_export_config.cpp
M  +1-0plugins/dockers/recorder/recorder_profile_settings.ui

https://invent.kde.org/graphics/krita/-/commit/40524a339fc519cec62ed6e1fab663e923111635

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 455006] Recorder resize function not working

2024-05-01 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=455006

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/40524a3
   ||39fc519cec62ed6e1fab663e923
   ||111635
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Emmet O'Neill  ---
Git commit 40524a339fc519cec62ed6e1fab663e923111635 by Emmet O'Neill, on behalf
of Ralek Kolemios.
Committed on 01/05/2024 at 22:07.
Pushed by emmetoneill into branch 'master'.

Reworked default FFmpeg profiles
Related: bug 450790, bug 429326, bug 485515, bug 485514

M  +2-0plugins/dockers/recorder/recorder_export.cpp
M  +166  -147  plugins/dockers/recorder/recorder_export_config.cpp
M  +1-0plugins/dockers/recorder/recorder_profile_settings.ui

https://invent.kde.org/graphics/krita/-/commit/40524a339fc519cec62ed6e1fab663e923111635

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 483526] Frames disappearing as I click through them with a pen

2024-04-02 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=483526

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Emmet O'Neill  ---
Hi. I think you're trying to animate using the layers docker, but with Krita
animation is generally done using frames within each layer, which you control
using the Animation Timeline Docker. For more information please check out
these links:

https://docs.krita.org/en/user_manual/animation.html

https://docs.krita.org/en/reference_manual/dockers/animation_timeline.html#timeline-docker

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480710] Frames error

2024-04-02 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480710

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||emmetoneill@gmail.com
 Status|REPORTED|NEEDSINFO

--- Comment #5 from Emmet O'Neill  ---
Waiting for more info on this one, because it's hard to tell whether this has
been fixed or not.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 483526] Frames disappearing as I click through them with a pen

2024-04-03 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=483526

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REOPENED|NEEDSINFO

--- Comment #5 from Emmet O'Neill  ---
I've watched the video but I'm not seeing anything animation related exactly.
The first half of the video is Adobe Photoshop stuff and the second half of the
video seems to be about arranging elements on the canvas in Krita. I'm guessing
you've accidentally uploaded the wrong video file for this bug. :)

>From your description it sounds like maybe you're getting accidental dragging
and dropping behavior on the Krita timeline when you click with your tablet
pen? And this is sometimes causing the frames to be lost entirely, if I
understand correctly. 

I'll test around and see if I can reproduce that issue, but if you have another
video then that might help too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 483526] Frames disappearing as I click through them with a pen

2024-04-11 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=483526

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|NEEDSINFO

--- Comment #9 from Emmet O'Neill  ---
Hey again Dynline, and thanks for the other video. :)

So I can't exactly reproduce this issue on the latest master development
branch, so it's possible that it's already been fixed.
I've tested with both a mouse as well as my drawing tablet pen.

Are you sure that you're not just accidentally dragging the animation keyframes
on top of one another?
Does the same thing happen if you slow down?

I've noticed that it's somewhat easy to do that when tapping really quickly
with a tablet pen, though I didn't have the problem as much as you seem to be,
based on your video. Either way, there may be things we can do to make the
drag-and-drop controls within the timeline more precise, so I'll keep that in
mind whether this is an actual implementation bug or not.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 474804] transform tool and mask

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=474804

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
  Component|Animation   |Tools/Transform

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478185] Playback doesn't work after scrubbing.

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478185

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Emmet O'Neill  ---
Thanks for the bug report, demo video and sound file. 

I'm confirming this based on your video. I'll try to sort it out. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478185] [Animation/Audio] Playback doesn't work after scrubbing.

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478185

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Playback doesn't work after |[Animation/Audio] Playback
   |scrubbing.  |doesn't work after
   ||scrubbing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 466977] Restore defaults option for the onion skin sliders

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=466977

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||emmetoneill@gmail.com

--- Comment #1 from Emmet O'Neill  ---
Good idea. I'll put this on my to-do list. :)

Thanks for the suggestion, Nagy.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 470109] Moving the timeline with the bar makes the zoom function on the timeline engage for some reason

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=470109

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||emmetoneill@gmail.com
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Emmet O'Neill  ---
The zoomable scrollbar on the animation timeline is designed to slide the
tileline left and right when you drag it left and right, while zooming in and
out when you drag it up and down. It's a bit unconventional, but this is a to
make it very quick and easy to pan and zoom the timeline with a single
press-and-slide motion of a mouse or pen.

In other words, it should only zoom in when you drag it in an upwards
direction, and it should only zoom out when you drag it downwards. 
As such, when dragging left and right, it shouldn't affect the zoom much (if at
all).

Right now it seems to be working as intended for me with both a tablet and
mouse, and because of that I can't confirm it.
If you feel like it's still not working the way you want or expect it to,
please feel free to reopen this bug and I can take another look at it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 472470] Anim Audio: Audio not staying in sync when restarting animation.

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=472470

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Audio   |Anim Audio: Audio not
   ||staying in sync when
   ||restarting animation.
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 472470] Anim Audio: Audio not staying in sync when restarting animation.

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=472470

--- Comment #1 from Emmet O'Neill  ---
Thanks for the kind words, Maxim! :)

Right now I can't reproduce this bug on Linux or Windows, and I don't
personally have a suitable Android device for testing yet. 
I've pinged the #krita development chat to see if anyone else can help test for
this bug on Android, and maybe we can go from there.

If you can give us any more details about specific steps to easily reproduce
this bug, it might help us find it faster.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 472470] Anim Audio: Audio not staying in sync when restarting animation.

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=472470

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Emmet O'Neill  ---
(Changing status to "waiting for info", for now.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 472983] Audio Scratching when scrubbing through Animation Timeline

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=472983

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #2 from Emmet O'Neill  ---
Hey Clyde, thanks for the report. 
I can confirm this behavior. :)

I think this happens mainly because of sudden jumps ("discontinuities") in the
audio waveform when we jump between different frames.
Something like what's being described here:
https://dsp.stackexchange.com/questions/22860/stitching-together-audio-buffers-with-potential-discontinuity-at-the-boundary

I have a few different ideas for how we *might* be able to mitigate these
annoying pops and scratches (like starting audio chunks only at zero crossings
or applying a simple fade in/out amplitude envelope), but it's a relatively low
priority task for now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478267] Could we import animation frames like a file layer?

2024-01-25 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478267

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Emmet O'Neill  ---
Hey there Michael Eric, thanks for the really great and detailed feature
request. :)

Sadly, I haven't had much time to work with Blender's Grease Pencil myself, but
as a user and fan of both tools I'm also very interested in finding various
ways to improve workflow interoperability between Blender and Krita if at all
possible! 

Without having investigated it specifically yet, I can't really say if doing
this would be easy/practical within the confines of our current animation
system. But it's a good idea that hasn't been raised before (to my knowledge),
so I'll definitely make a point to look into it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478134] Anim Audio: Timeline scrubbing pushing too much audio.

2024-01-26 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478134

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

--- Comment #1 from Emmet O'Neill  ---
Me again, just marking as confirmed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480647] Frames error

2024-02-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480647

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from Emmet O'Neill  ---
Hi there Mair, thank you for the bug report.

I'm having a hard time reproducing this bug with the latest version of Krita. 
That could mean that the underlying problem causing this behavior has already
been solved somewhere else.

With that said, if you're still having problems with glitchy pixelated
rendering, please let us know and I'll reopen this report and continue
investigating it. (On top of that, if you know of steps that I can use to
consistently reproduce this buggy behavior, or if it happens with a specific
file only, please let me know!)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 464488] Black and White Animation bug with Perspective Tool

2024-02-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=464488

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||emmetoneill@gmail.com
 Resolution|--- |WORKSFORME

--- Comment #1 from Emmet O'Neill  ---
Hey Brandon, thanks for the bug report.

Right now I'm not able to reproduce this behavior or either my Linux or Windows
test system. Are you still running into this bug?

If so, can you tell me any more about your current system and settings? For
example, what kind of GPU you have, whether you have "Canvas Acceleration"
turned on (in Settings > Display > Canvas Acceleration), whether your animation
cache settings are set to "in memory" or "on disk", etc.

In the mean time I'll be closing this bug report, but if you come back with
more information we can reopen it and I'll continue investigating it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 472936] the image doesn´t change when i go back one frame

2024-02-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=472936

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||emmetoneill@gmail.com

--- Comment #1 from Emmet O'Neill  ---
Hi there, thanks for the bug report.

Right now I'm unable to reproduce this glitchy animation rendering? Are you
still running into the issue yourself?

If so, please let me know and I'll continue investigating it.

(Note: Marking this as a duplicate of 480647, since it sounds like it might be
the same issue.)

*** This bug has been marked as a duplicate of bug 480647 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480647] Frames error

2024-02-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480647

Emmet O'Neill  changed:

   What|Removed |Added

 CC||eliaschin...@gmail.com

--- Comment #2 from Emmet O'Neill  ---
*** Bug 472936 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 481099] Inserted hold frame(s) will never update in the cache and halts playback (git 3ad80aa)

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=481099

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com
   Severity|normal  |major
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Emmet O'Neill  ---
Hi Cade, thanks for the detailed report. I can easily reproduce this bug with
your instructions.

For the time being, I think the quickest workaround is to right-click on the
frame time header bar (at the top, where you drag to scrub) and select "clear
cache" from the context menu. This rebuilds the animation cache and seems to
solve the broken playback.

I'm setting this to "confirmed", and hopefully we'll get this fixed by the next
released.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480759] onion skin doesn't reappear after scrubbing

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480759

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
 CC||emmetoneill@gmail.com

--- Comment #1 from Emmet O'Neill  ---
Confirming and assigning this bug. I hope to fix this in the next version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 480759] onion skin doesn't reappear after scrubbing

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=480759

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 466977] Restore defaults option for the onion skin sliders

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=466977

Emmet O'Neill  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/-/commit/e36d761
   ||cd2b1b6d20029c41a7eaa4d
   ||8d7ed8
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Emmet O'Neill  ---
Git commit e36d761cd2b1b6d20029c41a7eaa4d8d7ed8 by Emmet O'Neill.
Committed on 09/02/2024 at 04:39.
Pushed by emmetoneill into branch 'master'.

Feature@UI/Anim/OnionSkins: Can now reset onion skins to default values.

Right-clicking on the slider widget within the onion skins docker
will show a new context menu with a single "Reset" action, which
resets all of the slider values to their smooth defaults.

M  +0-8libs/image/kis_image_config.cpp
M  +22   -2plugins/dockers/animation/KisOnionSkinsDocker.cpp
M  +1-0plugins/dockers/animation/KisOnionSkinsDocker.h
M  +22   -1plugins/dockers/animation/kis_equalizer_widget.cpp
M  +3-0plugins/dockers/animation/kis_equalizer_widget.h

https://invent.kde.org/graphics/krita/-/commit/e36d761cd2b1b6d20029c41a7eaa4d8d7ed8

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 466977] Restore defaults option for the onion skin sliders

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=466977

--- Comment #3 from Emmet O'Neill  ---
Hi again, Nagy. 

I've added this feature and it should be included in the next release of Krita.
If you'd like to try it out sooner, you can get a "Krita Next" nightly preview
build from the Krita website.

To access this feature in future versions, right click on the slider section of
the Onion Skins Docker and select "Reset" from the context menu that appears.
This will reset all of the sliders to their smooth defaults. 

Thanks again for the feature request!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 478537] Animation exporting in a higher FPS when using audio

2024-02-08 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=478537

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Animation exporting in a|Animation exporting in a
   |higher DPS when using audio |higher FPS when using audio
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-15 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-15 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

--- Comment #7 from Emmet O'Neill  ---
Git commit 366e42d4448463b8571560a1c57aa651c6eaee27 by Emmet O'Neill.
Committed on 15/11/2021 at 23:06.
Pushed by emmetoneill into branch 'krita/5.0'.

Revert "Freehand Tool: Shift-Vertical Drag can now be used to resize too."

This reverts commit 4cb4711b0315b01b79d8064865ede596d1205368.

Dexterity considerations.

M  +2-3libs/ui/tool/kis_tool_freehand.cc

https://invent.kde.org/graphics/krita/commit/366e42d4448463b8571560a1c57aa651c6eaee27

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-15 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

--- Comment #8 from Emmet O'Neill  ---
Git commit 4807d9c8992454e1eb741edc96dc061c9fd42299 by Emmet O'Neill.
Committed on 15/11/2021 at 23:09.
Pushed by emmetoneill into branch 'master'.

Revert "Freehand Tool: Shift-Vertical Drag can now be used to resize too."

This reverts commit 4cb4711b0315b01b79d8064865ede596d1205368.

Dexterity considerations.


(cherry picked from commit 366e42d4448463b8571560a1c57aa651c6eaee27)

M  +2-3libs/ui/tool/kis_tool_freehand.cc

https://invent.kde.org/graphics/krita/commit/4807d9c8992454e1eb741edc96dc061c9fd42299

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-15 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |NOT A BUG

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-17 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |FIXED

--- Comment #10 from Emmet O'Neill  ---
(In reply to Tyson Tan from comment #9)
> Thank you Emmet! :)

You're welcome Tyson. If this is hurting your ability to illustrate with Krita,
then it's certainly safer and smarter to revert it for now.

However, I want to note a few things:

1. The ability to resize the brush by dragging vertically  (as an alternative
to the existing horizontal drag) was something that had been user requested.
This request seems pretty reasonable, as there's nothing that makes horizontal
dragging for brush size any more intuitive or ergonomic than vertical. While
reverting this patch is positive from your perspective (and that certainly
means a lot considering your long relationship the project), it's important to
keep in mind that it will be disappointing to those who requested it.

This can be remedied by making this behavior configurable, but even then people
will disagree over what the default behavior should be. 
It's also not something we can do right now, since we're in string freeze for
Krita 5.0.

2. From my personal testing and painting recently, I'd argue that the problem
is being overstated here. The awkward fighting/jumping between enlarging and
reducing brush sizes only occurs in two very specific directions, 4:30 and
10:30 o'clock, for lack of a better description. Of course, this is the natural
fulcrum/fault-line where we draw a distinction between enlargement (right/up)
and reduction (left/down). 

You'll notice that this issue has always existed with Krita, and continues to
exist after this patch has been reverted, it's just that we've shifted the
problem angles. If you hold shift and drag directly up or down even after the
revert, you'll experience the same annoying clash between brush enlargement and
reduction that this bug is describing, and (when you factor out muscle memory)
I'd argue that it's in an even more annoying place.

There's the possibility of creating a dead zone or buffer between the
enlargement direction and reduction direction, but that would of course mean
that nothing at all would happen when dragging perfectly along the fault-line.
I'm not sure if that's any better than the clashing situation, but maybe it's
worth trying...

3. I think we can agree that intuitive pen gestures like this are an important
part of painting workflow. I'd like us to have an open mind in the future and
explore other possibilities for improving quick gesture-based controls, because
it could lead to a more expressive and fluent interaction for artists. 

Since shift brush size change was the key function that brought you to Krita,
then I think it's safe to say that there is a lot of potential value in making
this feature better or developing related features--it's just a matter of
figuring out ways that we can do it that are net-positive and flexible enough
to suit the tastes of various artists, and your input will be a huge help in
getting there.

---

Anyway, I'm playing it safe here and reverting because your experience and
opinions are important to us! 
I hope you'll consider the points I'm making and let us know what you think can
be done to improve and build upon these kinds of gestures.

Thanks as always for the report Tyson,
Emmet

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.

2021-11-17 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=442544

--- Comment #11 from Emmet O'Neill  ---
Oh, and one other thing that I just thought of...

In regards to the NW - SE "fault-line" issue that I mentioned above: if you are
left handed like me, then a big part of the problem could be that this
fault-line coincides with one of the more naturally comfortable brush stroke
directions. Random thought, but that's certainly something to consider...

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 445657] Loading 250 Frames performance problem and jump back/forward buttons doesn't seem to do ANYTHING

2021-11-18 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=445657

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME
 CC||emmetoneill@gmail.com

--- Comment #5 from Emmet O'Neill  ---
(In reply to Hoang Duy Tran from comment #4)
> I was using nightly build (krita-nightly_d2f29d7.dmg), downloaded on
> 14/11/2021. After read your comment, I went to download the
> 'krita-5.0.0-beta2.dmg' (today, 18/11/2021) and was able loading all 250
> frames, with little delay (sustainable), I still notice the delay when I
> started playing 'Cache regeneration..' but no 99% stuck as previous version.
> Still the 'Skip Back' button moves 1 frame backward, identical to the 'Back'
> button, and 'Skip Forward' button is functioning exactly like the 'Forward'
> button. I don't understand why you'd need TWO BUTTONS performing exactly the
> same function. If I was editing I would JUMP by my mouse to a position where
> I would like to place my next frame, this must be done by MOUSE POINTER,
> only when I would like to jump to the beginning should I use 'Skip Back' (or
> rather misleading name, it looks more like 'First Frame' button) and the
> other looks more like 'Last Frame' button, honestly.

The "skip forward" button will jump to the next available keyframe on the
active layer. 
As such, if a keyframe exists on every available frame (on 1s, in animation
talk), both the next/skip forward buttons will appear to do the same thing.
As of now, if there are no keyframes on the active layer, nothing happens when
you when you hit the skip buttons.
We could probably still do something useful in that edge case, but I believe
the buttons are working as they should.

If things are not working as you expect, it's probably that you have the wrong
layer active.

Anyway, if this bug is something that can no longer be reproduced, I'm going to
close this report for now.
Thanks all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446009] New: Resource: Brush Tips: Preset initially loads incorrect brush tip.

2021-11-23 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446009

Bug ID: 446009
   Summary: Resource: Brush Tips: Preset initially loads incorrect
brush tip.
   Product: krita
   Version: 5.0.0-beta2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY
When loading the "v) Texture Impressionism MaskedBig" brush preset from Ramon's
impressionism bundle, the wrong brush tip is used. When viewed in the brush
editor > brush tip tab, a long vertical rectangle tip appears to be selected,
but when you paint the tip appears to be round.


STEPS TO REPRODUCE
1. Import Ramon Miranda's "Impressionism" resource bundle.
2. Select the "v) Texture Impressionism MaskedBig" brush preset.
3. Take note of the selected brush tip in the "Brush Tip" section of the brush
editor dialog.
4. Draw with the brush on the canvas.

OBSERVED RESULT
Although the tip appears to be a long rectangle in the brush editor window, the
stroke appears to have a round tip on canvas.


EXPECTED RESULT
The tip on canvas should correctly reflect the active tip in the brush editor.

WORKAROUND / NOTE
By switching brush tips away from the rectangular one that's associated with
the preset, and then switching back, you can make the brush function as
intended. (This might hint that the problem is not with how the brush resource
is stored, but instead with how it's being initially loaded.)

Krita 5.0 branch, resource testing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446009] Resource: Brush Tips: Preset initially loads incorrect brush tip.

2021-11-23 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446009

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446009] Resource: Masked Bush: Preset initially loads incorrect masked brush tip.

2021-11-23 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446009

Emmet O'Neill  changed:

   What|Removed |Added

Summary|Resource: Brush Tips:   |Resource: Masked Bush:
   |Preset initially loads  |Preset initially loads
   |incorrect brush tip.|incorrect masked brush tip.

--- Comment #1 from Emmet O'Neill  ---
Correction: It's not the regular brush tip, it's the brush tip associated with
masked brushes. 

Brush Editor > Masked Brush section > Brush tip.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 435293] color history popup shouldn't appear centered

2021-11-24 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=435293

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com

--- Comment #6 from Emmet O'Neill  ---
To add more information, the "color history popup" is a GUI element that can be
summoned by a keyboard shortcut action. (The default keybinding is `H`.)

I had no idea that this thing even existed, and you're right Manga Tengu, it's
not the best UX.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 435293] color history popup shouldn't appear centered

2021-11-24 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=435293

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #7 from Emmet O'Neill  ---
SySagar and I were able to confirm that this issue, so I've marked this as
confirmed.

Sy would like to take a crack at improving this, too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446148] Non-brush preset resources can be explicitly assigned to "All Untagged"

2021-11-29 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446148

--- Comment #2 from Emmet O'Neill  ---
Git commit 43b10e374180700577c012ea3a0f4c844046f664 by Emmet O'Neill.
Committed on 30/11/2021 at 06:05.
Pushed by emmetoneill into branch 'krita/5.0'.

Resources: Safe assert tagResource tag->id() is valid.

M  +3-2libs/resources/KisTagResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/43b10e374180700577c012ea3a0f4c844046f664

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446148] Non-brush preset resources can be explicitly assigned to "All Untagged"

2021-11-29 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446148

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/ea99c6a98
   ||d6e53b369a0df4269e63aed7ff7
   ||363c

--- Comment #3 from Emmet O'Neill  ---
Git commit ea99c6a98d6e53b369a0df4269e63aed7ff7363c by Emmet O'Neill.
Committed on 30/11/2021 at 06:05.
Pushed by emmetoneill into branch 'krita/5.0'.

Prevent 'Special' tags from showing up in right click assignemnt menu.

More clean-up in this class is necessary. I don't like how assigned tags
are shown in the assignable tags list.

M  +22   -31   libs/resourcewidgets/KisResourceItemChooserContextMenu.cpp

https://invent.kde.org/graphics/krita/commit/ea99c6a98d6e53b369a0df4269e63aed7ff7363c

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446148] Non-brush preset resources can be explicitly assigned to "All Untagged"

2021-11-29 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446148

--- Comment #4 from Emmet O'Neill  ---
Git commit 48b1261b1168d8545d53ca7748017905cd08bcc2 by Emmet O'Neill.
Committed on 30/11/2021 at 06:09.
Pushed by emmetoneill into branch 'master'.

Resources: Safe assert tagResource tag->id() is valid.


(cherry picked from commit 43b10e374180700577c012ea3a0f4c844046f664)

M  +3-2libs/resources/KisTagResourceModel.cpp

https://invent.kde.org/graphics/krita/commit/48b1261b1168d8545d53ca7748017905cd08bcc2

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446148] Non-brush preset resources can be explicitly assigned to "All Untagged"

2021-11-29 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446148

Emmet O'Neill  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/ea99c6a98 |hics/krita/commit/41f1e1fc2
   |d6e53b369a0df4269e63aed7ff7 |b3b9b45cf4efb509ce67965f4f5
   |363c|8afa

--- Comment #5 from Emmet O'Neill  ---
Git commit 41f1e1fc2b3b9b45cf4efb509ce67965f4f58afa by Emmet O'Neill.
Committed on 30/11/2021 at 06:10.
Pushed by emmetoneill into branch 'master'.

Prevent 'Special' tags from showing up in right click assignemnt menu.

More clean-up in this class is necessary. I don't like how assigned tags
are shown in the assignable tags list.


(cherry picked from commit ea99c6a98d6e53b369a0df4269e63aed7ff7363c)

M  +22   -31   libs/resourcewidgets/KisResourceItemChooserContextMenu.cpp

https://invent.kde.org/graphics/krita/commit/41f1e1fc2b3b9b45cf4efb509ce67965f4f58afa

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446586] Color Picker: Every time after the first one it thinks I'm taking the color I already have selected when over the canvas

2021-12-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446586

Emmet O'Neill  changed:

   What|Removed |Added

  Component|Color Selectors |Tools
Summary|Every time after the first  |Color Picker: Every time
   |one it thinks I'm taking|after the first one it
   |the color I already have|thinks I'm taking the color
   |selected when over the  |I already have selected
   |canvas  |when over the canvas
 CC||emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446586] Color Picker: Every time after the first one it thinks I'm taking the color I already have selected when over the canvas

2021-12-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446586

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446586] Color Picker: Every time after the first one it thinks I'm taking the color I already have selected when over the canvas

2021-12-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446586

--- Comment #1 from Emmet O'Neill  ---
Hey there,

Can you please check a couple things for me:

1. If you look at the "Tool Options" docker while the Color Sampler tool is
active, is it set to "Sample All Visible Layers" or "Sample Current Layer"? If
it is set to "Sample Current Layer", can you make sure that there is some
content in the current layer in the position that you're trying to sample from.

2. What is the "Blend" slider set to? (This setting is also in the Tool Options
docker whenever the Color Sampler tool is active.) When it's set to 100% it
will pick the exact color of the canvas, and anything lower than that will mix
in some amount of the previous active color.

3. It also might be worth checking that the "Radius" option is set to something
that you'd expect. A radius that's too big might cause the sampled colors to be
somewhat unexpected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446586] Color Picker: Every time after the first one it thinks I'm taking the color I already have selected when over the canvas

2021-12-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446586

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Emmet O'Neill  ---
Switched to "waiting for info".

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 446589] Krita deleted my saved .kra

2021-12-06 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=446589

Emmet O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||emmetoneill@gmail.com
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Emmet O'Neill  ---
Hi Chris. 

I'm sorry to hear that Krita crashed and that you to lost progress, but this
bug report doesn't convey any useful information.
In order for us to fix bugs and prevent future data loss, we need real details
about the crash, otherwise it's a waste of both of our time.

(Also, it's generally not suggested to do any serious work in a beta version,
because to some degree bugs and crashes are expected during this phase of
development.)

I'm closing this report for now, but if you take a look at the page that you
linked and come back with more actionable information, we can hopefully fix
whatever crash you ran into.
Emmet

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 453682] New: Animation / Multithreading : Creating animations with AutoKey causes Krita to get stuck in an unusable state.

2022-05-11 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=453682

Bug ID: 453682
   Summary: Animation /  Multithreading : Creating animations with
AutoKey causes Krita to get stuck in an unusable
state.
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: regression, release_blocker, reproducible
  Severity: major
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY

[Regression & Release Blocker]. 
Automatic keyframe creation (AutoKey) causes a number of major issues on
master:

1. Drawing multiple frames with autokey can cause Krita to lock up, as a
"freehand brush stroke job" becomes stuck in the system and never completes,
blocking other operations.

2. Drawing multiple frames with autokey can cause autokey to stop working
entirely.

STEPS TO REPRODUCE

1. On master, open Krita and create a new document.
2. In the Animation Timeline's popover menu, click the button to enable AutoKey
(blank mode). 
3. Select frame 0 and create a blank frame.
4. Draw something on frame 0.
5. Select another frame and draw something, letting AutoKey create new frames.
6. Loop step 5 a few times as if making an animation.

OBSERVED RESULT

We'll see that, somewhat randomly, AutoKey will either no longer work correctly
OR will cause the program to lock up as a "Freehand Brush Stroke Job" fails to
complete.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 453682] Animation / Multithreading : Creating animations with AutoKey causes Krita to get stuck in an unusable state.

2022-05-11 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=453682

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 453682] Animation / Multithreading : Creating animations with AutoKey causes Krita to get stuck in an unusable state.

2022-05-16 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=453682

--- Comment #2 from Emmet O'Neill  ---
Bisected to commit b3b33ae23426a96954e82839b8af5285924719ec.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 452307] New: New scene creates a frame on locked layers.

2022-04-05 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=452307

Bug ID: 452307
   Summary: New scene creates a frame on locked layers.
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Storyboard
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY:
Creating a new storyboard scene creates a new frame even when the layer is
locked.
It shouldn't!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 452307] New scene creates a frame on locked layers.

2022-04-05 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=452307

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 452307] New scene creates a frame on locked layers.

2022-04-05 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=452307

Emmet O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 452144] Opacity Keyframes can be added to a vector layer but they can't be Saved in the .kra file.

2022-04-05 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=452144

Emmet O'Neill  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/f54ec56e6
   ||d55e971020e9bef2a5547f5aadf
   ||052a
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Emmet O'Neill  ---
Git commit f54ec56e6d55e971020e9bef2a5547f5aadf052a by Emmet O'Neill.
Committed on 06/04/2022 at 01:19.
Pushed by emmetoneill into branch 'master'.

Animation: Fixed vector layer scaler keyframe loading.

Opacity channel now loads correctly for vector layers.

M  +1-0plugins/impex/libkra/kis_kra_load_visitor.cpp

https://invent.kde.org/graphics/krita/commit/f54ec56e6d55e971020e9bef2a5547f5aadf052a

-- 
You are receiving this mail because:
You are watching all bug changes.

  1   2   3   4   5   6   7   8   9   >