CompuServe Messages

Byron, As I explained on the phone, those problems that people are having are generally not bugs but related to people's memory configurations. I will attempt to restate the position so that its clear. When Microsoft came up with the virtual memory scheme it was not thinking about the demands of working with video and audio files because these weren't implemented at that time. Virtual memory is a great concept for handling large files where you only have to access parts of the file occasionally. A classic for instance is the case where you want to load a large still image. The machine can't handle the while thing so it pages out the file to disk until it needs it. With video and audio files it's different. The program needs access to all parts of the files all the time. When we show the filmstrips of the video on the Composition window we are displaying parts of file from the whole sequence of frames. Unfortunately this is where the memory scheme breaks down because we need to access extremely quickly lots of different parts of the file at the same time to get the video and audio information. In order to speed this process up incredibly we require 20 MB RAM. We used to work in 16 MB RAM but with the new upgrade this has now broken that barrier unfortunately. With this much RAM we can do lots of things really quickly. However this is where the virtual memory scheme gets in the way. If you have a swap file which is larger than your physical RAM then Windows thinks its OK to use your RAM in order to create your huge swap file. But with RAZOR PRO thats a NO-NO because then the program and the compressors don't have enough room to operate. I hope this answers your question as to why we recommend the size of the swap file that we do. We don't think that QEMM 7.5 doesn't work – we just think that if you have an earlier version you should upgrade to the latest version and then you won't have any problems. I explained over the phone about the camera*.bmp problem. When you load the image and it has a number at the end it knows that its in a sequence and so treats that file as being part of that sequence. If you have any other questions please let me know. Jamie Carr in:sync