Add support for styles like bold and italic, along with custom font colors and varying fonts and font sizes.252 votes
On OS X, we'd use the built-in spell checker. For Windows, we're looking at several options, and are currently leaning towards hunspell, an open-source project with support for several languages. The Open Office project also uses hunspell.238 votes
Add an AutoCorrect feauture, similar to those in mobile devices and word processors. Since some users type shorthand or use codes in their transcript, an ability to turn off this feature is essential.
It would be great to have the following:
- Automatically make every sentence start with a capital letter.
- Include a system that recognizes frequently used words and names.44 votes
That way the same inqscribe file can point to different media files. This is useful if, for example, you wanted to show lots of examples of the same category which occur in different media files.39 votes
Adding an option to display line numbers would make collaboration and identifying errors easier.34 votes
Hi, this is still in our feature queue. We hope to add it in a future release.
Instead of plain text area . Let us choose the number of colums visible.
Would be fare more useful and easily exporable for stuctural data instead of relying on TABs and returns that are not always visible.33 votes
Thanks for writing in the request! Naturally, having a spreadsheet work area would allow easy export to Excel, so I’ve added that to the description. We’ll consider spreadsheet support for a future InqScribe update. For a current workaround, head over to our blog: http://blogs.inquirium.net/inqscribe/2014/01/inqscribe-tips-format-transcripts-as-tables/
Implement some sort of arbitrary background/foreground coloring, as in the mac application Writeroom (e.g., White/Blue). Easy on eyes!
Also include custom coloring for the green bar at the top of the InqScribe window.32 votes
Thanks for writing in the suggestion. We will consider adding custom coloring for a future update of InqScribe!
I’ve edited the description to include custom coloring for the top green bar as per user request.
The timecode display right now is way too small and difficult to see. I wish it were bigger and more visible. Either Inquirium can make it so, or give us controls over its appearance, font, color, etc.31 votes
Thanks for writing in your request. We will consider either enlarging the current timeline text display, or allowing users to control the timeline font size.
add an option for a beep every xx seconds so the transcriber can insert a timstamp while listening...11 votes
Thanks for writing in the request! We don’t currently support automatic timecodes every xx seconds because words would get jumbled, coming out like th[00:00:11.11]is. So, your suggestion could provide a neat solution. We will consider it for a future InqScribe update.
Note that you can lay down timecodes every xx seconds before you start typing. Read how in our Knowledge Base: http://support.inqscribe.com/knowledgebase/articles/22885-can-i-automatically-insert-a-timecode-in-a-series
We also offer some general timecode insertion tips here: http://support.inqscribe.com/knowledgebase/articles/171934-can-i-automatically-insert-timecodes-at-regular-ti
Look at what happens in OpenOffice Writer. When the cursor reaches the top or the bottom of the text area (moving it with the up and down arrow keys or simply typing lines of text downwards) the block cursor+text is scrolled down or up (respectively) to "reposition" the used part of the text area near the vertical center of the window. This is very useful when typing, for example, because prevents the user typing all the time at the bottom of the window. Part of this behaviour (i.e. when typing at the bottom of the text area, and not when simply moving the cursor toward the upper or lower limit of the text area) appears in Microsoft Word too; in Microsoft Notepad and Microsoft Wordpad is absent. It's absent in Inqscribe too: when I type and reach the text area bottom, the text is moved upwards one line at a time, so I type at the bottom of the window all the time. What about implementing a scrolling behaviour like the one mentioned above? Thanks for your attention, have a nice day.
Look at what happens in OpenOffice Writer. When the cursor reaches the top or the bottom of the text area (moving it with the up and down arrow keys or simply typing lines of text downwards) the block cursor+text is scrolled down or up (respectively) to "reposition" the used part of the text area near the vertical center of the window. This is very useful when typing, for example, because prevents the user typing all the time at the bottom of the window. Part of this behaviour (i.e. when typing at the bottom of the text area, and not when…9 votes
In the transcript window, it would be helpful if there was a way to view the number of characters per subtitle/timecode. It can be difficult to quickly judge the number of characters otherwise.
Having a character count in-between timecodes would solve this problem.
Alternatively, the ability to place an adjustable vertical line across the transcript would allow you to quickly eyeball the relative length and consistency of each text chunk.6 votes
We use this program for our research with human subjects. For security sake, add a password protection on files. Right now, I have to move the files into an encryption folder, then extract them when I want to use the file again. Adding encryption or password protection directly on the .inq files would be more efficient.6 votes
Thanks for writing in the suggestion. If this idea gets enough votes, we’ll consider it for a future update!
From Danila: "Useful for looking up names and terms a transcriber is unfamiliar with."3 votes
We’ll consider the feature for a future update. Make sure to cast your votes if you’re interested in this idea.
Please add an interface that helps the users to send audio files to their accounts in Google Cloud to have them translated automatically and then corrected with InqScribe.
Create an instruction page to help your customers register with the Google Cloud Speech-to-Text API service.
I've been trying to use this service myself but am finding the instruction on Google too complicated. Too oriented to experienced software developers, which I'm not.1 vote
Per user request:
We do a lot of edits where the speaker has been misidentified. The usual format is to have the speaker ID at the start of the line followed by a colon. Right now we select the speaker with a double click and then hit a snippet key. It would be nice to be able to assign a speaker to the current line (or even multiple lines) without having to do the select. Allowing find/replace with a regex pattern, which could then to be assignable as a hotkey, would be perfect.0 votes
- Don't see your idea?