>
>
> Perhaps useful information for those who program, but irrelevant for
> this thread, since WAV files > 2GiB don't require 64bit at all.
>
> libsndfile on Arch, this is what the OP does use, is configured with
> "--prefix=/usr --disable-sqlite" and it's the latest official upstream
> release without patches and no changes excepted of
>
sed -i 's|#!/usr/bin/python|#!/usr/bin/python2|'
> src/binheader_writef_check.py \
> src/create_symbols_file.py programs/test-sndfile-metadata-set.py
> sed -i 's|python|&2|' src/Makefile.am
>
>
My guess is that libsndfile on 32 bit arch is not compiled
with _FILE_OFFSET_BITS set to 64, for some reason.
Hey hey again,
sorry to be back so soon. But both jack_rec and jack_capture with formats
ranging from wav, w64 to caf, break off after 2.1GB filesize. Since all of
these are uncompressed and the other variables stay the same, this equals six
hours, twelve minutes and 49 seconds.
My jack_capture commandline currently looks like this:
jack_capture -as -f caf -b 16 -c 1 -p system:capture_1 $FILENAME
I get no complaints, JACK is still running and the system is fine. I'm using
jack_capture 0.9.71 from Arch AUR.
Can anyone think of the issue in question or a solution or tests to approach
the problem?
Thanks and best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
> I didn't manage to get to the bottom of which piece of software
was causing the problem.
Sorry, it is both jack_rec and jack_capture.
Both use libsndfile, and neither should behave differently
when running on a 32 bit OS.
>*From the POV of libsndfile, it has had Large File Support (which
*makes file offsets 64 bit signed values) on 32 bit systems for over
a decade.
J.C: Could it be that your libsndfile is that old?
> However, it is possible for other software using libsndfile incorrectly
> (ie using a 32 bit integer to store file offsets) to cause this sort
> of a problem, but then I would expect it to go wrong on 64 bit systems
> because `int` is 32 bits there too. However on 32 bit Linux systems,
> `long` whereas it us 64 bits on 64 bit Linux systems.
Yes, but neither jack_rec or jack_capture uses long for this (jack_capture
uses int64_t), and jack_rec doesn't even use a counter, it just writes
and writes
until it stops. jack_capture has a counter, but that counter is only
used when writing
wav files, and only used to keep track of when to start writing on a
new file when reaching
the 4GB barrier.
This one is somewhat on the smoother side, incorporating various
percussive elements.
https://soundcloud.com/nominal6/jumanmai
Enjoy. Comments welcomed.
Cheers.
Hi all :)
I only recently found this list, and did not realise there were so many
people out there making music with open source, it's pretty awesome <3
I am currently making an EP, and my mixing/mastering skills are ok, but not
exactly honed yet! I would really appreciate another pair of ears or more
in the process, so if anyone would be up for giving my mixes a listen and
giving me some feedback, that would be greatly appreciated. Please let me
know if so, but FYI timescales are quite short, so it will only be over the
next few days/week probably.
Links to my various pages are on my website (http://www.emilyfoxmusic.co.uk/),
and particularly visit my YouTube if you want to have a hear at the kind of
thing I'm doing. The EP page for info about that is on Kickstarter here:
https://www.kickstarter.com/projects/1664667971/emily-fox-makes-a-real-ep
If anyone's up for lending me a pair of ears, that would be totally amazing.
Thanks a lot,
Emily
>
> On 07.11.2016 11:32, J. C. wrote:
> > Hey hey,
> > I tried to record over long periods of time (7-9 hours), using jack_rec,
> which
> > apparently relies on libsndfile for writing audiofiles. I started out
> using
> > .wav, which broke off after 6:12:49 (2.1G). Next time, I tried using the
> file
> > extension .w64, which yielded the same result.
> >
> > So, which format, or extension, would work for such periods of time?
>
> Have you tried with jack_capture?
>
> It uses libsndfile, too for codecs, but can dump raw samples to disk if
> you tell
> it to.
>
> So, if libsndfile should be the limiting factor, try dumping the raw
> frames and
> later analyze those.
>
>
libsndfile is not the limiting factor. It's the wav format that doesn't
support large files.
(The "raw" format is also handled by libsndfile, but again, libsndfile is
not to blame here,
so that doesn't matter.)
> jack_capture -f raw -b FLOAT snoring.bin
>
>
Besides this option (and -f w64 and -f CAF which has been suggested),
jack_capture continue writing to new files in case you try to write more
data than
is supported, so you can even use the default wav format for large files.
Hey hey,
I tried to record over long periods of time (7-9 hours), using jack_rec, which
apparently relies on libsndfile for writing audiofiles. I started out using
.wav, which broke off after 6:12:49 (2.1G). Next time, I tried using the file
extension .w64, which yielded the same result.
So, which format, or extension, would work for such periods of time?
Thanks and best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
Hey hey again,
the next thing I'm looking for is a program to detect volume over a certain
threshold, which can print out a marker there. This function should - at best
- be able to ignore new peaks within a certain period of time, like a gate
with very long release times.
To elaborate the scenario: I'm recording myself sleeping, to a) find
involuntary actions and b) do quick narrations of dreams, should I wake up and
remember anything. So, I'd like to jump to the short moments of "action"
within the relative silence.
Any help is appreciated, thanks for staying with me.
Best wishes,
Jeanette
--------
When you need someone, you just turn around and I will be there <3
hija all,
yesterday I finished a video and published the album release on
bandcamp...
The visual performance piece "Requiem for The Future" for which I
created music was premiered on 14. October. Since the music was made
very early in the process I managed to create a whole release including
a physical manifestation in a form of custom-made usb in a fold,
designed and printer and bound localy and able to offer that on the
premiere.
so few weeks later here's a video for an edited release (not exactly
how the music was in the performance, but very close).
the music was made in Renoise, and I used some older materials of mine
(granulated stuff in Pure Data, glitches from "cat /dev/sda | /dev/snd")
and reworked number of field recordings.
the video is using stock footage from archive.org (attribution cc
licence) but glitched using ffmpeg and SoX and edited in Kdenlive.
video: https://www.youtube.com/watch?v=HkFonGImAh0
bandcamp: https://novadeviator.bandcamp.com/album/requiem-for-the-future
patreon post: https://www.patreon.com/posts/requiem-for-7131878
the video has a connection to the live visual performance in the fact
that part of the performance were also two dogs doing a dog
choreography and the concept of the performance which deals with the
imaginary time when there are no humans left on earth, only A.I. and
animals/nature and how do we imagine they would co-exist. more about
the piece: http://aksioma.org/requiem/index.html
a bit on the process of glitching the video material:
http://nova.deviator.si/development-log/making-of-requiem
enjoy!
btw: if you want the USB, there's very few copies left...
--
Luka Prinčič / Nova deViator / http://deviator.si
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://novadeviator.bandcamp.com | http://patreon.com/novadeviatorhttp://wndv.si | http://kamizdat.si | http://emanat.si
jack-matchmaker
---------------
Version 0.5.0 is out with some breaking and other minor changes:
Changes:
* Reorganize command line options: -l/--list-ports is replaced by
-o/--list-outputs and -i/--list-inputs, which can be given on their
own or together and in combination with the -a/--list-aliases option.
* Remove prefixes and separators from port and connection listings (so
you can more easily parse the output in shell scripts or pipe the
output of jack-matchmaker -c into a file and directly use it with the
-p/--pattern-file option).
* Add --version command line option.
* Exclude currently unused alsainfo module from distribution.
* Some internal code re-formatting for PEP-8 conformity.
* AUR package added.
Where to find it:
GitHub: https://github.com/SpotlightKid/jack-matchmaker
PyPI: https://pypi.python.org/pypi/jack-matchmaker
AUR: https://aur.archlinux.org/packages/jack-matchmaker/
Share & Enjoy,
Chris Arndt