weconverse
18 Apr 2011, 15:54
Earlier I created and used a profile X on a PC running VidBlaster's Broadcast edition. When saved, and finally used, this particular profile did not use the TCP module. Possibly an earlier version of the profile, or a completely other profile previously edited on the same machine, did use the TCP profile.
When I loaded profile X on another machine running the Trial (Studio) edition I got an error message stating that "TCP module... is not supported" in that edition. Well, besides knowing that already, I also knew I was not using the TCP module in the profile.
To nail the thing, I loaded profile X again into the PC with the Broadcast edition and checked that I did not use the TCP module, including moving other modules around to check that no module was hidden behind another.
This happened on 1.27, and I have also found the same error in 1.19 (in which the API module was introduced).
When I loaded profile X on another machine running the Trial (Studio) edition I got an error message stating that "TCP module... is not supported" in that edition. Well, besides knowing that already, I also knew I was not using the TCP module in the profile.
To nail the thing, I loaded profile X again into the PC with the Broadcast edition and checked that I did not use the TCP module, including moving other modules around to check that no module was hidden behind another.
This happened on 1.27, and I have also found the same error in 1.19 (in which the API module was introduced).