ID3 tagging script Post: 302113870

Sponsored Content

Top Forums Shell Programming and Scripting ID3 tagging script Post 302113870 by SimonDorfman on Tuesday 10th of April 2007 09:39:48 PM

04-10-2007

Registered User

ID3 tagging script

I'm trying to get a little script working with DropScript 0.5 that edits the ID3 tags of an MP3. Here's what I've got:

Code:

#!/bin/sh

# Strip directory part but leave extension.
in_base=`basename "$@"`
# Strip extension.
in_noext=`echo "$in_base" | sed 's/\.[^.]*$//'`

/opt/local/bin/id3v2 --TPE2 "$in_noext" "$@"

It works fine when I drop one file on it at a time, but when I drop more than one file on it, it's writing a list of all the files to each individual file. I know I need to replace the first

Code:

$@

with something that will only look at each file, not all the files. But I'm such a shell scripting newb, that I don't know what to replace it with. Any ideas?

Many thanks in advance for any help!

SimonDorfman

View Public Profile for SimonDorfman

Find all posts by SimonDorfman

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

CVS Tagging Script

Hi All, We have to tag all source code files to prepare a release kit. We have one CVS Project under which all files have to be tagged. We use the following cvs command to tag a specific version of a file: 'cvs rtag -r X.XX -F "newbuild" somefile' This command asks for the CVS Login...

2. Solaris

Solaris 9 VLAN tagging with ce interface

Hi, Is it possible to VLAN tag with a ce interface on Solaris 9? Link speed is gb. ce:0:ce0:link_speed 1000 I have a ce0 interface I would need to have access to another VLAN as well as the one it's currently on. What commands would I need to run? Thanks.;)

3. What is on Your Mind?

Discussion (Thread) Tagging Upgrades

Dear All, I have made significant progress coding new discussion thread tagging features. As always, we want all users to tag thread and moderators to tag threads with relevant keywords. Moving forward, in addition to the #1 important "human tagging", we will also auto tag threads with one...

LEARN ABOUT SUSE

irsend

IRSEND(1)								FSF								 IRSEND(1)

NAME

       irsend - basic LIRC program to send infra-red commands

SYNOPSIS

       irsend [options] DIRECTIVE REMOTE CODE [CODE...]

DESCRIPTION

       Asks the lircd daemon to send one or more CIR (Consumer Infra-Red) commands. This is intended for remote control of electronic devices such
       as TV boxes, HiFi sets, etc.

       DIRECTIVE can be:
	  SEND_ONCE	    - send CODE [CODE ...] once
	  SEND_START	    - start repeating CODE
	  SEND_STOP	    - stop repeating CODE
	  LIST		    - list configured remote items
	  SET_TRANSMITTERS  - set transmitters NUM [NUM ...]
	  SIMULATE	    - simulate IR event

       REMOTE is the name of a remote, as described in the lircd configuration file.

       CODE is the name of a remote control key of REMOTE, as it appears in the lircd configuration file.

       NUM is the transmitter number of the hardware device.

       For the LIST DIRECTIVE, REMOTE and/or CODE can be empty:

	  LIST	 ""    ""   - list all configured remote names
	  LIST REMOTE  ""   - list all codes of REMOTE
	  LIST REMOTE CODE  - list only CODE of REMOTE

       The SIMULATE command only works if it has been explicitly enabled in lircd.

       -h --help
	      display usage summary

       -v --version
	      display version

       -d --device
	      use given lircd socket [/var/run/lirc/lircd]

       -a --address=host[:port]
	      connect to lircd at this address

       -# --count=n
	      send command n times

EXAMPLES

	  irsend LIST DenonTuner ""
	  irsend SEND_ONCE  DenonTuner PROG-SCAN
	  irsend SEND_ONCE  OnkyoAmpli VOL-UP VOL-UP VOL-UP VOL-UP
	  irsend SEND_START OnkyoAmpli VOL-DOWN ; sleep 3
	  irsend SEND_STOP  OnkyoAmpli VOL-DOWN
	  irsend SET_TRANSMITTERS 1
	  irsend SET_TRANSMITTERS 1 3 4
	  irsend SIMULATE "0000000000000476 00 OK TECHNISAT_ST3004S"

FILES

       /etc/lirc/lircd.conf
	      Default lircd configuration file.  It should contain all the remotes, their infra-red codes and the corresponding timing	and  wave-
	      form details.

DIAGNOSTICS

       If lircd is not running (or /var/run/lirc/lircd lacks write permissions) irsend aborts with the following diagnostics:
       "irsend: could not connect to socket"
       "irsend: Connection refused" (or "Permission denied").

SEE ALSO

       The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory.

       lircd(8), mode2(1), smode2(1), xmode2(1), irrecord(1), irw(1), http://www.lirc.org.

irsend 0.8.7pre1						     May 2010								 IRSEND(1)