#RAZOR PRO/PAR users
07-Feb-95 22:04:48
Sb: #151528-#RAZOR PRO/PAR users
Fm: Byron D. Bowles 72732,1172
To: Byron D. Bowles 72732,1172
To all,
This is to follow up on the mildly hostile message directed toward in:sync.
This evening I got a phone call from Jamie Carr and had a long pleasant
conversation. I wanted to set things straight and post answers to the
questions that I asked earlier in this thread.
I explained to him that I come from a development background, and was very
disturbed by the amount of low quality products being "thrown" out on the 3DS
bandwagon. Also, very frustrated that certain manufacturers blame other
manufacturers for their problems. I chose the Autodesk platform because of
their commitment to quality, and I expect the same standards from the 3rd party
manufacturers. He assured me that they are very concerned about quality and
are committed to customer support. He also very thoroughly answered my
questions and was very open to my suggestions. I apologize for my insinuating
and categorizing. I now feel very comfortable that I have invested my money
and trusted my business to an honest and capable company.
So here's what we talked about.
>> When Windows is set up on a machine it automatically sets the virtual
memory to be 2 or 3 times the amount of physical memory. This is a bug. It
should be set to be the same size as the physical memory or a smaller size.
Actually, I don't think it's a bug, but it's apparently not well suited for
real-time video. As you allocate more virtual memory, the overhead of
maintaining it uses more physical memory – to the point of diminishing return.
As we all know, less RAM and more swap is not good. Setting your swap high to
retouch those posters is fine, but don't do it for video!
>> …can you explain to me why I cannot use QEMM in my system anymore.
It seems that there have been problems with QEMM and the PAR software with SCSI
drives. They recommend removing QEMM as a troubleshooting measure. Basically
the answer is – if you've been using QEMM with no problems, then it should be
safe to continue using it. The new version of PAR software should address
these issues.
>> Here's a feature I can't explain. I copied the example CAMERA.BMP file
several times with the program manager (CAMERA2.BMP, CAMERA3.BMP,
CAMERA4.BMP)…
Duh! Razor Pro supports series of files in the BMP and TGA formats. You
cannot stretch out a still when it is part of a series.
>> Is there no way to display the filenames of the objects in the Composition
window?
Currently there is no way to extract the path/filename of a clip that is part
of a project. Once you drag a clip to the Composition window, you have no way
of telling where the source is coming from. The RP manual suggests putting all
clips in a common directory when using and archiving. My argument is if you
have the PAR, a CD-ROM, a tape drive, etc., it may be impossible or undesirable
to put all clips into a common directory on the hard disk. Being able to
extract the file and Library information from the project file helps you to
restore your system to its original configuration. In:sync is very interested
in hearing new suggestions and welcomes any discussion for improvement.
>> sound cards
One of the issues with sound cards is the thermal drift of the crystal
oscillators (because of the excessive heat inside the computer). If the time
base of the sound card drifts, you get into sync problems with the AV. In:sync
recommends Turtle Beach and Roland because these manufacturers are sensitive to
these issues.
—————————
Again, Jamie assures me that this product has been in the works for years, and
the latest version (1.0a) is very solid. If you encounter a problem, they want
to know immediately.
Well I hope this helps ease the mind of all. I wish manufacturers would not
keep us in the dark. Most of us are purdy educated and would be glad to
provide positive feedback if we worked together. [Join hands] We are the
world…(Spiral sweep wipe to Michael with a embossed displacement fade…)
byron
engineering arts