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.)
Designing own gobos: filenames and relative locations
-
mcallegari
- Posts: 4827
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
All the fixtures in the QLC+ library use bundled gobos, so relative paths are stored to save space in the fixture files.
Also, the gobos path is different on Linux, Windows and OSX and it is not predictable, especially on Windows and OSX.
If you use custom gobos, they can be anywhere in your hard disk, thus absolute paths are used.
As for names...there are more than 800 gobos. Do you really think I had the time to pick a unique name for each one of them ?
Also, a progressive number is easier to batch process with a script.
Your gobos: unless you have a written permission from Eurolite to use them, they will never get included into QLC+ for copyright reasons. By the way, most of them are already present in the library. Use those.
Also, the gobos path is different on Linux, Windows and OSX and it is not predictable, especially on Windows and OSX.
If you use custom gobos, they can be anywhere in your hard disk, thus absolute paths are used.
As for names...there are more than 800 gobos. Do you really think I had the time to pick a unique name for each one of them ?
Also, a progressive number is easier to batch process with a script.
Your gobos: unless you have a written permission from Eurolite to use them, they will never get included into QLC+ for copyright reasons. By the way, most of them are already present in the library. Use those.
-
polemon
- Posts: 15
- Joined: Thu Nov 12, 2015 11:36 am
- Real Name:
OK, I was just thinking that since local files for fixtures are merged with stock parts, one could to the same with gobos.
Relative names, as in relative to the user directory, etc. (.qlcplus on linux, AppData/qlcplus on windows or whatever, no idea about OSX).
As for "friendly names", OK, it's reasonable, etc.
I'm a bit amazed, that such simple shapes as pictographs of the gobos are protected. But OK, I guess I'll be the only person to use them, then.
Relative names, as in relative to the user directory, etc. (.qlcplus on linux, AppData/qlcplus on windows or whatever, no idea about OSX).
As for "friendly names", OK, it's reasonable, etc.
I'm a bit amazed, that such simple shapes as pictographs of the gobos are protected. But OK, I guess I'll be the only person to use them, then.