MC6 Track Input--Baffling Anomaly

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.

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). 

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

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 (???)

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.

I do not use a laptop. I have also run the Yeti via its own direct power connection instead of USB, but that made no difference.
 

Guitarhacker,
 
I am certain my device is being recognized. First of all, in the preferences, it shows up without issue. I receive no errors or messages complaining about it, and when I run the audio profiler, it finds everything and loads it up. Also, since I have disconnected every other single possible sound source to/from my computer, it is the only device still operational; I've removed the other devices in the Device Manager.
 
I assume by "Wave Profiler," you're referring to the Audio Profiler in the Preferences for Audio Devices in MC6? If so, yes...I've run that thing a million times going back and forth with the driver modes trying to fix this problem. Have run it 3 times today already, and figure I'll probably end up doing so another 5 times if its a slow day.
 
Everyone who is trying to help, please understand, my computer recognizes the USB Codec (the ART audio interface I'm using), I hear sound when not using MC6. MC6 recognizes the device. The ASIO panel recognizes it and says it is ready to go. MC6 picks it up in all driver modes, but on the individual track inputs it does not except when using WASAPI. Using the exact same configuration, I am able to use any mode in Reaper, including ASIO, without any problems. In MC6, I can do almost everything as always, except one really important thing: I can't get the actual input selector for any given track to show the device so I can record something with it except for any WASAPI. Like I mentioned before, a few weeks ago, when the problem first emerged, it was working only in MME-32, and when that crapped out for no reason, WASAPI picked up the slack it seems and started working.
 
I have all my settings correct, I'm 100% certain. I have only the one audio device to select from now, so there is no multi-device interference or confusion in the system. The mic is powered fine, and I have tried it both directly (plugging it into a wall socket via USB adaptor), and using phantom power through the ART. I hear playback just fine. I do screen capture using Camtasia sometimes, and that program picks up and records my voice even when I've got MC6 running. Everything but the damned track input selection itself is working perfectly. That's why this is utterly baffling. I want to use ASIO mode, for lower latency primarily, as I was doing for months and months and months before this came out of nowhere. Also, clearly given the bugginess I've experienced in MC6, it isn't very comforting knowing that any day now WASAPI mode could decide to take a vacation as well, leaving me absolutely no way to record anything.
 
Hope all that info helps. I'll do pretty much anything to get this figured out, so ask as many questions as you'd like and I'll be all over getting the responses out.

Might want to add a picture of the MC6 Preferences > Audio > Driver page for the recording mode being used.

Yeah, good old Seth. One thing though; doesn't he still work for Cakewalk? He shows as a "Developer" on the Steam Forums, and I know he worked with Ryan and some others on the latest tutorial videos they put out, 'cause he's in the credits.
 
As to getting the update, good idea to spread the word. It isn't really an update; you get the whole new package of MC6T. That's a pretty big deal and I wonder why, being subscribed to all things related to this stuff, I did not receive any notice that I had that product waiting for me, FREE, at the store? Odd.
 
Thanks again for your efforts!

Well, MC6T was not free to everyone. In fact, it is definitely a stand alone product, and sells on Steam whereas MC6 does not. However, anyone who registered MC6 after a certain date gets MC6T free it turns out, a decision made by Cakewalk relatively recently. I'm guessing MC6 was buggy enough that after the release of Touch they just decided to provide newer product. So it is an upgrade for me pretty much. Like you said, problem solved though, amen and hallelujah and all that good jazz. Onward and upward.