Designing own gobos: filenames and relative locations
Posted: Sun Nov 15, 2015 10:25 am
So, I began making a few qxf files for fixtures that don't come stock with qlcplus and that I couldn't find in the forum section where people are supposed to post their qxf files.
I have a few questions.
- Is there any reason why the filenames for gobos are "gobo000001.png", "gobo000002.png", etc. instead of giving them more meaningful names, like "star.png", etc?
- Since my gobo files are not in the stock directory, I've put them into ~/.qlcplus/fixtures/[manufacturer]/gobo*.png
However when I select one of these files via the fixture editor, the full path to that file is saved in the qxf, and not a relative path like in the stock fixtures. I noticed, that qlcplus makes local fixtures just as available, as stock ones. Is there any reasons, why things are different with gobos?
In case anyone is wondering, I've put the files on github: https://github.com/polemon/fixtures
The directory is just my ~/.qlcplus directory. (The name might be a little misleading, but it's the first thing I've come up with when making the repo.)
I have a few questions.
- Is there any reason why the filenames for gobos are "gobo000001.png", "gobo000002.png", etc. instead of giving them more meaningful names, like "star.png", etc?
- Since my gobo files are not in the stock directory, I've put them into ~/.qlcplus/fixtures/[manufacturer]/gobo*.png
However when I select one of these files via the fixture editor, the full path to that file is saved in the qxf, and not a relative path like in the stock fixtures. I noticed, that qlcplus makes local fixtures just as available, as stock ones. Is there any reasons, why things are different with gobos?
In case anyone is wondering, I've put the files on github: https://github.com/polemon/fixtures
The directory is just my ~/.qlcplus directory. (The name might be a little misleading, but it's the first thing I've come up with when making the repo.)