Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[negopus]

After installing the "DirectX Host" plugin, Media Center started playing very slowly. The first time I started playback in MC, CPU usage by MC would spin to 10-20%, the Windows cursor would turn to an hourglass, and after a minute MC would return idle, having to restart playback again (by mouse or keyboard).

Now I uninstalled the plugin, restarted MC, and the first playback starts fast as it should usually do.

The version I use is MC 10.0.144.

negopus

[Mastiff]

Gotta be something weird in your DirectX setup. I have five or six computers (counting the kid's PCs and my laptop) with MC and that host installed, running rgc high frequency stimulator, and I have no such problems on any of them. You forgot to state what version of DirectX you use.

[negopus]

I have never set up DirectX on my PC. Just installed it, and installed plugins. Versions: Windows XP sp1a, DirectX 9.0b.

[jleerigby]

I have the latest Direct X too and the DX Host plug in and RCG HFC plug in.  MC has been quite unstable for me lately and I can't figure out what it is.  Often MC crashes when first started after a reboot.  Also I've found that visualisations sometimes crash during the first session of MC.

Maybe this DX host has something to do with it.  After all it is still beta and has never really been worked on since first released.

[AoXoMoXoA]

I just happened across this post and decided to try uninstalling my DirectX plugin from MC.  Much faster start-up.  I will see in time if there are any less crashes.

[Zagnut]

It was dog slow on my system also. But I have a great many DX plugs installed, since I am a musician.

I think it either scans for, or initializes DX plugs in some way. Seems there should be some way for it to do that more efficiently, I have many DX host apps, none of them take anywhere near the time that this one does to load. They might THE FIRST TIME. But thereafter it's quick. This plug was sloooooooooooooowwwwwwwwwwww every time, and if you tried to quit, it gets marked as 'not responding' by the sytem so you have to task manage the bugger.

We must hope for imrovement.

-EDIT-

Actually, maybe the problem isn't the number of plugs, but the fact that some of them are synths rather than plugs? Perhaps the host doesn't expect them? Wavelab uses an exclusion txt file to deal with this issue.

[Mastiff]

Maybe that's why I have no problems - I have very few DirectX plug-ins. Only the ones Windows and WinDVD installs automatically, plus the RGC High frequency stimulator.

[negopus]

I have many DirectX plug-ins installed, and some of them are software synths.