I thought the info was important enough to share it here ASAP. My statement was based on the latest info I hear about internally and can communicate it more expediently on community forums. Sorry for the misunderstanding and thanks for your patience. A short period time needs to elapse in order for this to happen. Then, the info can be published in this doc, which also needs time to be revieweed and localized into multiple languages. Known Issues is a living doc and may change over the course of the release.įor this issue, it may take a bit of time while the team investigates the specifics of the issue and communicates it to the docs team. No issues were known about ahead of the release, so none were published ahead of time. The Known Issues doc published at launch are typically those that are known about ahead of the release. The issue is very new and was discovered by a user after the release was available. We're editing in several languages on the same timelines, and sometimes with mixed interviews (I translate the questions/answers for the two guests when they don't have a common language.), so for us, it's important to have the ability to switch the language render engine while we edit, and not as 'source'/static. I'm ok to run Premiere in english (like I do on After) to avoid mistakes, but it's not really easy to alternate the UI language in Premiere. That means, in french, that the text IS correct and not the ability to edit/correct text. Plus, in my case, I should add that the french translations of the menu are not very relevant: i.e a right-click on some text, displays "text correct" as the first item of the menu. IMO, as the behaviour of the text features is really quite différent compared to the previous versions (source/sequence/follow active monitor/static etc.): Adobe should publish a quick tutorial on how to use it, because it's really not easy to "guess" what you've described in your post (thank you). Yes, I have the update running on the Mac workstation so, I'll give feedback in another thread (+ suggestions as I edit a lot, based on text). One of the issues is that for source clips, it is looking only at Audio track 1. When you are ready for another go, ask about this. This depends on whether you are transcribing a source clip or doing a static transcription of a sequence. It's a simple sequence for the test: 12mn of talking head, one video track, one stereo audio track. Or it says "No dialog detected", or the result of 15mn is. > 4/ In our case, tried to transcribe some sequences in english. Not intuitive, but I found that much of the built-in workflow is good. I think "Follow active monitor" is set by default. Open the source clip in the Source Monitor, then go to the Text Panel -> Transcript tab, and Re-transcribe will be an option. Re-transcribe is greyed out if you are in the Timeline/Program Monitor and the transcription is of the source clip(s). Even if you don't enable language autodetection, it will save the default language you put there. See Edit -> Preferences -> Transcription. I have not tested all the variations, but I think this problem appears when transcribing source clips, not the (now called "static") transcription. You can pre-set this, but for most transcription options, you will find that it is available. > 3/ Transcription doesn't let you choose the language (except from Project Window). This 23.4.0 version added the new Text-based editing, and it changed several aspects of transcription. I suggest, when you're ready to try again, that you post your transcription issues in a new thread.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |