Nero AAC & EAC Why Isn't This Working? |
![]() ![]() |
Nero AAC & EAC Why Isn't This Working? |
Jan 31 2012, 17:30
Post
#26
|
|
|
Group: Members Posts: 2 Joined: 31-January 12 Member No.: 96832 |
ok i got the solution %s must be replaced by %source%, %d by %dest%
|
|
|
|
Jan 31 2012, 22:35
Post
#27
|
|
|
Group: Super Moderator Posts: 4347 Joined: 23-June 06 Member No.: 32180 |
|
|
|
|
Jan 31 2012, 23:43
Post
#28
|
|
|
Group: Members Posts: 174 Joined: 10-October 03 From: Florida, USA Member No.: 9235 |
I really do not understand why you guys do this to yourselves. I just create the directory C:\bin and add it to the path. I put all of my console apps there. One place to look and when something needs to be updated I don't have to look for it.
It also turns this "C:\Program Files\NeroDigitalAudio\neroAacEnc.exe" in to this C:\bin\neroAacEnc.exe No quotes required. Add with that directory in the system path I can call the encoder manually by using just its name. neroaacenc -q 4 -if test.wav -of test.m4a edited formatting. This post has been edited by tev777: Jan 31 2012, 23:44 -------------------- --
Eric |
|
|
|
Feb 1 2012, 20:42
Post
#29
|
|
|
Group: Super Moderator Posts: 4347 Joined: 23-June 06 Member No.: 32180 |
But that is not the problem. The placeholders were changed in EAC v 1.0b2, so the command-line must be altered accordingly, completely regardless of where the executable is.
|
|
|
|
Feb 3 2012, 04:10
Post
#30
|
|
![]() Group: Members Posts: 35 Joined: 3-February 12 Member No.: 96900 |
This worked for me.
CODE /c C:\"Program Files (x86)\#######\#######\encoder\m4a Nero (AAC)\neroAacEnc.exe" -q 1.00 -if %source% -of %dest% && C:\"Program Files (x86)\#######\#######\encoder\m4a Nero (AAC)\neroAacTag.exe" %dest% -meta:track="%numtracks%" -meta:artist="%artist%" -meta:album="%albumtitle%" -meta:title="%title%" -meta:year="%year%" -meta:composer="%albumcomposer%" -meta:genre="%genre%" Exact Audio Copy V1.0 beta 3 |
|
|
|
Feb 3 2012, 15:59
Post
#31
|
|
|
Group: Members Posts: 174 Joined: 10-October 03 From: Florida, USA Member No.: 9235 |
@db1989
I understand that was not the problem in this case, but reading through the thread clearly shows conversation about spaces and quotes. Plus look at the command line just above this. Almost half of it is encoder path info. Cleaning up the easy stuff makes it easier to find problems when they arise. -------------------- --
Eric |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 23rd May 2013 - 07:00 |