Jump to content
CameraBag & Fotograf Forums

ripienaar

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About ripienaar

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ripienaar

    Cinema LUT Parsing too strict

    yup! just had a chance to test it now and my problem files now work, well done thanks
  2. ripienaar

    Cinema LUT Parsing too strict

    thanks for the quick turn around, mines from the app store so I'll keep an eye out there
  3. ripienaar

    Cinema LUT Parsing too strict

    That's annoying, I'll see what I can do, the ones I have with this problem are commercial - so I might mail it to you instead Any event, I fixed all my cube files by just doing this in a unix terminal: find . -name \*.cube -print0|xargs -0 -I {} sed -i .bak '/^V^M$/d' "{}" This literally just nuke all the blank lines leaving the rest along.
  4. ripienaar

    Cinema LUT Parsing too strict

    Sorry for posting this in the wrong topic, somehow did not see the Cinema bugs forum
  5. ripienaar

    Cinema LUT Parsing too strict

    Various other combos of blank lines also confuse it, the example code from Adobe in the Cube LUT specification 1.0 (CubeLUT.cpp example) just ignores all blank lines, you should probably do the same.
  6. ripienaar

    Cinema LUT Parsing too strict

    hello, Many LUT .cube files I found from 3rd parties are in the form: TITLE "foo" LUT_3D_SIZE 64 0.0 0.0 0.0This does not parse correctly, if I hand edit the LUT file and make it: TITLE "foo" LUT_3D_SIZE 64 0.0 0.0 0.0Ie. just insert a blank line after TITLE and not after LUT_3D_SIZE it all works fine, this format you do not support seems popular and so it's quite a pain to use with your software. Please allow both formats. EDIT: Version 1.0.0 (EP)
×