Automate Scenarist hangs

[SlipGun]

Automate Scenarist hangs everytime on "Create New Scenario from Script window found," with at least 3 separate DVDs, using both the ISO and folder methods. I successfully encoded a few menus before, and I'm not sure what's causing this.

I'm using NuMenu4u 2.0.23, avisynth 2.5.6, Scenarist 3.0, pgcdemux 1.2.0.4/Decrypter 3.5.4 and eclPro 0.52 with ProCoder 1.5/2. Have tried reinstalling NuMenu4u, Scenarist and eclPro/ProCoder, but it remains the same. Anyone run into this problem before? I'm hoping there's a simple fix. Thanks.

Update: I did a full uninstall/reinstall of everything, and it worked fine ... for exactly one encode. Have no idea what's up.

[Zeul]

very strange
You can bypass automate if you want by selecting scenarist option 5 (manual use). Basically NuMenu will tell you when to launch scenarist and then will wait unitl you tell it that scenarist either compiled successfully or not.

[SlipGun]

Looks like the problem is that the Scenarist window that's supposed to come up on pressing "Import" never does. It works if I reboot and go straight into Scenarist, but through NuMenu4u I can't get it to work at all.

Update: I went ahead and did a full reinstall of Windows/progs. Everything works like it should now :)

[D3s7]

starting with scenarist 3.0, on startup it scans all devices in your machine (cdrom / dvdrom)

This scan is the cause of most of the automate issues.... if someone has time or knows how, an actual hook into the app might work better then our interface.. I have had this on my list of todo's but haven't got around to it

[SlipGun]

*sigh* Incredible ... it's happening again.

Only thing I did different was start using pgcdemux. Hmm.

I tried downgrading to 2.7, but no go. Wish I'd set a restore point.

[SlipGun]

Looks like the nVidia nForce IDE SW driver is to blame.

Install driver, window never shows up. Uninstall driver, problem solved.

[Zeul]

Ths a scenarist problem - well documented. At least Automate is not at fault here. What we would give for scenarist with commandline support.

[Xorcist]

I'm having the same problem using Scenarist 2.7. I'm also using an nVidia Nforce system.

[johnnytaco]

Guys, like a good citizen of forums I've been reading and not posting until proper searches. Which served me well for quite a few years, so first off, thank you all for the information and support.
:thanks:

I had to post this because I spend hours and days reinstalling combinations of XP and drivers on my Nforce3 board recently.:angry: I suspect others have as well.

The option to remove the IDE drivers for me is not an option due to the RAID 0 boot array I use.

I found a working solution that works with the nForce IDE drivers.

I copied 3 files into the C:\Program Files\Sonic\Scenarist directory:
wnaspi32.dll (version 4.71.1.0 - my date stamp read 5/6/2002)
msvcp70.dll (version 7.0.9466.0 - my date stamp reads 6/20/2003)
msvcr70.dll (version 7.0.9466.0 - my date stamp reads 6/20/2003)
(most were found in system32)

I suspect default Scenarist+ASPI+nForce=the problem.

I'm using Scenarist 3.0

Hope this works for you as well! enjoy :)

Lastly, there were many of these types of threads, so I just picked the one with the latest post.. I'll leave it to the admins to figure out how they might want to post this potential solution to the other threads.

[jel]

:goodpost:
thanks johnnytaco for taking the time to post your working solution for this problem. i hope it helps others in a similar position.

i will make a link to this thread in the FAQ sticky

cheers
j

[Xorcist]

:goodpost:

Thanks, this helped. I now got some SCSI error when starting Scenarist, but if I just press OK, everything seems to work fine

[PnoT]

I have tried the aboved mentioned fix and it still does not automate properly for me. I'm using an NFORCE 3 motherboard and find it hangs all the time. I have it setup on another computer and everything works fine.

Anyone else have any ideas?

*UPDATE*

I've went back to scenarist 2.7 and everything works like a charm. I'm not sure what's up with 3 but i'll wait till more information is available and sure fire fix before i try it again.