Hi David,

This is far from the case. We would never be able to transform our library data into a sufficiently functional GDTF that you would actually want to use rather than replace with another GDTF on the console. Not to mention that we are not allowed to export AtlaBase's library data so even if we could do it technically, we couldn't legally.

In reality the only viable option would be to have the user supply the GDTF files to bake into the export. Like an attachment.

I would add that we are looking into enhancing the placeholder GDTF files so they are more useful in identifying the correct DMX mode. The authors of GDTF and MVR are also going to place some new attributes in an upcoming version of MVR that will make it easier to work with placeholder GDTF files.

(A placeholder GDTF is a lightweight GDTF file that is only used to identify the type of a fixture. It doesn't actually contain a fixture definition.)

It seems like either way would solve the problem of reassigning the fixtures after every MVR import in GM3. I'm looking forward to seeing this implemented.

This is a problem on the GMA side. Whatever placeholder it is offered, it should remember the fixture association you do and when you import the same file again in the same show, it should have remembered thos associations. If you import the .mvr into a new show it makes sense you need to learn GMA again which fixture is which.

Hello everyone,

I'm bringing up this old topic again because I'm currently dealing with the same issue. 
Would it be an option to treat GDTF as a kind of parallel fixture? i.e. Capture works with its own lamp models, but keeps GDTF in the background to use it again when exporting?

Cheers from Berlin

Toto