Scenarist crashing problem

[DIggedy]

At the moment I'm reauthoring the r3 dts version of Monsters Inc in Scenarist 2.5. All the authoring is complete, but now my problem is when I tell Scenarist to create the layout ready for burning the program crashes instantly! I have not reencoded any files, just created my own menus which are legal ntsc resolution...
Also strangely when I run a simulation, selecting one of the video s I can hear the audio (except for dts of course) but do not see any image, but when I press stop the frame I stopped on appears as a still.
I noticed the HD I'm storing the video on was VERY fragmented, but after defragmenting I still get the same problem. Could my rips be corrupted because of this?

[Navellint]

it is always recommended by ripping tools and authoring progs to keep your hd defragmented or even use physically use another hd for OS and another for media (not just partitions), but i don't think that's the problem.

I think you'll have to give some info about the pc you're working on. I worked on an 1800+/XP/online/scenarist and a p550/2k/online/scenarist and they both crashed constantly and the scenarios vanished completely... At home i use p450/2k/scenarist/offline that doesn't nag. It has a udma66 maxtor 30 GB (for OS) and a udma100 western digital 80 GB (for content), both on one udma66 controller. I still don't know what the hell is the matter with the other two workstations.

[DIggedy]

Thanks for the reply. The system I'm using is pretty old now, it's a P!!! 800 running Win2K. The main HD is just a 7200rpm IDE drive (partitioned to 2x40Gig). I store the completed layouts on an external Firewire disc (7200rpm 80gig) which I take to work to burn the discs on my G4 Mac there.

[Arky]

I'm just curious - have you by any chance deleted any of the ".vif" files which were created when Scenarist imported your source files and parsed them..? They should be of exactly the same name (except for the file extension, of course) as the source file, in each individual case, and in exactly the same directory as the source file, in each individual case.


Arky ;o)

[Navellint]

arky:
ahum, i guess i did delete some of them files :( so that causes the crashes? Even if i move/rename certain directories/clips/sounds?

-------------------------------
p3-450, abit-be6 100 MHz fsb, 192 MB sdram, tnt2 ultra, 2x udma33, 2x highpoint udma66 controller, maxtor 30 GB 7200 rpm udma66, 80 GB wd 7200 rpm udma100, realtek pci ethernet 100mbit, 56k modem, sb pci128, tv-card, toshiba dvd-rom sd-m1212 rpc1, philips dvd+rw 228k f/w 1.36 rpc1, zip,
w2k, scenarist 2.6, netscape 7.0 phew

[Arky]

Well there's a simple way to find out - just create a brand new Scenario and import the identical files (from the identical directory), then, when Scenarist has parsed the imported files, exit the new scenario and return to the original scenario as though nothing had ever happened, and see if your problem is solved!

If it IS solved, then great - if it isn't, then fine, just repost and we'll try and work out another possible solution. I'll do my level best to help you.


Arky ;o)


As a general rule, you must never delete parsing files until your project is finished, and, likewise, you must never move or rename any asset, or that asset's path/directories, because Scenarist / Maestro will then be unable to use those assets when compiling the project. In fact, in the majority of cases, it won't even be possible to continue authoring unless the renaming/deletion is rectified. It's pretty logical really. Whenever I begin authoring a project, I first create a directory with the name of my project and place all my assets in that directory, to be left there for the entire duration of my project, and only moved/renamed or deleted after I have finished authoring and compiling/burning.

[Arky]

How did you get on, DIggedy?

I hope you got the problem sorted in the end..


Arky ;o)

[DIggedy]

Hi Arky, I've actually been away from home for over a week and won't be back until next week to try... I'm pretty sure I wouldn't have touched the vif files but may have by accident and not noticed. Anyway I will check it out when I get back and see how it goes.
Thanks for the help guys.

[DIggedy]

sorry, double post.... gotta stop hitting the back button :rolleyes: