IPB

Welcome Guest ( Log In | Register )

8 Pages V  « < 4 5 6 7 8 >  
Reply to this topicStart new topic
libebur128 - (yet another) EBU R 128 implementation
Raiden
post Apr 4 2011, 22:47
Post #126





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



I've uploaded 0.3.2 that fixes the slow down issue with denormal numbers. I'm using the "Fix-up solution" from here.

Download
Go to the top of the page
+Quote Post
Surfi
post Apr 5 2011, 08:25
Post #127





Group: Members
Posts: 175
Joined: 1-October 04
Member No.: 17420



::

Thanks! (... but can't download, receiving zero-byte achives.)
Any chance for getting a true peak tagging option?


Greetings ...

::
Go to the top of the page
+Quote Post
Raiden
post Apr 5 2011, 12:31
Post #128





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (Surfi @ Apr 5 2011, 08:25) *
Thanks! (... but can't download, receiving zero-byte achives.)
Whoops, went over my quota... the archives should be uploaded now.

QUOTE (Surfi @ Apr 5 2011, 08:25) *
Any chance for getting a true peak tagging option?
I'm not sure about this. I really want to follow the ReplayGain spec, but maybe adding a hidden, undocumented option for those you really want this feature won't hurt.


I've got a question about BS.1770: How is 7.1 audio handled?
Go to the top of the page
+Quote Post
Surfi
post Apr 5 2011, 20:49
Post #129





Group: Members
Posts: 175
Joined: 1-October 04
Member No.: 17420



QUOTE (Raiden @ Apr 5 2011, 12:31) *
..., but maybe adding a hidden, undocumented option for those you really want this feature won't hurt.

Awesome! smile.gif

QUOTE (Raiden @ Apr 5 2011, 12:31) *
I've got a question about BS.1770: How is 7.1 audio handled?

I'm sorry to say that I've no idea. sad.gif

Go to the top of the page
+Quote Post
gjgriffith
post Apr 6 2011, 18:13
Post #130





Group: Members
Posts: 7
Joined: 31-January 11
Member No.: 87795



Thanks again for such a great tool.

I've noticed that mono flacs are tagged for 3.01 dB more gain than a stereo (dual-mono) equivalent. ReplayGain does not work this way (it will calulate identical gain).

Although I understand why it is doing this (one speaker is 3 dB quieter than two), the vast majority of players will treat a mono file identically to its dual-mono equivalent, thus the present tagging will result in the mono flac playing 3 dB louder than its dual mono equivlaent.

Is there a chance of either changing this or adding an option to change it? I don't have many mono flacs, but I have enough that I don't relish tracking them down and treating them differently than stereo flacs.
Go to the top of the page
+Quote Post
Raiden
post Apr 6 2011, 19:38
Post #131





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (gjgriffith @ Apr 6 2011, 18:13) *
Is there a chance of either changing this or adding an option to change it?

I agree. Mono files should be treated as dual mono for the RG tags. Fixing this now.
Go to the top of the page
+Quote Post
Emery
post Apr 9 2011, 03:44
Post #132





Group: Validating
Posts: 4
Joined: 2-April 11
Member No.: 89497



I've been using this to set gain levels in an FM station's automation system and it tears through files four times faster than the last analyzer I was using.
Thanks

This post has been edited by Emery: Apr 9 2011, 04:30
Go to the top of the page
+Quote Post
audionuma
post Apr 13 2011, 21:23
Post #133





Group: Members
Posts: 6
Joined: 25-March 11
Member No.: 89293



ITU-R BS.1770-2 available.
75% overlapping and -10 dB relative gate ...
I guess the R128 should soon be modified in the same way.
Go to the top of the page
+Quote Post
Raiden
post Apr 13 2011, 22:20
Post #134





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (audionuma @ Apr 13 2011, 21:23) *
ITU-R BS.1770-2 available.
75% overlapping and -10 dB relative gate ...
I guess the R128 should soon be modified in the same way.
Great! Time to change the relative gate accordingly. The block overlap already is at 75%.

QUOTE (Emery @ Apr 9 2011, 03:44) *
I've been using this to set gain levels in an FM station's automation system and it tears through files four times faster than the last analyzer I was using.
Thanks for the positive feedback smile.gif

I should be releasing 0.4 in the next few days. Now there is only one scanner executable with different input plugins instead of one exe for each input library. The scanner automatically chooses the best input plugin for each file. This should make it easier to tag/scan different audio formats at the same time.
I've also implemented a hidden option "--tag-tp" for true peak tagging and fixed the ReplayGain loudness for mono files.
Go to the top of the page
+Quote Post
Surfi
post Apr 14 2011, 15:18
Post #135





Group: Members
Posts: 175
Joined: 1-October 04
Member No.: 17420



QUOTE (Raiden @ Apr 13 2011, 23:20) *
I've also implemented a hidden option "--tag-tp" for true peak tagging ...
::

Thank you very much! cool.gif
Can't wait to try it.

Greetings ...

::
Go to the top of the page
+Quote Post
Raiden
post Apr 26 2011, 00:24
Post #136





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



Finally, 0.4.0 is up! Now on GitHub, too!

change log:
- reorganized the project folder structure. The scanner and the library each get their own subdirectory.

Scanner:
- there is only one scanner executable now, using input plugins. The scanner will automatically choose the best plugin for each file. To get the old behaviour, use the option "--force-plugin" with a plugin name.
- add hidden --tag-tp flag for true peak ReplayGain tagging.
- improved output and help screen
- fix ReplayGain scanning for mono files

Library:
- set relative gate to -10dB according to the new BS.1770 revision
- don't expose library internals in header
- add dual mono support (a mono channel that counts twice, needed for proper ReplayGain support)


Download
Go to the top of the page
+Quote Post
krafty
post Apr 26 2011, 00:34
Post #137





Group: Members
Posts: 266
Joined: 20-March 10
Member No.: 79175



Thanks Raiden! Looking forward to re-scan my entire library when fb2K incorporates this version.
Go to the top of the page
+Quote Post
habasud
post Apr 26 2011, 20:03
Post #138





Group: Members
Posts: 15
Joined: 22-February 11
Member No.: 88387



[quote name='Raiden' date='Apr 26 2011, 00:24' post='753399']
Finally, 0.4.0 is up!

I noticed that files ending on ".MP3" are not processed properly. When I change the ending to lowercase everything works as expected...

Claus
Go to the top of the page
+Quote Post
habasud
post Apr 28 2011, 12:57
Post #139





Group: Members
Posts: 15
Joined: 22-February 11
Member No.: 88387



I've tinkered a little bit and found out, that the ffmpeg plugin is loaded when I use "force-plugin=ffmpeg0.5.2". Then files with the "MP3" ending in capitals are analysed. Just "...=ffmpeg" didn't work. Unfortunately some of the filetypes supported by ffmpeg don't work anymore. E.g. "mov" video files aren't recognized.

When a plugin can't be loaded the scanner nevertheless exits with exit code "0". Maybe it would be a good idea to change this.

So I think that the "case sensitivity" is not the point. Maybe different plugins are loaded depending on the ending - I don't know. Perhaps a debug option like "-v" that prints out the used plugin could help to determin, which plugin causes which behavior.

I used the precompiled 32bit/sse2 version on ubuntu...

Hope this helps - thanks!
Claus
Go to the top of the page
+Quote Post
Raiden
post Apr 28 2011, 17:15
Post #140





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (habasud @ Apr 28 2011, 12:57) *
I've tinkered a little bit and found out, that the ffmpeg plugin is loaded when I use "force-plugin=ffmpeg0.5.2". Then files with the "MP3" ending in capitals are analysed. Just "...=ffmpeg" didn't work. Unfortunately some of the filetypes supported by ffmpeg don't work anymore. E.g. "mov" video files aren't recognized.

Thanks for your feedback, the file extension recognition is now case insensitive.
When forcing the plugin, is the mov file analyzed? I've hardcoded the most common extensions in the input_*.c source files but forgot mov.
QUOTE (habasud @ Apr 28 2011, 12:57) *
When a plugin can't be loaded the scanner nevertheless exits with exit code "0". Maybe it would be a good idea to change this.

So I think that the "case sensitivity" is not the point. Maybe different plugins are loaded depending on the ending - I don't know. Perhaps a debug option like "-v" that prints out the used plugin could help to determin, which plugin causes which behavior.

Sounds good, I'll implement this.
Go to the top of the page
+Quote Post
habasud
post Apr 28 2011, 22:13
Post #141





Group: Members
Posts: 15
Joined: 22-February 11
Member No.: 88387



QUOTE
When forcing the plugin, is the mov file analyzed? I've hardcoded the most common extensions in the input_*.c source files but forgot mov.


No, it isn't:

CODE
user@lappi:~$ r128-scanner --force-plugin=ffmpeg0.5.2  Desktop/cimg9753.mov  
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x9fc7b20]moov atom not found
Could not open input file!
nan LUFS, Desktop/cimg9753.mov
--------------------------------------------------------------------------------
-inf LUFS

Go to the top of the page
+Quote Post
pbelkner
post Apr 29 2011, 06:56
Post #142





Group: Members
Posts: 412
Joined: 13-June 10
Member No.: 81467



QUOTE (habasud @ Apr 28 2011, 22:13) *
CODE
user@lappi:~$ r128-scanner --force-plugin=ffmpeg0.5.2  Desktop/cimg9753.mov  
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x9fc7b20]moov atom not found
Could not open input file!
nan LUFS, Desktop/cimg9753.mov
--------------------------------------------------------------------------------
-inf LUFS

This message seem to com from FFmpeg. The same message should appear if you run

CODE
ffmpeg -i Desktop/cimg9753.mov

There's a tool called "qt-faststart" which may help to re-arrange the MOV in order that FFmpeg can deal with it:

QUOTE
This utility rearranges a Quicktime file such that the moov atom is in front of the data, thus facilitating network streaming.


This post has been edited by pbelkner: Apr 29 2011, 06:57
Go to the top of the page
+Quote Post
habasud
post Apr 29 2011, 09:30
Post #143





Group: Members
Posts: 15
Joined: 22-February 11
Member No.: 88387



QUOTE
There's a tool called "qt-faststart" which may help to re-arrange the MOV in order that FFmpeg can deal with it
:

Yes, it worked - Thank you! I tried to analyse the mov with the old r128-ffmpeg and I must admit that it didn't handle the file either... sory!
Go to the top of the page
+Quote Post
Emery
post May 11 2011, 18:53
Post #144





Group: Validating
Posts: 4
Joined: 2-April 11
Member No.: 89497



I liked this so much I packaged it for gentoo and put it in the proaudio overlay.
So if you're using gentoo, you can install by doing this,
CODE
emerge -u layman
layman -a pro-audio
emerge -av r128-scanner
Go to the top of the page
+Quote Post
Raiden
post May 12 2011, 00:24
Post #145





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (Emery @ May 11 2011, 18:53) *
I liked this so much I packaged it for gentoo and put it in the proaudio overlay.
Wow, this is pretty awesome. Thanks for your efforts!

This post has been edited by Raiden: May 12 2011, 00:25
Go to the top of the page
+Quote Post
R_R
post Jul 7 2011, 16:24
Post #146





Group: Members
Posts: 3
Joined: 7-July 11
Member No.: 92111



Hello Raiden,

First, many thanks for your work on this.

I'm using the gentoo packet from the pro-audio overlay (tx Emery!). I've already scanned my collection, with very good results, but there are some glitches I want to share.

flac and ogg files get overwritten perfectly. No problem there.

On mp3 files, tags are not overwritten but duplicated.

On mp2 files there is an error when using the default plugin:
This error doesn't happen when forcing the ffmpeg plugin, but in any case tags are not written, contrary to stdout indication. This is a sample command output with default plugin:

> r128-scanner -t track Radio/+La_Casa_del_Sonido-110527.mp2

[id3.c:940] error: Invalid UTF16 surrogate pair at 982 (0xfeff).
[id3.c:940] error: Invalid UTF16 surrogate pair at 982 (0xfeff).
0.06 dB, sample peak: 0.53888178, Radio/+La_Casa_del_Sonido-110527.mp2
--------------------------------------------------------------------------------
0.06 dB, sample peak: 0.53888178
tagging...

I usually tag .mp2 files with Ex falso. They are ES mpeg files recorded from DVB card.

Thanks in advance,

Roberto
Go to the top of the page
+Quote Post
Raiden
post Jul 19 2011, 23:20
Post #147





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (R_R @ Jul 7 2011, 16:24) *
On mp3 files, tags are not overwritten but duplicated.
I can't reproduce this. Are your files tagged with ID3v1 tags? The scanner will always write ID3v2 tags which could show up as duplicates.

QUOTE (R_R @ Jul 7 2011, 16:24) *
[id3.c:940] error: Invalid UTF16 surrogate pair at 982 (0xfeff).
[id3.c:940] error: Invalid UTF16 surrogate pair at 982 (0xfeff).
I can't really supress those errors from the mpg123 library. It looks like your input file is somehow corrupt. I wouldn't worry about it, though.

QUOTE (R_R @ Jul 7 2011, 16:24) *
but in any case tags are not written, contrary to stdout indication.
Support for mp2 tagging is now in newest git. I'll try to get a new version out soon.
Go to the top of the page
+Quote Post
Surfi
post Jul 20 2011, 06:46
Post #148





Group: Members
Posts: 175
Joined: 1-October 04
Member No.: 17420



::

... don't forget to correct the issue noted in post #138, please. Mixed case endings should also be processed properly.


Greetings ...

::

This post has been edited by Surfi: Jul 20 2011, 06:46
Go to the top of the page
+Quote Post
Raiden
post Jul 20 2011, 09:35
Post #149





Group: Developer
Posts: 224
Joined: 14-September 04
Member No.: 17002



QUOTE (Surfi @ Jul 20 2011, 06:46) *
... don't forget to correct the issue noted in post #138, please. Mixed case endings should also be processed properly.

This should be fixed in newest git.
Go to the top of the page
+Quote Post
R_R
post Jul 20 2011, 10:31
Post #150





Group: Members
Posts: 3
Joined: 7-July 11
Member No.: 92111



QUOTE (Raiden @ Jul 20 2011, 00:20) *
QUOTE (R_R @ Jul 7 2011, 16:24) *
On mp3 files, tags are not overwritten but duplicated.
I can't reproduce this. Are your files tagged with ID3v1 tags? The scanner will always write ID3v2 tags which could show up as duplicates.


Yes, this seems to be the case, thank you.

QUOTE
Support for mp2 tagging is now in newest git. I'll try to get a new version out soon.


Great, this will be a very appreciated adition for me. Thanks again,

Roberto
Go to the top of the page
+Quote Post

8 Pages V  « < 4 5 6 7 8 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 17th April 2014 - 00:29