Re: [Kaldi-developers] Poor man's Kaldi recipe

[Daniel P. <dp...@gm...>]

I think for something like this it's not necessary to create a
branch-- you can just get it working on your local copy, and check it
in when it's done.  Since the stuff you're doing wouldn't break any
functionality in anything else, I don't think we need to test it too
thoroughly before adding it.  RE the binary that converts CMU's
feature files into a table-- do you have source for this?  Is it
written in the Kaldi style?  We could just include it in the tools,
e.g. in featbin/
BTW, the Apache copyright notice should have just your name-- it's
whoever wrote the tool.  Hopefully you don't work for a company that
claims ownership of whatever you do.
Dan

On Wed, Feb 22, 2012 at 4:59 AM, Vassil Panayotov
<vas...@gm...> wrote:
> Hello Dan,
>
> I am glad you like the idea!
> Of course, from maintanance and visibility point of view, it is always
> better for a recipe to be part of the official distribution. I am
> ready to help with the integration and maintanance of this recipe. How
> about setting a SVN branch, where these scripts will be integrated and
> merging it into trunk after it's ready?
> I agree, that the more exotic tools if needed should be kept
> separately from the core ones. The only binary tool that is essential
> here is the one that packs CMU's feature files into a Kaldi Table.
> Even this tool can be avoided, if needed, by shipping pre-built
> ark/scp.
>
> Vassil
>
> On Tue, Feb 21, 2012 at 5:44 PM, Daniel Povey <dp...@gm...> wrote:
>> Actually, I wonder whether it would make more sense to include your
>> recipe as an alternative within the examples in the sourceforge
>> repository?  E.g. egs/rm/s2 ?  We did need a recipe that didn't rely
>> on LDC data.  Perhaps we could add you as a committer on Sourceforge,
>> and you can check it in?  BTW, if you want to add any new tools e.g.
>> in the tools/ directory, I prefer if this is done by the scripts in
>> the egs/rm/s2 directory (or whatever it is called), rather than the
>> install scripts in tools/ itself, since those are supposed to be
>> things that are more universally used.
>>
>> Dan
>>
>> On Tue, Feb 21, 2012 at 10:35 AM, Daniel Povey <dp...@gm...> wrote:
>>> That's excellent!  I'll try to include a link to your blog from
>>> somewhere Kaldi-related.
>>> RE the pre-built acoustic models-- we'll have to think about this...
>>> it seems like a good idea, but it's a question of how to select them
>>> and update them, and to provide the extra stuff people would need
>>> (e.g. instructions how to use them).
>>>
>>> Dan
>>>
>>> On Mon, Feb 20, 2012 at 6:20 AM, Vassil Panayotov
>>> <vas...@gm...> wrote:
>>>> Hi everyone,
>>>>
>>>> Just wanted to let you know, that I just wrote a post on my brand new
>>>> blog about using Kaldi with the free RM1 subset available from CMU
>>>> (http://vpanayotov.blogspot.com/2012/02/poor-mans-kaldi-recipe-setup.html).
>>>> I do understand that the toolkit is targeted mostly toward the
>>>> researchers, but if other hobbyists want to try it, why not...
>>>>
>>>> I would also like to ask if it would be possible for you to make some
>>>> pre-built acoustic models available on Kaldi's SourceForge site or
>>>> elsewhere? I mean something like this:
>>>> http://www.keithv.com/software/htk/us/ and
>>>> http://www.keithv.com/software/sphinx/us/ .
>>>>
>>>> Regards,
>>>> Vassil
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Keep Your Developer Skills Current with LearnDevNow!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-d2d
>>>> _______________________________________________
>>>> Kaldi-developers mailing list
>>>> Kal...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers