Print

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

[Shadowen]

I've posted about this problem before but I just wanted to bring this up again since I haven't received a fix yet.

The JRiver Video Codec 1.0 is not being registered when I upgrade from one version to another.  I receive no error message as such, they just "go missing" from my list of available codecs in the TV Tuner recorder settings after an upgrade.

To get the codec to reappear, I have to manually register the files using the following commands:

regsvr32 /s "C:\Program Files\J River\Media Center\TV\MJVideoEncoder.ax"

regsvr32 /s "C:\Program Files\J River\Media Center\TV\MJVideoDecoder.ax"

JRiver is unable to duplicate the problem, but I am able to duplicate this problem over and over again.  JimH asked me to ask if other people are having this problem.
 
To try and duplicate this perform the following steps:
 
1 - Install MC (any build previous to current release)
2 - Go into TV Tuner options under Advanced.
3 - Select Recording tab and create a custom Recording/Timeshifting Profile that uses the JRiver Video Codec 1.0.
4 - Exit MC
5 - Upgrade MC to the latest build.
6 - Go back into TV Tuner options under Advanced.
7 - Go to Recording tab and edit the Recording/Timeshifting profile you previously created.
8 - Check and see if the profile is no longer using the JRiver Video Codec 1.0 and that it is missing from the pull-down list.

This is a real nuisance, because everytime JRiver updates Media Center, I have to manually run these commands after each install.

Please take a moment to test this out, and let me know one way or another if this is happening to you.  If you could think of anything that could be causing this that would be great also.

Thanks,
Shadowen

[JimH]

We've talked about this at length and can't think of what could be causing it.

It is probably specific to your system since nobody else has reported it.

My guess is that some other software is affecting it.  Perhaps something in the OS or some security application.

[Shadowen]

I was able to duplicate this issue again on a brand new system.

--Shadowen

[jleerigby]

What are the common factors between the new system and the old?  It might help to be totally exhaustive with this list i.e. note down EVERYTHING that is common to both systems in terms of:

Hardware
Software
Drivers
BIOS

[JiiPee]

I can confirm this happens to me also with every new build I install, I think(I haven't check always, because I don't use them).
No big deal. I just register them again if I need them.

win2000+sp4