similar to: Another suggestion for putting tinc to good use

1. The UDT library is a BSD-licensed accelerated UDP-based transport. Would tinc be able to use this for UDP-based connections and would the licensing be acceptable? http://udt.sourceforge.net/index.html 2. I would like to see a 3rd compression protocol added to tinc: one based on the Mahoney compression schemes would be worth investigating (need something fast and uses small RAM on

For tinc users on OpenWRT: https://dev.openwrt.org/changeset/29137 ciao :) Saverio

Hi mates, I've just installed camstudio on wine 1.2 without any problem. As a known issue, after trying to run for the first time, it complained a missing dll (mfc42.dll). That was easy to solve and I got camstudio opening the recorder. The problem started where, when I click on record. It says: Error creating avi file! I tryed so many things but the problem I found was the compressors

well if you think this is trolling youre probably right. but. there is a but. i've been using wine since years, from time to time, i compiled it, tried various versions both precompiled and source up to the present day. now i give up. wine is unusable. period. dont want to say it is a piece of crap because of all the hard work that is behind, but it is irritating to say the least. seriously

I'm amazed by how low the artifacts are when encoding with Vorbis, but I found problems (Vorbis version 1.00) on equalization (high vs midrange vs low pitches balance) when encoding my benchmark audio track, problems which are hard to go away even at very high bitrates. My benchmark audio track is composed by me and you can find it here http://www.trombettworks.com/drumswork.php in losslessly

I read this on the RHN commentary respecting cve-2014-3566: https://securityblog.redhat.com/2014/10/15/poodle-a-ssl3-vulnerability-cve-2014-3566/: . . . The first aspect of POODLE, the SSL 3.0 protocol vulnerability, has already been fixed through iterative protocol improvements, leading to the current TLS version, 1.2. It is simply not possible to address this in the context of the SSL 3.0

Hi Michael, when I was looking for information on tinc in combination with IPv6, I also found your new tutorial at that time (earlier this month). Somehow a couple of things are less clear to me in the newer tutorial (maybe the nice network topology image is missing). OK, you added the unique local addresses to the setup. But I dont't get it how the routing is done in your setup. You

On Fri, 2 Feb 2001, Josh Coalson wrote: > this is probably a good point to remind everyone that FLAC is still > beta so don't delete your originals! everyone here has been good > about it but I'm dreading that message from someone who lost all their > stuff. You mentioned that one update was to include an md5 signature of the compressed stream to detect errors? Could you

Hey All, So now that we''re up to 7 files, and hopefully more coming as the project grows, minimizing load latency seems much more important. Maybe it''s time to consider creating a single file distribution, much like what prototype.js is (a concatination of 6 or so other files)? re: packaging suggestions *) scriptaculous_only.js - all of the scriptaculous components w/o

Hello, I noticed that kbps jumps quite high in -q 10 mode and is nearing lossless compressors. Would it be a difficult task to make OGG a lossless compressor at -q 10? I don't know much about lossy/lossless compression internal logic, so excuse me if my question is out of place. But this would be a really nice feature that would make OGG an "all in one" tool. Cheers, Bostjan

On Thu, 4 Apr 2002, Akos Maroy wrote: > can you tell me more about these LADSPA plugins? LADSPA stands for Linux Audio Developer's Simple Plugin API (see http://www.ladspa.org/). Basically, it was pointed out on the linux audio dev (LAD) mailing list that numerous programs were using plugin architectures and all were different. So they fleshed out a plugin API and the rest, as they say,

Hi, It's going to depend a bit on what format you're going to use. If you plan to stream in ogg vorbis, you can use Ices 2.x and accept PCM via standard input. This means you could run a sox effect or ecasound to get and compress the sound from the soundcard before sending it on to ices. Ecasound can make use of LADSPA plugins which opens you to a range of compressors, such as the

[This email is either empty or too large to be displayed at this time]

hm, to have a look at Pure Data and external called oggcast~ http://www.akustische-kunst.org/puredata/ is recomended, you can set quality/bitrate/samplerate ... while streaming then, and do whateweryou want to your sound before sending it to icecast, including building your compressor-limiter. cheers Ales Zemene -- http://ales.mur.at irc.kunstlabor.at #kunstlabor citation of

Mr. Blum, I had to make some assumptions writing the driver, because I had no previous experience writing ACM drivers. I did what I could based in Microsoft's documentation but, of course, I made same mistakes. I had no time to test the code I wrote yet and will not in the next 2 weeks. All I can tell you now is about what I did and about my sources. So, considering your enthusiasm, I suggest

http://bugs.freedesktop.org/show_bug.cgi?id=15621 Summary: Support CSS color shorthand Product: swfdec Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: library AssignedTo: swfdec at lists.freedesktop.org ReportedBy: candrews at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've added lzo compression support for tinc 1.0pre8. Lzo is a very fast compressor (see http://www.oberhumer.com/opensource/lzo/). I've implemented it by using two new compression levels. Compression level 10 is for fast compression using lzo1x-1 algorithm. Compression level 11 is for slow compression using lzo1x-999 algorithm.

Martijn, > Currently FLAC already stores and restores most kinds of metadata > corruption without problems, so in most cases the conversion is > already bit-accurate. However, there are some kinds of corruption it > cannot handle. These are the kinds of corruption that invalidate your > considerations. For example, when a chunk length is incorrect, the > location and length

Hello, I am still progressing with very high compression and I have corrected a processing, so now very high compression (-l10 to -l13 quality settings) has really better precision and so better quality. I have also released a first draft of a new -l14 very high compression quality setting. More at: http://nhwcodec.blogspot.com/ Just a remark, the entropy coding schemes start to be less

Op do 3 nov. 2022 om 19:39 schreef Federico Miyara <fmiyara at fceia.unr.edu.ar>: > > > Martijn, > > Currently FLAC already stores and restores most kinds of metadata corruption without problems, so in most cases the conversion is already bit-accurate. However, there are some kinds of corruption it cannot handle. These are the kinds of corruption that invalidate your