So I'm trying to use these headphones for audio production:
Check out the Android app Neutralizer. It helps you come up with a good eq curve for as many different headphones as you use it with. It shows a FR curve of the resulting eq. You could port that back to some other system.
Last post by musikomaniak -
Thank you @kgena_ua
Last post by Phanton_13 -
You can also try to add more payload and/or make it more robust using forward error coding, the other thing is that the type of compromise that you can make and the type of audio that you want to compress have a lot of influence in what you can use and in some situations even Codec 2 at 700bps can be an option. Also try to view some things about digital modulation for radio communications as it have a lot of things in commom of what you want to do.
Last post by nu774 -
Nothing has changed regarding --no-delay option.
--no-delay is safe as long as the beginning (50ms or so) of input signal is digitally silent.
Moreover, even when the beginning of input signal is not silent, you won't hear any "glitches" as long as you listen to one file only.
The effect of --no-delay should become apparent only when you encode two or more gapless inputs, and you listen to the gapless transition between songs.
Last post by kgena_ua -
WSH Biography Text, Album Info, Picture. www.last.fm
language - left mouse double click on the text (or main menu or menu properties to set);
font size - shif + mouse wheel on the text;
move text - press left mouse button on the text and move;
previous, next img. - mouse wheel on the img;
selsect artist or album img. - left mouse double click on the img (order by most popular or release date - menu);
img. interval setting - shift + mouse wheel on the img;
check with aucdtect can cue corrector
Last post by OrthographicCube -
Thank you very much for the reply.
Yes, I considered that already, but unfortunately, many sites, including Facebook, reencode the image to fit their image encoding settings, so I can't expect that the encoded image and decoded image are identical, both pixel-value-wise and binary-wise.
That's why the image decoder accounts for pixel changes and rounds off the brightness to the nearest color that it recognizes (there are 5 accepted values represented as 5 shades of grey) and even if the program rounds off the value to a wrong value (for example, the original 4 value, encoded to JPEG becomes 4.6, and becomes interpreted as 5) my ADPCM-based audio codec will only introduce a faint click (resulting in low-frequency rumble noises if wrong round-offs are frequent) without having the program crash or having undecodeable audio (try bitflipping random bits on an MP3 or Opus and see what happens )
However, learning about how JPEG compresses pixel data could help me optimize the image encoding in a way that more information is preserved. Thanks!
As those of you who have followed this column for any length of time can attest, headphone mixing is one of the big no-no's around these parts. In our humble opinion, headphone mixes do not translate well in the real world, period, end of story. Other than checking for balance issues and the occasional hunting down of little details, they are tools best left for the tracking process.
Yeah sure....I guess that is why most of the new music out there sounds like sh*t. Use both!
Last post by knutinh -
If you upload a jpeg file of small dimensions/filesize, is that passed on unprocessed?
If so, perhaps you could dissect the jpeg format to figure out how a e.g. 640x480 pixel 200kB jpeg file is organized, what bits can be flipped while still being a legal jpeg file. I am guessing that you might get close to 200kB worth of entropy through such a file. Then it is only a matter of compressing your source audio using any regular codec into such a file size.
Yep. You now get a progress dialog like this when working with enough files...
My max was 100 entries...