Weekly news 2018-09-21: Scenarios of a trilogy
Added 2018-09-21 21:00:00 +0000 UTCHi Patrons!
This week I finally have the scenario for the trilogy of episode 27, 28 and 29. The hardest part was to find funny end-twist for each episodes and 'cut' the episodes into panels to fit the short format Pepper&Carrot.
For writing, I used the Ghostwriter. I really like this software for writing. I simply keep one line per panel. Ghostwriter improves my focus on writing with the ease of the Markdown format and the quick interactive rendering it has of the Markdown. I like the way I could customize the theme too. Another little feature I like about it: you can rename the filename from the File menu. Other text editor I have like Geany or Kate propose only to 'Save As' to enter a new filename and then you need to open your filemanager manually to delete the previous filename...
It's also the first time I work on three episodes at the same time and the main benefit is to be able to work on the continuity between the scenes and places where the characters are evolving. But I also worked on keeping the episodes 'stand-alone' (in case a new reader fall on episode 28, it should also 'work' as a gag without needing the context).
All in all, that's a lot of constrains and I had to work on a lot of revisions (for episode 27, I wrote 8 different stories!). That was necessary to find the good balance and not get a weak episode compare to the two others.
The future stories will happen in Qualicity and I'm doing now a bit of concept-art before making a cleaned storyboard for the contributors and proofreader of the story development on our collaborative tool Framagit.
I'll have to redraw, because right now, only me can understand my notes:
So my goal is to storyboard now the three episodes as I did for "episode 23: Take a Chance". The rendering for the storyboard of this episode was half way between a storyboard and a drawing step and this rendering really helped to plan the episode correctly and get good feedback from community of proofreader. I want to reproduce this experience.
But unfortunately, I'm a bit stuck by a Krita bug to enter text in speechbubble on my storyboard... This afternoon, I tested other solution and workaround for that: GIMP, AZPainter ...without success. I'll probably have to use an old appimage of Krita 3.x ; or see if I can work the storyboard with Krita and Inkscape. I'll let you know.
Concept-art are also appearing since I finished writing and twisting my brain. I'm working on a quick illustration to give news on social network and the blog. Here is a sketch of it, I'll color it maybe while I'll do the black and white storyboard. I'll need a bit of colors on the evenings :)
That's all; next week, I hope I'll have storyboard pages to show you, and why not, to share the first pages of episode 27 here too.
Have a good week-end all, and thank you for your support!
Comments
Ha, don't worry, I understand for the bug report. One issue is, with many user just skipping the text tool and give no feedback about it, the devs think the new text tool is fine, and only me complain while 10000 download of Krita happens each day. So I must be wrong. Thanks for the URL of SK1, I'll try it! For reporting a bug; you just need a single URL: <a href="https://bugs.kde.org/enter_bug.cgi?product=krita" rel="nofollow noopener" target="_blank">https://bugs.kde.org/enter_bug.cgi?product=krita</a> in your fav (and a account on this Bug tracker). Then reporting a bug is often just filling the form, add a good Title, and fill the content with steps on how someone else can reproduce the bug (eg. describing step by step the procedure for someone else to get the bug.). But it takes time and I understand how it can be hard to work and :get a BUG, loose time because of the bug, loose time because of reporting the bug and following discutions, testing, etc. It is unfair and impossible to manage in a professional environment.
David Revoy
2018-09-26 08:06:33 +0000 UTCTo tell the truth, I never know how to report bug... ;_; Have to learn now. I was impatient and when adding simple text just wouldn't stay in place I went back to Krita 3. Let's be real, text tool in Krita isn't good, but 3 was less broken than 4. Also, I didn't have to keep hitting return to make line breaks. I'm on Windows so it may be easier to keep multiple portable versions. I've been searching for another solution and found sK1 (<a href="https://sk1project.net/)." rel="nofollow noopener" target="_blank">https://sk1project.net/).</a> After a quick test I found a few things I like. It uses true vector text! Can produce multiple pages document! Faster and less cluster than Inkscape! Since I'm dealing with printing too, it's useful. But I have to test more to make sure. >_
2018-09-26 03:45:28 +0000 UTCHi, thank you for your feedback! I tried to investigate the bug myself (discution here: <a href="https://bugs.kde.org/show_bug.cgi?id=395769)" rel="nofollow noopener" target="_blank">https://bugs.kde.org/show_bug.cgi?id=395769)</a> but I failed. The only thing I found; it was working on the first Krita 4 version(4.0.0). This morning, while chating with the project leader -Boud-, he tested and confirmed it was a regression. Also, katearcher89 using Windows 7 joined the bug report to let know the bug was affecting Windows. So, now we are three user confirming the bug as reproducible (if you want, you can add your feedback on the bug report, it will help the developper to see this bug impact you, right now only three are complaining about it since June). All in all, I'm happy because Boud is looking at the report today when I asked him direct help. My workaround so far was: 1. to handwrite the text, but it felt as non-flexible as the bug when I started rewording or doing line-break. 2. to use Krita 4.0.0, but I'm spoiled with newer cursor option of Krita 4.1 and a couple of precious fix. It is hard to go back in a time where most of the bug I reported are still alive xD 3. to do text with Inkscape, and jump between apps, export layers, reimport to refresh, etc. Long and probably longer than redoing the line-break everytime. 4. to use other FLOSS manipulation image app with text abilities: GIMP (I tried AZpainter, but this one only 'stamps' text as raster objet, no possibility to edit them after). All in all, not really glorious :) I admire your courage to use 3.x for workaround!
David Revoy
2018-09-25 08:49:19 +0000 UTC
