Importing numbered sequence of Alembic files

[Nicholas Yue]

Hi,

I have been given a numbered sequence of Alembic files

splash.#.abc

i.e. splash.0001.abc, splash.0002.abc, ....

The mesh topology between frames are changing

Using AbcStitcher on the sequence crashes the AbcStitcher
application (I will be building a debug version and find out more)

In the meanwhile, how does one bring in a sequence of Alembic files
into Maya ?

In Houdini, it is straight forward, I just used $F4 in the Alembic
file SOP

Regards

--
Nicholas Yue
Graphics - RenderMan, Visualization, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
Management - Recruitment, career management
http://www.proceduralinsight.com/
http://au.linkedin.com/in/nicholasyue

[Steve LaVietes]

While not everyone agrees, the typical and intended alembic workflow is to store multiple samples in a single archive. In any case, the maya reader expects this currently.

That's definitely something we'd want to fix in AbcStitcher. If the crash isn't reproducible in a trivial topology-changing case, it'd be useful to get your example files.

-stevel

> --
> You received this message because you are subscribed to the Google
> Groups "alembic-discussion" group.
> To post to this group, send email to alembic-d...@googlegroups.com
> To unsubscribe from this group, send email to
> alembic-discuss...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/alembic-discussion?hl=en
>
> For RSS or Atom feeds related to Alembic, see:
>
> http://groups.google.com/group/alembic-dev/feeds
>
> http://groups.google.com/group/alembic-discussion/feeds

[Nicholas Yue]

On 10/05/12 13:24, Steve LaVietes wrote:
> While not everyone agrees, the typical and intended alembic workflow is to store multiple samples in a single archive. In any case, the maya reader expects this currently.
>
> That's definitely something we'd want to fix in AbcStitcher. If the crash isn't reproducible in a trivial topology-changing case, it'd be useful to get your example files.

Hi,

I have build the abcstitcher in 1.0.5 in debug mode, attached ddd
and found the crash occurred on line AbcStitcher.cpp line 755 from the
stacktrace

size_t index = minIndexMap.find(minVec[f])->second;
iOrderedArchives.push_back(iArchives[index]);

As the input files to abcstitcher are generated in-house (not from
existing 3d packages), it looks like related to time/time-stamp/sample-time

I will relook into the in-house Alembic file generation code.

In the above code, on frame 2, the return value from ->second has a
value of 140737488343320 which looks suspicious.

Some defensive coding there might help but garbage-in-garbage-out
so I need to fix my end.

[Lucas Miller]

Defense!

http://code.google.com/r/millerlucas-dev/source/detail?r=7c6fda8b54725002d195ce04e630d4a7779aaf71

Lucas

--
You received this message because you are subscribed to the Google
Groups "alembic-discussion" group.

To post to this group, send email to alembic-discussion@googlegroups.com

To unsubscribe from this group, send email to

alembic-discussion+unsub...@googlegroups.com

[Lucas Miller]

A clarification:

For those that haven't seen this recent related question from Nicholas:

http://groups.google.com/group/alembic-discussion/browse_thread/thread/ec9dd5ba38ce731b

The examples he sent to Steve was using only the default time sampling, which was causing the crash.

Setting the proper time sampling is critical in determining how the samples should be combined together, especially when you only have one sample per file.

Lucas