Page 1 of 2
No connection microphone
Posted: Tue Oct 28, 2008 2:34 pm
by hanskru
Hi VS friends,
IUsing VS12, however I cannot use my microphone when I want to add narration. My microphone works properly with other programs, but when in the audiomode and click on the microphone, I got an error message:
Device error, cannot open the wave-in device.
Any suggestions

Posted: Tue Oct 28, 2008 3:41 pm
by 2Dogs
Hallo Hansi mein kumpel!
(excuse my French!)
It's a while since I messed with mic inputs with VS, but it might be worth checking some basic settings. I'm still using XP, so if you have Vista I hope it's similar!
Click on the speaker icon in your system tray if you have one, which will bring up a Master Volume window.
Then click on Options > Properties and in the Properties window that should appear check the Recording radio button. (the Playback button is normally checked by default)
In the Recording Control window that appears, make sure that the check box below Microphone is checked. On my system there is also Stereo Mix and CD Player, but only one can be checked at any one time.
On my system also, there is also an Advanced button below the Microphone slider and checkbox, giving access to further tweaks.
If, on the other hand, you don't have the speaker icon in your system tray, you can access the same windows by going to Control Panel > Sounds and Audio Devices and in the resulting Sounds and Audio Devices Properties window that appears, click on the Volume button in the Sound Recording section.
That will spawn the same Recording Control window as described previously, where you can select the Microphone checkbox.
Hope that helps!
no connection microphone
Posted: Tue Oct 28, 2008 5:21 pm
by hanskru
Thanks for the reply, however I checked all the settings and the recording for the mic was switched on. So it is peculiar that I can record thru the mic by using the windows recording, but it wont work work with VS.
More advise

no connection microphone
Posted: Wed Oct 29, 2008 5:32 pm
by hanskru
I did some further investigation myself.
First I tried to use mic in VS10 and it worked. Then again I started VS12 and it worked. When I loaded my VSP project in the timeline than again the error message appeared Device Error

.
So when I put any thumnail in the time line the mic function works, however when I put my VSP project into the timeline I get the error message.
Any suggestions????
Re: no connection microphone
Posted: Wed Oct 29, 2008 6:36 pm
by Trevor Andrew
hanskru wrote: When I loaded my VSP project in the timeline than again the error message appeared Device Error

.
So when I put any thumnail in the time line the mic function works, however
when I put my VSP project into the timeline I get the error message.
Any suggestions????
Hi Hans
Do you mean, you open the project using File-Open project
Or
You start VS and add the project to the timeline, (using the 'insert video' option) your project will show as a single thumbnail. (this is a form of editing called nesting, causing problems if not implemented correctly)
Posted: Wed Oct 29, 2008 9:15 pm
by 2Dogs
If you are indeed trying to "nest" your project as Trevor suggests - I would ask the question - why?
VS10 vsp project files should be compatible with VS12, so you can simply open the VS10 project with VS12.
Of course once you save it as a VS12 project, it will not be compatible with VS10, but you can always make a backup copy of the VS10 project if you still need a VS10 version.
Posted: Wed Oct 29, 2008 9:24 pm
by Black Lab
Of course once you save it as a VS12 project, it will not be compatible with VS10, but you can always make a backup copy of the VS10 project if you still need a VS10 version.
Actually, you can go to File>Save As and save it as a v10, v11 or v12 project. Nice feature.
Posted: Wed Oct 29, 2008 9:50 pm
by 2Dogs
Maybe I've missed that feature in VS11 - or maybe it was introduced in VS12. I actually did think it might be possible - I use a particular CAD program in my work which allows you to save in earlier formats - but I have to admit I am pleasantly surprised to learn that corel introduced such a sensible feature!

Posted: Wed Oct 29, 2008 10:23 pm
by Trevor Andrew
Hi
Backwards compatibility was introduced with VS 10.
From the Save Window ---- the Save as Type can be changed to the earlier version ie VS 9
For VS 11 I think you can revert to VS 9 or 10
And for 12 trial to 10 or 11
Seams to be the last two versions.
But be careful, some editing options are not available in the earlier versions, and reverting to an earlier version may corrupt the VSP.
Posted: Thu Oct 30, 2008 8:40 pm
by hanskru
Hi all,
thanks for the replies.
I have to clarify something, I did not copy my VS12 project and put it into the timeline of VS10. I just checked in VS10 if the mic worked, and it did.
Then I went back to VS12 and loaded some thumbnails in the timeline and the mic worked OK.
When I loaded my VS12 VSP project thru Fie>Open into the timeline the mic did not work and I got the error message.
I went to the Share step and made a Video File of this project.
When I put tis videofile in the timeline than the mic did work

.
I am still wondering what caused the mic malfunction in my VSP project.
brgds Hans
Posted: Thu Oct 30, 2008 8:57 pm
by Ken Berry
The audio module has been a weak element of Video Studio for years for many users. That is why a lot of us here simply ignore it and instead use a third party audio editing software package (like the freeware Audacity or Nero WaveEditor or, with X2 Ultimate, Steinberger Wave Lab LE 6). We do our voiceovers externally in .wav format and insert those in the voice timeline. Ditto with editing and inserting background music. So if I were you, I would use that method and not get too worried about why VS audio is not functioning properly in this regard -- annoying though it might be, and regardless of how much you would like to solve the mystery...

If it's a bug it should be fixed with a patch
Posted: Fri Oct 31, 2008 3:33 am
by 2Dogs
That's all very well Ken, and you set out a perfectly feasible pragmatic solution to Hans' problem, but it does sound like VS12 has less functionality with respect to audio than earlier versions, and that can't be right.
If it's a bug, it should be fixed - with a patch, not a $50 upgrade to version X3....

Posted: Fri Oct 31, 2008 4:01 am
by Ken Berry
OK. Point taken.
So for the first time in several versions, I just opened an existing project at random in X2. It already had both added background music and some voiceovers. However, there was plenty of space between the latter for me to experiment with the X2 audio module. I just used my standard headset with microphone attached, which is plugged into the pink MIC jack (and green speaker jack). I had first tested it without the project open i.e. empty timeline, and it worked fine, creating a voice clip which played back perfectly.
I then opened the project, fixed the pointer above an empty space in the voice channel, and pressed the Record Voice button, then Start. I said a few words, then stopped the recording. A new audio clip was inserted in the audio channel. It played back perfectly both in Clip and Project mode.
So if I have read the OP's workflow correctly, and emulated it, then I am unable to reproduce the problem he is experiencing.
Posted: Fri Oct 31, 2008 10:18 am
by Trevor Andrew
Hi Hans
I also have tried to simulate your problem, everything seems to work just fine.
Are we to assume that it is only the one VSP that is giving problems.
If so may be we should be looking at the VSP content.
Perhaps a corrupt sound file.
As a test, opening the project in VS 10 may help prove a problem clip, especially if you have the same problem.
OK
Open the project in VS 12
Save As¡XGiving the project a new name, add ¡¥For VS 10¡¦ to the name.
From the ¡¥save as window¡¦ ¡V ¡¥Save as Type¡¦ select ¡¥Corel Video Studio 10 Project files (*.vsp)
Close VS 12
Open the VSP in VS 10
Do you have the same problem
Posted: Fri Oct 31, 2008 2:18 pm
by 2Dogs
Ken Berry wrote:OK. Point taken.
Sorry Ken, it seems like I was being a bit harsh - especially in view of the effort you've put into replicating the fault.
Judging by the results both you and Trevor have found, it now seems to me that it's likely to be some kind of configuration issue with Hans' pc.
Perhaps it's even a DirectX issue. To check your DirectX version, click on
Start > Run... then type in
dxdiag and your DirectX version will show at the bottom of the listing. On my XP laptop, it's 9.0c(4.09.0000.0904)
P.S. the forum is very slow today from here!