Jump to content

casterle

Members
  • Content Count

    428
  • Joined

  • Last visited

Everything posted by casterle

  1. I've still got an old Ensoniq SQ-80 from my playing with MIDI programming days in the mid-80's. I've probably got the old MIDI card and cables lying around as well. Things have changed and I think USB has been the catalyst for MIDI growth outside the music world. Being able to use a cheap MIDI controller easily (no special hardware or cables) makes all the difference. Now I've got a quality graphics tablet with 9 knobs and 22 buttons (counting those on the tablet itself) for under $150. I've spent the last week or two playing with the new Blender UI and am teetering on the edge of a very deep dive. I imagine the X-Touch Mini will be useful there as well, especially with the sequencer.
  2. Exactly. From my research (I've never used LR) it appears that LR exposes an API that supports reading/writing values. MIDI2LR (https://rsjaffe.github.io/MIDI2LR/) takes advantage of this and provides direct adjustment of values via MIDI encoders. The X-Touch Mini has a light ring around each encoder knob which can be configured in various ways. My understanding is that MIDI2LR can be configured to update these rings when the associated value is changed in LR. The X-Touch Mini also has 2 'layers' so that you can switch between, changing the function of the various controls and providing 16 encoder knob functions. I don't know if this can be supported via MIDI2LR, but 8 encoders and 16 buttons is still pretty awesome.
  3. It's pretty amazing how much a MIDI controller can speed up things that have nothing to do with music. MIDI controllers are now so inexpensive (I got my used X-Touch Mini in like-new condition for $47 from Adorama) and add so much convenience I'm surprised more folks aren't using them. Oh, and as it turns out, it's not a new one (although it was to me until recently). Turns out LR users discovered them long ago, perhaps because LR offers much better integration via an API. But you can make them work with any app that has keyboard shortcuts.
  4. Well then, this should make you happy. Everything you need, although if you're on a Mac the MIDI translator program I use isn't free.
  5. As @firstdefence noted, the software does not provide this functionality (yet). If you're on Windows and are comfortable with the process, it's not hard to do this manually.
  6. If you have a license for the release version you can download the beta version now. Both versions can be installed at the same time, and do not interfere with each other. Note that files saved by the beta are no longer compatible with the release version.
  7. Nice job. I found your accent not only understandable but enjoyable, and thought the pace was fine.
  8. But it should be. If I hide something, I don't want it to have an effect; it should act in the same manner as deleting it from the group. IMHO.
  9. While the behavior may be expected by the developers, there is no reason to expect it as a user. They need to revisit this issue. Requiring an image to be contained within the layer is problematic for two reasons. First, you must expand the size of your file by the size of your image for *every filter group* you want to apply. But more importantly, you are breaking a basic data design principle - data should exist in only one location within a DB (like an afphoto file). This concept was developed with good reason: If I find an record that needs to be updated, it should exist in only one place to prevent the DB from becoming inconsistent by inadvertently updating the record in one location but not the others. The reason this principle should be applied to AP is the same. If I find a flaw in my image, I want to be able to fix it in one place rather than having to remember the groups that must (incorrectly IMHO) also contain that layer to work. It's true that inconsistencies in images are generally more apparent than those in databases and thus easier to root out, but why should we have to root them out in the first place?
  10. I understand. Mucking about with these files is certainly not for everyone. I was trying to say what Walt said better .
  11. I like the suggestion in your OP, but I don't understand this comment. Are you miffed because no one from Affinity has replied?
  12. I think the trial is the same version as the release, but I"m not sure: 1.6.5.135. The exe is dated 9/24/2018.
  13. All these images are wonderful, but I find this one grabs me like none of these others. Now for the dumb question. I'm not a photographer so I wonder, are infrared images captured with a special infrared camera? My understanding of infrared is light outside (below) the visible spectrum so it seems special hardware would be required...
  14. The export/import functions are great, but there are many settings that aren't covered by this mechanism. On Windows, and I suspect on Mac as well, most of the settings are stored in .XML files. Here is a list of the settings files for both the release and beta folders (the filenames in red are different between the two folders): .: These files are just text, so you can examine them and copy settings from one to another. If you are comfortable with text editors (as opposed to word processors ) you can copy settings from one file to another, or copy the entire file from the release version to the beta and see what happens. As long as you follow Walt's excellent advice and back up the files you want to change first you can always get back to where you were when things go wrong. I've did this extensively when I first started playing with the beta without problems (I haven't used the beta in some time as I'm still in heavy leaning mode with AP). Note, however, that I am a retired software developer and thus very familiar with these things. If you are not confident in your abilities I would recommend you not proceed down this path.
  15. I'm the one who mentioned Everything in the first place .
  16. Yes, Everything is just a search utility. I imagine it uses the same mechanism to display preview images are Explorer.
  17. For those who not needing a DAM (and others as they wait), I've been using a free program, Everything (https://www.voidtools.com) ,to keep track of my Affinity related files, among others. Unfortunately, I do not believe they have a Mac version. Everything runs as a service and maintains an index of the drives/directories, and searches them with lightning speed. What makes it especially useful is that you can set up filters. I've got one for files I use with Affinity programs. Not DAM, but much better (and faster) than Explorer. This is especially useful for me as I am learning because while I might want to use a new technique, I surely won't remember where the associated files are or what they were called so I can brush up. Everything Affinity filter to rescue:
  18. "The idea is the list will never get longer. As we complete and release features then we will replace those features with new ones." There is no indication that the post has been updated since it was written.
  19. This isn't a roadmap as much as a discussion of things people would like.
  20. This doesn't sound like a hardware problem to me, but it is possible. Corrupted RAM, whether CPU or GPU, can manifest itself like this, but IMHO it is nearly impossible that this would occur without other symptoms.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.