Jump to content

Joachim Rensing

  • Content count

  • Joined

  • Last visited

  1. Joachim Rensing

    LUT Export not working

    Thank you for the files and the explanation. As I assumed, only the RED and BLUE channels are toggled. I checked my REGEX again and saw the error I made in the first try. I did a lot of tests, all is o.k., when I import the corrected .cube LUT in Affinity and compare it with the original adjustments. An additional test in Final Cut Pro with mLut was also successful. So here is my solution for all, who are interested: 1) open the wrong xy.cube from Affinity in a Text Editor with Regular Expression capability (BBEdit, Text Mate, …) 2) search this regex: ^([0-9\.-]+) ([0-9\.-]+) ([0-9\.-]+)$ 3) replace all with (BBEdit): \3 \2 \1 or (Text Mate): $3 $2 $1 Thats all! Save and you're done. Additionally here's a small bash-script as an alternative to the Editors: #!/bin/bash sed -E 's/^([0-9\.-]+) ([0-9\.-]+) ([0-9\.-]+)$/\3 \2 \1/' "$1" > "$2" exit 0 # script end Save as script file: xy.sh Make it executable in Terminal in pwd: chmod +x xy.sh Start the script in Terminal in pwd: ./xy.sh "path1" "path2" Parameter 1: path to wrong xy.cube Parameter 2: path to corrected .cube
  2. Joachim Rensing

    LUT Export not working

    Hello, what exactly means write order of the RGB channels? Is it for example BGR instead RGB in all lines of the LUT-file? I tested this with a simple REGEX search/replace in BBEdit and changed RGB values to BGR (column 123 to 321). But that gave me not the wished result. Could you tell me, what has to be changed, then I could write a shell script for easy converting?
  3. Joachim Rensing

    Affinity Designer - corrupt file

    Hello, yes, the original file was on a SMB mounted Volume (SMB 2) from a QNAP NAS with actual Firmware (4.2.0) My Mac runs OS X 10.9.5 Mavericks. So far I never had problems on working this way. Could it be, that Affinity uses a special kind of file writing? I noticed, that e.g. Photoshop saves first a temporary (hidden) file in the target, probably to have a safe copy of the new version, before writing the final file. What's also noticable for me, that saving a file with Affinity Designer is not regulary/only partial visible for the Mac fsevents. I use MacFSEvents sometimes to observe directories for file changes. It works very fine with a lot of file types but interestingly not with Affinity files. Nevertheless I like Affinity Designer very much! Regards.
  4. Joachim Rensing

    Affinity Designer - corrupt file

    Thank you! The file is uploaded to Dropbox.
  5. Joachim Rensing

    Affinity Designer - corrupt file

    Hi, I have trouble to reopen a Affinity Designer file, that had problems at saving (I had to force quit Affinity Designer). It is located on a smb-mounted network drive. I worked on it this way for some days without problems, but now it happened. After that I copied the file to the Desktop, but the same error occurs (Failed to open document error ... The file appears to be corrupted.). I read in this forum of similar situations of other users, where you could recreate the file. Could you try it with my file too?! It would be a big help! It's 157 MB, too big to upload here. What's the best way? Regards, Joachim Rensing

Important Information

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.