home.social

#sonicvisualiser — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sonicvisualiser, aggregated by home.social.

  1. "(Anasthesia) Pulling Teeth" (Metallica, Kill 'Em All, 1983)

    160kbps MP3 ripped with iTunes in 2016

    vs.

    #FLAC made with #Asunder this week

    Mixed channel spectrogram with #SonicVisualiser

    There's an awful lot being cut out of the MP3, and maybe you can hear it and maybe you can't. On this track, it probably doesn't make a difference. But it's a stark visual.

    #music #archive

  2. "(Anasthesia) Pulling Teeth" (Metallica, Kill 'Em All, 1983)

    160kbps MP3 ripped with iTunes in 2016

    vs.

    #FLAC made with #Asunder this week

    Mixed channel spectrogram with #SonicVisualiser

    There's an awful lot being cut out of the MP3, and maybe you can hear it and maybe you can't. On this track, it probably doesn't make a difference. But it's a stark visual.

    #music #archive

  3. "(Anasthesia) Pulling Teeth" (Metallica, Kill 'Em All, 1983)

    160kbps MP3 ripped with iTunes in 2016

    vs.

    #FLAC made with #Asunder this week

    Mixed channel spectrogram with #SonicVisualiser

    There's an awful lot being cut out of the MP3, and maybe you can hear it and maybe you can't. On this track, it probably doesn't make a difference. But it's a stark visual.

    #music #archive

  4. "(Anasthesia) Pulling Teeth" (Metallica, Kill 'Em All, 1983)

    160kbps MP3 ripped with iTunes in 2016

    vs.

    #FLAC made with #Asunder this week

    Mixed channel spectrogram with #SonicVisualiser

    There's an awful lot being cut out of the MP3, and maybe you can hear it and maybe you can't. On this track, it probably doesn't make a difference. But it's a stark visual.

    #music #archive

  5. "(Anasthesia) Pulling Teeth" (Metallica, Kill 'Em All, 1983)

    160kbps MP3 ripped with iTunes in 2016

    vs.

    #FLAC made with #Asunder this week

    Mixed channel spectrogram with #SonicVisualiser

    There's an awful lot being cut out of the MP3, and maybe you can hear it and maybe you can't. On this track, it probably doesn't make a difference. But it's a stark visual.

    #music #archive

  6. When I switch to the melodic range spectrogram layer, you can see WHERE the ref mix is louder. The low end is much more powerful throughout.

    But there are also some short higher pitches (xylophone, I think?) arpeggiating throughout that are much louder. It's PRETTIER, but I didn't actually like how bright they were in the ref mix.

    #ProAudio #SonicVisualiser

  7. When I switch to the melodic range spectrogram layer, you can see WHERE the ref mix is louder. The low end is much more powerful throughout.

    But there are also some short higher pitches (xylophone, I think?) arpeggiating throughout that are much louder. It's PRETTIER, but I didn't actually like how bright they were in the ref mix.

    #ProAudio #SonicVisualiser

  8. When I switch to the melodic range spectrogram layer, you can see WHERE the ref mix is louder. The low end is much more powerful throughout.

    But there are also some short higher pitches (xylophone, I think?) arpeggiating throughout that are much louder. It's PRETTIER, but I didn't actually like how bright they were in the ref mix.

    #ProAudio #SonicVisualiser

  9. When I switch to the melodic range spectrogram layer, you can see WHERE the ref mix is louder. The low end is much more powerful throughout.

    But there are also some short higher pitches (xylophone, I think?) arpeggiating throughout that are much louder. It's PRETTIER, but I didn't actually like how bright they were in the ref mix.

    #ProAudio #SonicVisualiser

  10. When I switch to the melodic range spectrogram layer, you can see WHERE the ref mix is louder. The low end is much more powerful throughout.

    But there are also some short higher pitches (xylophone, I think?) arpeggiating throughout that are much louder. It's PRETTIER, but I didn't actually like how bright they were in the ref mix.

    #ProAudio #SonicVisualiser

  11. Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

    Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

    #SonicVisualiser #ProAudio

  12. Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

    Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

    #SonicVisualiser #ProAudio

  13. Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

    Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

    #SonicVisualiser #ProAudio

  14. Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

    Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

    #SonicVisualiser #ProAudio

  15. Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

    Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

    #SonicVisualiser #ProAudio

  16. OK, another cool #SonicVisualiser trick:

    With the plugin pack installed (specifically the Match plugin), it can analyze and automatically line up audio files that are different versions of the same thing.

    So if you are A/B testing different revisions of audio (even different lengths as here), it will automagically sync them up

    and whichever you have selected is solo'd by default, so you can easily A/B test while you listen

    sonicvisualiser.org/doc/refere

    #Audio #MusicProduction #sound #OpenSource

  17. OK, another cool #SonicVisualiser trick:

    With the plugin pack installed (specifically the Match plugin), it can analyze and automatically line up audio files that are different versions of the same thing.

    So if you are A/B testing different revisions of audio (even different lengths as here), it will automagically sync them up

    and whichever you have selected is solo'd by default, so you can easily A/B test while you listen

    sonicvisualiser.org/doc/refere

    #Audio #MusicProduction #sound #OpenSource

  18. OK, another cool #SonicVisualiser trick:

    With the plugin pack installed (specifically the Match plugin), it can analyze and automatically line up audio files that are different versions of the same thing.

    So if you are A/B testing different revisions of audio (even different lengths as here), it will automagically sync them up

    and whichever you have selected is solo'd by default, so you can easily A/B test while you listen

    sonicvisualiser.org/doc/refere

    #Audio #MusicProduction #sound #OpenSource

  19. OK, another cool #SonicVisualiser trick:

    With the plugin pack installed (specifically the Match plugin), it can analyze and automatically line up audio files that are different versions of the same thing.

    So if you are A/B testing different revisions of audio (even different lengths as here), it will automagically sync them up

    and whichever you have selected is solo'd by default, so you can easily A/B test while you listen

    sonicvisualiser.org/doc/refere

    #Audio #MusicProduction #sound #OpenSource

  20. OK, another cool #SonicVisualiser trick:

    With the plugin pack installed (specifically the Match plugin), it can analyze and automatically line up audio files that are different versions of the same thing.

    So if you are A/B testing different revisions of audio (even different lengths as here), it will automagically sync them up

    and whichever you have selected is solo'd by default, so you can easily A/B test while you listen

    sonicvisualiser.org/doc/refere

    #Audio #MusicProduction #sound #OpenSource