From: Philippe C. <la-...@or...> - 2012-10-27 18:52:10
|
Hi everybody, I revisited the Monitor section for Saffire Pro 40. I give an instantaneous snapshot of the developments on this page: http://www.premiumorange.com/la-page-web-of-phil/index.php?page=P030602 Focusrite support provided the required information for Pro 14, I will soon implement for it. Now, including these devel in FFADO requires some further works, since all Saffire Pro devices (14, 24, 40) are involved; and to save time, I need to know the users position (referring to the present situation), especially the one of Pro 24 users. - Monitor section is presently non-existent for Pro 14, so there is no problem, I think (Tim ?) - Monitor section only very partially works for Pro 40, I doubt somebody would like to stay in the present state. - the situation is possibly different for Pro 24. I can manage either to extend this kind of monitoring section to Pro 24 or keep the present state. So please, let me know what you prefer. In any case, testing the new version will be needed. Best regards, Phil -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-04 15:47:58
|
Le dimanche 28 octobre 2012 à 18:23 +0100, Johannes Mueller a écrit : > Philippe Carriere: > > Hi everybody, > > > > I revisited the Monitor section for Saffire Pro 40. I give an > > instantaneous snapshot of the developments on this page: > > > - the situation is possibly different for Pro 24. I can manage > > either to extend this kind of monitoring section to Pro 24 or keep the > > present state. So please, let me know what you prefer. In any case, > > testing the new version will be needed. > > I've been waiting for this for so long, so I would be pleased if you extend it > to the Pro 24. I have a Pro 24 here and I can do testing and bug reporting. > Feel free to send code for testing. > > Johannes > Hi everybody, modifications for the new monitoring model have been commited in the trunk as revision 2248. It requires testing especially for Pro 14 and 24, since I have no such devices for testing. Please: - update your svn to 2248 - check compilation and install - if OK, with your device on, start ffado-dbus-server in a terminal window, then ffado-mixer in another one and check for any strange message as long as you change the settings. - for Pro 40 (Delpishtroumpf), you should obtained the same behaviour than me, that is every setting control working. Just recall that Focusrite firmware introduces some temporization in the volume control: so unactivating the soft control, you will have to turn the physical dial (and possibly the dim slider) so as to reach the existing setting before physical dial takes definitively the control. - for Pro 14, Tim, as you know, you have to test carefully, the one after the other, each part of the monitoring section and note any mis-behaviour. - this also true for Pro 24; I based my encoding according to what was yet existing; but it is easy to introduce some errors ...:-( Best regards, Phil -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Yves G. <yve...@nu...> - 2012-11-05 21:21:50
|
Le 04/11/2012 16:47, Philippe Carriere a écrit : > Le dimanche 28 octobre 2012 à 18:23 +0100, Johannes Mueller a écrit : >> Philippe Carriere: >> > Hi everybody, >> > >> > I revisited the Monitor section for Saffire Pro 40. I give an >> > instantaneous snapshot of the developments on this page: >> >> > - the situation is possibly different for Pro 24. I can manage >> > either to extend this kind of monitoring section to Pro 24 or keep the >> > present state. So please, let me know what you prefer. In any case, >> > testing the new version will be needed. >> >> I've been waiting for this for so long, so I would be pleased if you extend it >> to the Pro 24. I have a Pro 24 here and I can do testing and bug reporting. >> Feel free to send code for testing. >> >> Johannes >> > Hi everybody, > > modifications for the new monitoring model have been commited in the > trunk as revision 2248. It requires testing especially for Pro 14 and > 24, since I have no such devices for testing. > > Please: > - update your svn to 2248 > - check compilation and install Hi Phil After compilation and installation, when I start ffado-mixer or ffado-test, I get: Library version mismatch. (required: libffado 2.1.9999-2248, present: libffado 2.999.0-2214) Regards Yves > - if OK, with your device on, start ffado-dbus-server in a > terminal window, then ffado-mixer in another one and check for any > strange message as long as you change the settings. > - for Pro 40 (Delpishtroumpf), you should obtained the same > behaviour than me, that is every setting control working. Just recall > that Focusrite firmware introduces some temporization in the volume > control: so unactivating the soft control, you will have to turn the > physical dial (and possibly the dim slider) so as to reach the > existing setting before physical dial takes definitively the control. > - for Pro 14, Tim, as you know, you have to test carefully, the > one after the other, each part of the monitoring section and note any > mis-behaviour. > - this also true for Pro 24; I based my encoding according to what > was yet existing; but it is easy to introduce some errors ...:-( > > Best regards, > > Phil > > -- > Philippe Carriere <la-...@or... > <mailto:la-...@or...>> > |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Jonathan W. <jw...@ju...> - 2012-11-05 23:50:15
|
Hi Yves > After compilation and installation, when I start ffado-mixer or > ffado-test, I get: > Library version mismatch. (required: libffado 2.1.9999-2248, > present: libffado 2.999.0-2214) This sounds like you have two different libffado.so* files installed: the new one (r2248) and the old. This is likely to be due to the bump in the library version number. This changes the libffado.so* filename so the new revision will not overwrite the old. To fix this, check out ls -l /usr/local/lib/libffado.so* You'll probably find two shared libraries (in amongst a number of symlinks). Identify the older one (corresponding to libffado 2.999.0-2214) and delete it. Then run ldconfig. Once this has been done you should find the problem with ffado-test has been resolved. Note that this is a one-off task whenever the FFADO library version number if bumped. Code revisions which don't do this (ie: the vast majority) will overwrite the old libffado.so when you do an install as they always have. The root cause of this problem in your case is that your old FFADO dates from before the release of FFADO 2.1 while the new version comes from after this event. It was the release of FFADO 2.1 which required the change in library name. I hope that's clear. Let us know how you get on. Regards jonathan |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-06 19:01:38
|
Le mardi 06 novembre 2012 à 10:37 +0000, Tim Smith a écrit : > On 06/11/12 07:37, Philippe Carriere wrote: > > So just changing the configuration file worked ? Can you confirm since > > it has to be propagated to the trunk ? > > Yes ! Committed as revision 2249. |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-06 19:05:22
|
Le lundi 05 novembre 2012 à 20:49 +0000, Tim Smith a écrit : > Line/inst switches - only the inst radio buttons are shown activated if > the mixer has been set to inst from the last use. That is if input 1 or > 2 is already set to line, this is not > indicated with a radio bullet. > HI/Lo switches - the same thing here, only the Hi radio buttons show as > activated on start up.If you set the inputs to low all radio buttons > look inactive. > An attempt for corrections has been committed as revision 2250. Could you have a try ? It is hard to know anything with python, including the correctness of encoding. Best regards, Phil -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Yves G. <yve...@nu...> - 2012-11-07 21:46:27
|
Le 06/11/2012 00:49, Jonathan Woithe a écrit : > Hi Yves > >> After compilation and installation, when I start ffado-mixer or >> ffado-test, I get: >> Library version mismatch. (required: libffado 2.1.9999-2248, >> present: libffado 2.999.0-2214) > This sounds like you have two different libffado.so* files installed: the > new one (r2248) and the old. This is likely to be due to the bump in the > library version number. This changes the libffado.so* filename so the new > revision will not overwrite the old. > > To fix this, check out > > ls -l /usr/local/lib/libffado.so* > > You'll probably find two shared libraries (in amongst a number of symlinks). > Identify the older one (corresponding to libffado 2.999.0-2214) and delete > it. Then run ldconfig. Once this has been done you should find the problem > with ffado-test has been resolved. Hi Jonathan, Thank you for the advice, it worked. Hi Philippe, Now ffado-mixer can be executed, without errors. I verified that the sliders on the monitoring page work as expected, but I have not tested anything else. I hope to perform more complete tests, next week end. Regards Yves > > Note that this is a one-off task whenever the FFADO library version number > if bumped. Code revisions which don't do this (ie: the vast majority) will > overwrite the old libffado.so when you do an install as they always have. > The root cause of this problem in your case is that your old FFADO dates > from before the release of FFADO 2.1 while the new version comes from after > this event. It was the release of FFADO 2.1 which required the change in > library name. > > I hope that's clear. Let us know how you get on. > > Regards > jonathan > |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-08 07:13:32
|
Le mercredi 07 novembre 2012 à 22:46 +0100, Yves Grenier a écrit : > Le 06/11/2012 00:49, Jonathan Woithe a écrit : > > Hi Yves Hi Yves, > > > >> After compilation and installation, when I start ffado-mixer or > >> ffado-test, I get: > >> Library version mismatch. (required: libffado 2.1.9999-2248, > >> present: libffado 2.999.0-2214) > > This sounds like you have two different libffado.so* files installed: the > > new one (r2248) and the old. This is likely to be due to the bump in the > > library version number. This changes the libffado.so* filename so the new > > revision will not overwrite the old. > > > > To fix this, check out > > > > ls -l /usr/local/lib/libffado.so* > > > > You'll probably find two shared libraries (in amongst a number of symlinks). > > Identify the older one (corresponding to libffado 2.999.0-2214) and delete > > it. Then run ldconfig. Once this has been done you should find the problem > > with ffado-test has been resolved. > Hi Jonathan, > > Thank you for the advice, it worked. > > Hi Philippe, > > Now ffado-mixer can be executed, without errors. I verified that the > sliders on the monitoring page work as expected, but I have not tested > anything else. I hope to perform more complete tests, next week end. > OK. Let me know at that time if anything goes wrong. Apparently, Tim obtained a satisfying behaviour for Pro 14. > Regards > > Yves > Best regards, Phil -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Yves G. <yve...@nu...> - 2012-11-18 18:13:55
|
Hi Philippe Here are the results of my tests with Saffire Pro 24 (sorry for the delay, It was hard for me to find enough time for these small tests). In the monitoring tab, I can modify the level of all 6 output lines. For each line, UA, Mu and GM work as expected. The global Mute is OK. The H/W button inhibates the commands for the six lines, this is OK. What seems not to work: the global "Activate Dim", which has no effect, whatever the Dim Level is. As a consequence, the GD buttons have no effect for any of the six lines. I did not hear any difference when clicking on the Mono buttons. Another remark; the grey color is almost the same when the button is on or off. Maybe more contrasted values would help. Best regards Yves Le 07/11/2012 22:46, Yves Grenier a écrit : > Le 06/11/2012 00:49, Jonathan Woithe a écrit : >> Hi Yves >> >>> After compilation and installation, when I start ffado-mixer or >>> ffado-test, I get: >>> Library version mismatch. (required: libffado 2.1.9999-2248, >>> present: libffado 2.999.0-2214) >> This sounds like you have two different libffado.so* files installed: the >> new one (r2248) and the old. This is likely to be due to the bump in the >> library version number. This changes the libffado.so* filename so the new >> revision will not overwrite the old. >> >> To fix this, check out >> >> ls -l /usr/local/lib/libffado.so* >> >> You'll probably find two shared libraries (in amongst a number of symlinks). >> Identify the older one (corresponding to libffado 2.999.0-2214) and delete >> it. Then run ldconfig. Once this has been done you should find the problem >> with ffado-test has been resolved. > Hi Jonathan, > > Thank you for the advice, it worked. > > Hi Philippe, > > Now ffado-mixer can be executed, without errors. I verified that the > sliders on the monitoring page work as expected, but I have not tested > anything else. I hope to perform more complete tests, next week end. > > Regards > > Yves > > >> Note that this is a one-off task whenever the FFADO library version number >> if bumped. Code revisions which don't do this (ie: the vast majority) will >> overwrite the old libffado.so when you do an install as they always have. >> The root cause of this problem in your case is that your old FFADO dates >> from before the release of FFADO 2.1 while the new version comes from after >> this event. It was the release of FFADO 2.1 which required the change in >> library name. >> >> I hope that's clear. Let us know how you get on. >> >> Regards >> jonathan >> > > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > FFADO-devel mailing list > FFA...@li... > https://lists.sourceforge.net/lists/listinfo/ffado-devel > |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-19 18:31:10
|
Le dimanche 18 novembre 2012 à 19:13 +0100, Yves Grenier a écrit : > Hi Philippe > Hi Yves, > Here are the results of my tests with Saffire Pro 24 (sorry for the > delay, It was hard for me to find enough time for these small tests). > > In the monitoring tab, I can modify the level of all 6 output lines. For > each line, UA, Mu and GM work as expected. > > The global Mute is OK. The H/W button inhibates the commands for the six > lines, this is OK. > > What seems not to work: the global "Activate Dim", which has no effect, > whatever the Dim Level is. As a consequence, the GD buttons have no > effect for any of the six lines. > Ooooops. I mistook in the registers for Pro 24. I correct this as rapidly as possible. > I did not hear any difference when clicking on the Mono buttons. > Since Mu and GM buttons work, it means that the correct register is addressed. I will check the encoding, but possibly, it is not so evident to really hear a difference. > Another remark; the grey color is almost the same when the button is on > or off. Maybe more contrasted values would help. > I'm not a specialist of PyQt; but I think the final rendering might depend on your own configuration. Whatever, using different colors would be better but the few tests I did were not convincing. Note this is just matter of modifying the "ui" file using Qt designer, for instance - a fairly simple interface; there is no need for knowledge about programming. Possibly somebody would like to take time for this. > Best regards > > Yves > Best regards, Phil > > Le 07/11/2012 22:46, Yves Grenier a écrit : > > Le 06/11/2012 00:49, Jonathan Woithe a écrit : > >> Hi Yves > >> > >>> After compilation and installation, when I start ffado-mixer or > >>> ffado-test, I get: > >>> Library version mismatch. (required: libffado 2.1.9999-2248, > >>> present: libffado 2.999.0-2214) > >> This sounds like you have two different libffado.so* files installed: the > >> new one (r2248) and the old. This is likely to be due to the bump in the > >> library version number. This changes the libffado.so* filename so the new > >> revision will not overwrite the old. > >> > >> To fix this, check out > >> > >> ls -l /usr/local/lib/libffado.so* > >> > >> You'll probably find two shared libraries (in amongst a number of symlinks). > >> Identify the older one (corresponding to libffado 2.999.0-2214) and delete > >> it. Then run ldconfig. Once this has been done you should find the problem > >> with ffado-test has been resolved. > > Hi Jonathan, > > > > Thank you for the advice, it worked. > > > > Hi Philippe, > > > > Now ffado-mixer can be executed, without errors. I verified that the > > sliders on the monitoring page work as expected, but I have not tested > > anything else. I hope to perform more complete tests, next week end. > > > > Regards > > > > Yves > > > > > >> Note that this is a one-off task whenever the FFADO library version number > >> if bumped. Code revisions which don't do this (ie: the vast majority) will > >> overwrite the old libffado.so when you do an install as they always have. > >> The root cause of this problem in your case is that your old FFADO dates > >> from before the release of FFADO 2.1 while the new version comes from after > >> this event. It was the release of FFADO 2.1 which required the change in > >> library name. > >> > >> I hope that's clear. Let us know how you get on. > >> > >> Regards > >> jonathan > >> > > > > > > ------------------------------------------------------------------------------ > > LogMeIn Central: Instant, anywhere, Remote PC access and management. > > Stay in control, update software, and manage PCs from one command center > > Diagnose problems and improve visibility into emerging IT issues > > Automate, monitor and manage. Do more in less time with Central > > http://p.sf.net/sfu/logmein12331_d2d > > _______________________________________________ > > FFADO-devel mailing list > > FFA...@li... > > https://lists.sourceforge.net/lists/listinfo/ffado-devel > > > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > FFADO-devel mailing list > FFA...@li... > https://lists.sourceforge.net/lists/listinfo/ffado-devel -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-11-19 20:19:11
|
Le lundi 19 novembre 2012 à 19:30 +0100, Philippe Carriere a écrit : > > What seems not to work: the global "Activate Dim", which has no effect, > > whatever the Dim Level is. As a consequence, the GD buttons have no > > effect for any of the six lines. > > > > Ooooops. I mistook in the registers for Pro 24. I correct this as > rapidly as possible. > Corrected in last revision 2253. Yves, can you update and test again ? Best regards, Phil. -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Yves G. <yve...@nu...> - 2012-12-08 21:38:20
|
Le 19/11/2012 21:19, Philippe Carriere a écrit : > Le lundi 19 novembre 2012 à 19:30 +0100, Philippe Carriere a écrit : >>> What seems not to work: the global "Activate Dim", which has no effect, >>> whatever the Dim Level is. As a consequence, the GD buttons have no >>> effect for any of the six lines. >>> >> Ooooops. I mistook in the registers for Pro 24. I correct this as >> rapidly as possible. >> > Corrected in last revision 2253. > > Yves, can you update and test again ? Hi Philippe Sorry for testing so late. Dim now works for all 6 output channel (Dim level OK, button "Activate Dim" is OK, and buttons "GD" are OK). But there is something strange with Line/Out 1 and 2: the level is very weak, compared to Line/Out 3 to 6. Iverified all settings (especially the buttons for which there is a very weak contrast between on and off) but I could not find any explanation. I had not observed that with revision before 2253. Yet another remark: only the upper part of the scale for all the potentiometers can be used, otherwise the sound is totally muted when the cursor is in the lowest half. Regards Yves |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Philippe C. <la-...@or...> - 2012-12-09 10:58:51
|
Hi Yves, Le samedi 08 décembre 2012 à 22:38 +0100, Yves Grenier a écrit : > Le 19/11/2012 21:19, Philippe Carriere a écrit : > > > > > Le lundi 19 novembre 2012 à 19:30 +0100, Philippe Carriere a > > écrit : > > > > > > What seems not to work: the global "Activate Dim", which has no effect, > > > > whatever the Dim Level is. As a consequence, the GD buttons have no > > > > effect for any of the six lines. > > > > > > > > > > Ooooops. I mistook in the registers for Pro 24. I correct this as > > > rapidly as possible. > > > > > > > Corrected in last revision 2253. > > > > Yves, can you update and test again ? > > Hi Philippe > > Sorry for testing so late. > > Dim now works for all 6 output channel (Dim level OK, button "Activate > Dim" is OK, and buttons "GD" are OK). > That's nice. > But there is something strange with Line/Out 1 and 2: the level is > very weak, compared to Line/Out 3 to 6. Iverified all settings > (especially the buttons for which there is a very weak contrast > between on and off) but I could not find any explanation. I had not > observed that with revision before 2253. > Well, the monitoring behaviour is different between Pro 40 and Pro 24/14. More particularly, the front panel Monitor control; Focusrite documentation mentions: "Note that the front panel Monitor control affects only outputs 1 and 2, and is an additional volume control on top of the monitor level set in Saffire Mix Control software." It looks like it is a purely physical control, so moving this control should modify what you hear. Had you an attempt like this ? In any case, send me again the output of test-dice-eap -c1 -a --port=fw1, provided you run the command while your settings are active (and low output level for line 1/2 is obtained in comparison with other line levels). > Yet another remark: only the upper part of the scale for all the > potentiometers can be used, otherwise the sound is totally muted when > the cursor is in the lowest half. > There is no real muting with the sliders: they range from 0 to -128dB, knowing that, when dim is activated, they are modulated (simple addition) by the dim level which itself ranges from 0 to -128dB (so that the whole range is from 0 to -256dB; related to the fact that 4 bytes of the register are involved for each setting). It's probably true that -64dB is yet very low but this is a specific character of Saffire Pro. > Regards > > Yves > > Best regards, Phil -- Philippe Carriere <la-...@or...> |
Re: [FFADO-devel] [FFADO-user] Monitoring section for Saffire
(Pro40, Pro 14, and especially Pro 24)
From: Yves G. <yve...@nu...> - 2012-12-09 17:00:22
|
Hi Philippe Le 09/12/2012 11:58, Philippe Carriere a écrit : > Hi Yves, > > Le samedi 08 décembre 2012 à 22:38 +0100, Yves Grenier a écrit : >> Le 19/11/2012 21:19, Philippe Carriere a écrit : >> >>> Le lundi 19 novembre 2012 à 19:30 +0100, Philippe Carriere a écrit : >>>>> What seems not to work: the global "Activate Dim", which has no effect, >>>>> whatever the Dim Level is. As a consequence, the GD buttons have no >>>>> effect for any of the six lines. >>>>> >>>> Ooooops. I mistook in the registers for Pro 24. I correct this as >>>> rapidly as possible. >>>> >>> Corrected in last revision 2253. >>> >>> Yves, can you update and test again ? >> Hi Philippe >> >> Sorry for testing so late. >> >> Dim now works for all 6 output channel (Dim level OK, button >> "Activate Dim" is OK, and buttons "GD" are OK). >> > That's nice. > >> But there is something strange with Line/Out 1 and 2: the level is >> very weak, compared to Line/Out 3 to 6. Iverified all settings >> (especially the buttons for which there is a very weak contrast >> between on and off) but I could not find any explanation. I had not >> observed that with revision before 2253. >> > Well, the monitoring behaviour is different between Pro 40 and Pro > 24/14. More particularly, the front panel Monitor control; Focusrite > documentation mentions: > > "Note that the front panel Monitor control affects only outputs 1 and > 2, and is an additional volume control on top of the monitor level set > in Saffire Mix Control software." > > It looks like it is a purely physical control, so moving this control > should modify what you hear. Had you an attempt like this ? I had not attempted that, and I have done it now. I confirm that the volume control on the Saffire Pro24 labelled "Monitor" affects outputs 1 and 2. Since it was set to a very low level, this explains why outputs 1 and 2 were weak. Now the level is similar on 1/2, 3/4 or 5/6. And the various Dim buttons and cursors work on 1/2 exactly as on the others. Sorry, I should have checked this control. > In any case, send me again the output of test-dice-eap -c1 -a > --port=fw1, provided you run the command while your settings are > active (and low output level for line 1/2 is obtained in comparison > with other line levels). > >> Yet another remark: only the upper part of the scale for all the >> potentiometers can be used, otherwise the sound is totally muted when >> the cursor is in the lowest half. >> > There is no real muting with the sliders: they range from 0 to -128dB, > knowing that, when dim is activated, they are modulated (simple > addition) by the dim level which itself ranges from 0 to -128dB (so > that the whole range is from 0 to -256dB; related to the fact that 4 > bytes of the register are involved for each setting). > It's probably true that -64dB is yet very low but this is a specific > character of Saffire Pro. OK, so this is not a real problem, just slightly annoying. Regards Yves |