[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#712026: transcriber review



Il 12/08/2013 09:41, Paul Wise ha scritto:
> On Mon, 2013-08-12 at 00:05 +0200, Giulio Paci wrote:
> 
> [...] copyright_hints [...]
> 
> Maybe it would be best to drop it entirely, it doesn't seem that useful.

I have not yet a strong opinion on it.
More often than not, its presence just created small problems, like the one you reported, but sometime it also spotted real issues and proved to be useful.
I prefer to keep it there for now.

>> I do not think it is possible to solve this in transcriber. Am I wrong?
> 
> From debian/rules:
> 
> DEB_DH_INSTALL_ARGS = debian/transcriber.desktop usr/share/applications

I completely forgot that line... I got so used to that message not being correct in the past that I even did not check the rules... Sorry about that.
It is fixed now.

>> The sphere audio format is designed to cheat text editors: the header is 1024 bytes long and is plain ascii, so that most text editors will open the file as text.
>> So it is not a text file, but a binary one.
> 
> Hmm, ok. A weird audio format, I wonder why it is used instead of just
> ogg, flac or similar.

It is a little bit weird, I agree, but is also very widespread in the speech community.
Actually sphere is a container and not a codec and its direct competitor is Wav. The long and detailed header usually contains a lot of information about the recording
environment and this explains its large usage.
With respect to flac (the container, not the codec), it is able to contain A-law and u-law streams (useful when studying telephone speech) and shorten
(http://www.etree.org/shncom.html, used by some widespread speech Corpora, especially those from LDC).
If I remember correctly the ogg container is able to contain all the streams (probably with the exception of shorten) that can be contained by sph files and probably it is
also able to contain all the header information, but I am not sure of this and the format is much younger.

>> Unless any of the following is blocker, I prefer to fix/decide to not fix them later.
> 
> None are.

Fine.

Bests,
	Giulio.


Reply to: