Feature Requests and Response Status

[dlflannery]

You've already found the culprit. Consider coNFLict. Can you add something to the "nfl" match string to make it more selective, similar to "nba basketball"?

 

[TPeterson]

(Loud forehead slapping sound) Thank you. I guess I was assuming that the matches had to be freestanding words. I'll fix it.

 

[Ryland]

Any chance of getting support for Videoredo TVSuite 6 added?

 

[dlflannery]

Any chance of getting support for Videoredo TVSuite 6 added?

Yes a "chance" but I'm having trouble getting motivated to do it based on my initial assessment of the complications involved, most notably the introduction of AdDetective profiles. There's significant code complication already in place to deal with Output Profiles and I'm afraid dealing with AdDetective profiles will be complicated also -- plus there isn't much documentation available to help on this -- so I'm in the dark on how to approach it.

If there were a way to let VAP use a default AdDetective profile, perhaps one set manually in the TVSuite UI, that might allow a relatively easy modification to support TVS6 at least for a first cut at a functional TVS6-compatible VAP. But I have no idea how to do that.

 

[Ryland]

Yes a "chance" but I'm having trouble getting motivated to do it based on my initial assessment of the complications involved, most notably the introduction of AdDetective profiles. There's significant code complication already in place to deal with Output Profiles and I'm afraid dealing with AdDetective profiles will be complicated also -- plus there isn't much documentation available to help on this -- so I'm in the dark on how to approach it.

If there were a way to let VAP use a default AdDetective profile, perhaps one set manually in the TVSuite UI, that might allow a relatively easy modification to support TVS6 at least for a first cut at a functional TVS6-compatible VAP. But I have no idea how to do that.

You would think that the developers would want to help you out since you make a valuable addition to their software. Would emailing support help motivate them?

 

[Dan203]

Yes a "chance" but I'm having trouble getting motivated to do it based on my initial assessment of the complications involved, most notably the introduction of AdDetective profiles. There's significant code complication already in place to deal with Output Profiles and I'm afraid dealing with AdDetective profiles will be complicated also -- plus there isn't much documentation available to help on this -- so I'm in the dark on how to approach it.

If there were a way to let VAP use a default AdDetective profile, perhaps one set manually in the TVSuite UI, that might allow a relatively easy modification to support TVS6 at least for a first cut at a functional TVS6-compatible VAP. But I have no idea how to do that.

The old AdScan COM functions should still work just like they did before, it'll just use whatever profile or options the user last applied in VideoReDo. So shouldn’t require any change if you don’t want to fully support AdScan profiles.

 

[Dan203]

One thing I forgot the names of the AdScan functions for the legacy mode changed. They all now have "Interactive" in front of them. So...

InteractiveAdScanToggleScan
InteractiveAdScanIsScanning
InteractiveAdScanSetParameter
InteractiveAdScanGetParameter
InteractiveAdScanResetParameters

And when you get the list of profiles it'll also return AdScan profiles. To filter these out there is a function called ProfilesGetProfileIsAdScan that is used just like the ProfilesGetProfileIsEnabled function, just a simple BOOL value telling you if the profile is an AdScan profile or not.

 

[dlflannery]

Ok, with @Dan203 's help, and after some successful initial experiments, I'm encouraged and am working toward a VAP that can run TVS6. Since installations of VRD5 and VRD6 can co-exist, It looks like a given instance of VAP will have be configured upon initial startup to use either one or the other. A clean way to handle that is to actually have distinct versions, for example, VAP and VAP6.

 

[Ryland]

Let me know if there is anything I can do to help.

 

[jachin99]

Is there anyway you could compile this against a newer version of .net so windows 10 users don't have to enable legacy features like .net 3.5 in order to use it?

 

[dlflannery]

Is there anyway you could compile this against a newer version of .net so windows 10 users don't have to enable legacy features like .net 3.5 in order to use it?

Not sure I understand the problem. Currently it's set to need .net 2.0 and I alway assumed that would automatically be compatible with higher versions of .net. I run Windows 10 Pro and have no issues. Where is the setting to enable legacy features?

EDIT: I googled some info on this: https://www.howtogeek.com/250228/what-windows-10s-optional-features-do-and-how-to-turn-them-on-or-off/

I will experiment on my PC. One possible hitch is my Visual Studio development system is old (VS 2008) and it may not even allow me to build for .net greater than 3.5, which it appears would still require enabling the legacy option. It looks like enabling it is pretty easy, and only needs to be done one time, so I may just opt for providing instructions for that.

 

[jachin99]

If you bring up turn windows features on or off then you will see .net 3.5 listed as an option. I believe turning this off helps speed up the PC some and reduces the volume of updates windows will need as I have seen Microsoft patch .net 3.5 specifically. For windows 7 users this change will require us to download whatever version of .net you use as it only comes bundled with .net 3.5 and below

 

[dlflannery]

If you bring up turn windows features on or off then you will see .net 3.5 listed as an option. I believe turning this off helps speed up the PC some and reduces the volume of updates windows will need as I have seen Microsoft patch .net 3.5 specifically. For windows 7 users this change will require us to download whatever version of .net you use as it only comes bundled with .net 3.5 and below

As I suspected, my VS2008 doesn't support .NET beyond 3.5. The legacy option is already turned on in my Win 10, which is why I don't have any issues running my .NET 2.0 programs, including VAP. The legacy option includes 2.0, 3.0 and 3.5 and, if I understand correctly, windows automatically downloads the required code if needed. I have trouble imagining how having this option enabled would slow down the PC.

I don't plan to upgrade to a later version of VS as my usage of it amounts mostly just to maintaining/modifying a few programs (e.g., VAP) and that doesn't justify the $45/month cost.
Thus I plan to furnish the link I gave in a previous post to any users who encounter this issue. So far you are the only one I've heard of.

 

[dlflannery]

Let me know if there is anything I can do to help.

Try the (beta) 1.0B version of new program VAP6, which works ONLY with TVS6 -- see the new sticky thread here for download links:

VAP6 - TVSuite 6 Auto-Processor Program

WHAT IS IT? A free utility program for users of VideoReDo TV Suite 6 (TVS6). VAP6 detects video files being transferred into a designated monitor folder,and, when transfer completes, it automatically and silently runs VideoReDo processes on the files as configured by the operator in the...

www.videoredo.net

Be sure to read the section in VAP6-ReadMe.pdf for previous users of VAP, and item 21 in "Things to Know".

Note one timesaver: You can copy the "RenameTemplates.txt" and "VAPmetaParseTemplates.txt" files from your VAP data folder to your new VAP6 data folder. But you can't copy the "ProfileMatchList.txt" file, because TVS6 profiles have different names.

Please post any questions or problems in that new sticky thread.

 

[Ryland]

VAP6 doesnt like having network locations manually entered into the config file. It looked like it started but then went out of the tray. The config looks like this:

<TransferDirectory>\\tower\public\RecordedTv</TransferDirectory>
<InputDestDirectory>none</InputDestDirectory>
<QSFDestDirectory>E:\</QSFDestDirectory>
<FinalDestDirectory>\\tower\tvshows</FinalDestDirectory>

 

[dlflannery]

VAP6 doesnt like having network locations manually entered into the config file. It looked like it started but then went out of the tray. The config looks like this:

<TransferDirectory>\\tower\public\RecordedTv</TransferDirectory>
<InputDestDirectory>none</InputDestDirectory>
<QSFDestDirectory>E:\</QSFDestDirectory>
<FinalDestDirectory>\\tower\tvshows</FinalDestDirectory>

Nothing new or different in this regard about VAP6 compared with VAP. There are warnings in the tooltips and docs that network paths can be problematic. One possible workaround is to assign drive letters to the network locations. I assume you are editing the config file manually because you couldn't enter the paths in the VAP6 UI (??).

I don't have any network storage to test this issue with. This is an old issue so maybe another VAP user who has faced it can help here.

Also: For VAP6 problems, please post in the new VAP6 thread or, perhaps better, start a new thread.

Here are instructions for mapping network locations to drive letters in Win10:

How to Map a Network Drive in Windows 10

Give network drives their own letters (ex: Z:) so you can access them quickly and easily. Here's how to map your Windows 10 network drive.

www.laptopmag.com

 

[Ryland]

Whats weird is that the old version of VAP had no issues working with my network locations. I specifically dont have the paths linked as drive letters due to an over abundance of caution for encryption malware. You could create a "network drive" by sharing a directory on my machine and then refer to it by \\machinename\share name

 

[dlflannery]

Whats weird is that the old version of VAP had no issues working with my network locations. I specifically dont have the paths linked as drive letters due to an over abundance of caution for encryption malware. You could create a "network drive" by sharing a directory on my machine and then refer to it by \\machinename\share name

It could be a TVS6 vs. TVS5 issue. VAP uses TVS COM function calls not only to run AdScan and Encoding but also just when a file is first detected in the monitor folder, to get the Encoding type (which requires passing the file's path to the VRD COM object). There are absolutely no changes in the way VAP6 code handles files and folder access vs. VAP. Thus I have to suspect the COM objects, which are different between TVS5 and TVS6.

So you get no relevant error message either in the VAP6 log file or from Windows? That seems strange.

It would be interesting to know if the batch (or non-batch) processing in the TVS6 program handles your network paths OK.

 

[Ryland]

I will help out as much as I can since I have the setup which is causing the problem. These are the logs from my last few runs.

 

[dlflannery]

@Ryland further thoughts: May be unfair to single out the TVS6 COM functions for suspicion. What file extensions do videos in your monitored folder have? For .tivo files a 3rd party COM function is called to get metadata. For .wtv and .dvr-ms files, another 3rd party DLL is called. For .mp4 or .m4v files, yet another 3rd party program is run. All of these of course are passed a path to the video file. On the other hand, nothing has changed regarding these 3rd party programs, or the way they are invoked, between VAP and VAP6

Thanks for the log files. The ArgLog file shows that the last TVS6 COM call was to the function that gets data about the output profiles defined in TVS6, which is called immediately at startup, and only then. I didn't see anything suspicious in the VRDAutoProcessLog file, although I notice you're using the -hotstart CL option. Just to rule out a possibility, you might try running without that.