jack_capture
============
jack_capture is a program for recording soundfiles with jack. It's default
operation is to capture whatever sound is going out to your speakers into
a file, but it can do a number of other operations as well.
Normal URL:
http://www.notam02.no/arkiv/src/?M=D
Note that the above link doesn't seem to currently work
because of something which seems to be www upgrade
at Notam. But this link does seem to work for now:
http://old.notam02.no/arkiv/src/?M=D
0.9.10 -> 0.9.17:
-----------------
*Made sure the process thread won't continue sending
data when jack_capture is told to quit. This
led to a race conditions when recording too many channels
at once (which was 256 channels on my machine).
*Added the jack_capture_gui script, based on code
by Svend-Erik Kjær Madsen's.
*Replaced sh by bash to make it work in ubuntu.
*Fixed exact port name match and gen_setformat. Thanks to
Gabriel J.L. Beckers for reporting the bugs.
*Increased the time the console meter is displayed in red from
50ms to 2000ms. (when the recorded jack value is equal to or
higher than 1.0.)
*Added the -dBr argument to specify reference level when using
the console dB meter.
*Added the -mr argument to specify reference level when using
the meterbridge meter.
*Added peak indicators to the console meter. Code to do so taken
from meterbridge by Steve Harris.
*Updated --help and README with the new options.
*Added option "-mt" to change meterbridge type. Current valid
options are vu (default), ppm, dpm, jf or sco. It's not necesarry
to specify "-mb" if using "-mt".
*Added option "-dB" to get a dB meter for the console meter.
*Added examples how to record ogg and mp3 files using the -ws option.
*Decreased default buffersize from 60 to 20 seconds.
(I even had trouble provocing underruns using a minimal
0.05 seconds long buffer, so 60 seconds was obviously overkill)
*Fixed message and error printing to stderr when
vu meter is running.
Am Wednesday 02 July 2008 schrieb Loki Davison:
> On Wed, Jul 2, 2008 at 5:04 PM, Martin Horn <martin.horn(a)ostec.org> wrote:
> > Where are you buying from?
> >
> > There is a czech company named BACH Guitars. The gits are really cheap and
> > at least as good as the typical Harley Bentons and even the Epiphones you
> > can buy on Thomann. I bought a 335 copy from them for 300 Euro and its
> > really good quality. Shure the pickups are not the best, but for the price
> > the wood and mechanics are really good quality. I think better than an
> > Epiphone 335 copy. I don't know about the basses but I would give it a try.
> > You can buy a bassgit on ebay and send it back if you don't like it. The
> > best would be to go there and check out for the best guitar in stock but the
> > guy selling them lives in south of east germany and I don't know where
> > you're coming from...
> >
> > Just check it out:
> >
> > http://search.ebay.de/_W0QQsassZhomophonieQQhtZ-1
> >
> > Martin
> >
> >
> > On Mon, Jun 30, 2008 at 11:18 AM, schoappied <schoappied(a)gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> I'm searching for an (second hand) cheap bassguitar. Do you have
> >> suggestions for me? Which brands are 'good' in a low price class?
> >> Where should I be alert for when buying one?
> >> What about a amplifier? Do I need one, or can I play it using Linux?
> >>
> >>
> >> Thanks in advance,
> >>
> >> /D
> >>
>
> Bass shopping guide:
>
> Just try one at a pawn shop, etc and if you like it buy it. Reviews,
> etc on the net are a waste of time usually. It's how it is for you,
> not someone else. Not saying the reviews are a good source of making
> you feel better about the bass you bought ;) Of course, maybe if you
> are looking for an instrument, you can't go wrong with a Fender P or J
> Bass. It's really not that much money in the whole computer music $$$.
> It's also a nice simple instrument that does the job at hand. I play a
> washburn tarus t24 that i am very happy with and is quite cheap. $650.
>
> Loki
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
>
Not being a bass player, I still second that. Guitars are made from wood, and
especially with cheap instruments there can be huge differences between
instruments of the same brand/type. You have to play, hear and feel it yourself
to judge. A friend of mine recently got a very nice cheap telecaster copy, from a
series of ten in the shop it was the only good one, and he got it even cheaper
because some kids had made scratches to the surface when trying them out...
Edgar
Hi,
There is a discussion about more tablature-notation functions in
Lilypond, like bend, slides, pull off etc.
Are you a guitar, bass or other string player, and maybe a software
developer too?
Maybe you can offer you knowledge to lilypond and help develop these
tablature features!
Or maybe you like to see such features in lilypond and would give your
support and let the devs of lilypond know that you also like to see
those tablature features!
If so, subsribe to the lilypond-user mailinglist and give your support.
Roos
Arnold Krille:
> As the transfer from memory to hd is _the_ slow point of the setup,
> cache-misses or hits don't influence that at all. And when you are not
> calculating anything (apart from 64bit to 32bit double-to-float), you don't
> access the cache. DMA is the keyword. Still it doesn't make saving to disk
> faster than your disks and controllers speed. And I am pretty sure that there
> is _no_ compression involved in that part, otherwise this would seriously
> affect data-integrity if the controller did an unwanted compression.
Okay, but I'm also thinking about the HD cache and the cache between
the OS and the disk. I don't know how it works
exactly though, but I thought that maybe it didn't write to disk as
often if the cache is constantly filled with zeros.
> Is that enough back-up for my "bombastically spilled out" argumentation?
Sure, much better argumentation.
> A double (or float) to transfer to disk is still a double (float) to transfer
> to disk regardless wether the value is 0, close to zero or something close to
> INFINITY...
Yes, but no doubles or 64 bits are involved in this process, only
32 bit floats.
David Forsyth:
>
> At this point, I'd be happy to do an 8 track recording. For important
> live recordings I would not use a laptop, but instead a decent desktop
> with a RAID 0 array of at least 3 SATA2 disks for the audio files, with
> the system on another disk.
>
I think that is complete overkill. I just tried recorded 128 channels of
32bit/44100hz at once, without problem. And my machine is 5 years old
2Gz barebone, using only a single PATA ide disk.
This was using jack_capture, and only recording silence (ie. non-connected
jack ports). Maybe the silence makes a difference.(?)
256 channels did not work very well though.
Hi everyone,
I'm trying to get my Motu Traveler to work on Linux but...
The ffado mixer is working correctly, I can tune the settings of the Traveler
but when I start jackd, it crashes 2 seconds after. I've tried different
settings frames/period etc. but I always get the same behaviour. Does someone
have suggestions of what I could try next?
--
Raphaël.
Here is the output when I start jackd:
jackd -R -d firewire -v4
no message buffer overruns
jackd 0.112.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
SSE2 detected
04886716167: (ffado.cpp)[ 99] ffado_streaming_init: libffado 2.0.900-1268
built Jul 1 2008 21:43:54
04886904852: Debug (devicemanager.cpp)[ 510] discover: driver found for device
0
04886905183: Debug (devicemanager.cpp)[ 547] discover: discovery of node 0 on
port 0 done...
04886905191: Debug (devicemanager.cpp)[ 555] discover: Discovery finished...
04886905210: Debug (devicemanager.cpp)[1045] showDeviceInfo: ===== Device
Manager =====
04886905216: Debug (Element.cpp)[ 109] show: Element DeviceManager
04886905220: Debug (devicemanager.cpp)[1053] showDeviceInfo: --- IEEE1394
Service 0 ---
Iso handler info:
Dumping IsoHandlerManager Stream handler information...
State: 2
04886905233: Debug (devicemanager.cpp)[1063] showDeviceInfo: --- Device 0 ---
04886905237: Debug (devicemanager.cpp)[1066] showDeviceInfo: Clock sync
sources:
04886905254: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
Internal , Id: 0, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: Internal sync
04886905259: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
ADAT , Id: 1, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: ADAT optical
04886905264: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
SPDIF , Id: 2, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: SPDIF/Toslink
04886905268: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type: Erratic
type , Id: 3, Valid: 0, Active: 0, Locked 0, Slipping: 0, Description:
SMPTE
04886905273: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
WordClock , Id: 4, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: Wordclock
04886905278: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
ADAT , Id: 5, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: ADAT 9-pin
04886905282: Debug (devicemanager.cpp)[1075] showDeviceInfo: Type:
AES , Id: 7, Valid: 1, Active: 1, Locked 1, Slipping: 0,
Description: AES/EBU
04886943583: Debug (motu_avdevice.cpp)[ 980] prepare: Preparing MotuDevice...
Handler type................: Transmit
Port, Channel...............: 0, 1
Buffer, MaxPacketSize, IRQ..: 200, 616, 100
Speed, PreBuffers...........: 2, 0
Min ISOXMT bufferfill : 7999
Last cycle, dropped.........: -1, 0
Handler type................: Receive
Port, Channel...............: 0, 0
Buffer, MaxPacketSize, IRQ..: 400, 616, 85
Last cycle, dropped.........: -1, 0
04887356461: Debug (IsoHandler.cpp)[ 603] getPacket: (0x80832b8) dropped 3100
packets on cycle 199 (last_cycle=5098, dropped=0, skipped: 0)
04889449791: Warning (StreamProcessorManager.cpp)[ 898] waitForPeriod: Timeout
while waiting for activity
04889449800: Warning (IsoHandlerManager.cpp)[ 226] Execute: Timeout while
waiting for activity
04890449816: Warning (StreamProcessorManager.cpp)[ 898] waitForPeriod: Timeout
while waiting for activity
04890459018: Warning (IsoHandlerManager.cpp)[ 226] Execute: Timeout while
waiting for activity
04891449842: Warning (StreamProcessorManager.cpp)[ 898] waitForPeriod: Timeout
while waiting for activity
04891469020: Warning (IsoHandlerManager.cpp)[ 226] Execute: Timeout while
waiting for activity
04892329008: Fatal (IsoHandlerManager.cpp)[ 274] Execute: (0x807d680,
Transmit) Handler died: now: A9E6D856, last: A1E678DD, diff: 98322297 (max:
98304000)
04892329025: Warning (StreamProcessor.cpp)[ 108] handlerDied: Handler died for
0x8083848
04892449866: Warning (StreamProcessorManager.cpp)[ 898] waitForPeriod: Timeout
while waiting for activity
04892449890: Debug (StreamProcessorManager.cpp)[1022] waitForPeriod: Xrun on
XMIT SP 0x8083848 due to ISO side xrun
04892449897: Debug (StreamProcessorManager.cpp)[1026] waitForPeriod: Xrun on
XMIT SP 0x8083848 due to buffer side xrun
04892449901: Warning (StreamProcessorManager.cpp)[ 614] alignReceivedStreams:
xrun while aligning streams...
04892449905: Error (StreamProcessorManager.cpp)[ 583] syncStartAll: Could not
align streams...
04892449916: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449920: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449923: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892449927: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892449933: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449936: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449939: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892449942: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892449947: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449951: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449954: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892449957: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892449962: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449965: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449968: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892449972: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892449977: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449980: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449983: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892449986: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892449991: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892449994: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892449997: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892450007: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892450014: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892450017: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892450020: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892450023: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892450028: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892450032: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892450035: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892450038: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892450043: Error (IsoHandler.cpp)[ 652] prepare: Incorrect state, expected
E_Initialized, got 3
04892450046: Fatal (IsoHandler.cpp)[ 713] enable: Could not prepare handler
04892450049: Error (StreamProcessor.cpp)[1097] scheduleStartDryRunning: Could
not start handler for SP 0x8083848
04892450052: Error (StreamProcessorManager.cpp)[ 334] startDryRunning: Could
not put SP 0x8083848 into the dry-running state
04892450055: Fatal (StreamProcessorManager.cpp)[ 692] start: Could not
syncStartAll...
04892450078: Fatal (IsoHandlerManager.cpp)[ 274] Execute: (0x807d798, Receive)
Handler died: now: AA2F65FE, last: A22EC124, diff: 98335962 (max: 98304000)
04892450089: Warning (StreamProcessor.cpp)[ 108] handlerDied: Handler died for
0x8080a08
04892460300: Fatal (ffado.cpp)[ 204] ffado_streaming_start: Could not start
the streaming system
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
jackd watchdog: timeout - killing jackd
Aborted (core dumped)
G'day,
Can anyone suggest a USB MIDI device compatible with both recent
versions of Ubuntu (e.g. 8.04) and Mac OS X, for use with Rosegarden and
GarageBand?
--
James Cameron mailto:quozl@us.netrek.org http://quozl.netrek.org/
I'm gonna bite the bullet and rip all my music to play it around
the house via my computers. I've got really good music gear
for the job in my home studio. But, my turntable and record
collection is just about as far from there in my house as is
possible. I don't want to move either set of gear. Instead
I want to get sound adapter for a laptop I've got and do the
ripping at the location where my turntable resides now. My
laptop has USB. I don't know if it's USB1 or USB2. But, I can
get a cardslot to USB adapter for cheap, if need be.
I'm planning to store my digital music losslessly, in either FLAC
or WAVPACK. I want the music to sound as good after being ripped
as it did on my pretty good home stereo via the turntable. I
know I need at least 2 channels, but I'd go with 4 channels on
the adapter, if it didn't cost me double.
What would you recommend as a sound adapter for this job, and why?
Thanks....
--
Kevin
Thanks Ron for the info, we are already aware of this issue and are working
on it as fast as we can. As unlikely as it sounds, it appears we've had a
major thunderstorm that has knocked out several buildings on campus,
including the building hosting our server. Unfortunately, I've been out of
the country and unaware of this occurrence until it was brought to my
attention yesterday. Let me say that this is a very unusual and very much
unexpected occurrence. That being said, based on this unfortunate
development we will look to invest into better UPS asap to minimize any
potential downtime in the future.
As of 4:58PM the server should be back up and running.
Best wishes,
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology, CCTAD
CHCI, CS, and Art (by courtesy)
Director, DISIS Interactive Sound & Intermedia Studio
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-6139
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/faculty/bukvic/
> -----Original Message-----
> From: Ron Fox [mailto:rfox@aloha.com]
> Sent: Tuesday, July 01, 2008 9:08 AM
> To: ico(a)vt.edu
> Subject: Host 128.173.232.121 is unreachable via http or smtp ports
>
> Aloha Dr. Bukvic,
>
> I've been trying to reach the www.linuxaudio.org and
> lists.linuxaudio.org websites for a few hours without success. I'm
> sending this just in case you aren't aware of the situation.
>
> Mahalo,
> Ron Fox