16 Oct
2006
16 Oct
'06
8:34 p.m.
Hi
I'm interested in a 8-ch in sound card with preamps. Does anyone know if
the Focusrite Saffire Pro 26 I/O is working under linux? Seems like a
nice price...
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
16 Oct
16 Oct
9:33 p.m.
Atte,
Since it's 1394-based you'll find the best info on the FreeBob list.
Good luck,
Mark
On 10/16/06, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
Hi
I'm interested in a 8-ch in sound card with preamps. Does anyone know if
the Focusrite Saffire Pro 26 I/O is working under linux? Seems like a
nice price...
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
17 Oct
17 Oct
2:33 p.m.
I've got one of these and have been experementing, so far i've managed
to get it to play through the analog outs, but haven't got further in
my testing then that so not sure if recording or the digital stuff
works. I'd guess that recording will and ADAT etc.. wont as you have
to use the control panel to get at these under xp/osx but that is a
complete guess. Don't have time to fiddle right now but will keep you
posted.
On 16/10/06, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
Hi
I'm interested in a 8-ch in sound card with preamps. Does anyone know if
the Focusrite Saffire Pro 26 I/O is working under linux? Seems like a
nice price...
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
5:08 p.m.
Richard Taylor wrote:
<snip> Don't have time to fiddle right now
but will keep you
posted.
Thanks for the info. Sounds promissing. Looking forward to hear about
further investigations.
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
25 Oct
25 Oct
6:18 p.m.
Good news and bad news. Good news, recording does work.
Bad news, zero latency monitoring comes on by default and routes
itself to all the analog outputs so it's a bit useless really.
Maybe there's a setting somewhere i've missed - definately nothing
connected in jack tho.
On 17/10/06, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
Richard Taylor wrote:
<snip> Don't have time to fiddle right
now but will keep you
posted.
Thanks for the info. Sounds promissing. Looking forward to hear about
further investigations.
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
26 Oct
26 Oct
6:36 a.m.
Richard Taylor wrote:
Good news and bad news. Good news, recording does
work.
Bad news, zero latency monitoring comes on by default and routes
itself to all the analog outputs so it's a bit useless really.
Maybe there's a setting somewhere i've missed - definately nothing
connected in jack tho.
There might be a chance that the device remembers the last
mixer setting
on startup. So you what you can try is setting the mixer on a windows
machine (if you have one available) and see if it's settings are
retained on power cycles. The other option is to wait until we finish
the mixer control. I know that the current code already contains most of
the infrastructure to support this, but it's not finished. The
difficulty (and opportunity) is that the interface is the same for all
bebob devices, requiring it to be very flexible and hence pretty
complicated. Daniel is the expert on this, maybe he can shed a light
here. Maybe it's not very complicated to have a temporary tool that
kills all zero-latency monitoring paths.
Greets,
Pieter
On 17/10/06, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
> Richard Taylor wrote:
>
> > <snip> Don't have time to fiddle right now but will keep you
> > posted.
>
> Thanks for the info. Sounds promissing. Looking forward to hear about
> further investigations.
>
> --
> peace, love & harmony
> Atte
>
> http://www.atte.dk | quintet: http://www.anagrammer.dk
> | compositions: http://www.atte.dk/compositions
>
1:18 p.m.
New subject: [Freebob-devel] [linux-audio-user] Focusrite Saffire Pro 26 I/O
There might be a chance that the device remembers the
last mixer setting
on startup. So you what you can try is setting the mixer on a windows
machine (if you have one available) and see if it's settings are
retained on power cycles.
I don't think it does as I generally have monitoring turned off in
windows and have been flitting between that and linux throughout my
experements. I'll double-check when I'm back at home. I'll also mess
with the standalone mode setting as i think one of those does remember
the last configuration, so there's a vague chance that it will also
mess with the defaults in non-standalone mode.
The other option is to wait until we finish
the mixer control. I know that the current code already contains most of
the infrastructure to support this, but it's not finished. The
difficulty (and opportunity) is that the interface is the same for all
bebob devices, requiring it to be very flexible and hence pretty
complicated. Daniel is the expert on this, maybe he can shed a light
here. Maybe it's not very complicated to have a temporary tool that
kills all zero-latency monitoring paths.
Exciting news about the freebob mixer stuff, I hadn't realised this
was allready well under way. Will keep my eyes peeled.
Additional good news, bad news - Phantom power is not switchable from
the front panel unless you are in standalone mode. Once the unit has
gone into this mode you can't boot jack until you power cycle the
saffire, which switches the phantom power off.
Pretty bad news as I imagine phantom power switching is a focusrite
not a bebob feature so freebob is unlikely to support it (correct me
if i'm wrong)
Good news is that the focusrite tech support people were quite
understanding and agreed to forward my concerns to their dev team to
see if they could get some sort of solution worked out. No promises of
course, but i was pleasantly surprised to see that they appeared open
to the idea, and it was nice to encounter tech support that not only
reads emails but responds to them intelligently.
Had a brief flutter with smaller latencies last night, seemed to be
pretty stable in realtime mode. The only xrun i got was when i was
booting SuperCollider's server, however I *really* knew about it, very
loud, fairly long noise burst. The saffire has an assignable volume
control which isn't assigned to anything by default so it came out as
full scale nastiness. Thankfully i have the sensitivity of my monitors
tuned down as far as they go or i could have been collecting my
tweeters from the opposite side of the room. Serves me right really,
it was a bit idiotic to have them connected when testing something
like this, but just thought I'd warn everyone else. My girlfriend
heard the burst and thought I'd electricuted myself.. :)
Front panel headphone controls work so you can safely test via these
without ear damage.
Anyway, i digress - I didn't tax my computer that much and only went
down to 128 samples/period, but i'm pretty optomistic on the latency
front.
Still not tried any of the digital gubbins yet - that's my next stop..
27 Oct
27 Oct
4:30 a.m.
New subject: [Freebob-devel] [linux-audio-user] Focusrite Saffire Pro 26 I/O
Pieter Palmers wrote:
Richard Taylor wrote:
Unfortunately, I'm not familiar with the Saffire. I can't tell if the
box remembers the settings through out. Each BeBoB device seems to be a
bit different in respect to those things. Well, I guess this is called
customization :)
We face two main problems. First, we want to support mixer settings.
This can be achieved with a generic approach. The AV/C function block
which represents the mixer is most likely a bridgeco extension. So we
can write a generic piece of code for that.
Second, the additional switches and knobs etc which are [bridgeco's]
customers extensions. Normally, they are controlled over proprietary
AV/C extension or over the so called hispeed control interface, IRC. We
need some support from the manufactures to tell us how to control those
features and then we have to come up with some (generic?) control panel.
We have talked about the first problem and have agreed on some initial
steps to achieve it. I will implement the AV/C stuff but that is the
simple part. We (or better I) are still not sure how to abstract the
generic interface. I remember some discussion here but can't remember
the findings. Of course we need a GUI. We also got some inputs from lad
where this problem of a generic mixer was also a topic. It seems that a
form of a generic mixer is interesting for other projects besides freebob.
I haven't started to work on the mixer code since I'm still trying to
figure out how to support the m-audio fw410. I reckon there are many
users of fw410 around. The bad news is that it is rather broken device
and it is difficult to get it working. There are some notes [1] about my
undertaking but I don't know if this is worth spending more time on it.
Anyway the next thing I will work on caching the AV/C models in order to
speed up the device discovering. That means the mixer has to wait for a
while if I'm doing this.
Apropos zero latency: There is no such thing as zero latency for a BeBoB
device. You will always have a delay from the input to the output even
though it is routed entirely through the device. I don't have the
numbers and I can't tell if this is a problem or not but I just wanted
to point that out before too many are really disappointed about that fact.
cheers,
daniel
[1] http://freebob.sourceforge.net/index.php/FW410
Good news and bad news. Good news, recording does
work.
Bad news, zero latency monitoring comes on by default and routes
itself to all the analog outputs so it's a bit useless really.
Maybe there's a setting somewhere i've missed - definately nothing
connected in jack tho.
There might be a chance that the device remembers the last
mixer setting
on startup. So you what you can try is setting the mixer on a windows
machine (if you have one available) and see if it's settings are
retained on power cycles. The other option is to wait until we finish
the mixer control. I know that the current code already contains most of
the infrastructure to support this, but it's not finished. The
difficulty (and opportunity) is that the interface is the same for all
bebob devices, requiring it to be very flexible and hence pretty
complicated. Daniel is the expert on this, maybe he can shed a light
here. Maybe it's not very complicated to have a temporary tool that
kills all zero-latency monitoring paths.
6399
days inactive
6410
days old
linux-audio-user@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Atte André Jensen -
Daniel Wagner -
Mark Knecht -
Pieter Palmers -
Richard Taylor