miroVideo 300DV?

Grazie wrote on 9/25/2002, 10:41 AM
When I look at the properties of a clip, in the Media Pool, the format is in miroVIDEO 300DV. This is a Pinnacle format. How do I get a captured clip to "stay" as the DV AVI format I need? What do others see their Formats as being? - Yes I can render clips as AVI, but are they again in this miroVIDEO 300DV fomat?

Grazie

Comments

Chienworks wrote on 9/26/2002, 2:45 AM
Most likely the miro codec was the most recent software to "mangle" your registry and file type associations. The file you've rendered is a standard DV .avi file, but miro has told Windows to report such files as belonging to itself. It's not really a problem; it's just the name itself being shown that seems confusing. Probably the only way around it would be to reinstall the Microsoft DV codec. But in the meantime it shouldn't affect anything other than the name you see in properties.
Grazie wrote on 9/26/2002, 5:39 AM
Chienworks - thanks for the that! yeah, all my Media Pool icons are now blessed with the "Apple" quicktime icon, instead of the usual icon.

On another matter, I seem to have got a mixed set of ASPI drivers. As you know I'm running WinME, so I need to reinstall the correct set. I once got a Canopus set. Any other suggestions? It appears I've got the Win95 set! Could this be impeding my PTT?

Here's the "Report Log"

ASPICHK0438: OS = Windows 95 (4.90.3000)
UPGRADE1004: c:\windows\system\wnaspi32.dll dated 12/10/2001 16:32:56, 45056 bytes.
UPGRADE1062: c:\windows\system\wnaspi32.dll version 4.6.0.1021
UPGRADE1004: c:\windows\system\winaspi.dll dated 05/10/1999 11:06:00, 5600 bytes.
UPGRADE1062: c:\windows\system\winaspi.dll version 4.6.0.1019
UPGRADE1004: c:\windows\system\iosubsys\apix.vxd dated 12/10/2001 16:28:58, 22603 bytes.
UPGRADE1062: c:\windows\system\iosubsys\apix.vxd version 4.6.0.1021
UPGRADE1004: c:\windows\system\aspienum.vxd dated 05/10/1999 11:06:00, 7743 bytes.
UPGRADE1062: c:\windows\system\aspienum.vxd version 4.6.0.1019
ASPICHK0522: Inconsistent version numbers among components
ASPICHK0592: ASPI installation has problems

As always,

Regards

Grazie
randy-stewart wrote on 9/26/2002, 11:40 AM
Grazie,
This from a previous post may help:
*************
Grazie,
The correct link (http://aspi.radified.com/) takes you to a web site that tells all about the ASPI issue (sorry, I pasted in the e-mail web link that I sent to myself before which wouldn't work here). Go down to the ASPI section. It recommends a couple of options to fix the problem. The one I chose was to download the force ASPI software that replaces the 4.60 (1021) version files on my Windows ME system. To get the software, I had to go to the Cryus.troy site (it's a link on the web page above) and follow the directions to download the force ASPI program files. It takes about 10 seconds to download (I saved it to the desktop). Then I clicked on the folder and got a message that asks me to unzip the files and did I want to do that now. I said yes, then, after it unzipped, I opened the new folder and clicked on the install program (can't remember the full name but it has the word instal in it), ran the program, and voala, a DOS box came up, and installed the files I needed, and after reboot, it worked fine. I know this is a little bit involved but it fixed my problem. Check out the web site (just copy the address into your URL area up top (after you delete the current one, and hit go) as it has all the info needed. Hope you can get it to work.
Randy
JohnnyRoy wrote on 9/28/2002, 11:08 AM
Grazie,

The information you see in the properties of a clip is based on its fourCC code. This is a four-letter code (hence the name) that is imbedded in the header of the video file. For DV the fourCC is DVSD. If you look in your system.ini file in the [drivers32] stanza, you’ll see a bunch of entries that start with VIDC. These are the DLL’s for the video codecs registered to your system. If you find VIDC.DVSD= you will find the name of the DLL that will handle files requiring this codec.

To change it, just comment it out with a semi-colon (;) and make a new VIDC.DVSD= entry with the DLL you want to handle DV files. I don’t know which one is the Microsoft codec because I use the Panasonic DV codec as the default on my system because the Pinnacle miro codec will only decode and I couldn’t encode with it in any non-Pinnacle software. Perhaps someone else can append what theirs says for the MS DV codec.

Anyway, this is a lot faster than reinstalling software.

~jr