![]() W11 still ran o.k (although windows updates didn't work properly and having mild OCD ultimately resulted in me re-installing W11 ), and the hack worked, i was able to run saffire pro 40 via firewire on w11. I stumbled upon the TPM thing, because the first time I tried the hack i had accidentally borked a Windows 11 install by deleting the EUFI partition. Saffire pro 40 with firmware.bin file modded as above (Kudos to whoever tweaked the firmware from 3.7 to 3.4 for windows 10, it gave me the idea to try the same but with 3.7 and 3.81b on windows 11) I am using a pcie x1 generic firewire card with VIA chipset. Anyway, here’s hoping this beta works just slightly better than 3.7 did! Thanks again for your helpįor reference and in case any other Pro40 users stumble across this thread. I am using a Texas Instruments FireWire card (as that seemed to be the one most said worked best with saffire pro on newer windows. The 3.81b seems to be working well so far and I’ll find out Thursday I run into the Zoom issue. I had one issue in Zoom where it would cut out (start the clicking thing if you know that, and mixcontrol wouldn’t recognize anything anymore, even if you turned the pro 40 off and on). My issue wasn’t so much that my saffire pro 40 didn’t work-3.7 was working pretty well with my AWS and games and browsers. It installed and then asked to update the unit’s firmware, which I can’t ever remember happening with older mixcontrols (although maybe I just forgot). I actually did manage to find it yesterday, probably that same drive link, as my copy was downloaded from drive. However i take no responsibility for how others use it, and if they mess up their systems it's on them lol.īut for other hackers and in the interest of transparency, if it's possible to upload.i will. Implementing/installing it on W11 required a few hacks which i had to ascertain myself, and was trial and error. A Further/alternative rationale might be that they only want 100% stable and working firmware out there. IF this is the case it's a bit unethical imho, and surely it's better to support those who are more acclimated to the older gear. I suppose the rationale being, if people can use legacy gear with newer OS it may hinder them from purchasing newer gear. The only reason i can think of is that Focusrite doesn't want this version to propogate. I've still got a copy on my computer and other back-ups elsewhere off-line.īut searching for it via search engines doesn't seem to turn-up much either. ![]() A quick scan shows it's no longer hosted on there. I think i got my version direct from the Focusrite website a fair few months back. (In my case, my ASIO drivers didn't allow shared mode, at least in Win10, so this was the only way I could get DAW and Windows to play audio at same time. With that connected, the Pro 40 can play audio via ASIO drivers direct from my DAW, and Windows can play all other content via the optical cable. eg: In Mix control app, sample rate is set to 48kHz, and I matched this in the settings of the of the onboard audio: window looks a bit like the image here: I also had to set the built-in chipset audio to match the default sample rate of the Pro 40. In the Mixer/Settings app you can opt to use the optical in for a couple of different things - I select SP/DIF (from memory). I connected that to the optical IN of the Pro 40. My motherboard (Realtek chipset) has an optical digital output. ![]() Is anyone else running a Saffire FireWire device with Build 19043? Is it working fine for you? Does anyone maybe have a fix that I could try in order to get my device to show up again? However, before updating to the newest build today, I was using 19042, which was already several builds after 1809, so I am convinced that it should work. ![]() I reached out to Focusrite's excellent 24/5 instant chat support and their representative pointed me to this article, stating that, as per October 2019, Focusrite has ended developmental support for their Saffire FireWire range, thereby supposedly rendering Windows builds after 1809 incompatible with the device. Under Device Manager, it just shows up under "Other Devices" and cannot be used. I was using it just fine but uninstalled the driver today to solve a problem, and even after reinstalling Saffire MixControl, MixControl says no hardware is connected and Windows is not finding the driver to the device. I have a Saffire Pro 24 that is connected via FireWire to my computer running Windows 10 Home 64-bit Build 19043, which is the newest build as of 27 June 2021. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |