VLC HowTo/Use for transcription (Linux) - Revision history

DoesItReallyMatter: +{{Example code}}

2019-03-12T08:55:41Z

+{{Example code}}

← Older revision		Revision as of 08:55, 12 March 2019
Line 1:		Line 1:
	{{Howto\|use for transcription with *nix operating systems}}		{{Howto\|use for transcription with *nix operating systems}}
			{{Example code}}

	'''OVERVIEW:'''		'''OVERVIEW:'''

DoesItReallyMatter: syntaxhighlight

2019-01-29T08:31:27Z

syntaxhighlight

← Older revision		Revision as of 08:31, 29 January 2019
Line 51:		Line 51:

	<code></code>		<code></code>
	<~~pre~~> keybind key="F1"		<big><syntaxhighlight lang="xml"> keybind key="F1"
	action name="execute"		action name="execute"
	execute /home/delwin/vlccontrol.py jogbackward /execute		execute /home/delwin/vlccontrol.py jogbackward /execute
	/action		/action
	/keybind		/keybind
	</~~pre~~>		</syntaxhighlight></big>
	<br>		<br>

Line 66:		Line 66:

	<code></code>		<code></code>
	<~~pre~~>#!/usr/bin/env python		<syntaxhighlight lang="python">#!/usr/bin/env python
	#### licensing nonsense - short version: New BSD License		#### licensing nonsense - short version: New BSD License
	#Copyright (c) 2010, Derek Barnett, Skyehaven Transcription		#Copyright (c) 2010, Derek Barnett, Skyehaven Transcription
Line 284:		Line 284:
	else:		else:
	os.system('echo "normal" \| nc.openbsd -U ' + vlcin)		os.system('echo "normal" \| nc.openbsd -U ' + vlcin)
	</~~pre~~>		</syntaxhighlight>
	<br> <br>		<br> <br>

Line 292:		Line 292:

	<br> <code></code>		<br> <code></code>
	<~~pre~~>#!/usr/bin/env python		<syntaxhighlight lang="python">#!/usr/bin/env python
	#### licensing nonsense - short version: New BSD License		#### licensing nonsense - short version: New BSD License
	#Copyright (c) 2010, Derek Barnett, Skyehaven Transcription		#Copyright (c) 2010, Derek Barnett, Skyehaven Transcription
Line 523:		Line 523:
	else:		else:
	os.system('echo "normal" \| socat - unix:' + vlcin)		os.system('echo "normal" \| socat - unix:' + vlcin)
	</~~pre~~>		</syntaxhighlight>
	<br>		<br>

DoesItReallyMatter: c/e

2019-01-21T07:59:25Z

c/e

← Older revision		Revision as of 07:59, 21 January 2019
Line 2:		Line 2:
	'''OVERVIEW:'''		'''OVERVIEW:'''

	The purpose of this howto is to show you how to configure ~~vlc~~ and use the script below to enable you to control ~~vlc~~ with scripted commands and, most importantly, take a timestamp from ~~vlc~~ and automatically type it into whatever document you are working on, without ever needing to shift focus away from the document.		The purpose of this howto is to show you how to configure VLC and use the script below to enable you to control VLC with scripted commands and, most importantly, take a timestamp from VLC and automatically type it into whatever document you are working on, without ever needing to shift focus away from the document.

	<br> There are other ways to achieve what I've done with this, many of them likely better than what is here. But this works, and works well.  This script was written for ~~linux~~, but might have some useful information for anyone trying to do this on other platforms.<br>		<br>There are other ways to achieve what I've done with this, many of them likely better than what is here. But this works, and works well.  This script was written for [[Linux]], but might have some useful information for anyone trying to do this on other platforms.<br>

	<br> '''PREREQUISITES:'''		<br> '''PREREQUISITES:'''

	First, you need to have [~~http~~://www.videolan.org/vlc/ VLC] (obviously), [http://www.python.org/ python] 2 OR 3, [http://hoopajoo.net/projects/xautomation.html xautomation] OR a version of [http://www.semicomplete.com/projects/xdotool/ xdotool] (newer than august 2010), and you need the ~~openbsd~~ implementation of [http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/ netcat]--'''Note:''' see below for a version that uses the more readily available [http://www.dest-unreach.org/socat/ socat] package.		First, you need to have [https://www.videolan.org/vlc/ VLC] (obviously), [http://www.python.org/ python] 2 OR 3, [http://hoopajoo.net/projects/xautomation.html xautomation] OR a version of [http://www.semicomplete.com/projects/xdotool/ xdotool] (newer than august 2010), and you need the [[OpenBSD]] implementation of [http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/ netcat]—'''Note:''' see below for a version that uses the more readily available [http://www.dest-unreach.org/socat/ socat] package.

	<br> The ~~openbsd~~ version of netcat is in the repositories of most major ~~linux distirbutions~~ these days. This script is written for use in ~~Archlinux~~, so it's likely that you will need to change the command used by netcat in the script. Arch uses nc.openbsd, just replace it with whatever you need. Unfortunately, the GNU implementation of netcat, which is the default in most distributions, does not seem to support UNIX sockets (the -U switch for nc.openbsd). If you run ~~slackware~~ and can't find it, check [http://www.slackbuilds.org slackbuilds].<br>		<br> The OpenBSD version of netcat is in the repositories of most major Linux distributions these days. This script is written for use in [[Arch Linux]], so it's likely that you will need to change the command used by netcat in the script. Arch uses nc.openbsd, just replace it with whatever you need. Unfortunately, the GNU implementation of netcat, which is the default in most distributions, does not seem to support UNIX sockets (the -U switch for nc.openbsd). If you run [[Slackware]] and can't find it, check [http://www.slackbuilds.org slackbuilds].<br>

	<br> xautomation will almost certainly be in your repos, and xdotool might be. xautomation seems to be the better choice if you're only concerned about how quickly it does the job, but xdotool is nice as well if you're doing fancier things with it. However, if you do choose to try xdotool, you'll need a build done later than August 2010, as some of the features used in this script are not in the older versions available in most repositories.		<br> xautomation will almost certainly be in your repos, and xdotool might be. xautomation seems to be the better choice if you're only concerned about how quickly it does the job, but xdotool is nice as well if you're doing fancier things with it. However, if you do choose to try xdotool, you'll need a build done later than August 2010, as some of the features used in this script are not in the older versions available in most repositories.
Line 20:		Line 20:
	<br> To set up vlc to use this script, go to tools->preferences and click on "show settings->all" at the bottom. From that menu, select "Interface->Main Interfaces", and check the "Remote Control Interface" box. Next, select "Interface->Main Interfaces->RC", check the "Fake TTY' box, and enter 'home/YOURNAME/vlc.sock'in the "UNIX socket command input" field.		<br> To set up vlc to use this script, go to tools->preferences and click on "show settings->all" at the bottom. From that menu, select "Interface->Main Interfaces", and check the "Remote Control Interface" box. Next, select "Interface->Main Interfaces->RC", check the "Fake TTY' box, and enter 'home/YOURNAME/vlc.sock'in the "UNIX socket command input" field.

	<br> You probably also want to adjust the "Very short jump length" located in "Interface->Hotkeys settings". This script assumes that it is set for 5 seconds rather than the default of 3 seconds. It won't affect the script if you don't change this value, as it uses the 'very short jump' command rather than jogging a specific number of seconds. If you poke around the ~~vlc~~ docs, you'll see a seek command, but that is to go to a certain point in a file rather than going forward or backward a certain number of seconds.		<br> You probably also want to adjust the "Very short jump length" located in "Interface->Hotkeys settings". This script assumes that it is set for 5 seconds rather than the default of 3 seconds. It won't affect the script if you don't change this value, as it uses the 'very short jump' command rather than jogging a specific number of seconds. If you poke around the VLC docs, you'll see a seek command, but that is to go to a certain point in a file rather than going forward or backward a certain number of seconds.

	<br> Hit "Save". Restart VLC, and check to see if it creates "vlc.sock" in your home directory. This should be created automatically when ~~vlc~~ starts. If it doesn't, check your socket path and try again.		<br> Hit "Save". Restart VLC, and check to see if it creates "vlc.sock" in your home directory. This should be created automatically when VLC starts. If it doesn't, check your socket path and try again.

	<br> Next, you need to set up your control keys for your window environment. Remember to check to make sure that whichever control keys you wish to use are not already used by your window manager. Redefine these control keys or the defaults as necessary. I didn't have any luck with the global hotkeys settings within VLC but, personally, I like having these commands in the script. You may have better results with some experimentation.		<br> Next, you need to set up your control keys for your window environment. Remember to check to make sure that whichever control keys you wish to use are not already used by your window manager. Redefine these control keys or the defaults as necessary. I didn't have any luck with the global hotkeys settings within VLC but, personally, I like having these commands in the script. You may have better results with some experimentation.
Line 48:		Line 48:
	<br> If you use kde4, open system settings, click on 'Shortcuts and Gestures', then choose 'Custom Shortcuts'. In the second pane, under name, choose an appropriate group to put your new bindings (it might be a good idea to create a new group for these under 'Preset Actions', choose 'New Group' from the 'Edit' menu below the second pane.) Click on 'Edit', go to New->Global Shortcut->Command/URL, and name the action. While the new action is selected, click the 'Trigger' tab in the right hand pane, click shortcut box and hit the key you wish to bind to the action (F1). Then go to action and enter in the command for that action (/home/YOURNAME/vlccontrol.py jogbackward.)		<br> If you use kde4, open system settings, click on 'Shortcuts and Gestures', then choose 'Custom Shortcuts'. In the second pane, under name, choose an appropriate group to put your new bindings (it might be a good idea to create a new group for these under 'Preset Actions', choose 'New Group' from the 'Edit' menu below the second pane.) Click on 'Edit', go to New->Global Shortcut->Command/URL, and name the action. While the new action is selected, click the 'Trigger' tab in the right hand pane, click shortcut box and hit the key you wish to bind to the action (F1). Then go to action and enter in the command for that action (/home/YOURNAME/vlccontrol.py jogbackward.)

	<br> In any window manager which utilizes an rc.xml file for it's keybindings, like OpenBox, edit the rc.xml in a text editor and go down to the 'keybindings' section. Just follow along with the other keybind examples in the file, it's fairly ~~straightfoward~~, but your first entry should look something like this, although you will need to put in appropriate symbols around the keywords:		<br> In any window manager which utilizes an rc.xml file for it's keybindings, like OpenBox, edit the rc.xml in a text editor and go down to the 'keybindings' section. Just follow along with the other keybind examples in the file, it's fairly straightforward, but your first entry should look something like this, although you will need to put in appropriate symbols around the keywords:

	<code></code>		<code></code>
Line 549:		Line 549:
	<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.		<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.

	<br> Finally, variable bit ~~rates~~ are a pain for transcription. You'll get files which simply won't behave in a useful manner when you try and jog backward, et cetera. You can try converting those files to ogg format, and that generally solves the problem.		<br> Finally, [[variable bit rate]]s are a pain for transcription. You'll get files which simply won't behave in a useful manner when you try and jog backward, et cetera. You can try converting those files to [[ogg]] format, and that generally solves the problem.

	* More of [[VLC HowTo\|VLC HowTo]]
	<br> If you have any questions about this, I can be reached at derek at skyehaven.net.		<br> If you have any questions about this, I can be reached at derek at skyehaven.net.

			[[Category:Example code]]
	[[Category:GNU/Linux]]		[[Category:GNU/Linux]]
	~~[[Category:How_To]]~~

DoesItReallyMatter: Added page to :Category:GNU/Linux

2019-01-21T07:49:03Z

Added page to Category:GNU/Linux

← Older revision		Revision as of 07:49, 21 January 2019
Line 554:		Line 554:
	<br> If you have any questions about this, I can be reached at derek at skyehaven.net.		<br> If you have any questions about this, I can be reached at derek at skyehaven.net.

			[[Category:GNU/Linux]]
	[[Category:How_To]]		[[Category:How_To]]

DoesItReallyMatter: Add Template:Howto

2016-11-07T08:21:32Z

Add Template:Howto

← Older revision		Revision as of 08:21, 7 November 2016
Line 1:		Line 1:
			{{Howto\|use for transcription with *nix operating systems}}
	'''OVERVIEW:'''		'''OVERVIEW:'''

DoesItReallyMatter: DoesItReallyMatter moved page How to use VLC for transcription in linux to VLC HowTo/Use for transcription (Linux): Renaming how-to articles per Talk:VLC HowTo (permalink)

2016-11-07T08:19:17Z

DoesItReallyMatter moved page How to use VLC for transcription in linux to VLC HowTo/Use for transcription (Linux): Renaming how-to articles per Talk:VLC HowTo (permalink)

← Older revision	Revision as of 08:19, 7 November 2016
(No difference)

Chrisberov at 12:34, 28 November 2011

2011-11-28T12:34:59Z

← Older revision		Revision as of 12:34, 28 November 2011
Line 550:		Line 550:
	<br> Finally, variable bit rates are a pain for transcription. You'll get files which simply won't behave in a useful manner when you try and jog backward, et cetera. You can try converting those files to ogg format, and that generally solves the problem.		<br> Finally, variable bit rates are a pain for transcription. You'll get files which simply won't behave in a useful manner when you try and jog backward, et cetera. You can try converting those files to ogg format, and that generally solves the problem.

			* More of [[VLC HowTo\|VLC HowTo]]
	<br> If you have any questions about this, I can be reached at derek at skyehaven.net.		<br> If you have any questions about this, I can be reached at derek at skyehaven.net.

	[[Category:How_To]]		[[Category:How_To]]

J.L. Reid: Added a lightly modified version of the script that uses socat instead of openbsd's netcat build.

2011-01-26T05:09:40Z

Added a lightly modified version of the script that uses socat instead of openbsd's netcat build.

Show changes

Derek at 11:14, 6 October 2010

2010-10-06T11:14:33Z

← Older revision		Revision as of 11:14, 6 October 2010
Line 9:		Line 9:
	First, you need to have [http://www.videolan.org/vlc/ VLC] (obviously), [http://www.python.org/ python] 2 OR 3, [http://hoopajoo.net/projects/xautomation.html xautomation] OR a version of [http://www.semicomplete.com/projects/xdotool/ xdotool] (newer than august 2010), and you need the openbsd implementation of [http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/ netcat].		First, you need to have [http://www.videolan.org/vlc/ VLC] (obviously), [http://www.python.org/ python] 2 OR 3, [http://hoopajoo.net/projects/xautomation.html xautomation] OR a version of [http://www.semicomplete.com/projects/xdotool/ xdotool] (newer than august 2010), and you need the openbsd implementation of [http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/ netcat].

	<br> The openbsd version of netcat is in the repositories of most major linux distirbutions these days. This script is written for use in Archlinux, so it's likely that you will need to change the command used by netcat in the script. Arch uses nc.openbsd, just replace it with whatever you need. Unfortunately, the GNU implementation of netcat, which is the default in most distributions, does not seem to support UNIX sockets (the -U switch for nc.openbsd).<br>		<br> The openbsd version of netcat is in the repositories of most major linux distirbutions these days. This script is written for use in Archlinux, so it's likely that you will need to change the command used by netcat in the script. Arch uses nc.openbsd, just replace it with whatever you need. Unfortunately, the GNU implementation of netcat, which is the default in most distributions, does not seem to support UNIX sockets (the -U switch for nc.openbsd). If you run slackware and can't find it, check [http://www.slackbuilds.org slackbuilds].<br>

	<br> xautomation will almost certainly be in your repos, and xdotool might be. xautomation seems to be the better choice if you're only concerned about how quickly it does the job, but xdotool is nice as well if you're doing fancier things with it. However, if you do choose to try xdotool, you'll need a build done later than August 2010, as some of the features used in this script are not in the older versions available in most repositories.		<br> xautomation will almost certainly be in your repos, and xdotool might be. xautomation seems to be the better choice if you're only concerned about how quickly it does the job, but xdotool is nice as well if you're doing fancier things with it. However, if you do choose to try xdotool, you'll need a build done later than August 2010, as some of the features used in this script are not in the older versions available in most repositories.
Line 297:		Line 297:

	offsetneeded = True		offsetneeded = True
	vtch = 12 <--hours on the video timecode		vtch = 12 <--hours on the video timecode
	vtcm = 34 <--minutes on the video timecode		vtcm = 34 <--minutes on the video timecode
	vtcs = 56 <--seconds on the video timecode		vtcs = 56 <--seconds on the video timecode

	atch = 1 <---don't use a leading 0, or the script will puke		atch = 1 <---don't use a leading 0, or the script will puke
	atcm = 23 <--minutes on the playback time		atcm = 23 <--minutes on the playback time
	atcs = 45 <--seconds on the playback time		atcs = 45 <--seconds on the playback time

	<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.		<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.

Derek at 10:52, 6 October 2010

2010-10-06T10:52:47Z

← Older revision		Revision as of 10:52, 6 October 2010
Line 220:		Line 220:
	sec = int(sec)		sec = int(sec)

	#tempo - if you've adjusted the tempo ~~and~~ an audio file, in		#tempo - if you've adjusted the tempo of an audio file, in
	# audacity for instance, then you can use the tempo		# audacity for instance, then you can use the tempo
	# variable to give output for a timestamp postion in		# variable to give output for a timestamp postion in
Line 297:		Line 297:

	offsetneeded = True		offsetneeded = True
	vtch = 12 <--hours on the video timecode		vtch = 12 <--hours on the video timecode
	vtcm = 34 <--minutes on the video timecode		vtcm = 34 <--minutes on the video timecode
	vtcs = 56 <--seconds on the video timecode		vtcs = 56 <--seconds on the video timecode

	atch = 1 <---don't use a leading 0, or the script will puke		atch = 1 <---don't use a leading 0, or the script will puke
	atcm = 23 <--minutes on the playback time		atcm = 23 <--minutes on the playback time
	atcs = 45 <--seconds on the playback time		atcs = 45 <--seconds on the playback time

	<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.		<br> You can use offset with the tempo settings. Don't use the video timecode at 00:00:00 on the playback time, or the calculation will be off. Check the difference between the video timecode and the playback time at the beginning and end of your file to see if it's consistent, as that will tell you if there have been any edits made. If there are edits, just change the offset numbers when you get to those points.