S-video input and bothersome overlay screens

Moderator: Ken Berry

Post Reply
gnair
Posts: 2
Joined: Thu Aug 02, 2012 1:36 pm
operating_system: Windows 7 Professional
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: LENOVO 4286CTO
processor: 2.80 gigahertz Intel Core i7-2640M
ram: 6028 Meg
Video Card: Intel HD Graphics Family [Display adapter] Thin
sound_card: Conexant 20672 SmartAudio HD Intel Display Audi
Hard_Drive_Capacity: 441.03 Gig
Monitor/Display Make & Model: ThinkPad Display 1366x768 [Monitor]

S-video input and bothersome overlay screens

Post by gnair »

I must record some ultrasound machine output for some research I am doing. I discovered that your software would allow me to specify s-video as the source and so I was successful in capturing that output as well as the sound that went with it.

However, there are three vexing little problems that would make the program far easier to handle for this purpose:

1. Many actions in the program cause it to reset the source to the default internal camera instead of staying with my s-video selection. Is there a way to set the s-video as the default source?

2. When we begin the capture, Ulead displays an overlay every time telling us that the video quality is substandard and would we like to continue. Give the noisy signal that every ultrasound machine produces, this question comes up every time and has to be answered yes or no. Can the program be set to not show that overlay and cost us time?

3. After we answer the question posed by that overlay, if the machine doesn't "hear" any input, it defaults to an error within 1 second. So, before we answer the overlay question that we wish to continue, we have to have the person with the microphone talk continuously or the program will cancel the capture automatically. Again, is there a way around this time-consuming action?

Thank you for your help and consideration.

Prof. Garyth Nair
Music
Drew University
Madison, NJ, USA
skier-hughes
Microsoft MVP
Posts: 2659
Joined: Thu Jul 21, 2005 10:09 am
operating_system: Windows 8
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: gigabyte
processor: Intel core 2 6420 2.13GHz
ram: 4GB
Video Card: NVidia GForce 8500GT
sound_card: onboard
Hard_Drive_Capacity: 36GB 2TB
Location: UK

Re: S-video input and bothersome overlay screens

Post by skier-hughes »

Firstly 99.9% of the people who answer here are users and volunteers, not staff
What is your hardware?
Where is your s-video input on the computer?
Did this hardware come with any capture software?
Can you use this?

As for your questions, I'm not 100% sure, but feel as VS isn't designed to work with most analogue sources you are probably going to be out of look.
gnair
Posts: 2
Joined: Thu Aug 02, 2012 1:36 pm
operating_system: Windows 7 Professional
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: LENOVO 4286CTO
processor: 2.80 gigahertz Intel Core i7-2640M
ram: 6028 Meg
Video Card: Intel HD Graphics Family [Display adapter] Thin
sound_card: Conexant 20672 SmartAudio HD Intel Display Audi
Hard_Drive_Capacity: 441.03 Gig
Monitor/Display Make & Model: ThinkPad Display 1366x768 [Monitor]

Re: S-video input and bothersome overlay screens

Post by gnair »

Graham:

Thank you for your reply. I might not have been clear. The program did record the ultrasound output. I connected the ultrasound machine's s-video out to an A/D convertor, s-video in. ULead found the A/D convertor and I was then able to go into the options of ULead and change the source to the s-video. The problems begin at that point -- we were still able to record the output of the ultrasound machine just fine. What I was asking about was a way to stop the program from telling me, every time, that the incoming signal was not clear -- that is a given with ultrasound output. Then, after I told the program that I wanted to continue anyway, if we don't instantly make input for ULead, it returns an error and stops the capture. To get around that, we would begin speaking before we indicated we wanted to continue so the machine wouldn't return the error and keep recording.

My questions concerned changing the input to default to s-video, if we could then stop the notice that it is not a good signal, and then, how can we have the program go on capturing without giving the program continuous input until it is past the error point.

ULead recorded our material perfectly fine. It is those clumsy annoyances that sits at the heart of my post.

Thanks,

GNair
Post Reply