|
neilmcgillivray Posted Aug 17, 2016, 12:59 pm |
I'm trying to use id3edcmd with OS X 10.11.6
this code does not; Code: 1
id3edcmd -en 'LAME 3.98' /Users/xxxx/Desktop/test/Disclosure - Feel Like I Do.mp3 this code does work; Code: 1
id3edcmd -en 'LAME 3.98' /Users/xxxx/Desktop/test/Disclosure\ -\ Feel\ Like\ I\ Do.mp3 I'm trying to use id3edcmd with Hazel but it does not accept the escaped location. I noticed in the previous post about bash, a non escaped location was being used. |
|
markp Posted Aug 17, 2016, 6:31 pm |
Is there a reason not to put the path in quotes? As using escapes is very problematic in Unix scripts being a Mac only way of using paths with spaces.
For example: Code: 1
id3edcmd -en "LAME 3.98" "/Users/xxxx/Desktop/test/Disclosure - Feel Like I Do.mp3" |
|
neilmcgillivray Posted Aug 21, 2016, 5:10 pm |
Hi,
Thanks for the reply. id3edcmd -en 'LAME 3.98' "/Users/xxxx/Desktop/test/Disclosure - Feel Like I Do.mp3" In quotes, solves it nicely in Terminal. The developer of Hazel suggested, Code: 1
id3edcmd -en 'LAME 3.98' "$1" But although it does not throw any error in Hazel, it does not trigger id3edcmd. I've also tried; Code: 1
id3edcmd -en 'LAME 3.98' "{$1}" Also unsuccessful, unfortunately. |
|
neilmcgillivray Posted Aug 21, 2016, 6:03 pm |
I've found the problem and solved it;
The shell location was in correct for Hazel, I adjusted it and everything is working properly now. Code: 1
/bin/bash Code: 1 2
#!/bin/bash /usr/local/bin/id3edcmd -en 'LAME 3.98' "$1" Again, thanks for the help. Much appreciated. |