search for: grungy

.../wiki/Encode/HighQualityAudio https://wiki.hydrogenaud.io/index.php?title=Transcoding#Lossy-to-lossy_transcoding it basically comes down to Fraunhofer Institute's FDK AAC, but the articles are dated. Opus is supposed to be good but I always have the impression it doesn't deal well with loud/grungy/fuzzy/guitarry music, esp. at low bitrates. What do you say? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230415/23371709/attachment.htm>

...> > https://wiki.hydrogenaud.io/index.php?title=Transcoding#Lossy-to-lossy_transcoding > it basically comes down to Fraunhofer Institute's FDK AAC, but the > articles are dated. > Opus is supposed to be good but I always have the impression it doesn't > deal well with loud/grungy/fuzzy/guitarry music, esp. at low bitrates. > > What do you say? > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was...

...ki.hydrogenaud.io/index.php?title=Transcoding#Lossy-to-lossy_transcoding > > it basically comes down to Fraunhofer Institute's FDK AAC, but the > > articles are dated. > > Opus is supposed to be good but I always have the impression it > > doesn't deal well with loud/grungy/fuzzy/guitarry music, esp. at > > low bitrates. > > > > What do you say? > > > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > _______________...

Raghavendra, I've commited my tests case to https://github.com/powool/gluster.git - it's grungy, and a work in progress, but I am happy to take change suggestions, especially if it will save folks significant time. For the rest, I'll reply inline below... On Mon, Mar 5, 2018 at 10:39 PM, Raghavendra Gowdappa <rgowdapp at redhat.com> wrote: > +Csaba. > > On Tue, Mar 6, 201...

On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson <pha at umich.edu> wrote: > Raghavendra, > > I've commited my tests case to https://github.com/powool/gluster.git - > it's grungy, and a work in progress, but I am happy to take change > suggestions, especially if it will save folks significant time. > > For the rest, I'll reply inline below... > > On Mon, Mar 5, 2018 at 10:39 PM, Raghavendra Gowdappa > <rgowdapp at redhat.com> wrote: > > +Cs...

...:58 PM, Raghavendra Gowdappa <rgowdapp at redhat.com> wrote: > > > On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson <pha at umich.edu> wrote: > >> Raghavendra, >> >> I've commited my tests case to https://github.com/powool/gluster.git - >> it's grungy, and a work in progress, but I am happy to take change >> suggestions, especially if it will save folks significant time. >> >> For the rest, I'll reply inline below... >> >> On Mon, Mar 5, 2018 at 10:39 PM, Raghavendra Gowdappa >> <rgowdapp at redhat.com&...

...07&page=11 Eventually it would be nice to get both sets of code running on multiple platforms, for comparison's sake -- the code that's failing (machcon.f) is the code to define machine-dependent constants -- this is a fairly standard set of routines from NETLIB, but they're very grungy in that you're just supposed to uncomment the constants that are relevant to your system. There must be a better way to do this with configure/looking in system libraries etc. (I don't really know how this is done in FORTRAN). Does anyone out there have experience in porting code from N...

+Csaba. On Tue, Mar 6, 2018 at 2:52 AM, Paul Anderson <pha at umich.edu> wrote: > Raghavendra, > > Thanks very much for your reply. > > I fixed our data corruption problem by disabling the volume > performance.write-behind flag as you suggested, and simultaneously > disabling caching in my client side mount command. > Good to know it worked. Can you give us the

Raghavendra, Thanks very much for your reply. I fixed our data corruption problem by disabling the volume performance.write-behind flag as you suggested, and simultaneously disabling caching in my client side mount command. In very modest testing, the flock() case appears to me to work well - before it would corrupt the db within a few transactions. Testing using built in sqlite3 locks is