search

pombreda / alembic

Automatically exported from code.google.com/p/alembic
Other
0 stars 0 forks source link

QA Interooperability - round trips, as well as cross every writer to reader #193

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We currently have 2 writers - zeno and Maya, and we have 5 readers - zeno, 
maya, katana, houdini, and RiProcedural. We should generate files from both 
writers, take into opposite app, and write again. We should read an asset, 
write it back out and read it back in (we shouldn't loose data on going around).

There are some edge cases, such as names of objects that contain special 
characters (like : for maya, and maybe houdini?)

Original issue reported on code.google.com by ble...@gmail.com on 8 Jul 2011 at 6:00

GoogleCodeExporter commented 9 years ago 
Am scheduling to a different time based on today's call

Original comment by scottmmo...@gmail.com on 11 Jul 2011 at 11:13

GoogleCodeExporter commented 9 years ago

Original comment by ble...@gmail.com on 26 Aug 2011 at 11:51

GoogleCodeExporter commented 9 years ago 
Adding to Milestone 1.1

Original comment by scottmmo...@gmail.com on 6 Sep 2011 at 11:10

GoogleCodeExporter commented 9 years ago

Original comment by ble...@gmail.com on 19 Sep 2011 at 7:24

GoogleCodeExporter commented 9 years ago 
Namespace-d node names from Maya (names with ':' in it) indeed can't be 
imported by the Houdini Alembic SOP.

Original comment by tus...@gmail.com on 23 Sep 2011 at 12:59

GoogleCodeExporter commented 9 years ago 
Kirk S. has been building a set of geom primitives for testing in Katana. We're 
still developing the set and confirming export & import correctness. Once we 
have teh set of files we'll add them to the download page.

Original comment by ble...@gmail.com on 28 Oct 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
Issue is too broad and even references things not usable by the general public. 
(Zeno)

Original comment by miller.lucas on 25 Jun 2012 at 6:20