Has anyone solved those problems with adobe premiere and marvel?

[Wiken]

Well i have and have had problems with marvel and adobe for a long time, but i have had to use software codecs for capturing, but now, after a year i would like to use the built in mjpeg, if someone has solved those big problems.

what drivers to use
desktop settings,
or anything, what todo to get matrox and adobe cooperate with those built in mjpeg files) please let me know, would have been great to use that shiiiiitee for some time :P

[Fred H]

I heard/read somewhere that Premiere doesn't "like" Marvel.
Now I'm using only MSP6 and won't go back to Premiere.

System: AMD K6/2-400 64 Mb and Marvel G400-TV.

[Dr Mordrid]

You can get Premiere 5.1c to work with the Marvel, but it can be unstable. Hell, Premiere is unstable with cards it supposedly supports too, so what's the diff?

Dr. Mordrid

[Wiken]

Dr Mordrid: how do i get it work in premiere 5.1c then? i thought i had tried almost anything, but it still wont work, tell me what to do :P

[Dr Mordrid]

The software/driver installation order can be VERY important to a sucessfull Premiere install. In short: it's very, VERY picky.

1. Go to church/temple/mosque/whatever and make your peace. You're going to need all the help you can get.

2. Uninstall the display and capture drivers and reboot. On the reboot install the standard VGA display driver. At this point I usually run Microsofts RegClean program to clear a few cobwebs out of the registry.

3. NOW install Premiere 5.x and then the 5.1c update.

4. Install the display drivers. Reboot.

5. Install the video tools. I prefer ver. 1.52 as 1.54 has broken YUY2 support. Reboot.

6. Run the HDBenchmark.

7. NOW run Premiere for the first time, making sure you set up the video, audio and capture selections when prompted to the Matrox setups you want to use. Keep the audio settings at either 22.050 khz/16 bit stereo or 41.100 khz/16 bit stereo.

8. If you experience problems with Premiere 5.1c follow these directions as outlined in the Matrox Video Tools readme.txt;

====snip====

If you experience problems using Adobe Premiere (for example, the program stops unexpectedly), try creating or editing a text-only file named "Prem50.ini" in your Premiere folder. (You can use the Notepad program to edit or save this file.) "Prem50.ini" should contain the following lines:

[override]
NoDirectShow=1

[codec]
keepopen=dmb1

====snip====

Note: most times the Prem50.ini will already be in the folder. If so just add these entries. If not make the file & save it.

Also if Premiere starts acting up you can also try deleting the file "Prem50.prf" in it's install root directory. This will force Premiere to re-scan all it's plugins and setups.

This stuff isn't too unusual with Premiere. It's a flaky SOB even with the cards it purportedly supports. That's why I switched to MSPro a long time ago.

Unfortunately I'm stuck with Premiere with my RT-2000 system, but I do a lot of editing in MSPro6 before using Premiere to add the realtime effects and outputting the finished product to SVHS.

Dr. Mordrid



[This message has been edited by Dr Mordrid (edited 20 July 2000).]

[Wiken]

Thanx for the tip doc =)
But maybe i should rather go for the mspro60 since that seems alot easier, is there anything todo to get that running problem free with matrox mjpeg files? or is it simply just to install it and it works? if i have todo something special, let me know, cause im gonna try this at work on monday then.

[Dr Mordrid]

First of all ignore the Marvel/Rainbow Runner setups listed on Uleads webpage.

Here is how to make the Marvel G400 and MSPro6 play nicely together;

1. Install MSPro6 before installing the Video Tools. Now would also be the best time to refresh your DirectX and MediaPlayer installations, just in case their settings have been altered by another software installation. This happens way too often.

2. Once the Video Tools have installed load c:\windows\ulead32.ini into notepad.

3. Look for the following entry;

[Playback}
PlayDll5=C:\PROGRA~1\MATROX~1\MCLPlugin.dll

and change it thusly;

[Playback]
;PlayDll5=C:\PROGRA~1\MATROX~1\MCLPlugin.dll

See the difference? It's the semicolon before the PlayDll command. The actual number at the end of the PlayDll call may differ, but the idea is to put the semicolon before the entry that references MCLPlugin.dll.

This will fix a problem between MSPro6 and the Marvels MCLPlugin.dll. MCLPlugin.dll is the Marvel's cutlist editing driver, which is incompatble with OpenDML. With MCLPlugin.dll disabled the MSPro6 cutlist driver will be used, which is OpenDML compatable.

OpenDML allows the use of >2 gig files if the software supports it. OpenDML enabled files can be up to 4 gigs under FAT32 and of almost unlimited size under NTFS (WinNT4 or Win2000).

To use the (virtually) unlimited size .avi's with NTFS you need Win2000 and a set of Win2000 drivers for the Marvel. These aren't ready yet and the Win2000 beta Marvel drivers are still a bit rough around the edges, so stick with Win98 for now. Patience

Dr. Mordrid


[This message has been edited by Dr Mordrid (edited 23 July 2000).]