Become a member
Become a member

or
Continue with Google
Log in
Log in

or
Log in using a Google account

Thread Windows 10 and dual Saffire issues

  • 4 replies
  • 2 participants
  • 2,088 views
  • 3 followers
Thrax

Thrax

3 posts
New AFfiliate
First post
1 Posted on 02/07/2016 at 16:40:17
I have started to make my move over to Windows 10 and testing all my devices on the new OS. So far looks like everything is working apart from my Saffire 24pro cap and Saffire liquid 56.

I am using a Texas instruments based firewire card. My first problem was that on first installing Windows and the 3.6 focusrite drivers, the mix control would not see the devices. The firewire and locked lights on both the 24 and 56 would flash on and off. I then went to device manager and changed the firewire driver to the OHCI compatible one and this seemed to fix this problem. Mix control would then show the devices.

However I then tried to switch from the 56 to the 24 in mix control; this caused mix control to crash. The only way I can get to change settings for the 24 is to disconnect the 56.


This isn't a problem on my windows 7 installation so looks to be a windows 10 issue.

Another minor issue which I thought I should mention is that I cannot see a way to tell mix control which Saffire unit to output windows audio. On Windows 7, it outputs via the 24 but on Windows 10, it outputs via the 56. In a DAW, I can easily set the output but I cannot see an option in mix control or the Windows audio settings. Am I missing something?

[ Post last edited on 02/07/2016 at 16:40:50 ]

Thrax

Thrax

3 posts
New AFfiliate
2 Posted on 02/08/2016 at 12:56:40
There are three windows event log messages for whenever this occurs.

First message

Faulting application name: SaffireCpl.exe, version: 0.0.0.0, time stamp: 0x5677d896
Faulting module name: SaffireCpl.exe, version: 0.0.0.0, time stamp: 0x5677d896
Exception code: 0xc000001d
Fault offset: 0x00000000000b9447
Faulting process id: 0x5d0
Faulting application start time: 0x01d162b16ee85493
Faulting application path: C:Program FilesFocusriteSaffire MixControlSaffireCpl.exe
Faulting module path: C:Program FilesFocusriteSaffire MixControlSaffireCpl.exe
Report Id: c64200dc-a7c8-4467-9a3f-cb6e804a43f5
Faulting package full name:
Faulting package-relative application ID:

The Second message seems to indicate a file access issue. Additional data just has zeros so probably isn't helpful.

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program SaffireCpl.exe because of this error.

Program: SaffireCpl.exe
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

Third message

Fault bucket 120378535834, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SaffireCpl.exe
P2: 0.0.0.0
P3: 5677d896
P4: SaffireCpl.exe
P5: 0.0.0.0
P6: 5677d896
P7: c000001d
P8: 00000000000b9447
P9:
P10:

Attached files:
C:UsersThraxAppDataLocalTempWEREE42.tmp.WERInternalMetadata.xml

These files may be available here:
C:ProgramDataMicrosoftWindowsWERReportArchiveAppCrash_SaffireCpl.exe_6bfb9c82a9cd4f73c7aa5704356b6423e1f0d_931be1db_11adf844

Analysis symbol:
Rechecking for solution: 0
Report Id: a1ef1e2e-c9fb-4afa-b8f2-42e4bc42e40f
Report Status: 1
Hashed bucket: 7d9b427b92cdb98109aa7dc84d7feb96



Report.wer


Version=1
EventType=APPCRASH
EventTime=130994388955040025
ReportType=2
Consent=1
UploadTime=130994388955605097
ReportIdentifier=22e1c5a1-cea7-11e5-86fc-b41b6d023ad1
IntegratorReportIdentifier=a1ef1e2e-c9fb-4afa-b8f2-42e4bc42e40f
NsAppName=SaffireCpl.exe
Response.BucketId=7d9b427b92cdb98109aa7dc84d7feb96
Response.BucketTable=4
Response.LegacyBucketId=120378535834
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=SaffireCpl.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5677d896
Sig[3].Name=Fault Module Name
Sig[3].Value=SaffireCpl.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5677d896
Sig[6].Name=Exception Code
Sig[6].Value=c000001d
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000b9447
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2a0a
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2a0af7b0cd60114ec6d05a57f70d4973
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=4413
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=441340fc377ebef725000a249f33bde6
UI[2]=C:Program FilesFocusriteSaffire MixControlSaffireCpl.exe
UI[3]=SaffireCpl.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:Program FilesFocusriteSaffire MixControlSaffireCpl.exe
LoadedModule[1]=C:WindowsSYSTEM32
tdll.dll
LoadedModule[2]=C:Windowssystem32KERNEL32.DLL
LoadedModule[3]=C:Windowssystem32KERNELBASE.dll
LoadedModule[4]=C:Windowssystem32USER32.dll
LoadedModule[5]=C:WindowsWinSxSmd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22COMCTL32.dll
LoadedModule[6]=C:Windowssystem32GDI32.dll
LoadedModule[7]=C:WindowsSYSTEM32WINMM.dll
LoadedModule[8]=C:Windowssystem32msvcrt.dll
LoadedModule[9]=C:Windowssystem32COMDLG32.dll
LoadedModule[10]=C:Windowssystem32combase.dll
LoadedModule[11]=C:Windowssystem32shcore.dll
LoadedModule[12]=C:Windowssystem32RPCRT4.dll
LoadedModule[13]=C:Windowssystem32SHLWAPI.dll
LoadedModule[14]=C:Windowssystem32cryptPrimitives.dll
LoadedModule[15]=C:Windowssystem32SHELL32.dll
LoadedModule[16]=C:WindowsSYSTEM32WINMMBASE.dll
LoadedModule[17]=C:Windowssystem32cfgmgr32.dll
LoadedModule[18]=C:Windowssystem32windows.storage.dll
LoadedModule[19]=C:Windowssystem32dvapi32.dll
LoadedModule[20]=C:Windowssystem32sechost.dll
LoadedModule[21]=C:Windowssystem32kernel.appcore.dll
LoadedModule[22]=C:Windowssystem32powrprof.dll
LoadedModule[23]=C:Windowssystem32profapi.dll
LoadedModule[24]=C:Windowssystem32FirewallAPI.dll
LoadedModule[25]=C:Windowssystem32NETAPI32.dll
LoadedModule[26]=C:Windowssystem32ole32.dll
LoadedModule[27]=C:Windowssystem32WS2_32.dll
LoadedModule[28]=C:Windowssystem32SETUPAPI.dll
LoadedModule[29]=C:WindowsSYSTEM32DAVHLPR.DLL
LoadedModule[30]=C:WindowsWinSxSmd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_db007f1392e69ef4gdiplus.dll
LoadedModule[31]=C:Windowssystem32IMM32.DLL
LoadedModule[32]=C:WindowsSYSTEM32 wbase.dll
LoadedModule[33]=C:Windowssystem32uxtheme.dll
LoadedModule[34]=C:Windowssystem32MSCTF.dll
LoadedModule[35]=C:Windowssystem32dwmapi.dll
LoadedModule[36]=C:WindowsSYSTEM32WindowsCodecs.dll
LoadedModule[37]=C:WindowsSYSTEM32DEVOBJ.dll
LoadedModule[38]=C:Windowssystem32WINTRUST.dll
LoadedModule[39]=C:Windowssystem32MSASN1.dll
LoadedModule[40]=C:Windowssystem32CRYPT32.dll
LoadedModule[41]=C:WindowsSYSTEM32msimg32.dll
LoadedModule[42]=C:Windowssystem32clbcatq.dll
LoadedModule[43]=C:Windowssystem32dataexchange.dll
LoadedModule[44]=C:Windowssystem32dcomp.dll
LoadedModule[45]=C:Windowssystem32d3d11.dll
LoadedModule[46]=C:Windowssystem32dxgi.dll
LoadedModule[47]=C:Windowssystem32 winapi.appcore.dll
LoadedModule[48]=C:Windowssystem32crypt.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=SaffireCpl.exe
AppPath=C:Program FilesFocusriteSaffire MixControlSaffireCpl.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=4C01A0EC8CC3FA266D6FBD2E764CFC77

[ Post last edited on 02/08/2016 at 13:07:00 ]

Simon Focusrite

Simon Focusrite

207 posts
AFfinity Poster
3 Posted on 02/10/2016 at 05:17:19
Hi Thrax,

Thanks for the post and sorry you're having some issues. We're not aware of any consistent issues with the Saffire range, our Firewire driver and Windows 10 specifically, the SaffireCPL error you're seeing is generic and can relate to a number of different communication issues.
What we have seen is a number of Firewire cards that seemingly start to throw up issues under Windows 10 where they did not on previous Windows platforms, we've documented this here:

https://focusrite.com/answerbase/contact-0

Perhaps take a read and let us know your thoughts in the context of your setup. You may wish to update Mix Control to the latest 3.7 version to ensure that you're fully up-to-date.

With regards to the order of the devices, each connected Saffire will have a (fixed) internal hardware ID. We'd expect the Inputs and outputs from the Saffire with the lowest internal hardware ID (NOT the ID that appears in Mix Control 'About' menu) to always appear first in the i/o list of a DAW and therefore be the device that streams audio from your OS.
Your experience here is therefore quite unusual, and not a one that we're aware of, however I'll pass this to the developers to investigate further.

Hope this helps.
Let me know how you get on.

Simon // Focusrite Technical Support

Thrax

Thrax

3 posts
New AFfiliate
4 Posted on 02/10/2016 at 15:59:16
Hi Simon,

Thanks for the reply. Its was actually 3.7 I have installed. Since my previous post, I have experimented further and tried installing 3.4 and this version is working perfectly :)

I then reverted back to 3.7 and initially this was working fine. Then after changing settings, the control panel crashes started again. After some investigation, I have determined that changing the "sync source" to anything other than internal causes the control panel to crash when changing between saffire units. Changing it to internal, I can switch between the units without it crashing. I usually have my Saffire Pro 24 DSP set to sync to SPDIF at 44.1Khz with it being the sync master.

I then went back to 3.4 and set the same SPDIF and sync master settings and everything is working as it should be. I will be staying with version 3.4 for the time being.
Simon Focusrite

Simon Focusrite

207 posts
AFfinity Poster
5 Posted on 02/19/2016 at 02:15:41
Thanks for the feedback, we've not had any other consistent reports of these issues with 3.7, however I will report these back to the development team so we can try to repro the problems and resolve it.
Until then, I'm glad that 3.4 is working fine for you, please let us know if you need anything else.

Best regards
Simon // Focusrite Technical Support
cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Google Analytics
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Google Analytics

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.