INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: "Decoder for the new track could not be found" (new since build 80)  (Read 8738 times)

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile

I've been playing .m2ts files for some time now, but recently this error pops up everytime I play an .m2ts.  I can click through it and the file plays just fine.  What has changed?  I installed cccp with the default settings more than a year ago and never got this error before.
Logged

fitbrit

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4889
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #1 on: August 02, 2010, 10:42:20 am »

Have you changed any filter settings, or installed any other new directshow software? I got this message too, recently, and it was when I was applying DXVA without a valid subtitle solution on videos with subtitles.
Logged

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #2 on: August 02, 2010, 04:32:05 pm »

No I haven't added any filters or any software.  Only been updating MC on this machine.  I have only WMVideo Decoder DMO and Microsoft DTV-DVD Audio Decoder directshow filters checked.  I thought maybe it was only the .m2ts files with DTS audio, because some files (.m2ts) do not give the error.  Not the case though.... some files without DTS give the error.  I'm fairly certain this is caused by something new in MC.  Regardless, any ideas on a directshow filter configuration that might fix it?  Again the videos play fine as before.  Its just annoying to click past the dialog box with the remote.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72543
  • Where did I put my teeth?
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #3 on: August 02, 2010, 04:35:45 pm »

FFDShow handling changed.

Are you using build 87?
Logged

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #4 on: August 02, 2010, 04:37:06 pm »

FFDShow handling changed.

Are you using build 87?

Yes
Logged

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10949
  • Dogs of the world unite!
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #5 on: August 02, 2010, 06:06:00 pm »

Is that error message exactly the text you saw?  It does not look like it's from MC.  I can not find such text in our code.

I am able to play m2ts files on my computer.  It will require Haali Media Splitter.
Logged
Yaobing Deng, JRiver Media Center

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #6 on: August 02, 2010, 06:55:36 pm »

Here's a picture.  I assumed it was MC, but maybe not.....  As I said, I can play the m2ts file, I just have to click past this dialog box.

Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72543
  • Where did I put my teeth?
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #7 on: August 02, 2010, 07:49:56 pm »

What does it say?  Mikx?
Logged

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #8 on: August 02, 2010, 08:42:07 pm »

Actually, it says Mkx.  I Googled my way to another forum that stated the "Mkx" popup is a Haali media splitter error and it has something to do with subtitles.  HMMMM....  I'll keep searching.
Logged

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10949
  • Dogs of the world unite!
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #9 on: August 02, 2010, 08:51:43 pm »

This is interesting.  MC should have disabled Haali's popups on start up.  The only way the popups get reenabled would be to enable it in Haali's configuration while MC is already running.  Do you still get the error if you close MC and then restart it?
Logged
Yaobing Deng, JRiver Media Center

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10949
  • Dogs of the world unite!
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #10 on: August 02, 2010, 08:55:08 pm »

I can not see clearly on the picture, but the icon at the top-left of the popup looks like MC's logo.  That is weird.
Logged
Yaobing Deng, JRiver Media Center

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #11 on: August 02, 2010, 09:16:03 pm »

This is interesting.  MC should have disabled Haali's popups on start up.  The only way the popups get reenabled would be to enable it in Haali's configuration while MC is already running.  Do you still get the error if you close MC and then restart it?

Yes, if I restart, reboot, I still get the popup.

I can not see clearly on the picture, but the icon at the top-left of the popup looks like MC's logo.  That is weird.

Yes, that's the MC logo, but it appears to be unique to the Blue Steel skin.  I switched to Aruba and Noire and the popup has no logo.
Logged

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #12 on: August 05, 2010, 04:35:30 pm »

Any other thoughts here?  My next step I guess is to roll back to before build 80.
Logged

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10949
  • Dogs of the world unite!
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #13 on: August 05, 2010, 04:52:13 pm »

Any other thoughts here?  My next step I guess is to roll back to before build 80.

Please try that and see if the problem goes away.
Logged
Yaobing Deng, JRiver Media Center

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #14 on: August 05, 2010, 05:40:28 pm »

No change.  I installed every major release back to 68.  Still get the popup.  I re-installed CCCP.... no change.

Edit:  I guess this means something else (other than MC) changed on my PC, cause this just started happening.  Any troubleshooting ideas would be greatly appreciated.
Logged

Yaobing

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10949
  • Dogs of the world unite!
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #15 on: August 05, 2010, 09:02:18 pm »

Have you been using any unusual plug-in?
Logged
Yaobing Deng, JRiver Media Center

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #16 on: August 05, 2010, 11:18:48 pm »

Nope. 
Logged

fitbrit

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4889
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #17 on: August 05, 2010, 11:42:59 pm »

Filters that may fix this - be warned that you have to figure out how to register them by googling. It's fairly simple.
I think the issue may be with lack of a proper splitter for the audio/video/subtitle components of your video file.

MPC Video decoder
Matroska Source Splitter (also known as MPC-HC splitter, or Gabest's)
FFdshow audio decoder
EVR as renderer.

You might get more info out of the "Is anyone bitstreaming...?" thread.
Logged

badger

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 400
  • Change this by choosing profile
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #18 on: August 06, 2010, 11:19:14 pm »

Thanks fitbrit.  Since the popup only occurs with .m2ts and since I only have about 10 .m2ts movies, I've decided to convert them to .mkv in lieu of installing another splitter.  I've come to like .mkv better anyway because of the chapter & subtitle support.

As I was wracking my brain trying to figure out what software I could have introduced to my HTPC (which is none), I didn't even consider the fact that I installed a new video card several weeks ago.  Windows update installed the drivers for it (ATI radeon HD 4550).  I can only assume the card somehow caused these popups to start.
Logged

fitbrit

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 4889
Re: "Decoder for the new track could not be found" (new since build 80)
« Reply #19 on: August 07, 2010, 12:17:43 am »

Thanks fitbrit.  Since the popup only occurs with .m2ts and since I only have about 10 .m2ts movies, I've decided to convert them to .mkv in lieu of installing another splitter.  I've come to like .mkv better anyway because of the chapter & subtitle support.

As I was wracking my brain trying to figure out what software I could have introduced to my HTPC (which is none), I didn't even consider the fact that I installed a new video card several weeks ago.  Windows update installed the drivers for it (ATI radeon HD 4550).  I can only assume the card somehow caused these popups to start.

While I don't think it's the best idea, I've actually never had a problem just changing the .m2ts extension to .mkv to play back video. At least, not with the above or similar filters.
Logged
Pages: [1]   Go Up