 
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
|
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
74.69.242.210
I couldn't find any supporting info on the web, but I tried it just for the halibut. There is no mixer support, but playback via jackd on a realtime kernel works well at whatever sampling rate I tried. Now I can go back to using MPD.
Follow Ups:
I REALLY REALLY need to know..........REALLY!!!!!!!
PLEASE!!!!
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
Well,
I am running Mint on this particular machine.
I think the first thing I did was install the libffado0 and libffado-dev packages via the synaptic package manager.
I built jack-1.9.3 from source also, so that it would find libffado and enable firewire support, but you might just check to see if the prebuilt package supports it.
If you need to build jack from source, download jack-1.9.3.tar.bz2 then open a terminal and cd to the directory you downloaded to and run the following commands:
tar xjvf jack-1.9.3.tar.bz2
cd jack-1.9.3/
./waf configure --prefix=/usr
./waf build
sudo ./waf install
To start jackd with the firewire output, run something like the following from the command line:
jackd -d firewire -r 44100
If you install qjackctl, you can configure and start jack from a user interface instead of the command line.
I also built qjackctl from source after building jack, which was a pain because I had to install a bunch of qt libraries. QJackctl is not necessary but makes it easy to change routing and add ladspa plugins into the mix if you desire.
Anyway, I started jackd with the firewire output and the proper sampling rate, fired up aqualung, and it just worked.
If you are going to try to this and have specific questions, I'll be happy to answer any. This is my first trial with FFADO, so I need to do some more research as to whether anything other than jack supports it.
Alan
P.S. Looks like Jack is now at version 1.9.4 instead of 1.9.3
hey aljordan & users of Jack
I´ve been a very, sometimes happy and sometimes very frustrated user of JACK.
I´m very grateful for the usefulness of getting ASIO driven applications (like cPlay) connected with allocator (digital crossover). since cPlay has been equipped with a VST output, the JACK is obsolete in my system. -this has also enabled me to implement cMP so my audio experience in this regard is from JACK to noJACK and cMP, but the sonic improvement has been significant.
would not be able to quantify the share of degradation caused by JACK, but it´s sheer complicated setup would let me guess : quite considerable.....
or said in other words, I consider JACK a extremely useful application for high quality playback, but not ideal. for real highend it will just apply a little bit of "digital" sound (read jitter) and should be ultimately be avoided.....
especially when used in context with high performance gear !
sorry to be a showstopper.
Hi Play-mate,
Ryelands tried some experiments with netjack and had bad results under Windows. As a follow-up experiment, I implemented jack under Linux and under Windows XP on the same box. Jack sounds like crap under Windows, but sounds good under Linux. Maybe its that the underlying audio driver is different under each operating system.
Alan
and should be ultimately be avoided.....
especially when used in context with high performance gear !sorry to be a showstopper.
No problem play-mate, my gear is crap...I cant tell if jitter increases or not.
:-)
Either way, I still can't get the damn thing to work! But then it took me more than a year to get digital out of my motherboard's spdif. So I guess look for a Whohooo post from me sometime in 2011 concerning FFADO...:-(
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
Edits: 12/20/09 12/20/09
Were you able to build Jack from source?
yes I built from source, no errors either. Afterwards I installed qjackctl and made a output and input
Should I see jack when I do a aplay -L
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
A couple more things of note:
1) Even if you aren't running a realtime kernel, setting the realtime flag in qjackctl (or -R command line) makes a difference. On my lesser computer, I was getting xruns without realtime set even though I am not running a realtime kernel.
2) Whoever is starting Jackd has to have permissions to the device file /dev/raw1394. You can do this in a terminal window by typing:
sudo chmod o+wr /dev/raw1394
Good luck,
Alan
I don't think you should see anything in aplay because aplay is ALSA specific, and FFADO does not yet work with ALSA.After setting the JACK settings in qjackctl, you have to start the jack audio server by pressing the start button in qjackctl. If it is running properly, qjackctl will give some cpu percentage statistics in its main window. You can also open the messages window to see what is happening.
I've attached a screen grab of the settings in qjackctl for firewire. If you are not running a realtime kernel uncheck the realtime setting.
The following command line will also start jackd, and any error message should be printed out to the console window if it fails, if you don't want to use qjackctl.
jackd -R -d firewire -r 44100 &
Leave out -R if you are not using a realtime kernel.
Under jack, the same user that starts jackd also has to start the audio app that is accessing jack. So, if jackd starts properly, try something that definitely supports the jack output, like aqualung, but you have to specifically set the aqualung settings to use the jack output. MPD also has a jack output, so I'd be happy to pass along a configuration for that once you get it working with aqualung.
Alan
Edits: 12/20/09 12/20/09
Al
Yes I am running a rt kernel
I get this error when I start qjack
12:20:45.958 Patchbay activated.
12:20:45.972 Statistics reset.
12:20:45.988 Startup script...
12:20:45.989 artsshell -q terminate
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:20:46.001 ALSA connection graph change.
sh: artsshell: not found
12:20:46.508 Startup script terminated with exit status=32512.
12:20:46.508 JACK is starting...
12:20:46.509 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2 -P -o2 -zs
12:20:46.514 JACK was started with PID=20705.
/usr/bin/jackd: symbol lookup error: /usr/bin/jackd: undefined symbol: clock_source
12:20:46.519 JACK was stopped with exit status=127.
12:20:46.519 Post-shutdown script...
12:20:46.519 killall jackd
12:20:46.710 ALSA active patchbay scan...
12:20:46.711 jack_alsa: 14:0 Midi Through -> 14:0 Midi Through checked.
12:20:46.712 ALSA connection change.
jackd: no process killed
12:20:46.912 ALSA active patchbay scan...
12:20:46.913 jack_alsa: 14:0 Midi Through -> 14:0 Midi Through checked.
12:20:46.929 Post-shutdown script terminated with exit status=256.
12:20:48.717 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
I just googled:
jackd: undefined symbol: clock_source
And saw some posts regarding that you might have an old version of jackd installed. Did you build jack-1.9.4? If so, you will want to open Synaptic, search for jack, and see if you have a version of jackd installed. If you do, uninstall it and go back to your jack-1.9.4 directory and rerun
sudo ./waf install
Alan
Under the qjackctl setup button, you need to choose "firewire" at the "Driver" section.
Alan
12:33:50.776 Patchbay activated.
12:33:50.781 Statistics reset.
12:33:50.805 Startup script...
12:33:50.806 artsshell -q terminate
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:33:50.813 ALSA connection graph change.
sh: artsshell: not found
12:33:51.287 Startup script terminated with exit status=32512.
12:33:51.287 JACK is starting...
12:33:51.288 /usr/bin/jackd -R -dfirewire -r44100 -p1024 -n3 -o2
/usr/bin/jackd: symbol lookup error: /usr/bin/jackd: undefined symbol: clock_source
12:33:51.296 JACK was started with PID=4546.
12:33:51.303 JACK was stopped with exit status=127.
12:33:51.304 Post-shutdown script...
12:33:51.304 killall jackd
12:33:51.489 ALSA active patchbay scan...
12:33:51.490 jack_alsa: 14:0 Midi Through -> 14:0 Midi Through checked.
12:33:51.491 ALSA connection change.
jackd: no process killed
12:33:51.691 ALSA active patchbay scan...
12:33:51.692 jack_alsa: 14:0 Midi Through -> 14:0 Midi Through checked.
12:33:51.714 Post-shutdown script terminated with exit status=256.
12:33:53.495 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
See my other message. It looks like you have an old version of a library hanging around.
Also, I sent you a PM a week or so ago. Did you get it?
Alan
"See my other message. It looks like you have an old version of a library hanging around."
Yup...there's an old shared object laying around.
"/usr/bin/jackd: symbol lookup error: /usr/bin/jackd: undefined symbol: clock_source"
jack is trying to call the clock_source() function.
Nuke all the jack shared objects in /usr/lib -- open a term and execute the following (as administrator or use sudo)
rm -f /usr/lib/libjack*
rm -rf /usr/lib/jack
Then rebuild and reinstall your source package.
~Mike
I just noticed that the output patch socket has a red X in it...the input is green
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
yes i got your pm, did you get my return mail?
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
No, I didn't get it. Maybe my spam filter picked it up. Could you resend?Are you still getting the clock error?
You shouldn't be touching anything on the "Patchbay". If you open the "Connect" window, you should see something under "Writable Clients / Input Ports", and it should say "System". If you fired up an app like Aqualung, it would then show under "Readable clients / Output Ports", and the connection to the writable ports should automatically be made.
Edits: 12/20/09
When I select connect, under the alsa tab I see 14:Midi Through under both inputs and outputs.
The output is red and the input is green
I sent you a pm
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
dear dynaudio & aljordan
I´m, sorry to say, still not really convinced about JACK.
-as mentioned I´m grateful for the abilities Jack provided when I needed it, but I still think it´s an awful complicated application.
sure, it was written for linux and adapted to windows....nevertheless it´s a pain in the A... to work with, and I´m not quite sure why I did it so much waste of time.....eh, maybe because I had to !
if one really have to use JACK it´s mandatory to make very precise configurations and back them up with a disk-image.
runtime errors with almost every dot or paragraph change....it´s really only something for developers !
-and for high-end audiophiles it will just add too much processor "hash"
You really should differentiate between Jack on Linux and Jack on Windows. I haven't really spent time comparing Jack output on Linux to other output capabilities on Linux, but in my experience Jack is rock solid on Linux with good sound.
Alan
hey aljordan,
I do not hope I gave the impression that JACK is useless in even fairly advanced systems.
on the windows platform JACK requires an additional C++ code and THAT might not be very "runtime" friendly. I have realized combining cPlay ASIO with allocator VST through JACK, and I´ve been very happy with the result (possible even @192kHz sampling rate).
as we all know, less is more - and in this regard it was clearly beneficial for my system to get rid of JACK.
but even the most hardened PC freak must admit that JACK is not straight down the line to configure correct....
kind regards
If you are trying to get output via a Firewire device, you don't do anything with ALSA because it won't support the Firewire devices. You should be looking under the "Audio" tab in the "Connect" window, not the ALSA tab.
In particular you should be seeing if there is anything under "Writable Clients / Input Ports" where you should see a "System" fold-out. If your device is recognised, it will show at least two ports under "System", however, if it has 8 channels, you would see eight ports or more.
.
Music is the Bridge between Heaven and Earth - 音楽は天国と地球のかけ橋
Post a Followup:
| FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
||||||||||||||
This post is made possible by the generous support of people like you and our sponsors:
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2025, Audio Asylum, all rights reserved ]
