CompuServe Thread

MA>> I currently own a dc1tv card and your software. I have'nt used it much yet though. Hope you will like it. May I ask which our product they bundle with and what version? MA>> My question is what resolution and frame rate are you capturing for your demonstrations. I captured all clips in 320×240 30fps using miro's M-JPEG codec for that demo. Sometimes I capture them in a slightly larger size (328×248) and crop the border out to remove noise at the edge. I use a comercial VHS tape release from our gevernment about Chinese foods as my source. After capturing and editing, I print to video and also capture it to tape. I play the source to compare with my result side by side on two TV sets. I found there is little degration in video quality. But if I play the source and my result alone one by one, nobody can tell which is from the source tape and which is my work. I also found 320×240 30fps clips with "Zoom by 2" option of the Media Player turn on give me similar result on computer monitor for general usage. Most of the time when working on machines without a good M-JPEG board, I create AVI using Cinapak codec because it always gives me good result in playing back. MA>> I have a similar setup to yours (Pentium 90, 16 meg ram, Diamond Stealth 64 video card) and I would like to know what type of hard drives do you use? I encountered lots of problems in using Pentium/60 machines with various boards (including miro DC1 board), we can't even compile programs on them because it will hang. After I switched to Pentium/90, all problems are gone. If you want faster effects and editing, you may consider to add more RAM. If you do capture and play back most of the time with simple editing, then that's more than enough. I use two Micropolis 1.7G AV disks for each machine. There are 3G/4G disk from Micropolis and Seagate are rolling out 2G/4G/9G drives, however, they are too expensive. The 1.7G drive has the best price at that time. MA>> I have a Micropolis 1936av scsi with a future domain pci scsi adapter. I think this is the same disk that I connect to my Adaptec PCI SCSI card. MA>> I have'nt connected all the components yet and I'm wondering if there is anything special I would need to do as far as the scsi drive is concerned. I am also running windows for workgroups. I think you will not have big problems in doing that. Turn disk cache off (and 32-bit file access in WFWG) when you do capturing because it will slow you down in transferring data to your hard disk. If you like, turn disk cache back on when you do editing. If you don't do that, a litte bit more disk access will happen. –Vincent Chen PS: you may encounter this in WfWG 3.11 since you're dealing with big files now. ——————————————————————– The information in this article applies to: – Microsoft Windows for Workgroups version 3.11 ——————————————————————– SYMPTOMS ======== When you try to open or copy a file larger than 2 megabytes (MB), you may receive one of the following error messages: Segment Load Failure -or- Insufficient Memory CAUSE ===== These errors occur if both of the following conditions exist: – You are using a permanent swap file without 32-bit disk access enabled. This causes paging to occur through MS-DOS. -and- – You are using 32-bit file access. Since 32-bit disk access is disabled, the real-mode mapper (RMM.D32) is used to provide 32-bit file services. These errors do not occur if the permanent swap file is on a drive with 32-bit disk access enabled or if 32-bit file access is disabled. WORKAROUND ========== To work around these errors do one of the following: – If your hard disk controller is WD1003 compatible, enable 32-bit disk access. -or- – Disable 32-bit file access. STATUS ====== Microsoft has confirmed this to be a problem in Microsoft Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Bases as it becomes available. MORE INFORMATION ================ This size of the file needed to trigger this error is not always 2 MB. The limit is 512 multiplied by the size of the allocation unit for the drive where the target file resides. The allocation unit size is commonly 4096 bytes, thus the apparent 2 MB limit. In cases in which the allocation unit size is different, the limit is also different. Additional reference words: kbhw 3.11 wfw wfwg errors out of memory vfat fastdisk incompatible incompatibility doesn't work not working ============================================================================= Copyright Microsoft Corporation 1994.