Really need your help

[DMarie]

I could have posted in a couple of subs but, I decided to go with the "Windows" sub since that's my operating system. I am hoping there may be someone with the same setup who may guide me through this. I recently updated from Windows 7 to Windows 10. I'm not sure if that was a smart move LOL Anyway, I have 2 main issues. Setup is ...

Windows 10 Pro
Pro Tools Artist (Monthly subscription)
M-Audio Project Mix I/O
M-Audio Fast Track 8
Behringer X Touch One

I am currently only using the Project Mix since an issue has popped up.

Issue 1: Pro Tools recognizes all input and output of the project mix in setup. However, when assigning an input to a track, the option of "Interface Input L" or "Interface Input R" is all that is available. I don't see M-Audio Project Mix 1/2, 3/4, etc.

Issue 2: I have seen a YouTube video of a gentleman using the M-Audio Project Mix and the Behringer X Touch One with Pro Tools and they are acting as one unit. I hope he will respond lol I have assigned a HUI for each but 2 things happened: 1. The Project Mix works as it should, but the X Touch is limited in functionality - Fader doesn't move but the play, and stop and clock work for example. 2. The X touch works as it should and the Project Mix is sound only and has zero control.

Thank you so much for any guidance!!

[DMarie]

I just wanted to add that everything is working in Bandlab - just not in Pro Tools

[Darryl Ramm]

Originally Posted by DMarie

I recently updated from Windows 7 to Windows 10. I'm not sure if that was a smart move LOL Anyway, I have 2 main issues. Setup is ...

Windows 10 Pro
Pro Tools Artist (Monthly subscription)
M-Audio Project Mix I/O
M-Audio Fast Track 8
Behringer X Touch One

I am currently only using the Project Mix since an issue has popped up.

Issue 1: Pro Tools recognizes all input and output of the project mix in setup. However, when assigning an input to a track, the option of "Interface Input L" or "Interface Input R" is all that is available. I don't see M-Audio Project Mix 1/2, 3/4, etc.

Hi welcome to DUC.

Did you upgrade Pro Tools versions as well as upgrading Windows? From what to what?

What "setup" exactly are you looking at?

First make sure that the playback engine is actually set to the Project Mix. Actually check Setup>Playback Engine since Pro Tools can change the playback engine on you when you least expect it...

All that Pro Tools cares about in terms of I/O names it shows to users is what is setup in the Pro Tools Setup > IO > {input, output, bus} pages. Inputs on the input page there should show up in the input I/O selectors on a track if they are valid and enabled. But the text names associated with any I/O ports on those pages are purely symbolic/for the convenience of the user. The name strings change nothing about how an interface works and do not need to match the default I/O names. Pro Tools internally only refers to the I/O port numbering on an interface. You can rename any I/O name to be anything you want. If they don't appear to be what you expect by default click the "Default" button on each of those pages, and Pro Tools will populate that page with default names obtained through the device driver. You may have to select all the I/O paths on a page, click "Delete" to delete them, then click Default.

While a bit complex to get started with the configurable and flexible I/O setup in Pro Tools is one of it's strong points. You should read the Pro Tools Reference Guide stuff on this, play around changing names on those pages, to say name things to help you (like call I/O useful names like "Guitar main mic" or however you want to organized I/O names, and play with Defaulting I/O back again to the default).

If you are still stuck post screenshots of those three I/O pages and what is showing up in the input I/O selector on your track. Post those screenshots to a file or image sharing website and post the links here. Don't try to attach them to a DUC post, DUC downsamples images posted here so badly they are often useless.

[DMarie]

https://ibb.co/HFCLdJ0
https://ibb.co/8dKNn40
https://ibb.co/gZN5zmX


Thank you very much for your time. I want to clarify that I am not new to Pro Tools, but I am new to the "Artist" version. Previously, I used M-Audio Pro Tools 9. I don’t recall ever using a version of Pro Tools that doesn’t auto-label inputs on the track, or at least display them as IN 1, IN 2, IN 3, IN 4, and so on.

In the "Setup" section, everything appears to be correct and labeled as it should be. However, on the track, I can only see "Interface Input L" or "Interface Input R." I have 8 inputs and 8 outputs, but I am only given the option for these unusual L/R labels. Please see the images attached for reference.

Thank you again for your help! <3
ps. Forgive the headset in the list. I was listening to a book lol

[Darryl Ramm]

Thanks for the screen shots.

You should *NOT* be using "Windows Input Device" as your playback engine. That is the start and maybe end of your problems.

To work properly with Pro Tools this interface should have an ASIO driver and you should be selecting that ASIO device as the playback engine.

Did you install an ASIO driver for the interface? I'd be very surprised if there is one provided for Windows 10 given how old this interface is and how screwed up the whole Avid/M-Audio disaster was, but maybe older ones still work. .. and according to this thread https://duc.avid.com/showthread.php?t=381988 the driver for Windows 7 works, I have no idea where you download that driver from.

You never faced this problem in the past likely because you used an M-Audio specific version of Pro Tools which may have included the correct audio interface drivers (or had you install them?).

Any consumer product from M-Audio and/or Avid of this vintage is on borrowed time, may be a good idea to plan to transition to current interfaces from other manufacturers, especially those with better long-term support. RME, Focusrite, Universal Audio, Motu, and Apogee Digital are all good vendors making a wide variety of audio interfaces.

[DMarie]

The Windows device headset was on when I took the picture, but it's no longer connected, and unfortunately, the problem is still there. M-Audio's tech support provided me with the drivers, so I am hopeful that they will help.

I noticed the Project Mix is only working in WMD mode and not in ASIO (Since upgrading to Windows 10), which concerned me earlier today. I've emailed M-Audio again and am waiting for a response.

I may also try using the M-Audio Fast Track 8 for the input/output connections and use the Project Mix just as a control surface. Upgrading to Windows 10 is a key part of the UGH factor. Then again, everything is golden in Bandlab. Pro Tools - smh! lol

ps. As you can see, it IS working (sorta lol), but I do not have the ability to select IN 1 2 3 4 5 6 7 8 on the track. I have to do it in setup. Most likely lack of ASIO!

https://ibb.co/jVGf2QR

[DMarie]

Come to think of it, I don't see an option to select ASIO. I was thinking about Bandland. I only see Windows Audio Device. I will have another look at my device manager and make sure no "windows" sound device is enabled.

EDIT: The M Audio Project Mix was and is the "Windows Audio Device". With that selected, I am left with the option of "Interface Input L" or "Interface Input R". It must be a driver issue running on Windows 10. With the M Audio Project Mix not selected as a sound device and using the Fast Track instead, I now have the proper i/o of 1/2, 3/4, 5/6, and 7/8 as a track selection option. The Project Mix is now acting solely as a control surface. One way to skin a cat I suppose.

[Darryl Ramm]

I was not asking about headsets.

I would focus my efforts on finding a driver that support ASIO and then the interface will show up in the Playback Engine pull down options and you select that in the Playback Engine Dialog instead of "Windows Audio Device". If the driver bundle is supposed to include it, maybe it's not installing because of incompatibility with Windows 10. Who knows... nobody here has any clue what you are installing as a driver.

Avid claims Pro Tools supports WASAPI as well, that's uh... I would not bother.

And Pro Tools cannot use WDM devices unless wrapped with ASIO4ALL, which is often a mess.

Again, I'll repeat this very clearly: to use Pro Tools on any Windows PC you really should have an interface that supports native ASIO, with an ASIO driver supplied by the interface vendor. (not ASIO4ALL). That will give you the best chance of stuff working reliably. If you can't get an ASIO driver then I would roll back to what you had before on Windows 7 or look for a new interface.

And even more: for stable operation on Windows your ASIO device should be dedicated to Pro Tools, you should assign Windows sound to use a Windows audio sound card or motherboard chipset. Better quality ASIO drivers, especially those provided by RME, can often work fine with multiple clients, but not all drivers/interfaces can.

You have maybe lived a sheltered life with an MAudio bundle of hardware and software that made things easier for you.

[DMarie]

I appreciate your advice, but I don't believe that living a sheltered life is necessary or accurate. On/Off Pro Tools since 2002. Rolling back to Windows 7 is out of the question and also unnecessary. I work full-time in the industry, and I can no longer avoid upgrading. The audio soundware I develop sounds for requires me to run on Windows 10 and 11 now.

As I mentioned earlier, I realize that the issue stems from the lack of ASIO drivers, and I have contacted M-Audio to see if they have them available. In the meantime, I am using Pro Tools Artist with the M-Audio Fast Track, which is recognized as an ASIO device rather than a standard Windows device.

Additionally, the Project Mix is functioning properly as a dedicated control surface. I believe I'm all set for now. Thanks again, and I will update if M-Audio provides a solution!