Since scorefitter is part of the original plus installation, run the install disk and there will be a menu item for 'repair install'.

The repair may revert  you back to ver 12. If so, you'll have to update to 12.1 again.

This is not supposed to cause any loss of data.

Don

Yes Don, that's correct. You will need to run the repair for Studio 12 plus. It's also possible that the problem is from corrupted music.

No This changed nothing. I have always had the impession that the problem is limited to edit mode and I ran the full project (including the scorefitter music) through make file . No problems the file came out just as expected including the music

so it is not a coruption in the input data but somehow a conflict created by studio among the device drivers. I have just updated the screen driver to the latest verson. Devices are as listed in the profile.

 

You mentioned that it hangs. Does it hang on a specific part of your workflow? Do you have any videos in the preview at the time of the hang?

just a short reminder the most reproducible hang just now is :

open the demo project (our nature adventure)

wait until all activity has settled down (rendering etc)

press play and the system is hung

if I delete the score fitter tune at the beginning play works OK

(also note that even if I leave the scorefitter tune in place rendering to a file works fine)

other activities in the demo project, like double clicking on some video scenes can also make it hang, but the play is 100%reproducible

 

Please provide me you're system's MSinfo for further inspection.

MSinfo appended

 

MSinfo files appended

BUT i found something, I have always thought the problem lay on the input side (the error is in disk drivers and it was coupled to large numbers of pictures when I first saw it)

Therefore I never tested the one problem swithh in Studio ,background rendering, I Apologise

turning this off eliminated the problem in both S12 and S14.

Not that I want to run with background rendering of, one loses a lort of time that way, but studio works and i will do so for the present

if you find anything that can be the cause of the conflict I would love to hear it

Lars

 

msinfo part 1

msinfo part 2

Thank you for the files. I'll also note down your findings.

Computers are wierd (I still say so after working with them for 40 years)

What I said before is true , sett background compilation off mekes edit wwork in many places, and it makes the Play button in MyNatureAdventure work

but it does not inhibit all cases of the hangs, even in the demo project it is possible to hang when editing.

I also have a 2 hour project that apperently worked fine before as I have managed to edit int into shape but which now hangs frequently andreproducibly in both S12 and S14. Can installing S14 have changed anything in S12 ?

I also have a funny edit picture (in S12) but I am describing that in another  tread so as not to draw to many red herrings in this one

 

I think the problem is eliminated (not solved!!)

 

Marc thanks you for your patience and support .

Resolution:

Some time ago I tried to spread diskaccesses as much as possible and moved Studios render files over to my scratch disk (the 1TB disk listed in the MSinfo)

This must have been when the problems started. I connected the problems with the project I was working on at the time, with the large number of photos and so I happened to concentrate on the input side.

Note that there is nothing wrong with the disk, I have run chkdisk on all disks , there are applications using the disk, there is an secondary paging file on the disk. No problems. In fact whenever I compile a DVD from Studio I use that disk for the DVD image, so Studio has no real problems using it. But somehow the renderroutines do not like it.

I moved the render files over to another disk (the E: in the MSINFO) and all problems are gone !!

I think that the crashes in studio have led to some corruptions in studio files so I deinstalled all studio material and reinstalled it. This I however did before moving the render files ( I had not thought of that yet then) and it produced no change, not until I moved the temp files did the problem go away

So somehow the combination of the 1TB disk + rendering leads to the hangs in the disk driver.

I think all the problems mentioned in the other chain “funny editing” also are solved with these two activities.

And yes it applies to both S12 and S14 after moving the render files

Just lets hope that this is the final conclusion

 

 

Again something seems to be premature but I cannot understand it

I tersted OurNatureAdventure after redirecting the temp files , worked fine, I have worked all day on some of my most "hangable" projects, no problems, but when I now open OurNatureAdventure  and press play it hangs

life is never easy !

BUT and I have seen this before, if I delete temp files for ALL projects it wokrs fine again. How does this differ from delete for THIS project whne I am in a project, i.e. is there some overflow from one project to another in the helpfiles ?

 

That makes hardly makes any sense. What is it with this scratch disc that's causing this problem? Thanks for the further input once again.

I have no idea what could be the disc problemunless the render  routines have problem i handling such a large disc ? Maybe a timing issue ?

any one have any knowledge of a test program that can test several disks at once to look for possible interaction problems on the disc bus

That's a good question. I've stumbled upon something interesting. Maybe you can check it on your machine.

Yes the problem here is if an istallation or a program does not follow windows principles and intalls or writes to a hard name not a logical one. But I see no such problems in my system. And I am not (at least not now) going to reinstall all of studio to test it !

I do think thereis some kind of overspill between projects. I have noted several times that deleting temp files in this project might not save problems wereas deleting all might. I did some testing as shown below. I stopped all extra processes (msconfig) and rebooted to have a clean system and then timed how long it took to 1)start Studio  (from double click on icon until all activity had settled down) and then how long it took to load ourNatureAdventure. the one or two hangs produced on the way I did not include (yes I do get tem but so infrequent that I can work.) All timings were repeated at least 3 times

                                                                                             to start studio                           to load ONA 

OurNatureAdventure + one large project compiled                         50s                                                 10s

having deleted all temp except current project (ONA)                     30s                                               5s

having deleted all temp files                                                          25s                                                   5s

you see two things from this.

1) when Studio starts it looks at the available helpfiles, time goes from 50 s to 25 s when they are deleted

2)when opening ONA the time is influenced by the fact thet there is another project in the help files, time goes from 10 to 5 s

I believe if this opening hits a corrupt help file it can lead to problems in current project.

 

Good findings, I appreciate the nice table you made to show the difference. I'll continue to look around.

This is just to report a happy end and close this threat

yes it was a hardware error. When finally tracked down and the mother board was replaced things came back to normal . All now works including the large scratch disk.

The error was in the disk controller and only happened whan simultaneous requests were issued to several disks. This is very difficult to test with standard windows tools as most of them serialise the testing so much that the error does not show up. If any one wants the information there is a program called HD Tune that can be run in multiple instances , one for each disk. This will create the needed disk accesses.

apperently Studio is one of the few programs on my machine that can create sufficiently simultaneous requests to the disk to provoke the problem. I have had rare random hangs with other software but Studio "always "hung.

so all is well that ends well. Thanks for all the help i have had during this rather difficult period

and a Merry Christmas and a Happy New year to all of you

 

Thanks for the update LarsP.