Comments

TorS wrote on 5/6/2003, 3:52 PM
You mean other than ethical?
Tor
PS Ha ha.
BrianStanding wrote on 5/6/2003, 3:55 PM
Works for me. No conflicts.
Hitime wrote on 5/6/2003, 5:04 PM
works fine for me on a P4 2.4 and a gigabyte motherboard and DVStorm. DVstorm even works for VHS capture in Vegas. But why should you want to use premiere now? I thought I would use both but DVStorm/Premiere does not get much use now (3 months later). I shoot a lot of multi camera (3-5) shows mostly over 2 hours long -- in Vegas my editing rate is 6.5-7.5 mins/hr in Premiere I am lucky to better half that even though I know Premiere better.

Hope that helps
BillyBoy wrote on 5/6/2003, 5:23 PM
There isn't any known problems with Premiere, however some versions of Video Wave on the same machine can cause problems.
SonyEPM wrote on 5/7/2003, 11:18 AM
Premiere 6 and above should be fine. Watch out for 3rd party drivers or codecs if you are installing a card along with Premiere- that's where the troubles usually start (rogue DV drivers especially).
mikkie wrote on 5/7/2003, 11:23 AM
I have seen prob from the prem mainconcept stuff which installed in the win32 folder of win XP Pro.
MCTech wrote on 5/7/2003, 12:21 PM
Can you clarify the problems you've seen? The only thing installed at the system level is the decoder, but that shouldn't pose a problem. But if there is an issue, of course we'd like to know about it.

Mark
mikkie wrote on 5/7/2003, 12:51 PM
Someone else's mileage may vary of course, but I've seen/had prem 6.5 install their version of the mainconcept encoder files in the system32 folder for win XP. These files were named the same as some of those in the C:\Program Files\Sonic Foundry\Shared Plug-Ins\File Formats\MCMPEG folder the VV4b uses, but were older versions and incompatible with the Vegas stuff.

It could have been an anomoly, but I couldn't get windows to forget about those files and use the Vegas versions, nor could I get things working right by replacing these files with the Vegas versions. [used analogx dxman, regdrop, & tool from Xteq to register/unregister files/libraries]. Perhaps because they were in the windows path, the only cure I came up with was to remove the prem installed codec files in the system32 folder.

It should have been possible to relocate the prem mainconcept files back to the prem folder and reregister them there, but to be honest with you I was just trying something out so I just didn't bother.

IMO, nothing mainconcept should have been installed into the winxp folder, but figure it's a lost cause as just about any video/audio related software I've encountered always assumes you'll use their stuff, and never want to use anything else.

At any rate, if it happens to someone else, not hard to fix once you know potentially what to look for. If problems, just search the windows folder for the same file names in the SOFO MCMPEG folder listed above.
MCTech wrote on 5/7/2003, 8:55 PM
That's definitely an anomaly, because the encoder files definitely are not installed at the system level. Only the decoder files are installed there, and that is by design to allow Windows Media Player and other apps to play MPEG-2 files.

Mark