manrajsingh

I think you should refer to package.json for actual dependencies. But yes, I agree that tool dependencies are dependent on a lot of dependencies. I'll evaluate and reduce tool dependencies, if possible.

That being said, the gzipped js bundle size is fairly small (under 200kb).

Interesting usecase! Currently, the tool allows creation of datapoint along with reference transcripts. From what I understand, you wish to fix the subtitle start and end time while keeping the transcription for that segment same. If yes, we plan to add an enhancement where you can pass annotations aka segments with transcripts. This should solve your usecase.

Thank you for your suggestion! We're working hard to get a demo video out and intentionally left space for it. But sure, we can add a placeholder image till then.

Strange. Can you open an issue with logs and docker version?

We're working on a recorded demo. For now, the tutorial section explains the workflow well (with screenshots).

Even we used to do the same. Hence, we developed this tool to mitigate a lot of the pain points that previous tools brought. Thanks for sharing your experience and would love to hear your experience with this tool.

At our lab, we extensively work on problems that involve speech data. This includes tasks like speech recognition, speech scoring, emotion recognition, topic detection and speaker diarisation. Some of these tasks have public data available, while tasks like speech scoring and low-resource speech recognition, the data is fairly limited for supervised learning. Hence, we developed this annotation tool to generate corpus for our need.

To be honest, it's a happy coincidence. The name is an amalgamation of audio and annotation.

Yes! To add data to your project, we provide an API-Key and an endpoint to upload the data.

To export the data, there's an option on admin panel from where you can download it in JSON format.

Please check the tutorials section for more details: https://github.com/midas-research/audino/blob/master/docs/tu...

True, it took days to decide on the name.

Hi, I'm the author of the package. Thank you for the comment. You are correct. Halo works over py-spinners which has also been ported by me.

I spoke to @sindresorhus on Twitter and he was okay with me porting the libraries to Python (https://twitter.com/manrajsgrover/status/904396978531983360).

Check this out: https://github.com/yask123/AwesomeTwitterAccounts

Agreed. More damage can be done through JavaScript than CSS.

Thank you! My aim was to explore CSS features I didn't know were possible. Supporting different browsers was not aim of the project.

Sorry, I didn't get your second point. Please elaborate.