"Now that's a really neat idea. What (affordable) MIDI controller do you like?"
I use a Korg NanoKontrol. The one here with the sliders and knobs: http://www.korg.co.uk/products/software_controllers/nano2/sc_nano2.php I'm not sure how much it is but it's cheap compared to what there used to be. It's very small and portable so ideal for Gimp. It communicates with alsa (via USB). You have a small GUI app called aconnectgui where you can see the Korg output and Gimp input. You just connect them up. I actually do it from command but that's because I couldn't find aconnectgui in the Arch repo. Here's some info from the Ubuntu site: https://apps.ubuntu.com/cat/applications/precise/aconnectgui/ One problem is that you need the Korg editor (Windows or OSX) to change MIDI functions on the NanoKontrol. That should work via wine but I didn't try that. The reason you have to change some things is that by default some of the switches are momentary or maybe that wasn't the problem. I can't remember exactly but I had to edit a few things. I'm not on Linux at the moment to look at it exactly but you'll find MIDI under Input controllers in Gimp. You have a vast choice of Gimp parameters and you set them by choosing the one you want then moving the appropriate knob on the controller to set it to the parameter. There is stacks you can do. I like to set it to change colours i.e. one knob will increase red etc. Selecting colours, values etc in the colour wheel suddenly starts to become obsolete. Actually, thinking about that particular function, I think that was why I had to edit the Korg via its OSX(or Windows) editor. I think you need that particular value to not go to zero value. Probably I should document all this somewhere properly. The huge advantage over a graphics tablet slider is that MIDI has continuous controllers. This means you move the knobs and sliders up and down to exact values. You are not sending a keyboard command. It's really quite ingenious whoever thought of adding that to Gimp and I bet hardly anyone uses it. On 12 September 2012 17:02, Ryan Stark <efflux...@googlemail.com> wrote: > "It's not logical to save a whole session if all one does is touch up > a jpeg file." > > No, so then the logical thing is to export. Why is this such a > problem? Export is separated from save dialog to make it difficult to > accidentally lose you data. If you accidentally save to xcf rather > than export then no problem. If you do the opposite then it's possible > disaster. There have been a few occasions in the earlier Gimp where > I've exported when I should have saved. Not even a total accident in > some cases. I just though the editing was done whereas the new way > tends to remind me to keep the xcf. > > For very casual users, this may not be understood but the new way of > doing it is more friendly to people who understand it. It's not > difficult to deal with. Should Gimp be dumbed right down to cater for > people who don't understand things or should Gimp do things the right > way? Sometimes free software developers can make bad choices, that's > true, but sometimes (as in this case) they don't pander to what many > users want, instead they make the right change for the better and I > believe that most Gimp users will in fact realize that this simple > change is better. > > > On 12 September 2012 16:37, Ken Warner <kwarner...@verizon.net> wrote: >> It's not logical to save a whole session if all one does is touch up a jpeg >> file. >> >> On the other hand, for people who do complicated image building over many >> sessions, it makes sense to save a project and in that case it would be >> logical to have an option that allows gimp to open the previous project on >> restart. That would prevent work loss. >> >> >> On 9/12/2012 3:30 AM, Ryan Stark wrote: >>> >>> I see lots of complaints about the Gimp save and export. I've been >>> using Gimp for ages with this feature. It is entirely logical and I >>> don't understand the complaining. >>> >>> In a DAW (digital audio workstation application) you save the whole >>> project as a session. You export the final file as mixdown in MP3 or >>> whatever other format and you can import audio files into the project. >>> It's similar logic in Gimp and makes total sense. Lots of apps work >>> with this kind of method even when not as crucial as it is with DAW >>> software. >>> _______________________________________________ >>> gimp-user-list mailing list >>> email@example.com >>> https://mail.gnome.org/mailman/listinfo/gimp-user-list >>> >> _______________________________________________ gimp-user-list mailing list firstname.lastname@example.org https://mail.gnome.org/mailman/listinfo/gimp-user-list