dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
Win10/m-audio firewire 1814 issues
Last week I played back an mp4 using vlc to find I had no audio. Researched this, quite a lot out there, quite a few fixes, nothing worked.
Meanwhile, sonar, vegas and sound forge all had sound.
The fix seems to be completely uninstalling the driver then reinstalling it. Sometimes it works right away, other times requires a reboot.
Don't know if this is win10 related… yes I do, as the m-audio driver hasn't been updated since 2009.
Have I reached the end of the road with this device, time for a focusrite 6i6, or is it something that can be tweaked?
SONAR Platinum Lifetime 64-bit; Focusrite Scarlett 6i6 2nd Gen.; KRK Rokit 5; ASUS P9X79; INTEL I7-3820 3.6 GHZ;850 WATT POWER SUPPLY; EVGA NVIDIA GTX560 TI 1GB;Windows 10 Home 64-bit; 32GB RAM;2 Internal SSD Drives, 3 External USB drives.
|
dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:04:46
(permalink)
last week i tried to play an mp4 in VLC, only to find i had no audio. did the research... nothing worked. tried a different player. same thing.
i have the nvidia hdaudio driver disabled. only way to deal with it as win10 continues to try to install it.
anyway, the fix is to completely uninstall and reinstall the m-audio driver, which has not been updated since 2009, and won't be as the product is legacy. sometimes works right away, sometimes requires a reboot.
my question: is there something i'm missing, some tweak i can make to win10? or is it time to get a focusrite 6i6?
Edit: Sorry for the double post, my tablet gave an error message but apparently posted it anyway.
SONAR Platinum Lifetime 64-bit; Focusrite Scarlett 6i6 2nd Gen.; KRK Rokit 5; ASUS P9X79; INTEL I7-3820 3.6 GHZ;850 WATT POWER SUPPLY; EVGA NVIDIA GTX560 TI 1GB;Windows 10 Home 64-bit; 32GB RAM;2 Internal SSD Drives, 3 External USB drives.
|
eric_peterson
Max Output Level: -68 dBFS
- Total Posts : 1103
- Joined: 2003/11/25 10:24:05
- Location: The jungles of Oregon ...
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:08:39
(permalink)
When I installed Win10 it messed up my FW, everything I have needs the legacy driver. The Win10 upgrade un-installed the legacy driver. Once I got that dealt with everything started working again.
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:10:26
(permalink)
Since they contain slightly different information, I merge the two threads.
|
dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:10:57
(permalink)
are you saying the legacy windows firewire driver? if so, where did you get it? thanks.
SONAR Platinum Lifetime 64-bit; Focusrite Scarlett 6i6 2nd Gen.; KRK Rokit 5; ASUS P9X79; INTEL I7-3820 3.6 GHZ;850 WATT POWER SUPPLY; EVGA NVIDIA GTX560 TI 1GB;Windows 10 Home 64-bit; 32GB RAM;2 Internal SSD Drives, 3 External USB drives.
|
dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:12:31
(permalink)
SONAR Platinum Lifetime 64-bit; Focusrite Scarlett 6i6 2nd Gen.; KRK Rokit 5; ASUS P9X79; INTEL I7-3820 3.6 GHZ;850 WATT POWER SUPPLY; EVGA NVIDIA GTX560 TI 1GB;Windows 10 Home 64-bit; 32GB RAM;2 Internal SSD Drives, 3 External USB drives.
|
eric_peterson
Max Output Level: -68 dBFS
- Total Posts : 1103
- Joined: 2003/11/25 10:24:05
- Location: The jungles of Oregon ...
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:27:09
(permalink)
Yes, the legacy windows drivers, downloaded them from Microsoft's web site. I don't have a link.
|
eric_peterson
Max Output Level: -68 dBFS
- Total Posts : 1103
- Joined: 2003/11/25 10:24:05
- Location: The jungles of Oregon ...
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:28:06
(permalink)
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/windows-10-and-ieee-1394-firewire-legacy-drivers/27ae7f1b-c307-4159-802e-61a123d0de87?page=1
|
eric_peterson
Max Output Level: -68 dBFS
- Total Posts : 1103
- Joined: 2003/11/25 10:24:05
- Location: The jungles of Oregon ...
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/08 11:28:43
(permalink)
There might be something useful in that thread.
|
dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/09 12:16:13
(permalink)
ok, so i installed the 1394 driver and all was well. for a while.
Going back about ten days and beyond, i could always open any mp3, mp4, wav... file in VLC and it would play, regardless of what the current sample rate was set to. in other words, if the adapter was set to 48, VLC would still play a 44 file, and vice-versa. it was seamless. i guess VLC reset the adapter.
now, after win10 updates and maybe some sonar code(?) VLC will only play a file with the sample rate the adapter is set to. if the adapter is set to 44, VLC won't play a 48 song until i close VLC, change the adapter to 48, then reopen VLC. didn't used to be that way. now VLC can no longer reset the adapter.
imho in win10 MS is doing their best to totally phase out legacy HW like firewire audio and video gear. they've changed something recently that makes a 2009 driver quit or lose functionality. that's progress in redmond, what worked last week no longer does...
i guess i'll put up with this for a bit and eventually get a focusrite 6i6. but i'm wondering if MS has a nasty surprise for us down the road when they do the same thing to usb2.0...
SONAR Platinum Lifetime 64-bit; Focusrite Scarlett 6i6 2nd Gen.; KRK Rokit 5; ASUS P9X79; INTEL I7-3820 3.6 GHZ;850 WATT POWER SUPPLY; EVGA NVIDIA GTX560 TI 1GB;Windows 10 Home 64-bit; 32GB RAM;2 Internal SSD Drives, 3 External USB drives.
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: EDIT: WIN10 - m-audio firewire 1814 issues
2016/12/09 13:53:17
(permalink)
So far I had absolutely no problems with M-Audio Audiophile Firewire on my XP - Win8 - Win8.1 - Win 10 route. It is hanging on Pinnacle Studio Firewire board (more then 10 years old). One time I have "overplayed" with M-Audio/SB/VS20/ASIO4ALL drivers... and got some "pops/cracks" from all audio devices. But Windows Anniversary update has cured the problem automagically 
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|