dvrmtoolbox - The source filter for this file could not be loaded

Post Reply
pungo

Posts: 10
Joined: Sat Dec 21, 2013 8:37 pm
Location:

HTPC Specs: Show details

dvrmtoolbox - The source filter for this file could not be loaded

#1

Post by pungo » Tue Sep 25, 2018 3:17 am

Using dvrmtoolbox, MC addin, donator version of comskip
Everything has been working great for years and now it died.
I'm just started getting the error below in the FWlog when processing a file:

Get Video Information
The source filter for this file could not be loaded

What "source filter" does this need to "Get Video Information"?
Looking in the logs when it was working correctly, the "Get Video Information" returned the resolution of the video.

I removed and reinstalled dvrmstoolbox without any success.

Any help would be appreciated.

snip of log below with text in large font where the error is:

Start Process: 9/23/2018 : 7:55 PM
InputFile=H:\Recorded TV\9-1-1_WTTGH_2018_09_23_19_53_19.wtv
Processing actions, this may take some time!!
Current Affinity: 15 System Mask: 15
Getting MetaData
Testing "Processed Files"
Testing "Every Sage File"
Testing "Every File"
"Every File" is a match.
Run Profile = nativecommdetect
ProcessId = 3676
DvrmsToolbox Version: 1.2.2.5
Throttle DVRMStoMPEG
FWThrottle: H:\Recorded TV\9-1-1_WTTGH_2018_09_23_19_53_19.wtv
WaitTime: 5 PollTime
Waiting to process file
Waiting to process file: FT = 7:53 PM WT = 7:58 PM CT=7:55 PM LN=522977280
Waiting to process file: FT = 7:53 PM WT = 7:58 PM CT=7:56 PM LN=522977280
Waiting to process file: FT = 7:53 PM WT = 7:58 PM CT=7:56 PM LN=522977280
Waiting to process file: FT = 7:53 PM WT = 7:58 PM CT=7:57 PM LN=522977280
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=7:57 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=7:58 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=7:58 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=7:59 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=7:59 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=8:00 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=8:00 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=8:01 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=8:01 PM LN=971243520
Waiting to process file: FT = 7:57 PM WT = 8:02 PM CT=8:02 PM LN=971243520
Queue file

Duration = 00:07:01.2165939
Waiting for available worker: 9/23/2018 8:02 PM
Worker allocated: 9/23/2018 8:02 PM
Get Video Information
The source filter for this file could not be loaded.
Action did not complete successfully

Total Duration = 00:07:01.2565940

PW Exit: System.InvalidOperationException: No process is associated with this object.
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_HasExited()
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_ExitCode()
at Durrant.DVRMSFileWatcher.ProcessWrap.ap_Exited(Object sender, EventArgs e)
Start Process: 9/23/2018 : 8:24 PM

Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#2

Post by Space » Tue Sep 25, 2018 6:32 am

I'm not sure what the problem is, but it looks like some file got removed or corrupted. Is there a chance some new software was recently installed, or perhaps you got some malware or a virus?

One thing you can do to try to repair system files is:
sfc /scannow

You can also try to do a "System Restore" if you have a recent restore point that may have been made before you started having the issue.


These are just suggestions off the top of my head. I really don't know what the error means (although it seems to be related to a missing video/audio codec or filter, perhaps).

pungo

Posts: 10
Joined: Sat Dec 21, 2013 8:37 pm
Location:

HTPC Specs: Show details

#3

Post by pungo » Tue Sep 25, 2018 11:28 pm

space,

Thanks for your reply. I did try a sfc /scannow without success.

Somehow my restore points were all gone, don't know what happen, but there were none from a previous point in time.

Yes, I also think there is some codec/filter dvrmstoolbox is looking for to determine the resolution but, I have no idea which one? I tried to find a place to turn the debug level up in toolbox but no joy. I'd hate to reinstall Windows and all the other software just to get dvrmstoolbox working again, it's been at least 5 years since I installed everything and got it all working. What a pain....

Still looking for a solution.

Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#4

Post by Space » Wed Sep 26, 2018 1:47 am

Do you also get an error trying to play a WTV file in Windows Media Player? Even if not, perhaps the below fill fix your problem...

I found this:

https://forums.techguy.org/threads/reso ... ed.204132/

Which has a link to the Microsoft site which is no longer valid, but I found it moved here:

https://support.microsoft.com/en-us/hel ... or-message

I have no idea if any of that will help, but it may. I would think the most likely to help would be installing DirectX. I would make an image backup before you go crazy with installing/uninstalling stuff just in case you make it worse so you can go back to the image. At the very least make sure you make a restore point before making any changes.

pungo

Posts: 10
Joined: Sat Dec 21, 2013 8:37 pm
Location:

HTPC Specs: Show details

#5

Post by pungo » Wed Sep 26, 2018 3:36 am

Space,

WMC played WTV files just fine but WMP failed to play any video file, even mpg files.
I created a restore point then installed a Media Player Codec Pack and fixed the issue.
No more "The source filter for this file could not be loaded" in the log file so comskip started cranking away at processing my files.
So just like we though, there must have been a corrupt/missing codec/filter that prevented it from working.

Thanks for your help

Space

Posts: 2841
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#6

Post by Space » Wed Sep 26, 2018 4:57 am

Great! Glad to hear you got it working. I wonder what happened to break it in the first place?

Post Reply