dlflannery
Moderator
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"?
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.Any chance of getting support for Videoredo TVSuite 6 added?
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?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.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.
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?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?
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.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
Try the (beta) 1.0B version of new program VAP6, which works ONLY with TVS6 -- see the new sticky thread here for download links:Let me know if there is anything I can do to help.
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 (??).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>
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.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