), you would pull from Paratext locally on your machine.Here are some reasons why you might want to pull textual data from Paratext into Audio Project Manager or Desktop:
There is vernacular or back translation content in Paratext for the passage you will transcribe and you do not want to type it again.
Your workflow has a Sync to Paratext step. You ran checks in Paratext and you made corrections in Paratext. Or, you inserted verse numbers for individual verses instead of leaving a ranges of verses.
Note: Depending on how your team works, you may need to record another audio version to match the corrected transcription.
It might be from a previous transcription made in Audio Project Manager or Desktop with an earlier version of the audio file, and you want the complete history of a passage in Audio Project Manager (for data management purposes).
You can do this while online or offline. If offline (), you would pull from Paratext locally on your machine.
See: My Account overview.
You must be logged in if you will pull from Paratext online.
The audio project type must be Scripture (
).
In the Integrations dialog box:
The top control must show the correct choice: Vernacular or Back Translation.
the Select Paratext Project control must show the correct Paratext project.
Typically the vernacular and back translation data come from different projects. But both must be registered.
You must be in the Transcribe view.
Vernacular and back translation work typically results from different steps in the workflow.
Transcribe, Transcribing, Incomplete or Connection Needed.
In the Work view, click a passage you want to transcribe.
Click 
(Pull transcription from Paratext).
The transcription for that passage is pulled from Paratext into Audio Project Manager or Desktop.
It replaces any other transcription that was there.
Now you can continue with your workflow if you use one.