[AG-TECH] Re: Compiling VIC in Visual Studio 8 (2005)

[Sam Gundry]

Hi Socrates,

I actually commented out this line yesterday, before receiving this 
email. :)

Video images now display locally in both the consumer and producer windows.

What should that line of code do? I haven't noticed anything out of the 
ordinary yet...

Thanks,
Sam



Socrates Varakliotis wrote:
> Hi Sam,
> 
> I assume you're still building Vic on Windows.
> Can you comment out line 562 in tcl/ui-main.tcl and rebuild?
> 
> #$target enable_xv $enable_xv"
> 
> Let me know what happens then.
> 
> 
> Thanks,
> -- 
> Socrates.
> 
> 
> 
> 
> ----- Original Message ----- From: "Sam Gundry" <sgundry at vpac.org>
> To: <Andrew.Rowley at manchester.ac.uk>
> Cc: "Piers O'Hanlon" <p.ohanlon at cs.ucl.ac.uk>; <vic at cs.ucl.ac.uk>;
> "sumover-dev" <sumover-dev at cs.ucl.ac.uk>; <ag-tech at mcs.anl.gov>
> Sent: Tuesday, January 30, 2007 11:03 PM
> Subject: Re: [AG-TECH] Re: Compiling VIC in Visual Studio 8 (2005)
> 
> 
>> Hi Andrew,
>>
>> I am using multicast.  When I use the already compiled VIC binary (from
>> the UCL installer), video appears in both VideoConsumerService and
>> VideoProducerService windows.
>>
>> The issue occurs when I use a VIC binary I compiled in Visual Studio 8.0.
>>
>> When using the my compiled VIC, neither window has any video, but it is
>> transmitting correctly since a remote machine, using a standard VIC
>> binary, can see the video properly.
>>
>> I think I've caused bugs in the program when trying to compile VIC in
>> VS8.0. The following is the debug output:
>>> [224] [pid/224 +335 c:\sgundry\ucl media tools\common\src\mbus_config.c]
>>> [224] Closed registry entry...
>>> --GetMcast: 12fa19ac 890046f8
>>> --GetMcast: 12fa19ac 890046f8
>>> [224] vic-2.8ucl1.2.1.SharedVideo: tcl runtime error: vic: _o13: no such
>>> method (enable_xv)
>>> [224] stack trace:
>>> [224] vic: _o13: no such method (enable_xv)
>>> [224]     while executing
>>> [224] "$target enable_xv $enable_xv"
>>> [224]     (procedure "attach_renderer" line 38)
>>> [224]     invoked from within
>>> [224] "attach_renderer $src $w $enable_xv"
>>> [224]     (procedure "attach_window" line 2)
>>> [224]     invoked from within
>>> [224] "attach_window $src $stamp.video false "
>>> [224]     (procedure "build.src" line 11)
>>> [224]     invoked from within
>>> [224] "build.src $w $src 1"
>>> [224]     (procedure "really_activate" line 9)
>>> [224]     invoked from within
>>> [224] "really_activate _o10"
>>> [224]     ("after" script)
>>> [224] Please mail this error message and, if possible, an explanation
>>> [224] of what user-action caused it to vic at cs.ucl.ac.uk.
>>
>> The error occurs in the "really_activate" procedure, which,  according to
>> this article https://mediatools.cs.ucl.ac.uk/nets/mmedia/wiki/VicDev, is
>> responsible for creating the video thumbnail.
>>
>> Regards,
>> Sam
>>
>> Andrew A Rowley wrote:
>>> Hi,
>>>
>>> If you are using unicast, this is the way in which it works.  Only 
>>> one of
>>> the vic instances can bind to the unicast port, which means that
>>> sometimes you will see video in the VideoConsumerService window, and
>>> sometimes in the VideoProducerService window.  It is fairly random as to
>>> which gets the video.  In any case, the quickbridge process that 
>>> performs
>>> the bridging will never send anything you send back to you, so you will
>>> never see your video in the VideoConsumerService window when using
>>> unicast.  You should see your video in both windows when using 
>>> multicast,
>>> although this will depend on your networking setup and operating system.
>>>
>>> Andrew :)
>>>
>>> ============================================
>>> Access Grid Support Centre,
>>> RSS Group,
>>> Manchester Computing,
>>> Kilburn Building,
>>> University of Manchester,
>>> Oxford Road,
>>> Manchester, M13 9PL, UK
>>> Tel: +44(0)161-275 0685
>>> Email: Andrew.Rowley at manchester.ac.uk
>>
>> -- 
>> Centre for Computational Prototyping
>> Victorian Partnership for Advanced Computing
>> www.vpac.org
> 


-- 
Centre for Computational Prototyping
Victorian Partnership for Advanced Computing
www.vpac.org