similar to: Opus 1.1.4 released

On 16/06/17 18:47, Marvin Scholz wrote: > This concatenation are valid streams, it's called chaining, afaik. So > players not supporting them are broken and the authors should be > notified about it, I think. And my question is... Is THAT the way an OPUS source communicates new metadata to the icecast server?. That is the question I would like to know :-). -- Jesús Cea Avión

I am interested in being able to encode a single Opus stream using several CPU cores. I get a raw audio input and "opusenc" can transcode it at 1200% speed (Raspberry PI 3B+). It saturates a single CPU core, but the other three are idle. Is out there any project to add multithreading options to "opusenc", or something in that line? Looking around, I have found this:

On 16/06/17 21:18, Marvin Scholz wrote: > Exactly Ok, GREAT: Thanks. I have another question: Could a MP3 source send metadata updates using ICY metadata (like clients receive new metadata, but in reverse order) or MUST I update via the HTTP interface?. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/

Hi, Just to let everyone know that I released libopusenc version 0.1.1. It does not change the API/ABI compared to 0.1, but fixes a few bad bugs. You can get it from https://www.opus-codec.org/downloads/ For those interested in testing it, there's an experimental patch to make opus-tools use libopusenc for the encoder:

2017-06-16 10:28 GMT-05:00 Jesus Cea <jcea at jcea.es>: > On 16/06/17 13:18, Marvin Scholz wrote: >> The source client is supposed to encode the metadata into the stream, >> not use any endpoint whatsoever to send them, for Ogg and >> other supported formats. There is nothing confusing about this. The >> reason this is different for MP3 and AAC is, that it is

Opus 1.1.2. As experienced in previous release: """ ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file 2>&1 FAIL: celt/tests/test_unit_mathops """ -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea

Doing a "doveadm purge" today I got this: """ doveadm(jcea): Error: Corrupted dbox file /home/jcea/.thunderbird/dovecot/storage/m.686 (around offset=1385772): purging found mismatched offsets (1385742 vs 1380664, 185/275) doveadm(jcea): Warning: fscking index file /home/jcea/.thunderbird/dovecot/storage/dovecot.map.index doveadm(jcea): Warning: mdbox

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 zpool and zfs report different free space because zfs takes into account an internal reservation of 32MB or 1/64 of the capacity of the pool, what is bigger. So in a 2TB Harddisk, the reservation would be 32 gigabytes. Seems a bit excessive to me... - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea at jcea.es -

Most documents around there talk abour "dsync", but the modern way is "doveadm backup". This command is not documented in the wiki and there are a few details missing, like how to use it thru SSH. I am currently doing some tests about how to backup my mdbox. I can do tests in local using: $ doveadm backup -u jcea -m proveedores/dovecot mdbox:/tmp/aa/ This will

I am using Dovecot 2.3.4. I could upgrade if necessary. I see this capabilities after login in: """ a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN

Until today I could do this to backup my primary IMAP4 server: """ doveadm backup ssh csi doveadm dsync-server """ It doesn't work anymore after upgrading to Dovecot 2.2.18: """ jcea at ubuntu:~$ doveadm backup ssh csi doveadm dsync-server Enter passphrase for key '/home/jcea/.ssh/id_rsa': dsync-remote(root): Error: Mailbox INBOX: Failed

On 16 Jun 2017, at 5:41, Rick Keniuk wrote: > Is this the HTTP call for injecting the “song” metadata? > This is a capture (using RawCap in conjunction with Wireshark) of my > AAC+ stream metadata input to IceCast that works fine. > > GET > /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley > HTTP/1.0

I am using mdbox for dovecot storage. I wonder if I could skip "dovecot.index.cache" files and, in general, "*.cache" files when doing mail backup. Those files are big and change frequently. What I feel from reading documentation [1][2] is that they could be dropped in the backups, to be recreated on the fly if needed. But I would like expert confirmation. [1]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rsync 3.0.9 here. I am using a rsync script like: """ rsync -z --numeric-ids -a -H --inplace --delete --delete-excluded - --stats --progress -v --itemize-changes SOURCE DESTINATION """ I detected the following issue when RSYNCing a bunch of Mercurial repositories. It is very dangerous, because it will corrupt files.

Hi all, I have 2 question. First: I use dovecot (version 2.2.9) with mdbox mail format. When I run dsync tool with "mirror" or "backup" parameters my source and destination directory synchronize correctly but if I delete some messages in user mailbox, deleted messages does not synced to destination. For example : atif at domain.com path is /mail/domain.com/atif/ and its

Back in October/November 2007 when I asked about Sparc zfs boot and root capabilities, I got a reply indicating late December 2007 for a possible release. I was wondering what is the status right now, will this feature make it into build 79? This message posted from opensolaris.org

Hi everyone, I'm happy to announce that Opus 1.5 has just been released. Opus 1.5 is the first release to make extended use of ML in the encoder and decoder. You can read all the details in our demo page at: https://opus-codec.org/demo/opus-1.5/ Major changes since 1.4 include: - Significant improvement to packet loss robustness using Deep Redundancy (DRED) - Improved packet loss

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Just to let everyone know that Opus 1.1.2 is out. The release fixes two bugs: - - Resetting the encoder or decoder state with OPUS_RESET_STATE would disable some run-time selected architecture-specific optimizations; and - - In hybrid mode discontinuous transmission (DTX) operation, the comfort noise above 8 kHz was incorrectly estimated and

I am using mdbox storage format. As far as I know, ?doveadm purge? does a complete purge. The time and disk activity would be proportional to the number mdbox files on the storage. The purge time could be huge. I wonder if there is some way of doing a kind of incremental purge, stopping/restarting purging, etc. Purging by file range would be nice too. Advice? Thanks Enviado desde mi iPhone

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Indeed, the reason that -msse* are there is because it's needed for actually compiling the tests (because of the #include of the intrinsics). But of course, -msse* has the side effect of (sometimes) producing illegal instructions. We'll definitely need to fix this, but I don't know how yet. In the mean time, you can either trust that the