Scenaid 1.6 script crashes scenarist
Hi, have a problem with Nightmare before Christmas R1 - get done with the encode and try to create a new project from script in Scenarist, get through the import process to the Restoring Link -gt; and then get the standard XP quot;Scenarist has had an error and will be closedquot;..
Here's the link to the scp amp; debug log
What am I doing wrong?
you have non-seamless angles.... only scenarist 3.0 can import scripts w/ those
(VTS2 has the angle - vobid 2 and 3 it looks like)
thanks. I hate angles. Never seem to have success with either angles or vob-id processing.
Time to install Scenarist 3, as well...
heh... scenarist 3.0 can handle non-seamless w/out an issue.
I'd recommend as well if your having issues w/ vobid/angle demuxes you make sure the quot;pad length on vobid... quot; is enabled for audio and you may wish to try the DGdecode/index option - that helps w/ odd frame issues
Well, I installed Scenarist 3.0 and now it freezes after import - pegging the CPU utilization at 100%. I figured it was still doing something, so I let it go for two hours, still 100% utilization, so I killed it.
Not sure what to do from here. Thanks for the advice about padding the audio - I learned that trick, seems to help those pesky compile errors. I haven't messed around with DGIndex - will give it a try for future builds.
Are there any troubleshooting steps I can take as to why Scenarist doesn't like the script / my assets?
One thing I did notice - there are two tasks called Scenarist in the task manager - both are splitting the CPU processing. Is this normal in 3.0?
well.. with scenarist it could still be doing something
If the CPU is still pegged and memory is changing (or drive space usage) just let it go.... it'll come back to you
I (and with me some others) have had problems with the latest nforce2 drivers. Scenarist seems to vanish, but still uses 100% CPU.
well, maybe I'll let it run overnight and see what happens. VIA chipset here, so it's not the drivers.. thanks |