I am having a very irritating problem with my track input selection in Music Creator 6. Up until a few weeks ago, everything was fine, then suddenly this problem occurred and hasn't gone away since.
 
Basically, I select my audio playback and recording in Preferences, and everything is fine. I select ASIO drivers (using ASIO4ALL) and they are identified. In the ASIO panel, everything is fine and shows as working. In the preferences, everything shows as fine and working. On all playback, everything is fine and working.
 
However, when I go to the track pull down selection for an audio input, my Mic is not listed as an option--in fact, no audio input shows up at all.
 
The problem is made more annoying by the fact that when it first began, I was able to see my mic input on tracks/channels when using MME-32 mode. Later, that stopped working, but suddenly WASAPI allowed the input. So far (fingers crossed for a temporary ongoing relief), WASAPI still allows me access to the input device, but no other mode does.
 
I have created a quick little video to demonstrate the problem. which should ensure that anything obvious I'm missing (and I seriously doubt it), can be noted easily.
 
Thanks in advance for any help at all. This is most agitating.

ASIO4ALL is a temporary sort of fix, although many folks use it all the time.
 
A mic will not normally show up in the input list. That's where the midi devices and USB interfaces show up...unless it's a USB mic..... which is not the best option for Cakewalk software.
 
You can not post links until you reach 25 posts total..IIRC....
 
The best bet, if you plan to do this on any kind of a serious or ongoing hobby basis is to invest at some point in a nice USB musical Interface. One which uses ASIO drivers.  That usually solves this sort of issue and more.

I appreciate your response. However, I am using an audio interface, and the problem is not just with ASIO as I mentioned. It is with every type of driver except, currently, WASAPI. Two weeks ago that was among the non-working, and now it has replaced the MME-32 as the only working one.
 
Also, Mics DEFINITELY show up on the track input lists in MC6. How else could you tell the track where to get the information from which it records? If you can't select the input, you can't record. Also, that's where you tell it whether you're using a left, right or mono input from the source (I have a stereo mic, so that's important). 

What interface are you using? If it has native ASIO drivers, using ASIO4All is virtually guaranteed to cause problems.
In my experience, WASAPI showed great promise, but proved to be unstable. I gave up on it.
Please list you system specs and equipment in your signature.
This will help us immensely.
We want to help, but we need to know what you are up against.

Hey Robert. Thanks again for the response!
 
As to my Interface, it does not have native ASIO drivers. The microphone plugged into it does, but I don't use those since the interface does not have the drivers also.
 
Also, I have uninstalled ASIO4ALL in the process of troubleshooting this problem, and it made no difference. As a sidebar, I also use Reaper, and that program has no issues seeing the input device. I used all the driver modes, including ASIO, for many months in MC6 before this problem just cropped up out of nowhere. I do recall that occasionally there would be a small time period when the Input device would not show up, but in those cases, it showed as not working in the ASIO panel and a restart of the computer usually fixed the problem. It never lasted long either way. Now the ASIO4ALL panel shows everything working and connected, as does the preferences for MC6, but I simply can't get it to show up on the track input.
 
I wouldn't think ASIO4ALL would have anything to do with the problem anyway since it doesn't play into anything when I'm using MME-32 driver mode, which as I noted, has now crapped out. Before that, and after the problem started originally, it was working fine, and WASAPI was not. Now WASAPI is working, and MME-32 not (along with ASIO and WDM).
 
System Specs
General:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1     
System Manufacturer: HP-Pavilion
System Model: GC671AA-ABA a6130n
BIOS: Phoenix - AwardBIOS v6.00
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ (2 CPUs), ~2.6GHz
Memory: 3072MB RAM
Available OS Memory: 3070MB RAM
Page File: 2180MB used, 3958MB available
DirectX Version: DirectX 11
DX Setup Parameters: Not found
DxDiag Version: 6.01.7601.17514 32bit Unicode
 
Audio:
 Speakers (USB Audio CODEC )
 Default Sound Playback: Yes
 Default Voice Playback: Yes
 Hardware ID: USB\VID_08BB&PID_29B0&REV_0100&MI_00
 Manufacturer ID: 65535
 Product ID: 65535
 Type: WDM
 Driver Name: USBAUDIO.sys
 Driver Version: 6.01.7601.18208 (English)
 Driver Attributes: Final Retail
 Driver Provider: Microsoft
 
Sound Capture:
Description: Microphone (USB Audio CODEC )
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 6.01.7601.18208 (English)
Driver Attributes: Final Retail

Additional Note: Since you can't see the video I should mention that when I put it together, I noted early on that the room noise around me is noticeable as I'm recording it. I can not select the input for my mic on a track in MC6, but the mic, running through my interface and set up in my audio to use it, comes through the system and is recognized and played back when recording a screen capture situation.
 
Also, if you want to try, you can go to YouTube and search for "Track Audio Input Problem." When I do that search, the first thing that shows up is my video (by Joe Walter), but I don't know if that's just because it recognizes it as mine so shows it first on the list.

A USB-mic is identified in the input list because it is an audio interface. Normal microphone does not send any ID-data, it's simply listed according to the input it's plugged into. If you are using the mobo soundchip and a USB mic simultaneously, that alone may cause more than enough problems.
According to your gear list you don't have a separate audio interface, even though you say you do. Did you forget to write it? You're most likely using the motherboard soundchip. (You can not plug a USB mic into an audio interface.)
 
If you try to record through one primitive soundcard (the USB-mic) and play back through another primitive one (mobo chip) it is very unlikely you get anything done properly ever.
 
Why on earth don't you bother to tell the make and model of the USB-microphone? That is one of the crucial links in this query.
Could you not use that alone, and forget the mobo sound chip?
 
I see your loudspeakers are USB-connected as well. Don't say they include an audio interface :o) That would be the third one you are
trying to use simultaneously (???)

grizwalter
Hey Robert. Thanks again for the response!
 
As to my Interface, it does not have native ASIO drivers. The microphone plugged into it does, but I don't use those since the interface does not have the drivers also.
 
Audio:
 Speakers (USB Audio CODEC )
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: USB\VID_08BB&PID_29B0&REV_0100&MI_00

Type: WDM
Driver Name: USBAUDIO.sys

Driver Provider: Microsoft
 
Sound Capture:
Description: Microphone (USB Audio CODEC )
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 6.01.7601.18208 (English)
Driver Attributes: Final Retail

 
This looks to me like you are using the on board or factory sound card and not an interface such as one made by M-Audio, Presonus, Focusrite, or Roland.... a unique, USB connected, external device for audio and midi inputs.   The mic however, does appear to be a USB mic. 
 
So, you are using the factory sound chip.... hence no ASIO drivers. As has been noted, you have 2 soundcards and that is not a good situation.  2 soundcards because the USB mic is seen by the computer as a sound card to....and the USB mic clock and the factory card clock will not sync properly. Therein lies the heart of the problem.
 
If you insist on using a USB mic, you may wish to read this:  http://forum.cakewalk.com/Guide-SONAR-usb-mic-Samson-C01u-or-C03u-mic-m1618556.aspx   it might help you get rolling.
 
Read post 2 last sentence again.  Don't use the USB mic for recording.... sell it and buy a regular condenser mic and an interface with phantom power. Even though it is a USB device too.... it is specifically designed to work properly and use the native ASIO drivers. Life will be a breeze in your studio when you make this move. Everything will work like you expect it to. There might be a few setup tweeks, but after that, it will rock your world.
 
I would never go back to trying to use a factory card and ASIO4ALL..... actually, for full disclosure.... I never was able to get the factory card and A4A to work at all in my system. I started out by buying the external interface and after setting it up properly, I have not had any sort of issues since. I turn it on, plug in and press record.

Hey gentlemen. It seems that both of you are saying I'm not using an interface, but I am. I'd post a link so you could see a pic/specs, but Google can get you to it immediately.
 
The interface is the USB Dual Pre by ART.
 
Secondly, I am not using a USB microphone. I use a YetiBlue Pro Microphone. It plugs into my interface via XLR (5-pin to 2 3-pin stereo) into my interface. This is the "analogue" connection for the mic; The mic does have the ability to run USB, but I do not operate it that way.
 
The mic is a stereo condenser and requires power, which I can either get directly through a USB connection or, the way I do it, via phantom power from the USB Dual Pre.
 
The Input/output information you see should show you the USB Audio Codec for both. That is my interface. (Not sure why it says USB Audio Codec exactly, but that's the label it gets.)  Again, it is a USB interface, but my audio runs in and out of it, not directly into my system. The only device running into my computer separately is my MIDI controller.

ART and Yeti, well, that is the most important info that you should have written in your opening post, no links needed.
Are you powering the ART via USB? HP Pavillion is a laptop, isn't it? It's possible, that USB doesn't give ART enough power to maintain the phantom power for the Yeti. That might lead to the vanishing input info. Trying with battery or a powered USB-hub might be worthwhile.