INTERACT FORUM
More => Old Versions => Media Center 14 (Development Ended) => Topic started by: cnipares on January 26, 2010, 03:07:12 am
-
After the forced 14.0.130 upgrade I am not able to use the Theater Mode or 3D Visualizations. I get "Error starting Direct3D engine - (adapter 0 not capable of windowed mode)" I reloaded 14.0.96 and the problem goes away. Tried 14.0.131, same problem.
Help please.
System info:
Dell Latitude E6400 - Windows 7 Ultimate
Media Center 14.0.96 Registered -- C:\Program Files\J River\Media Center 14\
Workstation 6.1 (Build 7600)
Intel Pentium III 2020 MHz MMX / Memory: Total - 2097 MB, Free - 1111 MB
Internet Explorer: 8.0.7600.16385 / ComCtl32.dll: 5.82.7600 / Shlwapi.dll: 6.1.7600 / Shell32.dll: 6.1.7600 / wnaspi32.dll: N/A
Ripping / Drive D: Mode:Normal Type:Auto Speed:Max
Digital playback: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive D: TSSTcorp DVD+-RW TS-U633A Addr: 1:0:0 Speed:62 MaxSpeed:62 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: Yes
Use playback settings: No /
Portable Device Info
Removed devices:
Interface Plugins:
last.fm (Active)
Library Server (Active)
TiVo Server (Active)
UPnP Server (Active)
-
Update DirectX from Microsoft.
-
I did that, same problem. I had upgraded to DirectX 11, I did a system restore to remove it in case that was the cause. Now I would be at the Win 7 install version with the problem. Should I try DirectX 9? or 10? Question is what happened between .96 and .130?
-
You could try updating the video driver.
This isn't an MC problem. It's a hardware problem. Some older hardware doesn't support 3D at all.
-
Try installing the latest video driver.
-
Latest Video driver is installed from Dell. This a current laptop (Dell Latitude E6400, new 4/09), the video card does handle 3D. Seems to be related to the MC version, not the hardware. MC 14.0.96 works, no problem, .130 does not.
-
See if you can get a video driver from the chip maker, not from Dell.
-
MC 14.0.96 works, no problem, .130 does not.
That's really strange, because there haven't been any meaningful changes to the Direct3D startup.
The driver is reporting that it doesn't support windowed 3D. This is one of the first calls, so I don't see what else it could be than the driver.
If Intel or nVidia or ATI offer a newer driver for the video card, I'd try it.
You could also run dxdiag.exe (included with DirectX installation) to see if it reports anything strange.
-
Ran DXDiag, no problems. Updated driver from Nvidia site to Ver 8.17.11.9562. Direct X 11 is installed. Same issue MC 14.0.96 is OK. MC 14.0.131, .130 and .127 fail. I would try other versions if available to see exactly which version the problem starts at to narrow it down.
-
UPDATE of problem. I still can not get Theater View or 3D visualizations to work on my Dell E6400 Windows 7 machine. I loaded an 2nd hard drive with XP Pro SP2 installed on the same machine (Dell E6400). No problem, MC 14.0.130 work fine. It seems to be a Windows 7/MC14.0.130 incompatibility. Same machine works fine with XP Pro installed. I am committed to the Win 7 drive as my Media Center system. Can someone send links to the versions between MC 14.0.96 and MC 14.0.130 so I can narrow the problem down to a particular MC version? Note MC 14.0.96 does work on the Windows 7 machine. Help Please.
-
UPDATE of problem. I still can not get Theater View or 3D visualizations to work on my Dell E6400 Windows 7 machine. I loaded an 2nd hard drive with XP Pro SP2 installed on the same machine (Dell E6400). No problem, MC 14.0.130 work fine. It seems to be a Windows 7/MC14.0.130 incompatibility. Same machine works fine with XP Pro installed. I am committed to the Win 7 drive as my Media Center system. Can someone send links to the versions between MC 14.0.96 and MC 14.0.130 so I can narrow the problem down to a particular MC version? Note MC 14.0.96 does work on the Windows 7 machine. Help Please.
This probably means that the video driver or DirectX for XP work, but one of them doesn't on Win7. The version of MC isn't relevant.
-
This probably means that the video driver or DirectX for XP work, but one of them doesn't on Win7. The version of MC isn't relevant.
FYI I got this same message (on V131) after rebooting from the intstall, but I then changed versions and all is fine (but I did not test to see if this was a persistant issue) I did not see it with V130....Win7 32-Bit, ATI HD4550 HDMI out.
-
This probably means that the video driver or DirectX for XP work, but one of them doesn't on Win7. The version of MC isn't relevant.
Isn't relevant other that MC 12 and up to MC 14.0.96 does work. Explain that please.
-
I've had the some problem too. Homebuilt HTPC w/ATI HD 3200 Chipset and Windows 7. It worked fine up until the same update. I've updated to the latest Dx11 AND the latest ATI drivers and I still get the same thing when booting directly into theater mode.
Does anyone have any ideas??
-
Update DirectX from Microsoft.
Please try it.
Make sure your version of MC is up to date. 14.0.155 is on the download page.
-
I have already. I also have the latest Dx11. Got it today. I'm still getting the same thing. It only happens when I have jrmc booting up at startup and defaulting to theater mode.
Anything else to try?
-
Try updating the video driver.
Confirm the version of MC you're using.
-
I did confirm I had 14.0.155. I have updated the latest video drivers.
-
I continue to load and test each new update as they come out (.155 current), nothing working. So I reload .096 and disable "check for updates" to avoid the forced update. Sorry to be missing all of the new features of the current version. Such is life. Too bad I have been a long time user of MC, I started back at Ver 9. It has been disappointing to be held back to .096.
-
Please report the problem to the maker of the video hardware. It isn't an MC bug.
-
I'm having the same issue. Just started out of nowhere. Things were running fine then I get hit with it. However it only happens after I've been watching a movie. Now issue going in and out of theatre view only when I watch a movie and only if I've watch it for a certain period of time...haven't nailed it down but it appears anything over 20 mins or so.
I'm fully updated.
Did anybody on a pervious reply to this post get any resolution? Also, if it's not an MC issue why would you be concerned about the version?
This appears to be a windows 7 & video card conflict with mc in theatre mode. If anybody on the other posts can let me know where I can get .096 so I can see if it works that would be helpful...or pm me and I'll give you my email address.
The thing I can't figure it out is it worked great, then not....and I can access theatre mode no problem...it's just after a video and only after a specific amount of time.
-
I've experienced this error occasionally, but more often find myself presented with a blank screen after watching a movie. Both events seem to be related to the length of the video. I'm not sure, but that might be "frequently" for movies and "never" for TV programs. So I wonder if it has something to do with the computer's (Windows 7) power settings, as mine is set to go to sleep after one hour. I'll test my theory by changing that setting to 30 minutes.
The fix for both events, BTW, has been to press the key on my remote that's programmed with mc14.exe /Mode Theater to restart Theatre View. I've never bothered to get off the couch to investigate the nature of the blank screen state.
-
Hmm....I'm operating a logitech remote. How did you program mc14.exe /mode theatre on your remote? Does that restart mc14? If this only happens in movies it leads me to beleive there is a fixable bug here. Hopefully we can get Jim or somebody else to weigh in here. I know they've said it's no mc14 and it may not be the root cause but it may also be fixable. I'm really curious as to why it's only movies and why only after a certain period of time.
-
I performed a full uninstall, restarted and then reinstalled with the latest version. No joy. Frustrating to say the least. Windows 7....arrg! There has not be an answer here. Any way to debug? Any way I could get my hands on a past version of mc14.
-
I know you may not believe it, but this is almost certain to be the OS or the video driver. Update DirectX and the driver. Try another video card.
-
No I beleive it. None of this happened on my other computer. Issue is it's an acer revo. So no option to change video card. I've update directx and drivers still nothing. I'm looking for a copy of winxp 64bit so I can run a dual boot and finally get my problems solved which have all be related to video and win 7.
I just thought there may be some sort of tweak that was possible on mc's end.
As we speak, and I'm going to run a few more test, I changed the filter from coreavc to cyberlink and it didn't happen. The issue I was having before was cyberlink was stuttering a bit. This actually coincided (now that I think about it) with the issue. Does that make any sense?
-
Report it to Acer if you haven't. Tell them we'll provide a license if they want to test.
-
How did you program mc14.exe /mode theatre on your remote?
I use a Firefly (http://www.snapstream.com/products/firefly/) remote with LM Remote KeyMap (http://www.lmgestion.net/@en-us/4/22/60/article.asp). Among other things, that allows me to map any command to any key, according to which application has focus at the time. I don't know how other remotes work.
I'm really curious as to why it's only movies and why only after a certain period of time.
I have nothing further to report. Now that I've expressed a theory and am waiting for a recurrence, I'm half expecting it to never happen again. :D
-
Has anyone tried playing with the anti aliasing settings under options->Theater View?
I came across this:
http://social.technet.microsoft.com/Forums/fi-FI/w7itprohardware/thread/759dcf66-4e33-4374-a237-d4593de9f18d
-
Okay I've duplicated the error and it appears to be a coreavc 2.0 issue. Not that it's core it could very well be a collection of things including my card and os but I've narrowed it down at least. For now anyway. I've had a lot of problems with jrmc in win 7 not that it's jr's fault it's the os with the vid card I'm sure.
In any event I found it odd that it only happened after movies so I thought there was more to it than directx or video drivers. Now my issue is I have video stutter because the filters jrmc's is using is much slower but that's in another post...I'm hopeful I can get this figured out by the end of the day.
Thanks.
-
As I tend to I'm going to backtrack again...it's not just 2.0 I seem to be having that problem with 1.9.5 as well. I'm not sure why. I was also getting the error when I had it installed and playing m2t's...although I wasn't using coreavc it seemed to be interacting with the microsoft filter I was using. Once I uninstalled core it didn't happen.
-
It's back...working yesterday but not now. Very frustrating...what's even worse is they don't have drivers for xp...it's only a 7 computer. Nice...now I'm screwed and out $400.
-
It's back...working yesterday but not now. Very frustrating...what's even worse is they don't have drivers for xp...it's only a 7 computer. Nice...now I'm screwed and out $400.
Out of curiosity did you try my suggestion?
-
Yes I did...no joy. I've also e-mailed acer as suggested and they won't support the issue because it's an o/s issue. Bastards...they only provide drivers for 1 o/s then tell you they don't support it. Makes no sense.
So I'm basically out of support, I have a relatively new machine that doesn't work. JimH, is there any way to get an earlier version of 14 to see if that would work? I just need to test all possibilities.
Thanks.
-
Try this
http://files.jriver.com/mediacenter/MediaCenter140130.exe
I believe it's NVidia in the Revo? Maybe worth talking to them, also trying both old and newer drivers?
I've had issues where downgrading the driver resolved the issue.
-
Nvidia points to the manufacture. I have tried to go back and I guess I'll keep trying the issue is that it happens 20mins + of video so whenever I want to troubleshoot it takes 20 mins each time.
I had that version and that's where it started.
Any idea how to force directx to install. I go to their website and it says detected newer or equivalent and won't install.
-
Earlier builds are not available it would appear...
-
Thanks. If there is anybody out there with an earlier build they could e-mail me I'll pm you my address.
Thanks. Oh and I found a redist directx so I managed to force the download which didn't do anything nor has going back on the driver...I'm on my 6th driver.
-
Fixed....so far anyway. I had the .096 version which I wasn't aware of the it fixed a few issues including this one. So although jriver says it's not a jriver issue, going back to that version fixed it. Odd. Something you may want to investigate.
Also, does jrmc auto update and if so how do I get to stop?
-
Fixed....so far anyway. I had the .096 version which I wasn't aware of the it fixed a few issues including this one. So although jriver says it's not a jriver issue, going back to that version fixed it. Odd. Something you may want to investigate.
Also, does MC auto update and if so how do I get to stop?
Does seem given that multiple users are seeing the same issue with different video card manufacturers, it would be worth users being able to determine which version of MC the issue starts occurring...
Unfortunately I had a clear out of my setup files recently...
-
Off the top of my head I think it was 115? Does that sound right...11 something. This is odd because I didn't install any updates from the .096 version so again, is there an auto update feature? I've unclicked check for updates every 1 day but that's it.
-
And as I side note while I appreciate the help of the development team I think sometimes you dismiss claims about the product far too quickly and simply push it off as windows and drivers as if there couldn't be anything wrong with your software.
Because you told me that I went on a wild goose chase with Acer only to find out that it was the software version (which was the last thing I tried) and this in turn also alleviated a filter issue I was having. I understand it's a combinatino of a lot of variables but I think it's important to also look internally before completely dismissing the issue.
-
And as I side note while I appreciate the help of the development team I think sometimes you dismiss claims about the product far too quickly and simply push it off as windows and drivers as if there couldn't be anything wrong with your software.
Check it out. Here's a list of problems that people reported with Media Center but turned out to be drivers, etc.
http://yabb.jriver.com/interact/index.php?topic=24031.0
The fact that it works with an older version of MC probably means that something was added to MC that causes the bug in the driver to appear.
If it were a bug, it would probably be more common.
If you have any older versions that were not downloaded from JRiver, uninstall them and reboot.
Disable or uninstall any virus checkers, pop up blockers, etc. (for testing).
-
Is it possible to translate the error message into an error number from DirectX?
This might help these users find other applications that are hitting these issues, and possible resolutions.
DirectX is used by a huge number of Games and Apps. If there's a problem with it and video drivers/ Windows 7 it should be pretty to find out what is causing it, and other users experiencing it with a bit of Googling.