Andrew Grathwohl:
>
> Hi list,
>
> I am using jack_capture to record 2 inputs and 20 outputs going through
> SuperCollider for a duration of between 30-45 minutes, using the
> following command line:
>
> jack_capture -f wavex -p supernova:* test.wav
>
> This has worked well for my use case for several years. However, since
> yesterday this command line fails to capture the entire recorded
> performance, despite jack_capture showing the meters responding to the
> audio correctly. Whenever the recording duration exceeds approximately
> 20 minutes, the output file will only contain the first 5-10 minutes.
> However, if we only do a 5-10 minute recording, the entire recording is
> captured and saved properly.
>
> Seeking any insights about how to diagnose/fix these problems. Anyone
> here know where I ought to start?
>
Hi, I'm the author of jack_capture.
Were you able to record more than 20 minutes of 22ch before with
jack_catpure before, and now it suddenly fails?
Have you upgraded or downgraded jack_capture and/or libsndfile since then?
Which version of jack_capture are you currently using?
Have you tried a different format than wavex?
(wav is probably the the safest format to try since it's one that has
been the most tested. Wav files has a 2gb limitation though, but
jack_capture automatically writes to a new file whenever it reaches
that limit.)
There was a problem many years ago that I used (by accident) a 32 bit
integer instead of 64 bit integer. Perhaps you are using one of those
quite old versions of jack_capture.
Hi list,
I am using jack_capture to record 2 inputs and 20 outputs going through
SuperCollider for a duration of between 30-45 minutes, using the
following command line:
jack_capture -f wavex -p supernova:* test.wav
This has worked well for my use case for several years. However, since
yesterday this command line fails to capture the entire recorded
performance, despite jack_capture showing the meters responding to the
audio correctly. Whenever the recording duration exceeds approximately
20 minutes, the output file will only contain the first 5-10 minutes.
However, if we only do a 5-10 minute recording, the entire recording is
captured and saved properly.
Seeking any insights about how to diagnose/fix these problems. Anyone
here know where I ought to start?
Thanks much,
Andrew
Hey hey,
I have just uploaded four sample libraries that I created with AutoSampler and
DrumSampler:
http://juliencoder.de/sound/index.html
They are:
Prophet Guitar: a guitar/clav like patch on the hybrid analogue/digital
DSI/Sequential Prophet 12 (part of my Jeanny's Genius soundsets).
Brute Bass: a solid bass patch on the analogue semi-modular Arturia MiniBrute
2s.
Coast Bass: a gnarly, woddy "plucked" bass patch on the west/east coast
semi-modular Make Noise 0-Coast.
RD8 Kit 1: one drum kit (no congas) on the analogue Behringer RD-8 (Roaldn
TR-808 clone), solid, but conservative, so no overlong boomy kick :) ).
Hope someone can have some fun with them.
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
It's not complicated
We just syncopated
We can read each others' minds <3
(Britney Spears)
Hey hey,
AutoSampler version 3.0 is here (and will probably be the last, except for
possible bugfixes):
http://juliencoder.de/sound/autosampler-3.0.zip
(Tested with Csound 6.15, might run with 6.14).
There is one autosampler which can pause after a specified number of notes, so
you can retune your old analogue synth. You can interactively choose a
reference note, byt playing notes on a connected keyboard. A reference tone
will be played from within the program.
The next sampler is really new: Drum Sampler is specially designed to work
with drum machines. It starts in play/exploration mode, where you can tweak
sounds and listen. Then in record mode all played notes/sounds/trigger-buttons
will be recorded. You can specify MIDI notes for hihats, they will be put into
a mute group for the SFZ.
SFZ files are created at the end. Round robins will automatically be detected.
Play a note as often as you like. Files are named based on the MIDI note.
You can simply rename them.
I have recorded a sample set with each sampler, if anyone's interested, I can
upload them.
Good sampling and best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
Baby, take the time to realize
I'm not the kind to sacrifice <3
(Britney Spears)
Hey hey,
I have released a small autosampler, implemented in Csound. It's easy enough
to set up.
http://juliencoder.de/sound/autosampler.csd
Documentation for non-Csound users is at the top and again at the bottom.
The autosampler support velocity layers, round robins, overall note range,
note intervals, both mono and stereo sampling. The sampler will wait for a
note to decay, but does not (yet) produce key release samples.
Output files are named:
chosen_name-MIDI_note_number-velcity-round_robin_index.wav
I hope someone finds a use for it. :)
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
All I need is time
A moment that is mine
While I'm in between <3
(Britney Spears)
>
> If your goal is just to install Qsampler, there's a PPA which Rui always
> keeps up-to-date with the latest version. The applications and libs are
> in separate repos with the same signing key, not sure if you need both
> for Qsampler.
>
>
>
Thank you for your reply, Roger. I was sent a personal e-mail advising me
to install qttools5-dev-tools. This included /usr/lib/qt5/bin/lupdate.
After doing so, the source code compiled and installed without error. As I
mentioned, I was missing something obvious. Still, unless you know it, you
don't know it....
Tom
Hello, List--
Actually, qsampler configures without errors. Running make returns no
errors, either. When I run sudo make install, I get this error:
lupdate: could not exec '/usr/lib/qt5/bin/lupdate': No such file or
directory
make: *** [Makefile:97: translations_lupdate] Error 1
I don't know much about coding, but took a look at the Makefile, which
contains this line:
export LUPDATE=/usr/bin/lupdate
I tried putting lupdate in /usr/bin/qt5/bin, but that only made my terminal
hang.
I'm compiling on Ubuntu Studio 20.04. I'm sure I've missed something
obvious. All help is appreciated.
Take care!
Tom
Hey hey,
I have just released this piece (best listened to on headphones):
https://youtu.be/U6GKSp1_vT8
It's a virtual journey from free space through the layers of Neptune's
atmosphere down to the planet's core. All sounds are synthesized, but based on
audio recordings from NASA's Voyager II when it had passed the planet. These
would be audio representations of different instruments aboard the space
probe. The text is an impression or short fragment that I had written down on
some journey, not to Neptune though. :)
The image is also synthesized, though not with Csound but with POV-Ray.
Feedback is welcome, I hope you enjoy it.
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
You should never try to change me
I can be nobody else
And I like the way I am <3
(Britney Spears)
Hi David, all,
Creating a new thread as the old one was pretty long...
On 19/03/2021 15:22, David Kastrup wrote:
[...]
>> - Zoom H5 shows 4 inputs in jack: the L/R mics and the inputs 1 and 2
>
> Oh, can you just put the headphones right next to the mics (makes
> astonishingly little difference in comparison to direct connections) and
> use jack_iodelay for measuring out the latency of the H5 with your
> settings?
>
> Numbers are surprisingly hard to come by for any audio interface.
>
This is what I got by connecting jack_delay to one output and putting
the headphone right in front of the microphones (connected only one to
the jack_delay input). These are common jack settings I use or have used
with this device, although the 32 Frames is very unstable and the 64
Frames one gets a few xruns depending on what it's used with (but still
more usable). The 128 Frames settings is very stable.
SR Fr/p Avg. delay reported (ms)
------+-------+-------------------------
48000
128,2 22.7
64,3 18.7
32,3 14.2
44100
128,2 25.2
64,3 20.6
96000
128,2 22.6
64,3 18.6
88200
64,3 18.6
Hope this is useful /interesting
Lorenzo.