Menu
▾
▴
ffado-user
|
From: Eric K. <eri...@ic...> - 2014-06-12 08:56:15
|
Thank you very much, Jonathan. I will update my Debian asap. Admittedly I found myself a bit confused reading over the documentation for installing from source, but I am sure I can figure it out with some hardcore concentration. As for Debian, I failed to mention that I have a different HDD with the latest AVLinux installed as well... it has FFADO version 2.1.9999-2468. I get the same behavior on AVLinux so I will just concentrate on Debian for the moment and update FFADO and will post any results. Thank you again for your help! Best Regards, Eric On Jun 12, 2014, at 10:23 AM, Jonathan Woithe <jw...@ju...> wrote: > Hi Eric > > I'm short of time right now, so here's a quick reply. > > On Thu, Jun 12, 2014 at 07:01:19AM +0000, Eric Klinger wrote: > > I would love to get Jack and my FF LS56 to play nice together but so far I > > my efforts have been fruitless. Having read as much info as I could find > > on the Focusrite line in general, it seems users avoid the LS56 like the > > plague and there is a space needing filled in terms of info on this > > particular unit. If any devs are interested, please let me know what you > > need from me. > > My understanding is that the Focusrite LiquidSaffire-56 can be driven by > FFADO as if it were a non-liquid Saffire. That is, while basic audio I/O is > possible, software control of the liquid hardware is not possible. This is > due to the liquid control protocol being unknown to us - it has not been > released by Focusrite. Having said that, I don't personally work on the > DICE/Saffire drivers so some of these details may be out of date. > > > Here is a bit about what I am using: > > HW: FF Liquid Saffire 56 > > Comp: HP Workstation xw4600 | 2.66 C2D | 4GB DDR667 > > SW: Debian 7.5, RT Kernel, FFADO 2.999.0, Jack 1.9.9 > > In general this should be ok, but see below. > > > The error I receive from trying to connect to jackd is as follows: > > libffado 2.999.0- built Jun 28 2012 14:30:13 > > In the first instance you will need to upgrade to a newer version of FFADO. > Version 2.2.1 (released a week or so ago) would be a good place to start. > There have been a lot of fixes applied to code which the DICE-based Saffire > driver users, so starting with a recent version is important. Let us know > if you need assistance with the upgrade. If your distribution doesn't have > FFADO v2.2.1 available our website (especially the development wiki) has > some hints which might prove helpful. > > Regards > jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-12 12:06:03
|
On Jun 12, 2014, at 01:00 PM, Phil/La Page Web of Phil <ph...@la...> wrote: > > Hi Eric, > > Le jeudi 12 juin 2014 à 07:01 +0000, Eric Klinger a écrit : >> Greetings, >> I would love to get Jack and my FF LS56 to play nice together but so far I my efforts have been fruitless. Having read as much info as I could find on the Focusrite line in general, it seems users avoid the LS56 like the plague and there is a space needing filled in terms of info on this particular unit. If any devs are interested, please let me know what you need from me. >> >> In terms of user ability, I have used Linux for more than 10 years, though on and off, so while I am quite comfy at the command line, my general knowledge of shell tools and troubleshooting knowledge are quite low, so please be specific if telling me to perform anything. :-) >> >> Here is a bit about what I am using: >> HW: FF Liquid Saffire 56 >> Comp: HP Workstation xw4600 | 2.66 C2D | 4GB DDR667 >> SW: Debian 7.5, RT Kernel, FFADO 2.999.0, Jack 1.9.9 > As mentionned by Jonathan, install a more recent version of FFADO. This one is more than two years old, before the support of Dice Saffire. > >> >> The error I receive from trying to connect to jackd is as follows: >> libffado 2.999.0- built Jun 28 2012 14:30:13 >> 00613107311: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM: Could not read from node 0xFFC0 addr 0x000100000174 >> 00613107323: Error (focusrite_saffirepro.cpp)[ 421] updateClockSources: getSpecificValue failed >> firewire ERR: FFADO: Error creating virtual device >> Cannot attach audio driver >> > It means that your Liquid Saffire 56 is recognized as a bebob device by FFADO while it is based (to my knowledge) on a Dice chipset. So most probably there is something wrong in the FFADO config file with respect to your device. Now, as mentioned above, we could be of help only with a recent FFADO release. > The best thing would be to install from the subversion repository: then, if some corrections have to be included, you could be able to directly obtain these ones from the subversion tree. > > Follows the guidelines of the development wiki: the highest difficulty is to ensure you install over your present FFADO install. Thank you very much for the reply! At the moment I am following the dev wiki and installing dependencies as I write this. Instead of wrestling with older packages from Debian, I quickly loaded up Fedora 20 on an extra SSD drive - I thought maybe a more bleeding edge distro would offer up some of the latest packages (for deps). Then for FFADO and Jack I will compile and install from source - that way I won't have to worry (this time) about having parallel installs etc. > >> Any help at all would be most appreciated! >> > You can further ask for any help you would need to install the development version. > >> Best Regards, >> Eric >> > Best regards, > > Phil Thanks again, Phil! Best Regards, Eric |
|
From: Eric K. <eri...@ic...> - 2014-06-12 16:16:46
|
On Jun 12, 2014, at 2:05 PM, Eric Klinger <eri...@ic...> wrote: > On Jun 12, 2014, at 01:00 PM, Phil/La Page Web of Phil <ph...@la...> wrote: > > >> >> Hi Eric, >> >> Le jeudi 12 juin 2014 à 07:01 +0000, Eric Klinger a écrit : >>> Greetings, >>> I would love to get Jack and my FF LS56 to play nice together but so far I my efforts have been fruitless. Having read as much info as I could find on the Focusrite line in general, it seems users avoid the LS56 like the plague and there is a space needing filled in terms of info on this particular unit. If any devs are interested, please let me know what you need from me. >>> >>> In terms of user ability, I have used Linux for more than 10 years, though on and off, so while I am quite comfy at the command line, my general knowledge of shell tools and troubleshooting knowledge are quite low, so please be specific if telling me to perform anything. :-) >>> >>> Here is a bit about what I am using: >>> HW: FF Liquid Saffire 56 >>> Comp: HP Workstation xw4600 | 2.66 C2D | 4GB DDR667 >>> SW: Debian 7.5, RT Kernel, FFADO 2.999.0, Jack 1.9.9 >> As mentionned by Jonathan, install a more recent version of FFADO. This one is more than two years old, before the support of Dice Saffire. >> >>> >>> The error I receive from trying to connect to jackd is as follows: >>> libffado 2.999.0- built Jun 28 2012 14:30:13 >>> 00613107311: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM: Could not read from node 0xFFC0 addr 0x000100000174 >>> 00613107323: Error (focusrite_saffirepro.cpp)[ 421] updateClockSources: getSpecificValue failed >>> firewire ERR: FFADO: Error creating virtual device >>> Cannot attach audio driver >>> >> It means that your Liquid Saffire 56 is recognized as a bebob device by FFADO while it is based (to my knowledge) on a Dice chipset. So most probably there is something wrong in the FFADO config file with respect to your device. Now, as mentioned above, we could be of help only with a recent FFADO release. >> The best thing would be to install from the subversion repository: then, if some corrections have to be included, you could be able to directly obtain these ones from the subversion tree. >> >> Follows the guidelines of the development wiki: the highest difficulty is to ensure you install over your present FFADO install. > > Thank you very much for the reply! At the moment I am following the dev wiki and installing dependencies as I write this. > > Instead of wrestling with older packages from Debian, I quickly loaded up Fedora 20 on an extra SSD drive - I thought maybe a more bleeding edge distro would offer up some of the latest packages (for deps). Then for FFADO and Jack I will compile and install from source - that way I won't have to worry (this time) about having parallel installs etc. > >> >>> Any help at all would be most appreciated! >>> >> You can further ask for any help you would need to install the development version. >> >>> Best Regards, >>> Eric >>> >> Best regards, >> >> Phil > > Thanks again, Phil! > > Best Regards, > Eric Yikes! What a day. After three installs of Fedora 20 this afternoon, I finally arrived to Jack 1.9.9.5 and FFADO 2.2.1. Unfortunately I am still receiving an error as follows: 1402585517727317: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1-Unversioned directory built Jun 12 2014 16:38:53 05397823297: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM: Could not read from node 0xFFC1 addr 0x000100000174 05397823334: Error (focusrite_saffirepro.cpp)[ 421] updateClockSources: getSpecificValue failed firewire ERR: FFADO: Error creating virtual device Cannot attach audio driver JackServer::Open failed with -1 Any other ideas? Thanks much! Eric |
|
From: Stefan R. <st...@s5...> - 2014-06-12 17:28:38
|
On Jun 12 Eric Klinger wrote: > Instead of wrestling with older packages from Debian, [...] FFADO 2.2.1 is available as a package on Debian. -- Stefan Richter -=====-====- -==- -==-- http://arcgraph.de/sr/ |
|
From: Phil/La P. W. of P. <ph...@la...> - 2014-06-12 19:14:35
|
Hi Eric,
Le jeudi 12 juin 2014 à 18:16 +0200, Eric Klinger a écrit :
>
> Yikes! What a day. After three installs of Fedora 20 this afternoon, I
> finally arrived to Jack 1.9.9.5 and FFADO 2.2.1.
>
> Unfortunately I am still receiving an error as follows:
> 1402585517727317: (ffado.cpp)[ 92] ffado_streaming_init: libffado
> 2.2.1-Unversioned directory built Jun 12 2014 16:38:53
> 05397823297: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM:
> Could not read from node 0xFFC1 addr 0x000100000174
> 05397823334: Error (focusrite_saffirepro.cpp)[ 421]
> updateClockSources: getSpecificValue failed
> firewire ERR: FFADO: Error creating virtual device
> Cannot attach audio driver
> JackServer::Open failed with -1
>
> Any other ideas?
>
I checked that the configuration file does not include the Liquid
Saffire 56: I was quite surprised that Jonathan did not push the
information for it some times ago but, of course, there is a good reason
for this. What does matter is that the device identifier (0x00000006) is
identical to the one for the Pro 10, a bug from the manufacturer,
indeed.
And as the Pro 10 is supported by FFADO (as many other bebob devices) a
long time ago, one can not change the configuration file; a specific
hack would have to be implemented so as to choose between the two
devices but this is an other story.
I am not sure you can avoid a reinstall but you can try at first to
modify the configuration file of your present install. It is located at
in the directory: /usr/share/libffado/ and is named configuration. First
check by:
$ ls -l /usr/share/libffado/configuration
Then you will try to edit the file (as root), search for the next lines
...
{
vendorid = 0x00130e;
modelid = 0x00000006;
vendorname = "Focusrite";
modelname = "Saffire Pro10IO";
driver = "BEBOB";
mixer = "SaffirePro";
xmit_max_cycles_early_transmit = 4;
},
...
you will change for
{
vendorid = 0x00130e;
modelid = 0x00000006;
vendorname = "Focusrite";
modelname = "Liquid Saffire 56";
driver = "DICE";
mixer = "Generic_Dice_EAP";
},
provided you do not use a Pro 10 together ! :-)
Then, have a try if your device is recognized. If it does not work, you
will have to do the same applied to the source code and then compile and
install (over your yet installed FFADO library). Note this latter is
surely the best way, but possibly the preceding hack would work.
> Thanks much!
> Eric
>
>
Best regards,
Phil
|
|
From: Jonathan W. <jw...@ju...> - 2014-06-13 00:39:40
|
Hi Eric On Thu, Jun 12, 2014 at 09:14:24PM +0200, Phil/La Page Web of Phil wrote: > I checked that the configuration file does not include the Liquid > Saffire 56: I was quite surprised that Jonathan did not push the > information for it some times ago but, of course, there is a good reason > for this. What does matter is that the device identifier (0x00000006) is > identical to the one for the Pro 10, a bug from the manufacturer, > indeed. Indeed, that is the case. I remember now - thanks for being onto this Phil. As an aside, we should probably try to come up with a way of working around this problem. As Phil said, this is an issue caused by the device firmware. Technically it isn't a bug since vendors are free to do whatever they like with the modelid field. Most treat it as a unique identifier for a particular device, and Focusrite have done this - expect in the case of the LS56. Whether this was accidental or a result of a specific reason I don't know. > I am not sure you can avoid a reinstall but you can try at first to > modify the configuration file of your present install. It is located at > in the directory: /usr/share/libffado/ and is named configuration. Editing this "configuration" file will be sufficient - there will be no need to recompile or reinstall anything. This file is read at runtime by libffado, so any changes you make will take effect. If there are still issues after making this change it will be for other reasons. Regards jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-13 05:50:30
|
On Jun 12, 2014, at 7:28 PM, Stefan Richter <st...@s5...> wrote: > On Jun 12 Eric Klinger wrote: >> Instead of wrestling with older packages from Debian, > [...] > > FFADO 2.2.1 is available as a package on Debian. > -- > Stefan Richter > -=====-====- -==- -==-- > http://arcgraph.de/sr/ I see it’s in sid though… which I avoid… in fact I never even thought to look there. |
|
From: Eric K. <eri...@ic...> - 2014-06-13 06:20:31
|
On Jun 12, 2014, at 9:14 PM, Phil/La Page Web of Phil <ph...@la...> wrote:
> Hi Eric,
>
> Le jeudi 12 juin 2014 à 18:16 +0200, Eric Klinger a écrit :
>>
>>
>> Yikes! What a day. After three installs of Fedora 20 this afternoon, I finally arrived to Jack 1.9.9.5 and FFADO 2.2.1.
>>
>> Unfortunately I am still receiving an error as follows:
>> 1402585517727317: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1-Unversioned directory built Jun 12 2014 16:38:53
>> 05397823297: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM: Could not read from node 0xFFC1 addr 0x000100000174
>> 05397823334: Error (focusrite_saffirepro.cpp)[ 421] updateClockSources: getSpecificValue failed
>> firewire ERR: FFADO: Error creating virtual device
>> Cannot attach audio driver
>> JackServer::Open failed with -1
>>
>> Any other ideas?
>>
> I checked that the configuration file does not include the Liquid Saffire 56: I was quite surprised that Jonathan did not push the information for it some times ago but, of course, there is a good reason for this. What does matter is that the device identifier (0x00000006) is identical to the one for the Pro 10, a bug from the manufacturer, indeed.
> And as the Pro 10 is supported by FFADO (as many other bebob devices) a long time ago, one can not change the configuration file; a specific hack would have to be implemented so as to choose between the two devices but this is an other story.
>
> I am not sure you can avoid a reinstall but you can try at first to modify the configuration file of your present install. It is located at in the directory: /usr/share/libffado/ and is named configuration. First check by:
>
> $ ls -l /usr/share/libffado/configuration
>
> Then you will try to edit the file (as root), search for the next lines
> ...
> {
> vendorid = 0x00130e;
> modelid = 0x00000006;
> vendorname = "Focusrite";
> modelname = "Saffire Pro10IO";
> driver = "BEBOB";
> mixer = "SaffirePro";
> xmit_max_cycles_early_transmit = 4;
> },
> ...
> you will change for
> {
> vendorid = 0x00130e;
> modelid = 0x00000006;
> vendorname = "Focusrite";
> modelname = "Liquid Saffire 56";
> driver = "DICE";
> mixer = "Generic_Dice_EAP";
> },
>
> provided you do not use a Pro 10 together ! :-)
>
> Then, have a try if your device is recognized. If it does not work, you will have to do the same applied to the source code and then compile and install (over your yet installed FFADO library). Note this latter is surely the best way, but possibly the preceding hack would work.
>
>> Thanks much!
>> Eric
>>
>
> Best regards,
>
> Phil
Very interesting emails, thank you guys!
For what it’s worth, I did add the entry found on this page => http://www.ffado.org/?q=node/2062 though I never changed anything with the Pro10 entry. But I see that the “driver” line is different anyway. So I will make the appropriate changes to the Pro10 entry (and remove my LS56 entry) as soon as I get that first moment - Friday is baby duty day ;-)
While I was easily able to build and install FFADO with the proper prefix, I didn’t have the same success with Jack... I downloaded the files from the Jack git site, but I kept receiving compile errors (the exact errors escape me for the moment) so finally I ended up using the default Yum repo which installs 1.9.9.5 (if I recall correctly) but libffado 2.1.0 is a dependency - so it wouldn’t install without it and I am not savvy enough to force that, or prefix it to install in the directories shown in the FFADO docs, so I ended up with a FFADO library conflict. After cleaning out the 2.1.0 files, FFADO was fine and Jack seems fine (starts with alsa driver).
Thank you guys very much! Can’t wait to try it later this afternoon! I will post my results!
By the way - the FFADO mixer - should I / do I need to install it? If so, from reading the faq, I understand it as that I have to startup Jack before I start the mixer, otherwise the mixer only identifies whether or not there is a FFADO device attached. Is this correct?
THANKS!!!
|
|
From: Jonathan W. <jw...@ju...> - 2014-06-13 07:04:31
|
Hi Eric On Fri, Jun 13, 2014 at 08:19:53AM +0200, Eric Klinger wrote: > > I am not sure you can avoid a reinstall but you can try at first to > > modify the configuration file of your present install. It is located at > > in the directory: /usr/share/libffado/ and is named configuration. First > > check by: > > > > $ ls -l /usr/share/libffado/configuration > : > > For what it?s worth, I did add the entry found on this page => > http://www.ffado.org/?q=node/2062 though I never changed anything with the > Pro10 entry. But I see that the ?driver? line is different anyway. So I > will make the appropriate changes to the Pro10 entry (and remove my LS56 > entry) as soon as I get that first moment - Friday is baby duty day ;-) With the original Pro10 entry still present I expect the software was matching against that before ever seeing the LS56 entry you created. Your new plan sounds good to me. > While I was easily able to build and install FFADO with the proper prefix, > I didn?t have the same success with Jack... For what it's worth there probably wouldn't have been any need to recompile jackd. If you compile FFADO and install it "over the top" of the version provided by your distribution ("PREFIX=/usr" usually) things should just work. In any case, I'm glad you got it sorted in the end. > By the way - the FFADO mixer - should I / do I need to install it? If so, > from reading the faq, I understand it as that I have to startup Jack > before I start the mixer, otherwise the mixer only identifies whether or > not there is a FFADO device attached. Is this correct? Ffado-mixer and the audio streaming system (jackd/ffado) operate pretty much independently. That is, you don't have to have one running in order to run the other. If there's an entry in the FAQ which makes people think otherwise we should fix that. Could you tell me exactly what part lead you to this conclusion? Put another way, you can run ffado-mixer with or without jackd running, and you can run jackd with or without ffado-mixer running. They don't depend on each other. Note that ffado-mixer uses ffado-dbus-server, so if ffado-dbus-server is not running when ffado-mixer starts it will be automatically started. ffado-dbus-server accepts dbus messages and drives the interface hardware. ffado-mixer is a GUI interface which sends dbus messages to ffado-dbus-server in response to user actions. This architecture was chosen to separate the hardware interface code (in ffado-dbus-server) from the GUI mixer code (in ffado-mixer). Although it's never been done to my knowledge, this makes the device control accessible to other programs (in addition to ffado-mixer) if any were to be written. Note that with the LS56, ffado-mixer will only present device controls which are made available via the standard DICE platform. These do not include any Liquid channel controls as far as I know, which are (as mentioned earlier) controlled using vendor specific extensions which we have no documentation for. Regards jonathan |
|
From: Stefan R. <st...@s5...> - 2014-06-13 07:01:11
|
On Jun 13 Eric Klinger wrote: > By the way - the FFADO mixer - should I / do I need to install it? > If so, from reading the faq, I understand it as that I have to > startup Jack before I start the mixer, otherwise the mixer only > identifies whether or not there is a FFADO device attached. Is > this correct? Quoting the FAQ: ---- 8< ---- Submitted by ppalmers on Fri, 07/04/2008 - 08:37. Q: I started ffadomixer and it shows a control panel, but the controls don't seem to work. A: The control panel for the Saffire devices only works when the device is streaming. In other words: jackd (or another ffado client) has to be running before the control panel will work. This is a hardware-side choice of Focusrite. ---- >8 ---- This looks outdated or/and incomplete to me. In *general*, i.e. across a wide range of different device types, ffado-mixer and jackd run independently of each other, although ffado-mixer's ability to control some of the device properties depend on the streaming state of the device. For example, the device generally won't let you switch to a different clock source while streaming is on. Now, the FAQ entry says it was the other way around. I *suppose* that the older BeBoB based Saffires had this property that the controls wouldn't work while streaming is down. But at least in case of the DICE based Saffire PRO 24, and I very much suspect in case of all DICE based Saffire models, it is the other way around: You can manipulate all device controls in ffado-mixer while streaming is down (i.e. jackd is not running), but you can manipulate only a (large) subset of the device controls while streaming is up (i.e. while jackd is running). A pro pos BeBoB: This latter style of interaction between ffado-mixer functionality and device streaming state --- i.e. the device can be fully controlled while streaming is down whereas some controls are inactive while streaming is up --- is also true for a BeBoB based device that I have, a Terratec one. -- Stefan Richter -=====-====- -==- -==-= http://arcgraph.de/sr/ |
|
From: Jonathan W. <jw...@ju...> - 2014-06-13 07:09:07
|
Hi Stefan On Fri, Jun 13, 2014 at 09:00:56AM +0200, Stefan Richter wrote: > Quoting the FAQ: > ---- 8< ---- > Submitted by ppalmers on Fri, 07/04/2008 - 08:37. > > Q: I started ffadomixer and it shows a control panel, but the controls > don't seem to work. > > A: The control panel for the Saffire devices only works when the device is > streaming. In other words: jackd (or another ffado client) has to be > running before the control panel will work. This is a hardware-side choice > of Focusrite. > ---- >8 ---- > > This looks outdated or/and incomplete to me. > > In *general*, i.e. across a wide range of different device types, > ffado-mixer and jackd run independently of each other ... Thanks for pointing this out. > Now, the FAQ entry says it was the other way around. I *suppose* that the > older BeBoB based Saffires had this property that the controls wouldn't > work while streaming is down. I was not aware of this; thank you for raising it. > But at least in case of the DICE based Saffire PRO 24, and I very much > suspect in case of all DICE based Saffire models, it is the other way > around: You can manipulate all device controls in ffado-mixer while > streaming is down (i.e. jackd is not running), but you can manipulate only > a (large) subset of the device controls while streaming is up (i.e. while > jackd is running). Your suspicion is correct as far as I can tell. As you said, the FAQ entry is outdated and should be changed to reflect the fact that the "ffado-mixer needs jackd" thing is really only true for a small subset of devices (namely, BeBoB-based Saffires). Regards jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-13 07:52:35
|
On Jun 13, 2014, at 9:08 AM, Jonathan Woithe <jw...@ju...> wrote: > Hi Stefan > > On Fri, Jun 13, 2014 at 09:00:56AM +0200, Stefan Richter wrote: >> Quoting the FAQ: >> ---- 8< ---- >> Submitted by ppalmers on Fri, 07/04/2008 - 08:37. >> >> Q: I started ffadomixer and it shows a control panel, but the controls >> don't seem to work. >> >> A: The control panel for the Saffire devices only works when the device is >> streaming. In other words: jackd (or another ffado client) has to be >> running before the control panel will work. This is a hardware-side choice >> of Focusrite. >> ---- >8 ---- >> >> This looks outdated or/and incomplete to me. >> >> In *general*, i.e. across a wide range of different device types, >> ffado-mixer and jackd run independently of each other ... > > Thanks for pointing this out. > >> Now, the FAQ entry says it was the other way around. I *suppose* that the >> older BeBoB based Saffires had this property that the controls wouldn't >> work while streaming is down. > > I was not aware of this; thank you for raising it. First, thank you Jonathan and Stefan. Your help is much appreciated! With the title being “Why doesn’t my mixer do anything else beside identify?” and the last sentences saying "The Focusrite Saffire devices only allow mixer and configuration changes when the audio streams are running. The hardware is simply designed this way. This means that jack (or any other ffado client) has to be running for configuration changes to have any effect.” just led me to think that the mixer needs Jack running before any changes can be made. Of course, it should be known that I have no idea what the mixer looks like other than the message stating that there aren’t any recognized devices attached (I don’t recall the exact message). Working or not, I have no idea what to expect, normally I use Mac/Pro Tools and any audio in Linux is totally brand new to me. So, my understanding at the moment is that without Jack running, I should be able to start the mixer and change sample rates, but then once jack is started I can change other parameters… not sure what - is there routing available? I realize that the Liquid Pre’s won’t work and in fact of all of my tests in the past, I prefer the stock pres to the Liquid ones anyway. I am not sure what will/won’t work on the LS56, there are 16 additional adar in/outs etc… my goal here, ultimately, is to get my 8 mic preamps in and out of Harrison Mixbus (and probably Ardour 3 as well). Everything else is “gravy” :-) - Mixbus’ operation is in my opinion, totally unusable in Mac… it runs nice in Windows and from my recent tests even better in Linux (having tried it on Debian 7.5 first) - Harrison has the absolute nicest sounding mixer I have ever heard in digital audio… something to do with their eq/comps/and tape saturation feature in combination with perhaps some proper dithering… not sure of the formula, just know I love it!… okay falling off track! Best, Eric > >> But at least in case of the DICE based Saffire PRO 24, and I very much >> suspect in case of all DICE based Saffire models, it is the other way >> around: You can manipulate all device controls in ffado-mixer while >> streaming is down (i.e. jackd is not running), but you can manipulate only >> a (large) subset of the device controls while streaming is up (i.e. while >> jackd is running). > > Your suspicion is correct as far as I can tell. As you said, the FAQ entry > is outdated and should be changed to reflect the fact that the "ffado-mixer > needs jackd" thing is really only true for a small subset of devices > (namely, BeBoB-based Saffires). > > Regards > jonathan |
|
From: Jonathan W. <jw...@ju...> - 2014-06-13 08:24:43
|
On Fri, Jun 13, 2014 at 09:52:22AM +0200, Eric Klinger wrote: > With the title being ?Why doesn?t my mixer do anything else beside > identify?? and the last sentences saying "The Focusrite Saffire devices > only allow mixer and configuration changes when the audio streams are > running. The hardware is simply designed this way. This means that jack > (or any other ffado client) has to be running for configuration changes to > have any effect.? just led me to think that the mixer needs Jack running > before any changes can be made. Yes, I can understand that. We clearly need to determine what the real situation is with different devices and edit the FAQ to reflect this. > Of course, it should be known that I have no idea what the mixer looks > like other than the message stating that there aren?t any recognized > devices attached (I don?t recall the exact message). With the configuration file tweak described by Phil you should not get this anymore. > Working or not, I have no idea what to expect, normally I use Mac/Pro > Tools and any audio in Linux is totally brand new to me. :-) Hopefully you'll find out soon enough. > So, my understanding at the moment is that without Jack running, I should > be able to start the mixer and change sample rates, but then once jack is > started I can change other parameters? Those "other parameters" will probably also be changeable when jackd isn't running. Things like sample rate (and other settings which determine things like the number of active channels) will be uneditable once jackd starts. > not sure what - is there routing available? I realize that the Liquid > Pre?s won?t work and in fact of all of my tests in the past, I prefer the > stock pres to the Liquid ones anyway. I don't know off-hand what the more recent DICE mixer code will do with the LS56. The best way to find out will be to try it and see. We will be interested to read about your findings. > I am not sure what will/won?t work on the LS56, there are 16 additional > adar in/outs etc? All audio ins and outs should be accessible via jackd. At least in theory. :-) Regards jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-12 12:08:38
|
On Jun 12, 2014, at 01:35 PM, Jörn Nettingsmeier <net...@st...> wrote: > On 06/12/2014 09:01 AM, Eric Klinger wrote: > > Greetings, > > I would love to get Jack and my FF LS56 to play nice together but so far I my efforts have been fruitless. Having read as much info as I could find on the Focusrite line in general, it seems users avoid the LS56 like the plague and there is a space needing filled in terms of info on this particular unit. If any devs are interested, please let me know what you need from me. > > > > In terms of user ability, I have used Linux for more than 10 years, though on and off, so while I am quite comfy at the command line, my general knowledge of shell tools and troubleshooting knowledge are quite low, so please be specific if telling me to perform anything. :-) > > > > Here is a bit about what I am using: > > HW: FF Liquid Saffire 56 > > Comp: HP Workstation xw4600 | 2.66 C2D | 4GB DDR667 > > SW: Debian 7.5, RT Kernel, FFADO 2.999.0, Jack 1.9.9 > > > > The error I receive from trying to connect to jackd is as follows: > > libffado 2.999.0- built Jun 28 2012 14:30:13 > > 00613107311: Error (focusrite_generic.cpp)[ 187] getSpecificValueARM: Could not read from node 0xFFC0 addr 0x000100000174 > > 00613107323: Error (focusrite_saffirepro.cpp)[ 421] updateClockSources: getSpecificValue failed > > firewire ERR: FFADO: Error creating virtual device > > Cannot attach audio driver > > > > Any help at all would be most appreciated! > > http://www.ffado.org/?q=node/2062 > > i've since sold mine in favour of a MADI setup, so i won't be able to > comment further, but the basic features used to work for me quite reliably. > > best, > > jörn Thank you, Jörn for the info. That was one of the first docs I cam across and I did add that info to the configuration file in both Debian and in AV Linux to no avail. But they were still both older releases. I have since fresh installed Fedora 20 to have a repo with more current packages. Fingers crossed! Best Regards, Eric |
|
From: Eric K. <eri...@ic...> - 2014-06-13 17:14:18
|
On Jun 13, 2014, at 10:24 AM, Jonathan Woithe <jw...@ju...> wrote: > On Fri, Jun 13, 2014 at 09:52:22AM +0200, Eric Klinger wrote: > > With the title being ?Why doesn?t my mixer do anything else beside > > identify?? and the last sentences saying "The Focusrite Saffire devices > > only allow mixer and configuration changes when the audio streams are > > running. The hardware is simply designed this way. This means that jack > > (or any other ffado client) has to be running for configuration changes to > > have any effect.? just led me to think that the mixer needs Jack running > > before any changes can be made. > > Yes, I can understand that. We clearly need to determine what the real > situation is with different devices and edit the FAQ to reflect this. > > > Of course, it should be known that I have no idea what the mixer looks > > like other than the message stating that there aren?t any recognized > > devices attached (I don?t recall the exact message). > > With the configuration file tweak described by Phil you should not get this > anymore. > > > Working or not, I have no idea what to expect, normally I use Mac/Pro > > Tools and any audio in Linux is totally brand new to me. > > :-) Hopefully you'll find out soon enough. > > > So, my understanding at the moment is that without Jack running, I should > > be able to start the mixer and change sample rates, but then once jack is > > started I can change other parameters? > > Those "other parameters" will probably also be changeable when jackd isn't > running. Things like sample rate (and other settings which determine things > like the number of active channels) will be uneditable once jackd starts. > > > not sure what - is there routing available? I realize that the Liquid > > Pre?s won?t work and in fact of all of my tests in the past, I prefer the > > stock pres to the Liquid ones anyway. > > I don't know off-hand what the more recent DICE mixer code will do with the > LS56. The best way to find out will be to try it and see. We will be > interested to read about your findings. > > > I am not sure what will/won?t work on the LS56, there are 16 additional > > adar in/outs etc? > > All audio ins and outs should be accessible via jackd. At least in > theory. :-) > > Regards > jonathan Update - So, I added the updates to the Pro10IO to reflect my LS56. Nothing changed. So I recompiled FFADO with an already changed configuration file in the src compile directory and rebooted. Now the mixer shows the Focusrite (yeah!!!!) and I sent the info/registration that was requested. Now in Jack, I am unable to start Jack with Qjackctl, but it starts from the command line using; jackd -d firewire -r 48000 -p 512 So I am sending this email and can't wait to play around with Mixbus!!! Will report back soon! Thanks so much! Best, Eric |
|
From: Jonathan W. <jw...@ju...> - 2014-06-14 12:20:15
|
Hi Eric On Fri, Jun 13, 2014 at 05:14:05PM +0000, Eric Klinger wrote: > So, I added the updates to the Pro10IO to reflect my LS56. Nothing > changed. So I recompiled FFADO with an already changed configuration file > in the src compile directory and rebooted. Now the mixer shows the > Focusrite (yeah!!!!) and I sent the info/registration that was requested. Hmm. Changes to the configuration file do not require that libffado be recompiled - it is a static file which is only read by libffado on startup. The contents of this file do not affect the code compilation in any way. The above behaviour suggests that perhaps there is a FFADO configuration file left on the system by some other version of FFADO and that you changed that one, leaving the currently used one (in some other directory) unchanged. Regardless, it is good that with the correct configuration entry your LS56 is recognised. > Now in Jack, I am unable to start Jack with Qjackctl, but it starts from > the command line using; > > jackd -d firewire -r 48000 -p 512 I can't comment on qjackctl issues since I don't use it myself. My only guess (which is totally uninformed) is if qjackctl relies on jack-dbus support and if you're using a self-compiled jackd which doesn't include dbus support then this could explain the inability of qjackctl to start jackd. Do you receive any error message from qjackctl? If you select the ALSA backend in qjackctl does jack start? If you have issues running jackd as above you might like to try adding "-n 3". I think the jackd default is "-n 2", and this is sometimes a little tight for firewire interfaces. Regards jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-13 19:24:50
|
On Jun 13, 2014, at 07:14 PM, Eric Klinger <eri...@ic...> wrote: > > On Jun 13, 2014, at 10:24 AM, Jonathan Woithe <jw...@ju... > wrote: > > > On Fri, Jun 13, 2014 at 09:52:22AM +0200, Eric Klinger wrote: > > > With the title being ?Why doesn?t my mixer do anything else beside > > > identify?? and the last sentences saying "The Focusrite Saffire devices > > > only allow mixer and configuration changes when the audio streams are > > > running. The hardware is simply designed this way. This means that jack > > > (or any other ffado client) has to be running for configuration changes to > > > have any effect.? just led me to think that the mixer needs Jack running > > > before any changes can be made. > > > > Yes, I can understand that. We clearly need to determine what the real > > situation is with different devices and edit the FAQ to reflect this. > > > > > Of course, it should be known that I have no idea what the mixer looks > > > like other than the message stating that there aren?t any recognized > > > devices attached (I don?t recall the exact message). > > > > With the configuration file tweak described by Phil you should not get this > > anymore. > > > > > Working or not, I have no idea what to expect, normally I use Mac/Pro > > > Tools and any audio in Linux is totally brand new to me. > > > > :-) Hopefully you'll find out soon enough. > > > > > So, my understanding at the moment is that without Jack running, I should > > > be able to start the mixer and change sample rates, but then once jack is > > > started I can change other parameters? > > > > Those "other parameters" will probably also be changeable when jackd isn't > > running. Things like sample rate (and other settings which determine things > > like the number of active channels) will be uneditable once jackd starts. > > > > > not sure what - is there routing available? I realize that the Liquid > > > Pre?s won?t work and in fact of all of my tests in the past, I prefer the > > > stock pres to the Liquid ones anyway. > > > > I don't know off-hand what the more recent DICE mixer code will do with the > > LS56. The best way to find out will be to try it and see. We will be > > interested to read about your findings. > > > > > I am not sure what will/won?t work on the LS56, there are 16 additional > > > adar in/outs etc? > > > > All audio ins and outs should be accessible via jackd. At least in > > theory. :-) > > > > Regards > > jonathan > > > > Update - > > So, I added the updates to the Pro10IO to reflect my LS56. Nothing changed. So I recompiled FFADO with an already changed configuration file in the src compile directory and rebooted. Now the mixer shows the Focusrite (yeah!!!!) and I sent the info/registration that was requested. > > Now in Jack, I am unable to start Jack with Qjackctl, but it starts from the command line using; > > jackd -d firewire -r 48000 -p 512 > > So I am sending this email and can't wait to play around with Mixbus!!! > > Will report back soon! > > Thanks so much! > > Best, > > Eric progress report. I have not had any luck getting Jack started at all outside of root (must have been what I did above) - so I have yet to hear any audio come out yet. The FFADO mixer seems to recognize the unit fine - though I must say I am quite confused by it - is there perhaps a manual for it somewhere :-)? My current errors are: JACK server starting in realtime mode with priority 70 1402686896234672: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1- built Jun 13 2014 18:17:09 1402686896238790: [31mError (PosixThread.cpp)[ 161] Start: Cannot create realtime thread (1: Operation not permitted) [0m1402686896238913: [31mError (PosixThread.cpp)[ 162] Start: priority: 75 [0mfirewire ERR: FFADO: Error creating virtual device Cannot attach audio driver JackServer::Open failed with -1 I will be researching as much as I can in the meantime. Once again, thank you guys for getting me this far!! Best Regards, Eric |
|
From: Phil/La P. W. of P. <ph...@la...> - 2014-06-13 19:56:21
|
Hi Eric, Le vendredi 13 juin 2014 à 19:24 +0000, Eric Klinger a écrit : > On Jun 13, 2014, at 07:14 PM, Eric Klinger <eri...@ic...> wrote: > > > > > On Jun 13, 2014, at 10:24 AM, Jonathan Woithe <jw...@ju... > wrote: > > > > > On Fri, Jun 13, 2014 at 09:52:22AM +0200, Eric Klinger wrote: > > > > With the title being ?Why doesn?t my mixer do anything else beside > > > > identify?? and the last sentences saying "The Focusrite Saffire devices > > > > only allow mixer and configuration changes when the audio streams are > > > > running. The hardware is simply designed this way. This means that jack > > > > (or any other ffado client) has to be running for configuration changes to > > > > have any effect.? just led me to think that the mixer needs Jack running > > > > before any changes can be made. > > > > > > Yes, I can understand that. We clearly need to determine what the real > > > situation is with different devices and edit the FAQ to reflect this. > > > > > > > Of course, it should be known that I have no idea what the mixer looks > > > > like other than the message stating that there aren?t any recognized > > > > devices attached (I don?t recall the exact message). > > > > > > With the configuration file tweak described by Phil you should not get this > > > anymore. > > > > > > > Working or not, I have no idea what to expect, normally I use Mac/Pro > > > > Tools and any audio in Linux is totally brand new to me. > > > > > > :-) Hopefully you'll find out soon enough. > > > > > > > So, my understanding at the moment is that without Jack running, I should > > > > be able to start the mixer and change sample rates, but then once jack is > > > > started I can change other parameters? > > > > > > Those "other parameters" will probably also be changeable when jackd isn't > > > running. Things like sample rate (and other settings which determine things > > > like the number of active channels) will be uneditable once jackd starts. > > > > > > > not sure what - is there routing available? I realize that the Liquid > > > > Pre?s won?t work and in fact of all of my tests in the past, I prefer the > > > > stock pres to the Liquid ones anyway. > > > > > > I don't know off-hand what the more recent DICE mixer code will do with the > > > LS56. The best way to find out will be to try it and see. We will be > > > interested to read about your findings. > > > > > > > I am not sure what will/won?t work on the LS56, there are 16 additional > > > > adar in/outs etc? > > > > > > All audio ins and outs should be accessible via jackd. At least in > > > theory. :-) > > > > > > Regards > > > jonathan > > > > > > > > Update - > > > > So, I added the updates to the Pro10IO to reflect my LS56. Nothing changed. So I recompiled FFADO with an already changed configuration file in the src compile directory and rebooted. Now the mixer shows the Focusrite (yeah!!!!) and I sent the info/registration that was requested. > > > > Now in Jack, I am unable to start Jack with Qjackctl, but it starts from the command line using; > > > > jackd -d firewire -r 48000 -p 512 > > > > So I am sending this email and can't wait to play around with Mixbus!!! > > > > Will report back soon! > > > > Thanks so much! > > > > Best, > > > > Eric > > > > progress report. > > I have not had any luck getting Jack started at all outside of root (must have been what I did above) - so I have yet to hear any audio come out yet. The FFADO mixer seems to recognize the unit fine - though I must say I am quite confused by it - is there perhaps a manual for it somewhere :-)? As you are compiling, why not 2.2.1 ? The mixer would be more friendly. > > My current errors are: > > JACK server starting in realtime mode with priority 70 > > 1402686896234672: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1- built Jun 13 2014 18:17:09 > > 1402686896238790: [31mError (PosixThread.cpp)[ 161] Start: Cannot create realtime thread (1: Operation not permitted) > You should be a member of the jackuser group under Fedora (and whatever, join also the audio group). Have a look to the /etc/security/limits.d/95-jack.conf to see if your priority level is suitable: you should have something like rtprio 99. > [0m1402686896238913: [31mError (PosixThread.cpp)[ 162] Start: priority: 75 > > [0mfirewire ERR: FFADO: Error creating virtual device > > Cannot attach audio driver > > JackServer::Open failed with -1 > > > I will be researching as much as I can in the meantime. > > Once again, thank you guys for getting me this far!! > > > Best Regards, > > Eric Best regards, Phil |
|
From: Eric K. <eri...@ic...> - 2014-06-14 06:56:51
|
Hi Phil.
Good news!
On Jun 13, 2014, at 9:56 PM, Phil/La Page Web of Phil <ph...@la...> wrote:
> Hi Eric,
>
> Le vendredi 13 juin 2014 à 19:24 +0000, Eric Klinger a écrit :
>>
>> On Jun 13, 2014, at 07:14 PM, Eric Klinger <eri...@ic...> wrote:
>>
>> >
>> > On Jun 13, 2014, at 10:24 AM, Jonathan Woithe <jw...@ju... > wrote:
>> >
>> > > On Fri, Jun 13, 2014 at 09:52:22AM +0200, Eric Klinger wrote:
>> > > > With the title being ?Why doesn?t my mixer do anything else beside
>> > > > identify?? and the last sentences saying "The Focusrite Saffire devices
>> > > > only allow mixer and configuration changes when the audio streams are
>> > > > running. The hardware is simply designed this way. This means that jack
>> > > > (or any other ffado client) has to be running for configuration changes to
>> > > > have any effect.? just led me to think that the mixer needs Jack running
>> > > > before any changes can be made.
>> > >
>> > > Yes, I can understand that. We clearly need to determine what the real
>> > > situation is with different devices and edit the FAQ to reflect this.
>> > >
>> > > > Of course, it should be known that I have no idea what the mixer looks
>> > > > like other than the message stating that there aren?t any recognized
>> > > > devices attached (I don?t recall the exact message).
>> > >
>> > > With the configuration file tweak described by Phil you should not get this
>> > > anymore.
>> > >
>> > > > Working or not, I have no idea what to expect, normally I use Mac/Pro
>> > > > Tools and any audio in Linux is totally brand new to me.
>> > >
>> > > :-) Hopefully you'll find out soon enough.
>> > >
>> > > > So, my understanding at the moment is that without Jack running, I should
>> > > > be able to start the mixer and change sample rates, but then once jack is
>> > > > started I can change other parameters?
>> > >
>> > > Those "other parameters" will probably also be changeable when jackd isn't
>> > > running. Things like sample rate (and other settings which determine things
>> > > like the number of active channels) will be uneditable once jackd starts.
>> > >
>> > > > not sure what - is there routing available? I realize that the Liquid
>> > > > Pre?s won?t work and in fact of all of my tests in the past, I prefer the
>> > > > stock pres to the Liquid ones anyway.
>> > >
>> > > I don't know off-hand what the more recent DICE mixer code will do with the
>> > > LS56. The best way to find out will be to try it and see. We will be
>> > > interested to read about your findings.
>> > >
>> > > > I am not sure what will/won?t work on the LS56, there are 16 additional
>> > > > adar in/outs etc?
>> > >
>> > > All audio ins and outs should be accessible via jackd. At least in
>> > > theory. :-)
>> > >
>> > > Regards
>> > > jonathan
>> >
>> >
>> >
>> > Update -
>> >
>> > So, I added the updates to the Pro10IO to reflect my LS56. Nothing changed. So I recompiled FFADO with an already changed configuration file in the src compile directory and rebooted. Now the mixer shows the Focusrite (yeah!!!!) and I sent the info/registration that was requested.
>> >
>> > Now in Jack, I am unable to start Jack with Qjackctl, but it starts from the command line using;
>> >
>> > jackd -d firewire -r 48000 -p 512
>> >
>> > So I am sending this email and can't wait to play around with Mixbus!!!
>> >
>> > Will report back soon!
>> >
>> > Thanks so much!
>> >
>> > Best,
>> >
>> > Eric
>>
>>
>>
>> progress report.
>>
>> I have not had any luck getting Jack started at all outside of root (must have been what I did above) - so I have yet to hear any audio come out yet. The FFADO mixer seems to recognize the unit fine - though I must say I am quite confused by it - is there perhaps a manual for it somewhere :-)?
> As you are compiling, why not 2.2.1 ? The mixer would be more friendly.
>
I tried and tried to fulfill all of the dependencies, and I feel confident that I did, but no matter what I did I couldn’t get the mixer to compile, I always received the message
"I couldn't find all the prerequisites ('pyuic4' and the python-modules 'dbus'
and 'PyQt4', the packages could be named like dbus-python and PyQt) to build the
mixer.
Therefor the qt4 mixer will not get installed."
The only way I could see to get the mixer up to date was to install the unstable testing branch for Fedora (version, 21 - Jessie) this loaded up libffado 2.2.1 along with 1 GB of other updated packages. Then I ended up recompiling over top again with the prefix setting and with all of the updated packages the mixer re-compiled to 2.2.1 - and yes, there is a HUGE difference in mixers from 2.2.0 to 2.2.1 - thanks for that tip!
>> My current errors are:
>>
>> JACK server starting in realtime mode with priority 70
>>
>> 1402686896234672: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1- built Jun 13 2014 18:17:09
>>
>> 1402686896238790: [31mError (PosixThread.cpp)[ 161] Start: Cannot create realtime thread (1: Operation not permitted)
>>
> You should be a member of the jackuser group under Fedora (and whatever, join also the audio group).
> Have a look to the /etc/security/limits.d/95-jack.conf to see if your priority level is suitable: you should have something like rtprio 99.
And this is how it finally worked, I changed the priority level from 70 to 99 and it worked, though it was in mono, no matter what I did - that is until I upgraded to Fedora 21 (see above). At the moment everything seems to work great - at least for playback - I have yet to try and get any analog audio through the LS56 into Mixbus. That will be my job for today!
>
>> [0m1402686896238913: [31mError (PosixThread.cpp)[ 162] Start: priority: 75
>>
>> [0mfirewire ERR: FFADO: Error creating virtual device
>>
>> Cannot attach audio driver
>>
>> JackServer::Open failed with -1
>>
>>
>> I will be researching as much as I can in the meantime.
>>
>> Once again, thank you guys for getting me this far!!
>>
>>
>> Best Regards,
>>
>> Eric
>
> Best regards,
>
> Phil
Have I said thank you? I can’t say it enough, Thanks very much.
Best Regards,
Eric
|
|
From: Stefan R. <st...@s5...> - 2014-06-14 07:58:21
|
On Jun 13 Phil/La Page Web of Phil wrote: > You should be a member of the jackuser group under Fedora (and whatever, > join also the audio group). > Have a look to the /etc/security/limits.d/95-jack.conf to see if your > priority level is suitable: you should have something like rtprio 99. ...and memlock unlimited. https://web.archive.org/web/20140330103313/http://jackaudio.org/linux_rt_config Also, an almost trivial point but which is easily overlooked: After group membership of a user or realtime privileges of a group were modified, those changes are only applied once the user logs in newly. I.e., best quit the X session and log into a new one; or as a minimum use "su --login username" in a terminal to get a commandline with the fresh new privileges. -- Stefan Richter -=====-====- -==- -===- http://arcgraph.de/sr/ |
|
From: Phil/La P. W. of P. <ph...@la...> - 2014-06-14 15:08:20
|
Le samedi 14 juin 2014 à 09:58 +0200, Stefan Richter a écrit : > On Jun 13 Phil/La Page Web of Phil wrote: > > You should be a member of the jackuser group under Fedora (and whatever, > > join also the audio group). > > Have a look to the /etc/security/limits.d/95-jack.conf to see if your > > priority level is suitable: you should have something like rtprio 99. > > ...and memlock unlimited. > https://web.archive.org/web/20140330103313/http://jackaudio.org/linux_rt_config > > Also, an almost trivial point but which is easily overlooked: After > group membership of a user or realtime privileges of a group were > modified, those changes are only applied once the user logs in newly. > I.e., best quit the X session and log into a new one; or as a minimum use > "su --login username" in a terminal to get a commandline with the fresh > new privileges. Yes, nice to recall these points. Regards, Phil |
|
From: Jonathan W. <jw...@ju...> - 2014-06-14 12:25:51
|
Hi Eric On Fri, Jun 13, 2014 at 07:24:41PM +0000, Eric Klinger wrote: > progress report. > > I have not had any luck getting Jack started at all outside of root (must > have been what I did above) - so I have yet to hear any audio come out > yet. The FFADO mixer seems to recognize the unit fine - though I must say > I am quite confused by it - is there perhaps a manual for it somewhere > :-)? Later emails suggested that ffado-mixer was an older version. That probably explains part of the mixer's interesting appearance. Having said that, you will be using a generic mixer so it's possible some of it will be a bit strange. As Phil said though, the 2.2.1 mixer will be better than the 2.1.0 one. > JACK server starting in realtime mode with priority 70 > 1402686896234672: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.2.1- built Jun 13 2014 18:17:09 > 1402686896238790: [31mError (PosixThread.cpp)[ 161] Start: Cannot create realtime thread (1: Operation not permitted) This is at least part of the problem. It seems your user doesn't have permission to activate realtime threads. Regards jonathan |
|
From: Eric K. <eri...@ic...> - 2014-06-15 10:33:12
|
Hi Guys On Jun 14, 2014, at 5:08 PM, Phil/La Page Web of Phil <ph...@la...> wrote: > Le samedi 14 juin 2014 à 09:58 +0200, Stefan Richter a écrit : >> >> On Jun 13 Phil/La Page Web of Phil wrote: >> > You should be a member of the jackuser group under Fedora (and whatever, >> > join also the audio group). >> > Have a look to the /etc/security/limits.d/95-jack.conf to see if your >> > priority level is suitable: you should have something like rtprio 99. >> >> ...and memlock unlimited. >> https://web.archive.org/web/20140330103313/http://jackaudio.org/linux_rt_config HA - it’s a cached page of Jack! I was hoping to come across one, unfortunately Google’s cached page is of the same thing - and so much going on I didn’t look very far into it. Glad to have it though - I want to read up on the Linux implementation of it. Speaking of the Jack website being down, I am a pretty good web developer should the group ever need one. As an aside - I am also quite good with graphics, writing tutorials, writing documentation in ways that beginners can understand, etc. >> >> Also, an almost trivial point but which is easily overlooked: After >> group membership of a user or realtime privileges of a group were >> modified, those changes are only applied once the user logs in newly. >> I.e., best quit the X session and log into a new one; or as a minimum use >> "su --login username" in a terminal to get a commandline with the fresh >> new privileges. > Yes, nice to recall these points. > > Regards, > > Phil Back to the task(s) at hand. In previous emails I spoke of attempting to compile the mixer etc and it not working. I have to remember that I often must restart the machine to allow new installs etc a chance to have a fresh login. Also when changing user mod settings. So the fact was everything was quite fine earlier on than I expected, I just never restarted the machine. (dolt!) Another idiotic thing I was trying to do was trying to satisfy dependencies at the ‘scons install' part of the installation. I never recompiled after satisfying reps. Later I found out that was another huge mistake on my part. So at this point my memlock is set (this was by default) to the amount of ram installed - which was 4GB, but I will set to unlimited anyway as I plan to upgrade to 8GB soon anyway. And changing priority to 99 for the jackuser made a huge difference as well (could finally start jackd). ALSO, having a few drives laying around with different distress installed - Debian, Fedora, AV Linux - I prefer Fedora. AV Linux was by far the easiest to set up quickly, obviously it has everything there already and updating to the latest libffado was super easy. I like Fedora though because then I can only install what I want, but on my system, Fedora was impossible to use with the ccrma rt kernel. Once that was installed it was easy sailing. So at this point I think we can call this a case closed ordeal :-) Next is figuring out the mixer - I see how the matrix works etc - it’s the naming that confuses my… like AES (why 8 or those?), MixerIn, MixerOut… etc - how they relate to the physical analog/digital in/outs is in need of a translation for my brain. Thanks everyone for an enjoyable time! (I like to figure things out :-) ) Best Regards, Eric |
Thanks for helping keep SourceForge clean.
X