Re: [PD] CRAZY! mcdvd_32.dll
matteo sisti sette wrote: Hi, I have a project that I made with an old version of GEM under Windows, namely a 0.90 compiled on August 3 2004 (a precompiled binary I downloaded from iem.at or somewhere). At that time, I had many difficulties in finding a version that wouldn't crash AND that supported dv-pal; however I did find it and the project has always worked fine. In this project I used dv-pal-encoded AVI files and I'm not sure whether that version of GEM uses Quicktime or Directshow to open them, but I think directshow (apparently supports both). Currently, for other projects, I usually use a more recent and stable version of GEM (still not the latest), but I had some troubles trying to upgrade this project to the new version; so, since it just works fine, I always run it with its own dedicated version of GEM, that of 2004. I have run it in a few machines without problems, but now I have copied it into another machine and it crashes. The funny thing is that the module that crashes is mcdvd_32.dll that is found in windows/system32, but on the machine where gem does not crash I don't even have that dll anywhere [snip] So what is mcdvd_32.dll? MainConcept DV Codec according to http://www.softwaretipsandtricks.com/dll/14693-Mcdvd_32dll.html Why is gem using this dll, if the same gem on another machine is not using it (it isn't even present in that machine)? How can I force him not to use it? I am not sure, but try moving the dll out of the way, if you have qcap.dll in the same folder, according to http://forum.doom9.org/archive/index.php/t-1.html HTH, Thomas -- Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance. (Leto II. in: Frank Herbert, God Emperor of Dune) http://thomas.dergrossebruder.org/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] CRAZY! mcdvd_32.dll
Hi, I have a project that I made with an old version of GEM under Windows, namely a 0.90 compiled on August 3 2004 (a precompiled binary I downloaded from iem.at or somewhere). At that time, I had many difficulties in finding a version that wouldn't crash AND that supported dv-pal; however I did find it and the project has always worked fine. In this project I used dv-pal-encoded AVI files and I'm not sure whether that version of GEM uses Quicktime or Directshow to open them, but I think directshow (apparently supports both). Currently, for other projects, I usually use a more recent and stable version of GEM (still not the latest), but I had some troubles trying to upgrade this project to the new version; so, since it just works fine, I always run it with its own dedicated version of GEM, that of 2004. I have run it in a few machines without problems, but now I have copied it into another machine and it crashes. The funny thing is that the module that crashes is mcdvd_32.dll that is found in windows/system32, but on the machine where gem does not crash I don't even have that dll anywhere The pd executable and gem.dll running in the 2 machines are the same: the whole pd folder is the same on the two machines. Obviously the patches are the same, and also the video files. There should be apparently no difference in what I am running. Both machines have Quicktime and DirectShow installed. The info GEM prints out at startup is the same on both machines: GEM: ver: 0.90 GEM: compiled: Aug 3 2004 [...] pix_film: avi support pix_film: quicktime support In the machine that works, for every video file it loads, it prints the message new movie might crash... ...survived While in the machine that crashes, it DOESN't print those messages!! It crashes when I create the gemwin (NOT when loading files). So what is mcdvd_32.dll? Why is gem using this dll, if the same gem on another machine is not using it (it isn't even present in that machine)? How can I force him not to use it? Is it possible that for some reason the working one is using DirectShow while the crashing one is using QuickTime? Or viceversa? Why? If I try to upgrade to the version of GEM that I usually use, the problem is that dv-pal avi's are rendered at 1/4 resolution, and I don't know how to tell quicktime to render them at full quality. I usually use mov's, so that I can put the high quality flag into them with QuickTime Pro; but there's no such flag in avi files, and I'd like to avoid converting all files to mov, it would take ages! -- Matteo Sisti Sette [EMAIL PROTECTED] http://www.matteosistisette.com ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] CRAZY! mcdvd_32.dll
So what is mcdvd_32.dll? MainConcept DV Codec according to Yeah sorry, it was kinda stupid of me to ask that question to the list rather than to google. I am not sure, but try moving the dll out of the way, I removed it and it work. It wasn't easy though; I tried to uninstall it politely in the video codecs panel of Windows' Device Manager... but it just wouldn't disappear. So I deleted it manually, and even if according to Windows it is still in the codecs list, GEM now works fine. At first I thought the file was magically regenerating itself, since after deleting it it and searching it would still be found... but then I realized it was found in the Trash. Thanks m. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] CRAZY! mcdvd_32.dll
I recall having problems with some of the commercial DV and JPEG codecs on Windows. A lot of these are legacy VfW codecs and not DirectShow filters and they seem to be written to work only in Premier or some other editing app. The best solution I found was installing FFDShow which includes a large set of codecs that are pretty stable and perform well. On Thu, Apr 3, 2008 at 7:51 AM, matteo sisti sette [EMAIL PROTECTED] wrote: So what is mcdvd_32.dll? MainConcept DV Codec according to Yeah sorry, it was kinda stupid of me to ask that question to the list rather than to google. I am not sure, but try moving the dll out of the way, I removed it and it work. It wasn't easy though; I tried to uninstall it politely in the video codecs panel of Windows' Device Manager... but it just wouldn't disappear. So I deleted it manually, and even if according to Windows it is still in the codecs list, GEM now works fine. At first I thought the file was magically regenerating itself, since after deleting it it and searching it would still be found... but then I realized it was found in the Trash. Thanks m. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
