Page 1 of 2

Alembic Stitch Crashes

Posted: Thu Aug 17, 2017 10:31 am
by nshaun
Hi,

I'm having trouble stitching alembic (.abc) files using the Stitcher in Realflow.
I'm on the latest version of Realflow and my PC has 64gb of RAM and more than enough storage space.
I can stitch the same sequence if it's about 500 .abc files, but anything above that RF starts not responding.
The meshes aren't even that big in size (less than a mb each).

Thanks in advance.

Re: Alembic Stitch Crashes

Posted: Wed Aug 23, 2017 3:29 am
by nshaun
Anything?
I am still having this problem and can't seem to find a solution.

Re: Alembic Stitch Crashes

Posted: Wed Aug 23, 2017 5:17 am
by ChristianZ
Hi

I had problems with the stitcher before, but it was difficult to see a pattern. Is the problem only with the number of files, with the final size of the stitched abc or with the size of the single files?

Re: Alembic Stitch Crashes

Posted: Wed Aug 23, 2017 6:25 am
by nshaun
Thanks for the reply.

Each .abc file is less than 1mb each so I doubt it's a problem with file size.
I have stitched ~100GB .abc's in the past with more frames (1000 frames+).

Right now I can't really seem to find a pattern :|

Re: Alembic Stitch Crashes

Posted: Sun Apr 22, 2018 11:44 pm
by Evoconian
I've been having this problem too; It wasn't an issue with name length or characters, just the size (600 frames, largest ~4.7MB)

A workaround I found works is to stitch one half, name it something like "01" and then stitch the other half "02" then stitch those 2 together. Annoying, but it works!

Re: Alembic Stitch Crashes

Posted: Fri Apr 27, 2018 7:07 am
by harley
This topic is most useful.

Re: Alembic Stitch Crashes

Posted: Sun May 13, 2018 11:42 am
by Evoconian
Since I can't find any way to edit my previous comment, I'll put this final word in for anyone struggling:

As of now (Realflow v10.1.2.0162) the built in GUI alembic stitcher WILL NOT do consecutive stitching (E.G. it will stitch first and second 300 frames separately, but then fails when stitching those two together) no matter the naming scheme.

It just won't.

To stitch those pre-stitched files, you need to edit this batch script to suit your file path(s), then run it:

Code: Select all

import glob, subprocess

# prepare command line
args = ['C:/Program Files/Next Limit/RealFlow 10/stitcher.exe', '--in']

#get files

for files in glob.glob("D:/PrestitchedABC/Basic/usemeVDB01_*.abc"):
   args.append(files)

# rest of the commandline
args.append('--out')
args.append("E:/StitchedAlembic/Basic/final_file_stitched.abc")

# stitch them
p = subprocess.Popen(args, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)

# print stitch output
for line in p.stdout.readlines():
    scene.message(line),
retval = p.wait()


Make sure you name your files akin to the default realflow naming scheme (E.G. blankVDB01_00001)

This *should* work for anyone struggling, and hopefully they will work out these bugs in the future.

Re: Alembic Stitch Crashes

Posted: Sun May 13, 2018 4:24 pm
by ChristianZ
Hi Evoconian,

thanks for this information!

I am glad it works for you now. So you are able to stitch 300 small files in one go.

Re: Alembic Stitch Crashes

Posted: Sun May 13, 2018 4:59 pm
by Evoconian
No problem!

The number varies based on the simulation length. I've gotten up to 550 smaller files stitched in one go before, however I'll sometimes have to drop that number down to as low as 50 with higher resolution simulations.

So far having a different amount of frames in the pre-stitched .abc files hasn't mattered, but anything is possible.

Adding on, I've always deleted the first "VDB01_00000" file with the stitching.

Re: Alembic Stitch Crashes

Posted: Thu Jun 21, 2018 7:46 pm
by SherbetKing
Understanding that I sound like a noob here: how do I use that batch script? I got as far as copying the code into notepad, saving as a .bat file, changing the file paths to match mine, but when I run it (by just double clicking the file), nothing happens? I feel like I'm definitely missing something, but it's probably something obvious?

To clarify, I'm stitching together 500 frames at a time into files named usemeVDB01_1.abc, usemeVDB01_2.abc, etc., then pointing the second file path to the first prestitched abc, and adjusting the last file path to the desired output location and filename.