[krita] [Bug 373652] New: Crash when playback is running
https://bugs.kde.org/show_bug.cgi?id=373652 Bug ID: 373652 Summary: Crash when playback is running Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Created attachment 102782 --> https://bugs.kde.org/attachment.cgi?id=102782=edit log I dont know what triggers this,but it has happened multiple times this evening crashlog in attachment in 3.0.94 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373573] New: Specific Color split (like COLOR TO ALPHA and LAYER SPLIT)
https://bugs.kde.org/show_bug.cgi?id=373573 Bug ID: 373573 Summary: Specific Color split (like COLOR TO ALPHA and LAYER SPLIT) Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Color Split would be actually similar to layer split but you can limit the split to a chosen color,and only THAT color gets removed. By design i think it would be necessary that it can be applied to a range of selected frames,cause needing to do it one by one ,while possible will need a lot of tweaking before you can merge the extracted layers down again. So it will have to extract the picked color,only one, according to a fuzzy factor (like similar color selector wand) and put it into a new layer This would be a very powerful tool to reuse work that is already done. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373571] New: Color replace (like COLOR TO ALPHA)
https://bugs.kde.org/show_bug.cgi?id=373571 Bug ID: 373571 Summary: Color replace (like COLOR TO ALPHA) Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Color to alpha is great,but it would be ncie to also have different filters with different aims. Color to color or Replace Color ,would be same as alpha but to change a certain color to another one. selecting with "similar color selector wand" and then applying fill is too slow to do it on aevery frame of an animation. Also you loose the ability to use selection to exclude similar colors you dont want replaced. This new function would give more power to the user. Would also be nice to have it be able to apply to a range of frames. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373305] Apply operation on whole frame selection
https://bugs.kde.org/show_bug.cgi?id=373305 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- a few other operations it would be good to be able to mass-apply 4) fill color 5) clear 6) stroke -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373493] Flattening an animation with transform mask results in crash or artefacts
https://bugs.kde.org/show_bug.cgi?id=373493 --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- Created attachment 102724 --> https://bugs.kde.org/attachment.cgi?id=102724=edit there is a layer with transform to flatten. Also a layer with an EXAMPLE, to show what happens on my system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373495] New: Render cache should not be affected by onion skin
https://bugs.kde.org/show_bug.cgi?id=373495 Bug ID: 373495 Summary: Render cache should not be affected by onion skin Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Maybe this is impossible but I hope it isn't. When working on a bigger animation,having a cache ready to go is great. There are some issues still with how fluently it renders,but those are probably seperate from this. When you activate onion skins krita removes ALL cached frames. even if it would be impossible to not have onion skins influence the cached animations. at the least it should only remove the frames that are actually onion skinned,not dump 100 cached frames at once. I have the memory to make it work,but krita needs to remember the cache. Ideally this would also be true for canvas-only when going canvas-only the cache gets dumped. Maybe it should start a seperate cache for a single layer and keep the global cache? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373495] Render cache should not be affected by onion skin
https://bugs.kde.org/show_bug.cgi?id=373495 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Severity|wishlist|minor -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373493] Flattening an animation with transform mask results in crash or artefacts
https://bugs.kde.org/show_bug.cgi?id=373493 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373493] New: Flattening an animation with transform mask results in crash or artefacts
https://bugs.kde.org/show_bug.cgi?id=373493 Bug ID: 373493 Summary: Flattening an animation with transform mask results in crash or artefacts Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- i have an animation of a bird ,200 frames long that i need to duplicate and move elsewhere,resize. I use transform mask for this,and that works well,no bugs ,but since transform masks are slow to render I flatten the layer. This sometimes results into crashes. Other times the merge is succesful but some frames have also some of the other frames as its contents. For this animation i could erase it out,one by one,but for bigger ,overlapping frames that would not work as the lines would run through each other I think. This is fairly serious as we need this to reuse animations for crowd animation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373473] New: make frame 1 step longer/shorter with shortcuts or RMB
https://bugs.kde.org/show_bug.cgi?id=373473 Bug ID: 373473 Summary: make frame 1 step longer/shorter with shortcuts or RMB Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- if you select a frame and press a shortcut (usually + and -,but should be customizable)) then you add or remove a frame to that keyframe. Every frame that follows either gets pushed back (+) or pulled in (-) Adding a frame doesnt duplicate or make a newframe it just makes the keyframe longer. Removing instances should not delete single keyframes,they remain a single keyframe (length=1) Selecting a range of frames will work the same for every keyframe that is selected,add or remove 1 from their framecount. Selecting a range of frames and removing instances constantly should result in only the keyframes remaining. This will help tremendously with frame managment and speed up timing opetations -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373360] render export - export visible layers seperatly
https://bugs.kde.org/show_bug.cgi?id=373360 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added OS|Linux |MS Windows Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373360] New: render export - export visible layers seperatly
https://bugs.kde.org/show_bug.cgi?id=373360 Bug ID: 373360 Summary: render export - export visible layers seperatly Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- a very useful function would be to have the option to export each visible layer seperatly as a PNG (or whatever you choose) This because sometimes you need many different layers to then assemble again in another program at the highest possible quality. just a checkmark would suffice I think,but maybe there are extra needs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373357] New: add marker to show where start/end of anmation is
https://bugs.kde.org/show_bug.cgi?id=373357 Bug ID: 373357 Summary: add marker to show where start/end of anmation is Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- on the top or the timeline where caching of the frames is shown (with grey rectangles) there could be 2 colored markers/rectangles for start/end that you see in animation docker. When you change the values in the docker,they should be updated in the timeline. Potentially just using the TINT color from the onion skins could suffice,but if this needs to be seperate , seperate colors are fine too. if the value is the same ,maybe show a rectangle with both colors,cut in half? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373316] New: center or follow layer in timeline when going down the layer stack
https://bugs.kde.org/show_bug.cgi?id=373316 Bug ID: 373316 Summary: center or follow layer in timeline when going down the layer stack Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- when you go up or down the layer stack, krita shows the layer in focus. even if you scroll out of range,if you do one "page up" shortcut it will refocus on the layer,and show it. This also happens when you PICK the layer on the canvas. but it doesn not happen for the timeline and I would like that it does. This should perhaps be an option though, but for now i don't see what advantages the current way of working has compared to the one i propose. Selecting a layer in the layer box should also focus that layer in the timeline. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373315] playback cache doesn't get loaded in a good way
https://bugs.kde.org/show_bug.cgi?id=373315 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373315] New: playback cache doesn't get loaded in a good way
https://bugs.kde.org/show_bug.cgi?id=373315 Bug ID: 373315 Summary: playback cache doesn't get loaded in a good way Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- it takes sometimes a long time and multiple 'playbacks' before all the frames are rendered and retained in cache for fluid playback When that happens,playback is great. But before that it chugs and sputters anyway so that doesn't seem to useful. there should perhaps be a rule that krita force-loads the frames before playback,instead of gradually like it does now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373305] New: Apply operation on whole frame selection
https://bugs.kde.org/show_bug.cgi?id=373305 Bug ID: 373305 Summary: Apply operation on whole frame selection Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- if i select a range of frames or even with CTRL-select, various frames ,scattered, it would be great to then just apply the next operations you do to that selection A few things I can imagine 1)delete/create frame 2)apply filter to selection (recolor,blur,color to alpha etc...) 3)transform it's not a big issue if for bigger operations krita needs to calculate and apply to each frame in succession,the main issue is to save time and not have to do it step by step. There are probably more operations that could be useful to mass-apply but these for now would already be great -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372823] image size settings for render export
https://bugs.kde.org/show_bug.cgi?id=372823 --- Comment #3 from Bollebib <kwadraatn...@hotmail.com> --- A second reason to do the scale in the krita settings itself rather then with FFMPEG is that you can APPLY the image resize BEFORE export. If you do it AFTER, export will be MUCH slower. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372823] image size settings for render export
https://bugs.kde.org/show_bug.cgi?id=372823 --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- (In reply to Boudewijn Rempt from comment #1) > To what format are you rendering? Anything but gif, and you should be able > to add a custom ffmpeg commandline option in the settings dialog that scales > the output. I see, does that get saved in the file ,though? I will need to test this first. if it works the urgency will be less high. But having a graphical input box would be preferable to some code in a narrow text field where you need to be very careful not to delete a single character by mistake. And you only realise that mistake after a lengthy export process. Since you cant point to existing pngs to encode(another wish i have),messing with the code can result in lots of trial and error. I have already done so. I have also already encoded . manually,it works. Ut really takes you out of krita which is time waste when you're painting. Few normal users are technical enough to manage it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373039] New: Checkbox to disable automatic backup for RENDER EXPORT
https://bugs.kde.org/show_bug.cgi?id=373039 Bug ID: 373039 Summary: Checkbox to disable automatic backup for RENDER EXPORT Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Render export works with creating PNG s and then creating a video out of those PNG's we have a way to delete PNG's when the vid is created I would like a way to keep PNG's but also prevent backup PNG's being created This is useful for single artworks,not so much for animations it results in a lot of folder managment. So it would be nice to be able to prevent it in render export settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372823] New: image size settings for render export
https://bugs.kde.org/show_bug.cgi?id=372823 Bug ID: 372823 Summary: image size settings for render export Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- for rendering animations it would be a huge timesaver and also be much safer to have export dimensions,that are preferably also saved in the document. This has a few benedfits. It will keep your sourcefile intact,and speed up exporting for big files. We can indeed just resize manually,but that is a dangerous proposition when in the midst of working you can forget that you resized at all,and continued working on the smaller sized file. Not only do you run the risk of doing wasteful work,you can loose your original bigger file if you save too often. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372698] auto-expand timeline range more
https://bugs.kde.org/show_bug.cgi?id=372698 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Summary|auto-expand timeline range |auto-expand timeline range ||more -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372698] New: auto-expand timeline range
https://bugs.kde.org/show_bug.cgi?id=372698 Bug ID: 372698 Summary: auto-expand timeline range Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- https://www.youtube.com/watch?v=6-VD-TNnhto As you can see,workflow with lots of frames on the timeline tends to be somewhat annoying. You expand the range,go back,and then you need to expand it again. There are a few options A fixed space of at least half the timeline after the LAST frame could work. Another option is to auto increase the range when dragging the timeline bar. Doesn't need to be infinite,it can increase in increments ,but it maybe needs to be remembered. Although if it gets remembered and is actually too long there maybe need to be a way to reset it maybe a RMB mousclick function or something else? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372695] data loss when duplicating animated layer and editing
https://bugs.kde.org/show_bug.cgi?id=372695 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- A way to see that the layers are linked is to change the color of a single frame ->linked frames will change color While this is something that could be useful for future features that have been discussed (linked frames)this is actually the wrong way to go as it doesnt provide any visual feedback,and creating a linked frame should be a concious choice,not an accidental one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372695] New: data loss when duplicating animated layer and editing
https://bugs.kde.org/show_bug.cgi?id=372695 Bug ID: 372695 Summary: data loss when duplicating animated layer and editing Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- 1)Make an animation,and duplicate it. 2)now delete or move frames on the duplicated layer. 3)Save and reopen the file. =>the original layer will have the same changes made to it as you did to the duplicated layer. only way to solve this is to duplicate->save->close->reopen so there is a workaround,but this bug IS dangerous and has resulted in data loss for me as I didn't know or forgot about this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #11 from Bollebib <kwadraatn...@hotmail.com> --- just as an update this still seems to be an issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372171] Show in timeline,framerate and frame range doesn't get saved
https://bugs.kde.org/show_bug.cgi?id=372171 --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- https://www.youtube.com/watch?v=4Zhf6CmjCFk made a vid to show the issue first 2 krita instances is 91 version 2 last krita instances is 92 version (newest) as you can see, first 3 times there is no issue when i save the file in 92 ,and then open,everhting i mentionned is forgotten -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372171] Show in timeline doesn't get saved
https://bugs.kde.org/show_bug.cgi?id=372171 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- start and end,as well as framerate doesn't get saved either -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372171] Show in timeline,framerate and frame range doesn't get saved
https://bugs.kde.org/show_bug.cgi?id=372171 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Summary|Show in timeline doesn't|Show in timeline,framerate |get saved |and frame range doesn't get ||saved -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372171] New: Show in timeline doesn't get saved
https://bugs.kde.org/show_bug.cgi?id=372171 Bug ID: 372171 Summary: Show in timeline doesn't get saved Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- sometimes save and reopening a file results in 'show in timeline" being forgotten for all layers. This was not a problem 2 versions of unstable ago and is only present in the latest. I cannot test this in the version just before the latest. just mark all layers with show in timeline active and it will disable and not load these settings correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372133] re-apply worskspace when resizing/starting krita window
https://bugs.kde.org/show_bug.cgi?id=372133 --- Comment #3 from Bollebib <kwadraatn...@hotmail.com> --- (In reply to Boudewijn Rempt from comment #2) > It actually should be correct on restarting because the way we restore the > dockers from the workspace selector is exactly the same as the way we store > and restore the user's configuration between sessions. There's not a single > line of Krita code that handles that... so it should already be working as i described? and somehow it's not working? Or do you mean something else? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 336899] JJ "activate next/previous layer" shorcut
https://bugs.kde.org/show_bug.cgi?id=336899 --- Comment #6 from Bollebib <kwadraatn...@hotmail.com> --- right now ,this is actually solved. But it does not go into hidden groups i think even for hidden groups this should work,and go through EACH layer might perhaps be necessary to close this bug and open a new one? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372134] remember timeline size setting on startup
https://bugs.kde.org/show_bug.cgi?id=372134 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372134] New: remember timeline size setting on startup
https://bugs.kde.org/show_bug.cgi?id=372134 Bug ID: 372134 Summary: remember timeline size setting on startup Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- each new startup i need to zoom out the timeline to show the keyframes smaller. It's a preference I have,i like to see more frames on the screen. But i need to do this EVERY time. It would be great if krita saved this setting so i wouldn't need to reset it every time. I'm trying to reduce the settings i need to redo every startup so that i can just jump in and start painting/working on the timeline,right now I get slowed down each time,to redo 3-4 small tweaks on every startup. Especially due to crashes or some snapping issue,this would make restarting less of a pain. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372133] re-apply worskspace when resizing/starting krita window
https://bugs.kde.org/show_bug.cgi?id=372133 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- Created attachment 102067 --> https://bugs.kde.org/attachment.cgi?id=102067=edit correct -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372133] New: re-apply worskspace when resizing/starting krita window
https://bugs.kde.org/show_bug.cgi?id=372133 Bug ID: 372133 Summary: re-apply worskspace when resizing/starting krita window Product: krita Version: 3.0.2 Alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Created attachment 102066 --> https://bugs.kde.org/attachment.cgi?id=102066=edit averaged Each time on opening,or unmaximizing krita,the dockers get averaged outin width or height. This especially annoying if you encounter some bugs and restarting is necessary I need to do multiple things on startup and anything that can reduce those tedious steps would be great, so that one day i can just jump in and work without needing to adjust3-4 things everytime. On starup and unmaximizing the layout is avaraged out,but if i press my custom workspace the proportions are correct. Maybe there should be an automatic override,or re-applying of the workspace each time? could maybe be an option,but together with the other things I need to do every startup it really builds up frustration. comparison included in attachments -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370566] Larger documents do not get saved with Save as
https://bugs.kde.org/show_bug.cgi?id=370566 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #9 from Bollebib <kwadraatn...@hotmail.com> --- I have this problem kn windowed 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370483] render export remember location in file
https://bugs.kde.org/show_bug.cgi?id=370483 --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- and where you open file should be different from where you export or save files. I often open files somewhere,then save or export somewhere else. I always feel hampered ,when i want to do that.. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370483] render export remember location in file
https://bugs.kde.org/show_bug.cgi?id=370483 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- this is actually not limited to animation,i would enjoy this too for normal files -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370483] New: render export remember location in file
https://bugs.kde.org/show_bug.cgi?id=370483 Bug ID: 370483 Summary: render export remember location in file Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com right now render animation remembers the last used location which is fine for some uses. But usually you have a particular folder structure with a lot of scenes. Each scene is a different animation and thus a different export location. Sometimes you need to re-export a lot and it would be a huge timesaver to have krita remember the location for exporting specific to that file,as you would lose less time browsing. also it would be good to have maybe a relative path? cause sometimes you need to move whole folders at once,and not having to update that would be great But i'm not sure this last request is doable...it's just something i was thinking of for future uses,cause this would have to work the same for sound file locations,where krita looks for it,unless krita would load the file itself?. Just food for thought... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke
https://bugs.kde.org/show_bug.cgi?id=370237 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #4 from Bollebib <kwadraatn...@hotmail.com> --- you don't have stabilizer or another smooth option active per mistake? I would assume not,as advanced color selector has nothing to do with that,but it might be something to eleminate first,and be absolutely sure -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369993] New: seperate eraser smooth setting
https://bugs.kde.org/show_bug.cgi?id=369993 Bug ID: 369993 Summary: seperate eraser smooth setting Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Talked this over with Animtim and we agreed it would be a good idea to have a seperate smooth setting option for eraser. in the similar way as there is a seperate option for size and opacity , for eraser, it would be good to have a seperate smoothing for eraser. Usually you don't need stabilizer or weighted smooth for eraser. so when you use either of those for painting/animating,you constantly need to de- and reactivate the smooth each time. A setting to remember the smooth for each mode would be the last main problem concerning this workflow issue,i think -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367817] Krita crashes with specific animation workflow with keyframes
https://bugs.kde.org/show_bug.cgi?id=367817 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #3 from Bollebib <kwadraatn...@hotmail.com> --- i also get this result -- 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
https://bugs.kde.org/show_bug.cgi?id=369503 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Severity|normal |wishlist OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369503] New: Render animation encode resume after error,by looking at folder
https://bugs.kde.org/show_bug.cgi?id=369503 Bug ID: 369503 Summary: Render animation encode resume after error,by looking at folder Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Render animation sometimes fails to render to mp4 if the naming in the export name field is empty or wrong. A lot of times the png's have exported succesfully anyway. There should perhaps be a way to use the folder with png's as a source to start encoding. Another way would be to make it impossible to have wrong naming convention, or offer away to give a name after it fails and to just continue the process. either of those options,or maybe even all of those could be useful. The first option would be good to reuse png's even if you closed krita and reopened a day after and you really need to make an mp4 quickly. Not having to redo the png export would be such a timesaver ,if you can just make it pount to FFmpeg in some way. An option 'png source' or something like that -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369487] Render animation results in crash if start in animation docker = bigger then zero
https://bugs.kde.org/show_bug.cgi?id=369487 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- Animtim encountered this bug also as well as Dan77 on the krita IRC -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369487] Render animation results in crash if start in animation docker = bigger then zero
https://bugs.kde.org/show_bug.cgi?id=369487 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369487] New: Render animation results in crash if start in animation docker = bigger then zero
https://bugs.kde.org/show_bug.cgi?id=369487 Bug ID: 369487 Summary: Render animation results in crash if start in animation docker = bigger then zero Product: krita Version: 3.0.2 Alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com trying to export to mp4 an mkv (possibly other ones as well) results in crash if the file animation start is set to anything else then "0" if set to zero,no problems occur. You can export with values other then 0 in the export dialog itself,no issues there. Exporting to only PNG does not crash krita. Feedback from Animtim 17:52:25 - Animtim: [image2 @ 0x919e60] Could find no file with path '/my/file/path/frame%04d.png' and index in the range 0-4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369413] Make it possible to have brushes bigger then 1000 pixels
https://bugs.kde.org/show_bug.cgi?id=369413 --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- A second size slider perhaps? that you can add in the toolbar settings? another way would be like the brush pattern scale dropdown of x1 ,x2,x10 to change the slider scale not very elegant but it could work -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369413] New: Make it possible to have brushes bigger then 1000 pixels
https://bugs.kde.org/show_bug.cgi?id=369413 Bug ID: 369413 Summary: Make it possible to have brushes bigger then 1000 pixels Product: krita Version: 3.0.2 Alpha Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com this is something we would need for example for image brushes ,where we select something from the canvas and want to reuse it ,like for example a head or complete character. This is a common technique in animation but can also be good for art to have very big brushes if your pc can handle it. Especially with big canvasses a limit of 1000 is too small. It also helps to select the whole canvas,make a brush out of i then use it on another layer as an improvised "merge" ,as merging a single frame on an animation layer is a tedious task. probably we would need an option next to the slider or in the settings,to unlock this feature to those who want it. I'm not sure this should be default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369335] New: Copy+Dragging a frame onto first frame results in crash
https://bugs.kde.org/show_bug.cgi?id=369335 Bug ID: 369335 Summary: Copy+Dragging a frame onto first frame results in crash Product: krita Version: 3.0.2 Alpha Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com 1) Make an animation layer 2)Draw 5 or so frames 3)CTRL+drag a frame to the 1st frame (timestamp 0) to attempt to copy-overwrite the first frame Krita will crash every time Windows 10 krita.exe caused an Access Violation at location 089B09B0 in module libkritaimage.dll Reading from location 0010. AddrPC Params 089B09B0 7F1A2DC0 7F1A2DB0 086F0EFF libkritaimage.dll!frameIdAt [C:/dev/krita/libs/image/kis_raster_keyframe_channel.cpp @ 77] 08B1B78B 00B38C60 4608C6C0 libkritaimage.dll! ?? [C:/dev/krita/libs/image/kis_paint_device_strategies.h @ 37] 08936D3D 7F1A2DC0 00B38B50 00B38B50 libkritaimage.dll!compositionSourceColorSpace [C:/dev/krita/libs/image/kis_paint_device.cc @ 114] 08A97169 0005 4571D850 00B38BC0 libkritaimage.dll!getDeviceLazy [/dev/i/include/QtCore/qsharedpointer_impl.h @ 192] 089033D0 4571C8B0 00010005 48204601 libkritaimage.dll!projection [C:/dev/krita/libs/image/kis_layer.cc @ 735] 08904C2E 00180CC0 7FFD004D 00180150 libkritaimage.dll!changeRect [C:/dev/krita/libs/image/kis_layer.cc @ 744] 0890B3A8 0040 libkritaimage.dll!changeRect [C:/dev/krita/libs/image/kis_layer_projection_plane.cpp @ 111] 08AA1C15 55397C50 0001 00B39180 libkritaimage.dll!collectRects [C:/dev/krita/libs/image/kis_simple_update_queue.cpp @ 94] 088D8F39 00B38ED8 00B38ED4 394B86B8 libkritaimage.dll!addJob [C:/dev/krita/libs/image/kis_simple_update_queue.cpp @ 191] 088D92E1 0001 54DA1480 3C0567C0 libkritaimage.dll!addUpdateJob [C:/dev/krita/libs/image/kis_simple_update_queue.cpp @ 157] 088DCE3D 1BA4 00B38FE0 0006 libkritaimage.dll!updateProjection [C:/dev/krita/libs/image/kis_update_scheduler.cpp @ 131] 088F62DD 54DA1480 460926E0 libkritaimage.dll!requestProjectionUpdateImpl [C:/dev/krita/libs/image/kis_image.cc @ 1443] 088F64C2 03F60201 04B50484 0002 libkritaimage.dll!requestProjectionUpdate [C:/dev/krita/libs/image/kis_image.cc @ 1470] 089A9A1C 00B392C0 6441ED19 00B391C0 libkritaimage.dll!requestUpdate [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 505] 089AB870 54EF6840 64403AE4 025C libkritaimage.dll!removeKeyframeLogical [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 252] 089AC7AC 4609E940 089AD0BF 00B392B0 libkritaimage.dll!replaceKeyframeAt [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 220] 089AD3B5 0008 libkritaimage.dll!redo [C:/dev/krita/libs/image/kis_keyframe_commands.cpp @ 14] 089AA395 00B394A0 68B574A0 libkritaimage.dll!deleteKeyframeImpl [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 180] 089AA57B 4609E940 00B395A0 libkritaimage.dll!insertKeyframe [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 133] 089AB5D5 089A8F50 454780B0 libkritaimage.dll!copyKeyframe [C:/dev/krita/libs/image/kis_keyframe_channel.cpp @ 126] 42D64731 00B39670 0004 0020 kritaanimationdocker.dll!KisAnimationUtils::moveKeyframes 42D553A3 4571C8B0 3BFD8E00 00B39770 kritaanimationdocker.dll!KisTimeBasedItemModel::offsetFrames 42D5AE73 458838B0 00B39F80 0001 kritaanimationdocker.dll!TimelineFramesModel::dropMimeData 02D88132 0011001C 000D000D 4510193B Qt5Widgets.dll!QAbstractItemView::dropEvent 42D5EE4E 0001 kritaanimationdocker.dll!TimelineFramesView::dropEvent 02B9D828 3B9D95E0 0010 55321310 Qt5Widgets.dll!QWidget::event 02C8664E 61001170 55321310 61001170 Qt5Widgets.dll!QFrame::event 02D936F1 0400 0001 Qt5Widgets.dll!QAbstractItemView::viewportEvent 68A0E7BD 68B59200
[krita] [Bug 367873] New: Fuzzy Stroke doesn't work correctly in windows
https://bugs.kde.org/show_bug.cgi?id=367873 Bug ID: 367873 Summary: Fuzzy Stroke doesn't work correctly in windows Product: krita Version: 3.0.1 Beta Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Rotation and other dynamics don't seem to work correctly for windows. tested in beta with multiple brushes just activate fuzzy stroke on rotation on a few image brushes to reproduce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #9 from Bollebib <kwadraatn...@hotmail.com> --- this is potentially a duplicate of this bug? https://bugs.kde.org/show_bug.cgi?id=344907 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 --- Comment #8 from Bollebib <kwadraatn...@hotmail.com> --- I also encounter this consisently on windows version of krita 3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 338354] Show layer name feedback when not in canvas-only mode
https://bugs.kde.org/show_bug.cgi?id=338354 --- Comment #5 from Bollebib <kwadraatn...@hotmail.com> --- (In reply to Boudewijn Rempt from comment #4) > WISHGROUP: Small Usability Fixes > > Additional comment from Dmitry: it would be useful if the layerdocker is not > visible because another tab is chosen. Should we only show it when then > layerdocker is invisible? That's up for discussion. I don't think so,but that's what I think about it. Also because I'm working with timeline which is also a layer docker,but with some missing features. If you only show it if layerdocker is hidden,do you then follow the same for timeline? even though currently timeline doesn't reflect layer docker fully? The line is kind of blurry,perhaps. Also to me it seems good to always look at the same corner for certain info, good visual feedback,that doesn't change on whether or not some dockers are hidden. Maybe configuration is in order? but that makes it more complex,probably... Just my thoughts on it ,I welcome other views. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362743] Conflicting shortcuts don't get solved with 'reassign'
https://bugs.kde.org/show_bug.cgi?id=362743 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Bollebib <kwadraatn...@hotmail.com> --- this seems solved for now so I'm closing this -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364741] Save layer group crashes krita
https://bugs.kde.org/show_bug.cgi?id=364741 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If a layer in layer docker is clicked and the docker has a scrollbar , canvas zoom with scrollwheel is gone
https://bugs.kde.org/show_bug.cgi?id=364850 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- for my system it seems to work fine Maybe it's a linux only issue? Can you test it out on a windows rig just to compare? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364023] Some brush presets cannot be added to favorites.
https://bugs.kde.org/show_bug.cgi?id=364023 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Bollebib <kwadraatn...@hotmail.com> --- confirmed for me as well,so i'm changing the status to help triage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364023] Some brush presets cannot be added to favorites.
https://bugs.kde.org/show_bug.cgi?id=364023 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- I also encounter this issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364741] New: Save layer group crashes krita
https://bugs.kde.org/show_bug.cgi?id=364741 Bug ID: 364741 Summary: Save layer group crashes krita Product: krita Version: 3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Using the save layer group function seems to lead to a crash https://www.youtube.com/watch?v=6N358nFcTO8=youtu.be While the file I recorded with has lots of layers I also recorded it with only 1 group of 20 some layers and it still crashed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 325052] JJ: Isolate layer mode
https://bugs.kde.org/show_bug.cgi?id=325052 --- Comment #16 from Bollebib <kwadraatn...@hotmail.com> --- Oooh,okay. I didn't realize that. Thanks for confirming =) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 325052] JJ: Isolate layer mode
https://bugs.kde.org/show_bug.cgi?id=325052 --- Comment #14 from Bollebib <kwadraatn...@hotmail.com> --- (In reply to Boudewijn Rempt from comment #13) > Bugzilla wants a comment. Is that directed at me? I'm sorry I don't understand. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added CC||kwadraatn...@hotmail.com --- Comment #18 from Bollebib <kwadraatn...@hotmail.com> --- I seem to be experiencing this as well I use a Yiynova 22 inch ,and it happens on Windows 8 on a laptop,with every 3.0 version I tried. 2.9 doesn't have this issue. My Yiynova works perfectly on windows 7,with stable AND 3.0 variants. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 325052] JJ: Isolate layer mode
https://bugs.kde.org/show_bug.cgi?id=325052 --- Comment #12 from Bollebib <kwadraatn...@hotmail.com> --- https://www.youtube.com/watch?v=KbCcjjPcUAw=youtu.be I made a video to illustrate my issue. The main thing this would solve is speed an ease of use for constant layer-switching which I need to do a lot,depending on the project at hand. You clearly see that comparing and browsing layers is much faster this way. And yes it is only possible with isolate layer. Hiding ,unhiding layers will never be as fast as this. You can compare and browse quickly,disable layer only and continue working. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362743] Conflicting shortcuts don't get solved with 'reassign'
https://bugs.kde.org/show_bug.cgi?id=362743 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- I think it's mainly an issue with overwriting default shorcuts -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362743] New: Conflicting shortcuts don't get solved with 'reassign'
https://bugs.kde.org/show_bug.cgi?id=362743 Bug ID: 362743 Summary: Conflicting shortcuts don't get solved with 'reassign' Product: krita Version: 3.0 Beta Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com for example when I try to set the brush tool that is assigned to B to P ,I get a message that there are conflicting shorcuts. I press reassign,and it doesn't actually register. I have to manually go to the conflicting shorcuts and give them another shorcut.Only then it doesn't give me the error message anymore. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362306] brush outline green color
https://bugs.kde.org/show_bug.cgi?id=362306 --- Comment #1 from Bollebib <kwadraatn...@hotmail.com> --- Created attachment 98617 --> https://bugs.kde.org/attachment.cgi?id=98617=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362306] brush outline green color
https://bugs.kde.org/show_bug.cgi?id=362306 Bollebib <kwadraatn...@hotmail.com> changed: What|Removed |Added Version|unspecified |3.0 Alpha -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362306] New: brush outline green color
https://bugs.kde.org/show_bug.cgi?id=362306 Bug ID: 362306 Summary: brush outline green color Product: krita Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com https://www.dropbox.com/s/prbke5othddoyws/Screenshot%202016-04-26%2016.27.58.png?dl=0 the brush outline is stuck at green for me. I have heard other people mention it as well. Reproducible: Always Steps to Reproduce: look in settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 325052] JJ: Isolate layer mode
https://bugs.kde.org/show_bug.cgi?id=325052 --- Comment #11 from Bollebib <kwadraatn...@hotmail.com> --- (In reply to Boudewijn Rempt from comment #10) > WISHGROUP: Larger Usability Fixes > > This really needs to be discussed with Dmitry again because we cannot figure > out the actual use-case. talk to me on IRC if you like I did explain the usecase in this comment thread It's to have a permanent isolate layer going,so you can jump through your layers while searching for something. Another usecase is if you have an animation on different layers,you can go up and down the stack to check if the flow is correct. This is something I have needed when I worked on skullgirls. They want their animations in a PSD ,so the only way to do this was put the layers in sequence . But to still be able to work on them even after you put them in layerstack ,isolatat layer mode would be useful. Regardles if krita has animation,this is an actual usecase I have had to use for several months. Besides that it's just easier to flip through layers and compare without needing to input shortcuts all the time. I'm a heavy isolate layer user,but it's easier to just activate it and flip through layers ,then deactivate. Then to press the shortcut,siwtch layer,press shortcut again,switch layer,etc X20 expecially for MANY layers this becomes a huge issue. -- You are receiving this mail because: You are watching all bug changes.
