Announcement

Collapse
No announcement yet.

Possible MSPro 7.2 software conflicts....

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Possible MSPro 7.2 software conflicts....

    Here we go again....

    Like others my co-mod at DMN, Rob Tywlak, has been having problems with MSPro 7.20.0006.

    Major symptoms: when creating MPEG's he's seeing VERY slow field rendering vs. frame rendering (3.5x slower). For field rendering to be slightly slower than frame rendering is normal, but 3.5x longer is rediculous. He's also been seeing some other things that may or may not be related.

    In the midst of preparing for hari-kari Rob decided to install MSPro 7.20.0006 to a fresh Win2K build without any other software.

    POOF!! Rendering problems gone. He's still testing to see if his other issues are gone as well.

    He finally traced it down to his ATI display cards MultiMedia Center (MMC) software. Most likely there is a shared library that Ulead's not overwriting and/or that ATI may have modified.

    On the other hand I use Matrox Parhelia, Matrox P-750 and Matrox G-450 eTV's and see nothing of the kind.

    Uppance: anyone who has MSPro 7.20 installed with non-Ulead video software that also uses the MainConcept encoding engine and is having problems may want to take this into consideration.

    I've reported this to Ulead through the beta channels, so we'll see what happens.

    Dr. Mordrid
    Dr. Mordrid
    ----------------------------
    An elephant is a mouse built to government specifications.

    I carry a gun because I can't throw a rock 1,250 fps

  • #2
    Another minor? problem with MSP 7.2 is that the Vixen filter from Xentrik (which is quite good for white balance and colour correction) does not work. It used to work fine with all MSP versions 6.x till version 7.1 (included).
    mits,
    System specs: primary : Asus P5B Dlx/Wifi, C2Duo E6600 with thermalright 120 and 120mm Scythe S-Flex
    model E, 2 Gb Ram Kingston HyperX PC6400, MSI RX1950Pro with ViVo, 2 * WD3200AAKS, Sound Blaster Audigy ES, NIC onborad, IEE1394 TI onboard, dvd-rw Nec/Sony Optiarc AD-7173A, dvd-rom Pioneer 106-s, Win XP SP2. Secondary : Asus P4B266-E, P4 2GHz (Northwood), ram 512 MB DDR400 , 2*80 Maxtor, vga asus 9600XT with vivo, sound card c-media 8738 onboard, NIC D-Link 538TX, dvd-rw sony dru500AX, cd-rw yamaha 2100E, Win2k SP4.

    Comment


    • #3
      Why do shared library problems still exist?

      W2K & XP both support "side by side" DLLs meaning ULEAD can install MSP to only use the DLLs it was developed with, despite other applications "updating" comon components. The disk and memory constraints that led to the shared library mess in the first place aren't that big a deal anymore.

      Now if its a non-redistributable windows DLL "repaired" by windows update we're SOL short of not updating.

      --wally.

      Comment


      • #4
        This patch is getting to be the joke of the year !!

        Debbie
        We pass this way only once. Make the most of it !

        Comment


        • #5
          Depends on what program is messing with shared dll's, if any. IMO there is some other program or driver doing something. Otherwise you wouldn't have many systems working fine with others not working at all. The problem is which one.

          Dr. Mordrid
          Dr. Mordrid
          ----------------------------
          An elephant is a mouse built to government specifications.

          I carry a gun because I can't throw a rock 1,250 fps

          Comment

          Working...
          X