Hi Matt Back when I was still in the corporate world when we had identified that a client needed some kind of data migration that wasnt simply database to database, we would set up meetings to lay the ground work for whatever import / export spec needed to be created.
Your last sentence was pretty much verbatim what we used to ask them at the first of those meetings ;) ________________________________________ From: Matt Lind [speye...@hotmail.com] Sent: 02 June 2015 11:58 PM To: softimage@listproc.autodesk.com Subject: RE: Writing custom loaders for .emdl and .scn files in other apps Having file specs only gets you part of the way. You still need to write an importer/exporter to move the data around. The only thing that could be gained at this point is exposure to critical data that isn't accessible in the SDK. There isn't much you can't touch in the SDK. If memory serves from my experience trying the compound file viewer, the .emdl and .scn file formats didn't look very different from what you see in the scene explorer. Mostly just data packed in encrypted ways to be be more efficient on disc. I have been working on an exporter to export from Softimage|3D and import into Softimage|XSI using my own file format as the medium to exchange information. I have used a similar file format for many years to move between newer/older versions of XSI so data is version independent. Most of the file format is structured as you see it in the scene explorer, with some exceptions. Works for most applications. The real question is - what exactly needs to be exported, and where does the data need to go? Matt Date: Tue, 2 Jun 2015 20:11:39 +0000 From: Angus Davidson <angus.david...@wits.ac.za> Subject: RE: Writing custom loaders for .emdl and .scn files in other apps To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> Maybe now that Soft is EOL, the best goodwill gesture from Autodesk would be to actually release the file specs. It serves the purpose for them of allowing people a way forward without having to try and convert decades of stored assets. The digital version of closure. = <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table
