I have been using now the 8.000.28 trial version of MP8 for a few days, and it seems to be very unstable. Sometime it willrun for an hour, sometime it will crash every few minutes, corrupting project files. This happens mainly when I launch a "Create video file", or when I try to move the preview markin/markout marker using the bars on the Preview window. BUt it happend in a sort of nonconsistent way.
Other times when trying to preview (not in instant mode) or create a video file, will complain that cannot read from file, or that the audio driver is missing. If I close, reopen and regenarte all the temporary files, then it will work.
Some other times I try to select a clip and press tha Canc button in order to delete it, but nothing happens. So I am forced to right click on the clip and explicitly select clear from pop up menu.
The controls cointained in the effect windows, sometime will be out of the window, and force you to enalrge the window to the rieght in order to be able to see them.
Also my all MP5 runs fine (except from time to time).
I run on Windows XP, and I have plenty of software installed on my machine, which includes different VC compilers, which run all just fine.
I think it is a very nice product, with lots of useful features, but overall I have the impression the release is not very stable and ready for thr market yet. A part from small bugs (like the one of the Canc button), as a programmer, the inconsistent way in which the problems show up makes me suspect there are serious problems with the synchronization of threads within the application. I wonder if somebody is eperiencing similar problems.
Best regards,
Fabio
MP8 Unstable?
-
fabiocannizzo
Ops, ignore my previous mail, so many typos it is hard to read it...here a corrected version
I have been using now the 8.000.28 trial version of MP8 for a few days, and it seems to be very unstable and buggy. Sometime it will run for an hour, sometime it will crash every few minutes, most of the times corrupting project files. This happens mainly when I launch a "Create video file", or when I try to move the preview markin/markout marker using the bars on the Preview window. The crashes seems to happen in a sort of non-consistent way.
Other times when trying to preview (not in instant mode) or create a video file, it will complain that cannot read from file, or that some audio driver is missing. If I change the position of markin/markout and run a preview, then it will either stop complaining or crash.
Some other times I try to select a clip and press tha Canc button in order to delete it, but nothing happens. So I am forced to right click on the clip and explicitly select Clear from the pop up menu.
The controls cointained in the effect windows, sometime will be trimmed out of the window (the small preview monitor, for example), depsite there is plenty of room on the left. So I am forced to enalrge the window to the right in order to be able to see them.
I run on Windows XP, and I have plenty of software installed on my machine, which includes different VC++ and VC# compilers, and all of them run just fine. Also my old MP5 runs fine (it crashes from time to time, but it happens so seldom I can live with that).
I think MP8 is a very nice product, with lots of useful features (as the multiple-timeline), but overall I have the impression the release is not very stable and definitely not ready for the market yet. A part from small bugs (like the one of the Canc button), the inconsistent way in which the problems show up makes me suspect there are serious problems with the synchronization of threads within the application.
I wonder if I am the only one eperiencing similar problems!?
Best regards,
Fabio
I have been using now the 8.000.28 trial version of MP8 for a few days, and it seems to be very unstable and buggy. Sometime it will run for an hour, sometime it will crash every few minutes, most of the times corrupting project files. This happens mainly when I launch a "Create video file", or when I try to move the preview markin/markout marker using the bars on the Preview window. The crashes seems to happen in a sort of non-consistent way.
Other times when trying to preview (not in instant mode) or create a video file, it will complain that cannot read from file, or that some audio driver is missing. If I change the position of markin/markout and run a preview, then it will either stop complaining or crash.
Some other times I try to select a clip and press tha Canc button in order to delete it, but nothing happens. So I am forced to right click on the clip and explicitly select Clear from the pop up menu.
The controls cointained in the effect windows, sometime will be trimmed out of the window (the small preview monitor, for example), depsite there is plenty of room on the left. So I am forced to enalrge the window to the right in order to be able to see them.
I run on Windows XP, and I have plenty of software installed on my machine, which includes different VC++ and VC# compilers, and all of them run just fine. Also my old MP5 runs fine (it crashes from time to time, but it happens so seldom I can live with that).
I think MP8 is a very nice product, with lots of useful features (as the multiple-timeline), but overall I have the impression the release is not very stable and definitely not ready for the market yet. A part from small bugs (like the one of the Canc button), the inconsistent way in which the problems show up makes me suspect there are serious problems with the synchronization of threads within the application.
I wonder if I am the only one eperiencing similar problems!?
Best regards,
Fabio
The best advice I can give is to have a dedicated machine for video work. Certainly, the more non-video stuff you have is just one more risk that you are taking. In particular, I recommend NO Internet, NO anti-virus, NO firewall, NO anti-malware, NO spam detection, NO desktop search software, NO anything else that hogs resources etc. You must have every ounce of power available for your video.
If I were you, assuming you do not wish to invest in a dedicated computer, is that you install a dual-boot system, using XP (no SPs, as these all introduce resource hogging de luxe) and you use that just for your video work and NOTHING else.
My MSP8 is stable.
If I were you, assuming you do not wish to invest in a dedicated computer, is that you install a dual-boot system, using XP (no SPs, as these all introduce resource hogging de luxe) and you use that just for your video work and NOTHING else.
My MSP8 is stable.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
-
fabiocannizzo
The trial which I am using is build 28, not 13 (that's what it says in the "About" dialog).
I appreciate Devil's suggestion may indeed help to solve the problem.
Though I have been doing some computationally intensive software development myself in the past. Should I tell my users that they need a dedicate machine to run my app I do not think that would land very well.
Talking about others vendors, the MS VC++ compiler for instance, makes intense use of Ram, disk and CPU, still it does not need a dedicated machine.
Last, I have to say that I have plenty of Ram, and disk space available.
Scarsity of resources is supposed to cause "slow down" of an application, not crashes. If an app cannot cohesxist with other apps, it is faulty.
Best regards,
Fabio
I appreciate Devil's suggestion may indeed help to solve the problem.
Though I have been doing some computationally intensive software development myself in the past. Should I tell my users that they need a dedicate machine to run my app I do not think that would land very well.
Talking about others vendors, the MS VC++ compiler for instance, makes intense use of Ram, disk and CPU, still it does not need a dedicated machine.
Last, I have to say that I have plenty of Ram, and disk space available.
Scarsity of resources is supposed to cause "slow down" of an application, not crashes. If an app cannot cohesxist with other apps, it is faulty.
Best regards,
Fabio
In which case you need to tell that to ALL the NLE software makers AND Microsoft, because, if you scan the forums relative to video, none of them are 100% stable, probably because of DirectX quirks.
Video editing is much more resource-intensive than things like compiling high-level code and, if you don't put everything in your favour, then there is a possibility you will run into trouble. Like most serious video guys, I have a stand-alone video rig and I allow NOTHING on it that is not strictly for video work and I use no SP on XP for it (SP2 is notorious as reducing compatibility with many video items, both hard and soft, and MS have issued numerous updates to try and resolve the problems, only partially successful).
If you buy a Ferrari, you can expect it to require repair more often than a Toyota Corolla, especially if you put poor grade fuel in it.
Video editing is much more resource-intensive than things like compiling high-level code and, if you don't put everything in your favour, then there is a possibility you will run into trouble. Like most serious video guys, I have a stand-alone video rig and I allow NOTHING on it that is not strictly for video work and I use no SP on XP for it (SP2 is notorious as reducing compatibility with many video items, both hard and soft, and MS have issued numerous updates to try and resolve the problems, only partially successful).
If you buy a Ferrari, you can expect it to require repair more often than a Toyota Corolla, especially if you put poor grade fuel in it.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
fabiocannizzo
Hi Devil.
I take your point, and by the way I am not a serious vdeo-editing guy, as you are. I am just an amateur who enjoys playing with home made movies.
Though, I am not very convinced about the directx explaination. I ahve experienced crashes in sistuations where directx should not be involved at all. As a programmer, what I see makes me think more to thread synchronization problems within MP8. Multithreading programming is a very complex thing to implement correctly, and I believe MP8 has some problems there. That's my opinion.
However I admit the fact you are not experiencing problems is a good argument to support your opinion. Otherwise you should experience problems too.
Well, I guess I'll simply stick to MP5 a little bit longer.
I take your point, and by the way I am not a serious vdeo-editing guy, as you are. I am just an amateur who enjoys playing with home made movies.
Though, I am not very convinced about the directx explaination. I ahve experienced crashes in sistuations where directx should not be involved at all. As a programmer, what I see makes me think more to thread synchronization problems within MP8. Multithreading programming is a very complex thing to implement correctly, and I believe MP8 has some problems there. That's my opinion.
However I admit the fact you are not experiencing problems is a good argument to support your opinion. Otherwise you should experience problems too.
Well, I guess I'll simply stick to MP5 a little bit longer.
-
spurrymoses
Hi Fabio,
Yes, I don't want to whinge about it too much because there are many things about MSP8 that really make me happy. And these things outweigh the bad. And I know that this board isn't about just venting frustration but getting help.
However, I do experience a lot of stability problems with the same build you have '28'. And in the same way. So, I'll share.
That is, there are times I go for quite a while without any crashes. Some projects I work on seem to have no problem at all.
The video I'm working at the moment though, where the source video files are many small videos that are 640x480 30fps MJPEG, from a digital camera (maybe this makes it harder...?) I'm lucky to last 20 minutes without a crash. Not just a small crash, but one where my project file was being written to and then crashed, and so the project file was deleted. There were backups of course. But there were times where I gained 10mins of editing, then lost the last 3 minutes, edited for 10, lost another 2 etc.
One interesting thing about many of the crashes lately, is that the Error Message Box will appear while MSP8 is still processing or playing in the background. So I can literally watch MSP8 continue processing even though it has crashed and I know when I press OK, the whole thing will die. This seems to suggest threading problems as you mentioned.
I'd accept all the corresponding points about additional software. I know when I run anything to do with video there's often Invalid Protection Faults with people's well-meaning software. I suspect there's a problem with relying on other people's dll (codecs) to do the processing. And conflicts are always possible.
But as you suggest some crashes are almost certainly due to MSP8 all it's own - like crashing in the middle of writing a project file and then losing it. I believe it would be possible to code this so that the file is never mistakenly deleted.
My limited experience then suggests that MSP8 may have problems with file formats other than DV and/or when there are many files rather than a few big ones. If this helps, so be it
Yes, I don't want to whinge about it too much because there are many things about MSP8 that really make me happy. And these things outweigh the bad. And I know that this board isn't about just venting frustration but getting help.
However, I do experience a lot of stability problems with the same build you have '28'. And in the same way. So, I'll share.
That is, there are times I go for quite a while without any crashes. Some projects I work on seem to have no problem at all.
The video I'm working at the moment though, where the source video files are many small videos that are 640x480 30fps MJPEG, from a digital camera (maybe this makes it harder...?) I'm lucky to last 20 minutes without a crash. Not just a small crash, but one where my project file was being written to and then crashed, and so the project file was deleted. There were backups of course. But there were times where I gained 10mins of editing, then lost the last 3 minutes, edited for 10, lost another 2 etc.
One interesting thing about many of the crashes lately, is that the Error Message Box will appear while MSP8 is still processing or playing in the background. So I can literally watch MSP8 continue processing even though it has crashed and I know when I press OK, the whole thing will die. This seems to suggest threading problems as you mentioned.
I'd accept all the corresponding points about additional software. I know when I run anything to do with video there's often Invalid Protection Faults with people's well-meaning software. I suspect there's a problem with relying on other people's dll (codecs) to do the processing. And conflicts are always possible.
But as you suggest some crashes are almost certainly due to MSP8 all it's own - like crashing in the middle of writing a project file and then losing it. I believe it would be possible to code this so that the file is never mistakenly deleted.
My limited experience then suggests that MSP8 may have problems with file formats other than DV and/or when there are many files rather than a few big ones. If this helps, so be it
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
I edit and/or export DV, HDV, MPEG-2, MJPeg, MJpeg2000, DivX, YUY2, RGB24, *.tga image sequences and a few other formats. Hmmm.......
The companies that make other editing programs recommend they be run on dedicated systems, or at the very least on a dualboot machine with minimal other software installed. This is almost a given in the video editing world given the complexity of the software, which is greater than a C++ compiler
Why you may ask is this so critical? Because editing on a general purpose system means all the backwater trash they accumulate comes along for the ride; TSR's, un-necessary processes etc. etc. Ex: iPodService.exe, iTunesHelper.exe, virus checkers, firewalls etc. etc. etc. Other useful things to do include not using indexing, turning off disc compression, turning off system sounds, not installing the toys that come with your audio and video cards, various internet plugins and other such resource eaters. The list is not short.
Other editing specific Windows optimizations are also recommended by most software companies and editing sites, many of which are not compatable with general purpose computing....ergo a dedicated bootup. Otherwise tracking down problems is a task best left to a Shaman.
My rigs get a WinXP SP2 install with the minimal hardware drivers, fully updated Dx and Windows Media plus my editing, animation and image editing software.....PERIOD.
Once installed to the second boot of a dualboot the whole thing gets Ghosted, just in case something messes it up. Same happens before I install any patches to ANY of the programs. Yes, this takes a dedicated backup HDD, which in my case is an external USB2 drive.
The companies that make other editing programs recommend they be run on dedicated systems, or at the very least on a dualboot machine with minimal other software installed. This is almost a given in the video editing world given the complexity of the software, which is greater than a C++ compiler
Why you may ask is this so critical? Because editing on a general purpose system means all the backwater trash they accumulate comes along for the ride; TSR's, un-necessary processes etc. etc. Ex: iPodService.exe, iTunesHelper.exe, virus checkers, firewalls etc. etc. etc. Other useful things to do include not using indexing, turning off disc compression, turning off system sounds, not installing the toys that come with your audio and video cards, various internet plugins and other such resource eaters. The list is not short.
Other editing specific Windows optimizations are also recommended by most software companies and editing sites, many of which are not compatable with general purpose computing....ergo a dedicated bootup. Otherwise tracking down problems is a task best left to a Shaman.
My rigs get a WinXP SP2 install with the minimal hardware drivers, fully updated Dx and Windows Media plus my editing, animation and image editing software.....PERIOD.
Once installed to the second boot of a dualboot the whole thing gets Ghosted, just in case something messes it up. Same happens before I install any patches to ANY of the programs. Yes, this takes a dedicated backup HDD, which in my case is an external USB2 drive.
Terry Stetler
-
Mischa Faverey
Fabio
I experienced the same. I found out that MSP crashes after i switched from preview in instant mode to preview on external device such as monitor or DV cam. To prevent MSP from crashing you need to switch to the desired preview mode, than save your work and than start the actual preview. If you don't, windows will display the message that MSP caused an error and will be shut down etc etc etc.fabiocannizzo wrote: I have been using now the 8.000.28 trial version of MP8 for a few days, and it seems to be very unstable and buggy. Sometime it will run for an hour, sometime it will crash every few minutes, most of the times corrupting project files. This happens mainly when I launch a "Create video file", or when I try to move the preview markin/markout marker using the bars on the Preview window. The crashes seems to happen in a sort of non-consistent way.
If you check the link to the reports, windows dispays the message that the error was caused by some program named appcompat. That's all i can tell you. I would very much like to know what I can do about this 'appcompat'-thing. As mentioned before in the topic from Fabio the error comes in a very inconsistent way. I too can edit for almost a whole day without any problems but than suddenly the errors come one after another. I also tried cleaning the temp folders wich msp uses for preview. And sometimes I just select All on my timeline and copy ecerything to a new file, saving it, overwriting the old one or even renaming the new file.I experienced the same problem testing the trial version 7 before i decided to purchase MSP 8.
My machine is fully dedicated to video editing. No other stuff runs on this machine. I always ran MSP or Studio 9 or canopus software on this computer. There were no problems at all untill this popped up.
Mischa
Yes a dedicated editing machine would help the cause out alot. I just completed two chapters on my new 'dedicated' machine (pentium dual core 3.0 ghz / 1 gig ram) and I had only 1 crash in about 14 hours of HDV work.
On my previous semi dedicated system (amd 3.4ghz / 2 gigs ram), which had a game or here on it / word / excel / surfed the internet from time to time, the crashes were every 2 to 5 hours. Again this is with HDV. With this system and working with standard DV, I have yet to encounter a crash.
I'm not expert, but just from my experience, you need to keep your system as dedicated as possible because the computer really chugs along and does alot of processing and who knows what program (running in the background or not) on the computer will cause msp8 to crash.
It's great software and I love it. Just waiting for more of those SC templates!
On my previous semi dedicated system (amd 3.4ghz / 2 gigs ram), which had a game or here on it / word / excel / surfed the internet from time to time, the crashes were every 2 to 5 hours. Again this is with HDV. With this system and working with standard DV, I have yet to encounter a crash.
I'm not expert, but just from my experience, you need to keep your system as dedicated as possible because the computer really chugs along and does alot of processing and who knows what program (running in the background or not) on the computer will cause msp8 to crash.
It's great software and I love it. Just waiting for more of those SC templates!
The question is not if compilers or video software are simpler. Compilers may be even more complicated, but compilers are more standalone, more independent of other programms. Most video software uses directx for doing the job. So directx decides which drivers / modules / converters / codecs to load and to use.
The advantage of this is, that you are relative free to select your comcorder, videoboard, firewire interface, graphic card, monitor and so on. You need only from every manufactor a suitable driver (codec ...).
The disadvantage however is, that if there is any bad behaving component in your system, your video eding software may crash, even if it self does not contain bugs.
Therefore it will even not help to have a dedicated pc for video eding!!!! Because you will even then have components from more than one manufactor on that pc. And most probably you would like to have more than one image / video / audio / dvd / burning programm on that pc.
Example:
With the magzine ct special Digital-Video comes a DVD with some software, among that the tool "abcAVI tag editor". If you install that MSP8 will crash, if you try to edit an avi file, even when this programm is not running. Since I am myself a developer it was relativly easy for me to see why. abcAVI had installed an avi filter, which got loaded from MSP by directx. Obviously this tool is bad programmed and caused segmentation violations. As a normal user you wont see that it is abcAVI, instead windows tells you that MSP had a problem... To say even something good about abcAVI: it has a good deinstaller, so it is easy to get rid of it.
So the only thing that helps is to select the components you use carefully.
More to the stability of MSP8:
If you create a project with MSP8, use AVI format for your files and for eding, it is very stable.
IF you convert a MSP7 project, there is a 50/50 chance that it will crash. A crash seems to be shure if there need files to be relinked. So relink them first with MSP7 and try again. But I had also a (avi) project which worked very fine with MSP7 and in SP8 it was enough to scroll back in the timeline after loading the project to crash MSP8.
Eding mpeg files / projects it is not so stabil, but it seems better for me than MSP7. IF it crashes, it crashes most often if you scrub backward. I think it has problems finding the previous I-frame. I experienced such problems with mpeg files, which used much higher data rates than they should. So the guildy part is probably not MSP but the encoder I used. On the other hand windows media player had no problems to play them.
(I solved the problem converting the files with tmpgenc to avi (which was not possible with MSP).)
I am not a friend of workarounds and I prefer a good and stabil software. I often wonder how patient some users are, if I read topics in newsgroups of some other companies. But if it is easy to avoid some minor bugs, then I can live with them. E.g. I knew at leased one method to surely crash dws2 or video capture8, but I simply dont do it.
The advantage of this is, that you are relative free to select your comcorder, videoboard, firewire interface, graphic card, monitor and so on. You need only from every manufactor a suitable driver (codec ...).
The disadvantage however is, that if there is any bad behaving component in your system, your video eding software may crash, even if it self does not contain bugs.
Therefore it will even not help to have a dedicated pc for video eding!!!! Because you will even then have components from more than one manufactor on that pc. And most probably you would like to have more than one image / video / audio / dvd / burning programm on that pc.
Example:
With the magzine ct special Digital-Video comes a DVD with some software, among that the tool "abcAVI tag editor". If you install that MSP8 will crash, if you try to edit an avi file, even when this programm is not running. Since I am myself a developer it was relativly easy for me to see why. abcAVI had installed an avi filter, which got loaded from MSP by directx. Obviously this tool is bad programmed and caused segmentation violations. As a normal user you wont see that it is abcAVI, instead windows tells you that MSP had a problem... To say even something good about abcAVI: it has a good deinstaller, so it is easy to get rid of it.
So the only thing that helps is to select the components you use carefully.
More to the stability of MSP8:
If you create a project with MSP8, use AVI format for your files and for eding, it is very stable.
IF you convert a MSP7 project, there is a 50/50 chance that it will crash. A crash seems to be shure if there need files to be relinked. So relink them first with MSP7 and try again. But I had also a (avi) project which worked very fine with MSP7 and in SP8 it was enough to scroll back in the timeline after loading the project to crash MSP8.
Eding mpeg files / projects it is not so stabil, but it seems better for me than MSP7. IF it crashes, it crashes most often if you scrub backward. I think it has problems finding the previous I-frame. I experienced such problems with mpeg files, which used much higher data rates than they should. So the guildy part is probably not MSP but the encoder I used. On the other hand windows media player had no problems to play them.
(I solved the problem converting the files with tmpgenc to avi (which was not possible with MSP).)
I am not a friend of workarounds and I prefer a good and stabil software. I often wonder how patient some users are, if I read topics in newsgroups of some other companies. But if it is easy to avoid some minor bugs, then I can live with them. E.g. I knew at leased one method to surely crash dws2 or video capture8, but I simply dont do it.
-
Mischa Faverey
thnx for the explanation. I had already figured that it is not the machine or my editing software. although it won't get me 100% security I will try not to install anything else than my editingsuite on this machine. I have plenty of other computers running in my studio where I can install other stuff like burning programs, audio-editing, etc. Your message sureley helps understanding the behaviour of windows-based machines. The ultimate thing for me to do now is to setup both Apple machines I just bought and then switch to non-windows software. I've had it up to here with windows and the software that's been developed for windows but that gives me so much headache.
Mischa
Mischa
Using MAC you wont be attempted so much to install freeware or shareware (I dont even kow if such exists for the MAC), but you could avoid to install this also on a pc.
If you go really so far to run each programm on its own pc, than you will even with window have no or very few problems, but you will instead have a lot of network traffic
If you go really so far to run each programm on its own pc, than you will even with window have no or very few problems, but you will instead have a lot of network traffic
-
spurrymoses
Recently I created a batch file (see printout below) which I ran just before starting MSP8. At that time, I found it did not help at all with the stability of the program.
net stop "AVG7 Alert Manager Server"
net stop "AVG7 Update Service"
net stop "Securepoint Personal Firewall"
net stop "Automatic Updates"
net stop "Windows Time"
net stop "Help and Support"
net stop "IPodService"
net stop "Computer Browser"
net stop "Cryptographic Services"
net stop "SQL Server (SQLEXPRESS)"
net stop "SSDP Discovery Service"
net stop "Task Scheduler"
taskkill /IM e_s4i3t1.exe /T /F
taskkill /IM RegKillTray.exe /T /F
taskkill /IM avgcc.exe /T /F
And of course, I disconnected from the internet.
What I have found recently, though, is that using Keyboard shortcuts instead of the mouse possibly bypasses some of the threading problems and crashes that usually go on. Which might also explain why the more experienced users in this forum don't seem to have as many problems. I haven't had a crash in a while and one difference has been that I'm not clicking the mouse much at all. Especially when doing things like previewing and then trying to stop the preview and then trying to click on a clip in the timeline... all without waiting for the program to catch up. In the past, just clicking around quickly on different windows like this was a sure-fire way to crash the program for me.
I can't substantiate this, but I will make an effort to test this theory more extensively later on. But for now, I'm going to avoid using the mouse for productivity as well as stability.
net stop "AVG7 Alert Manager Server"
net stop "AVG7 Update Service"
net stop "Securepoint Personal Firewall"
net stop "Automatic Updates"
net stop "Windows Time"
net stop "Help and Support"
net stop "IPodService"
net stop "Computer Browser"
net stop "Cryptographic Services"
net stop "SQL Server (SQLEXPRESS)"
net stop "SSDP Discovery Service"
net stop "Task Scheduler"
taskkill /IM e_s4i3t1.exe /T /F
taskkill /IM RegKillTray.exe /T /F
taskkill /IM avgcc.exe /T /F
And of course, I disconnected from the internet.
What I have found recently, though, is that using Keyboard shortcuts instead of the mouse possibly bypasses some of the threading problems and crashes that usually go on. Which might also explain why the more experienced users in this forum don't seem to have as many problems. I haven't had a crash in a while and one difference has been that I'm not clicking the mouse much at all. Especially when doing things like previewing and then trying to stop the preview and then trying to click on a clip in the timeline... all without waiting for the program to catch up. In the past, just clicking around quickly on different windows like this was a sure-fire way to crash the program for me.
I can't substantiate this, but I will make an effort to test this theory more extensively later on. But for now, I'm going to avoid using the mouse for productivity as well as stability.