Skip to main content
Recent Posts
1
General - (fb2k) / Re: Reading codec info in some video files
Last post by wcs13 -
Thank you zeremy. :) I have just tested your script on some test files. It works... but not as it should  :D Maybe you don't know how the m-TAGS component for foobar works, so here it is :

1. All the .tags files generated by the m-TAGS component have the same exact name : "!.tags". Litterally, with an exclamation mark. Not "[nameofthevideo].tags".

2. Every "!.tags" file contains info for one or several video files. Like I said, here's an example when several video files are in the same folder (which is the case for the featurettes) :

Code: [Select]
[
   {
      "@" : "Creating Nerve.mkv",
      "CREATION_TIME" : "2016-10-16T15:51:50.000000Z",
      "DATE" : "2016",
      "DURATION" : "1606.3550000",
      "ENCODER" : "libebml v1.3.3 + libmatroska v1.4.4",
      "GENRE" : "Featurettes",
      "TITLE" : "Creating Nerve",
   },
   {
      "@" : "Player Profiles.mkv",
      "CREATION_TIME" : "2016-10-16T16:03:56.000000Z",
      "DURATION" : "347.6030000",
      "TITLE" : "Player Profiles"
   },
   {
      "@" : "The Fat Jewish Gets Tattewish - Outtakes.mkv",
      "CREATION_TIME" : "2016-10-16T16:11:23.000000Z",
      "DURATION" : "168.1040000",
      "TITLE" : "The Fat Jewish Gets Tattewish - Outtakes"
   },
   {
      "@" : "The Governor's Ball Takeover.mkv",
      "CREATION_TIME" : "2016-10-16T16:24:23.000000Z",
      "DURATION" : "165.4590000",
      "TITLE" : "The Governor's Ball Takeover"
   }
]
What I need is for the WIDTH and HEIGHT info to be inserted into each "!.tags" file, but always at the right places in the file ! Appending them at the end of the file simply won't work.

Here's an example of how the previous "!.tags" file should be once the WIDTH and HEIGHT info are inserted at the right places :

Code: [Select]
[
   {
      "@" : "Creating Nerve.mkv",
      "WIDTH" : "1920",
      "HEIGHT" : "1080",
      "CREATION_TIME" : "2016-10-16T15:51:50.000000Z",
      "DATE" : "2016",
      "DURATION" : "1606.3550000",
      "ENCODER" : "libebml v1.3.3 + libmatroska v1.4.4",
      "GENRE" : "Featurettes",
      "TITLE" : "Creating Nerve",
   },
   {
      "@" : "Player Profiles.mkv",
      "WIDTH" : "1920",
      "HEIGHT" : "1080",
      "CREATION_TIME" : "2016-10-16T16:03:56.000000Z",
      "DURATION" : "347.6030000",
      "TITLE" : "Player Profiles"
   },
   {
      "@" : "The Fat Jewish Gets Tattewish - Outtakes.mkv",
      "WIDTH" : "1920",
      "HEIGHT" : "1080",
      "CREATION_TIME" : "2016-10-16T16:11:23.000000Z",
      "DURATION" : "168.1040000",
      "TITLE" : "The Fat Jewish Gets Tattewish - Outtakes"
   },
   {
      "@" : "The Governor's Ball Takeover.mkv",
      "WIDTH" : "1920",
      "HEIGHT" : "1080",
      "CREATION_TIME" : "2016-10-16T16:24:23.000000Z",
      "DURATION" : "165.4590000",
      "TITLE" : "The Governor's Ball Takeover"
   }
]
Or this if you prefer, nevermind :

Code: [Select]
[
   {
      "@" : "Creating Nerve.mkv",
      "CREATION_TIME" : "2016-10-16T15:51:50.000000Z",
      "DATE" : "2016",
      "DURATION" : "1606.3550000",
      "ENCODER" : "libebml v1.3.3 + libmatroska v1.4.4",
      "GENRE" : "Featurettes",
      "TITLE" : "Creating Nerve",
      "WIDTH" : "1920",
      "HEIGHT" : "1080"
   },
   {
      "@" : "Player Profiles.mkv",
      "CREATION_TIME" : "2016-10-16T16:03:56.000000Z",
      "DURATION" : "347.6030000",
      "TITLE" : "Player Profiles",
      "WIDTH" : "1920",
      "HEIGHT" : "1080"
   },
   {
      "@" : "The Fat Jewish Gets Tattewish - Outtakes.mkv",
      "CREATION_TIME" : "2016-10-16T16:11:23.000000Z",
      "DURATION" : "168.1040000",
      "TITLE" : "The Fat Jewish Gets Tattewish - Outtakes",
      "WIDTH" : "1920",
      "HEIGHT" : "1080"
   },
   {
      "@" : "The Governor's Ball Takeover.mkv",
      "CREATION_TIME" : "2016-10-16T16:24:23.000000Z",
      "DURATION" : "165.4590000",
      "TITLE" : "The Governor's Ball Takeover",
      "WIDTH" : "1920",
      "HEIGHT" : "1080"
   }
]
So, we're making progress, but we're not there yet :) Thanks !
2
Audio Hardware / Re: Help me build my first serious music (stereo) system
Last post by LazyBorzoi -
So, a bunch more questions:

1) Do you have a carpet in the room? No carpet. But there is another smaller room that is carpeted that I could move my music system to.
2) Have you run the Audyssey room correction? Yes, and it does seem to help a little.
3) If so, do you have the option of viewing the results in a menu (it will look like a sort of rough EQ graph) and No, my AVR doesn't seem to have this option...
4) Do you use the Audyssey, Audyssey Flat, L/R Bypass or Off settings? (if you have them) Just Audyssey
5) To the extent you can tell, is the harshness in the upper-midbass region 150-250 Hz or midrange 1-2Khz?  Or elsewhere? Highs
6) Does it change if you get up and walk around, sit on the floor, etc? I don't know as I usually don't walk around while listening.
7) Lastly (for today), how old are you and do you have any hearing problems (tinnitus, etc) or are you exposed to loud noise?
Mid 30s, no hearing issues other than my ears are very sensitive - hence I prefer to listen to music at low to mid volumes :-)


4
MP3 / Re: best mp3 encoder with something better than a command line interface?
Last post by saratoga -
Default settings are choosen by the devlopers for a reason. If you're the kind of user who thinks posting spectrograms of mp3s is a good idea, you should probably should stick to the defaults.
Are you happy now? Check the ABX tests. The encoded sample sounds better, more vivid and selective sounds, less noise.

That is an ABX test comparing a WAV and an MP3.  Assuming the WAV is the lossless file and the MP3 is your custom compile, that shows is that your MP3 is not transparent, which is a bad thing.

I posted spectograms only to see the encoded .mp3 was not butchered by the encoder (trimmed from 20 kHz to 16 kHz), as you suggest with the default settings and so on.

A spectrogram cannot show you if a file was "butchered".  It just shows you the spectrum, which is irrelevant.  It is not impossible that you might outsmart the developers, but if you're looking at spectrograms, it is very, very unlikely.

May you tell me what is the reason the developers locked for general use the fine tuning (psychoacoustics) of lame v3.100?

Generally settings are exposed if there is a reason a user might need to change them.  For things that don't have a reason to change they're not exposed.

5
MP3 / Re: why does the file sound better
Last post by greynol -
If you were to tell me that you could discern 160kbit mp3 from the original source, I'd believe you.  An ABX test should be performed, but 160kbit mp3 is commonly accepted as non-transparent.

If you're experiencing a large jump in volume from mp3 to wave then the issue will likely be caused by the mp3 containing replaygain data and the player using this data, whereas the level correction was not employed when the wave file was played back.  This could either be that the replaygain data was discarded during the conversion or was maintained as a RIFF chunk in the wav file which was not used by the player.  It could instead/also be limiting by the OS, but I seriously doubt it.  The existence of replaygain data in the mp3 file can be determined with a proper tag editor such as mp3tag or foobar2000.  If you use foobar2000 for playback and/or conversion you can elect whether not to use this data.  I can't speak for dbpoweramp.

It's also possible, that converting mp3 to flac will retain replaygain data, which would likely mean the playback level between the two won't change.  However, it seems like the differences you're describing do not include the same change in level, in which case it's simply placebo effect.  Decoding mp3 results in the exact same audio data regardless of whether the destination format is flac or wave.

While it might feel insulting to be told you're imagining differences, placebo effect/expectation bias is quite normal.

Without a proper ABX log and audio samples (which don't exceed 30 seconds in order to help address copyright infringement) we can't really know what is really happening.
6
CD Hardware/Software / Re: EAC on Win10 - process launched, no GUI
Last post by DVDdoug -
My first preference is now CueRipper because it's easy to setup and use.    But, it seems to fail quite a bit (I forget the failure message but it just stops).    When that happens I go back to EAC.

I know this doesn't help you, but I've got EAC on at least one 32-bit Win10 system, and on a couple of 64-bit Win10 systems and it's working.
8
MP3 / Re: best mp3 encoder with something better than a command line interface?
Last post by BrilliantBob -
Default settings are choosen by the devlopers for a reason. If you're the kind of user who thinks posting spectrograms of mp3s is a good idea, you should probably should stick to the defaults.
Are you happy now? Check the ABX tests. The encoded sample sounds better, more vivid and selective sounds, less noise.

I posted spectograms only to see the encoded .mp3 was not butchered by the encoder (trimmed from 20 kHz to 16 kHz), as you suggest with the default settings and so on.

May you tell me what is the reason the developers locked for general use the fine tuning (psychoacoustics) of lame v3.100? I remember in lame v3.98 these settings was available, not locked. Commercial reasons whatever?

GiT gUd
9
MP3 / Re: why does the file sound better
Last post by tpijag -
Quote
Now if i convert from mp3 to flac, if i understand correctly the compression on the source will still take place, 'like winzip', the source in this case is mp3, whereas mp3 to wav there is no compression and sounds like the the file has been eq slightly.

At the very least, you seem to be confusing types of compression. Lossy compression such as used in creating a MP3 file by using a Psycho Acoustic Model to remove bits of audio that are likely to not be missed. [simplistic explanation].

Lossless compression - flac - as you referenced "like winzip' that removes 0 information and upon decoding is the same audio file as your wav file.

And your results, as others have tried to explain to you, is simply a possible difference in volume [perceived by most humans as better sound], something broken in what you are doing, or delusional, placebo thinking.

Continuing to tell us that you listen carefully and there are differences is pointless. Take the time to learn to volume level match your files and do a ABX test and report back.   Foobar2000 would be an easy and acceptable program to used for double blink ABX test.

10
MP3 / Re: why does the file sound better
Last post by greynol -
mp3 track will say compressed 89%
flac will say 36% compressed
whereas wave say 0 compressed
This is all about file size and nothing about quality.

[using my ears]
Your ears have clearly deceived you.
https://en.wikipedia.org/wiki/Placebo

Quote
TOS 8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objective support for their claims.  Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings.  non-blind listening tests [...] are not acceptable
Quote
You can read how to easily perform double blind listening tests here :
What is a blind ABX test ?
https://www.foobar2000.org/
https://www.foobar2000.org/components/view/foo_abx

As it stands your anecdotal evidence of what you hear is useless.

As was mentioned, peaks in mp3 files can go above 0 dBFS.  Insofar as to whether your operating system is limiting the mp3 file, this will need to be taken into account in order to perform an apples to apples to comparison.  However, peaks from mp3 files exceeding 0dBFS will result in wave files that will reach 0dBFS which can and likely will be limited as well.
SimplePortal 1.0.0 RC1 © 2008-2018