Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: qtaacenc: a command-line QuickTime AAC encoder for Windows (Read 408854 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #175 –
Quote from: Larson on
(i know it's off topic but with lastest XLD version i encounter a bug or what? example "1-04 X.flac becomes when converted 04 X.m4a and so on,it skips the compilation from the title thus getting file names with multiple cds disorganized; before it kept the structure normally, maybe i'm getting wrong something. Sorry for going out of theme but I didn't know where to post this)

Send me a PM (or directly email me). It seems your PM is disabled...

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #176 –
Code: [Select]
2010/7/25

    * Added encoder configuration info to the tool metadata


new version...
_

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #177 –
Can qtaacenc encode to Apple Lossless using quicktime engine too?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #179 –
Yes i know about qaac but honestly i don't care about that, i have even some problems. I care about qtaacenc since nao is so kind to give us support ect =)

Nao I wanted to ask you if you plan to add alac encoding to qtaacenc in the future.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #180 –
@nao

It seems that this cmd-line encoder can't support the path with the unicode U+FF62 included, which is a HALFWIDTH LEFT CORNER BRACKET.
Would you like to fix this issue?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #181 –
No problem on my machine.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #182 –
I tried to check if any updates are available, but the site didn't exist anymore.

From: http://tmkk.hp.infoseek.co.jp/qtaacenc/
Quote
インフォシークからのお知らせ
「iswebライト」は2010年10月31日をもってサービス提供を終了いたしました。
長年ご愛顧いただきありがとうございました。

Google Translate:
Quote
News from Infoseek
"Isweb Light" is the service ended on 31 October 2010.
Thank you for your patronage for many years.

If Google translated it correctly the hosting service has ended.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #184 –
Thanks!

Could a moderator fix the link in the first post in this thread?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #185 –
Quote from: nao on
No problem on my machine.

Strange.
If I name a directory as "?? ", the converter will not finish encoding the music file in this directory, instead of reminding me the following msg in console.
Code: [Select]
...An error occurred while finalizing the encoding process (Object not found) ...

But the FULLWIDTH CORNER BRACKET "?? " works fine.

My os: Win7 32-bit 7600 Ultimate English
fb2k ver: 1.1.1
qtaacenc ver: 1.2.2.4
qt-lite ver: 7.6.6

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #186 –
Does it work if you encode the file directly in a cmd prompt without using foobar?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #187 –
Quote from: nao on
Does it work if you encode the file directly in a cmd prompt without using foobar?

It can't work.
Code: [Select]
Error: input file does not exist.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #188 –
Then it seems to be a locale-specific issue. qtaacenc shows the error when the path in argv is not found with GetFileAttributes API, so maybe there is something wrong with the user codepage <-> Unicode routine in OS when handling the character.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #189 –
Quote from: nao on
Then it seems to be a locale-specific issue. qtaacenc shows the error when the path in argv is not found with GetFileAttributes API, so maybe there is something wrong with the user codepage <-> Unicode routine in OS when handling the character.

No way to get it resolved except to change the path name?
But LAME works fine with the chars in path.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #190 –
If I could reproduce the problem on my machine I'd like to fix it. But at this moment, no clue.
LAME isn't a unicode-based app, so it is a different case.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #191 –
Would it be possible to have qtaacenc work without having to use full paths to source and destination files? If I already have cd'd to a certain directory on a certain drive, it would be nice to use paths like f:source.wav f:source.m4a instead of writing the full path for both files.
 

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #192 –
qtaacenc accepts both absolute and relative paths.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #193 –
Quote from: nao on
qtaacenc accepts both absolute and relative paths.

Relative paths didn't work for me, qtaacenc complains about the file not being found. I cannot post the exact error message right now as I'm at work.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #194 –
Quote from: nao on
If I could reproduce the problem on my machine I'd like to fix it. But at this moment, no clue.

The problem is fixed in the latest update. It happened because of a locale-specific behavior of QuickTime.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #195 –
nao qtaacenc has a problem with 24 bit material, even if you do for example cvbr 256, the encoding doesn't give the results it should give but it does have a lot lower bitrate than that. The same thing happens with true vbr; no problem with XLD on Mac, so it is qtaacenc related.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #196 –
Please upload the problematic sample. As far as I've tested there is no problem with 24-bit files.

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #197 –
It happens with 88.1 and 96 khz 24 bit files; no problem at all with 44,1 and 48khz/ 24 bit ones.

EDIT: here it is a 96/24 sample, i've taken one peace of the whole song just to let you try the conversion and see the problem. I'm using --cvbr 256 --highest - [outfile] command on dbpoweramp with latest version of qtaacenc and I get a file with a bit rate around 130 kbps; if I do the conversion with XLD it is how it's supposed to.

http: //www.mediafire.com/?4wg45e8oawv4lu  [when you copy and paste the link make sure you take off the space between : and /, please mods don't delete the link it's just a sample testing for nao]

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #198 –
Quote
2010/11/15
Fixed a problem that caused an error when a current directory path contained invalid characters for the default character set
Gah, in this case QT changes the current directory path without any notice.


@nao

Thanks for your GREAT WORK, it works fine now!
But could you explain how did you re-produce the issue & solve it?

qtaacenc: a command-line QuickTime AAC encoder for Windows

Reply #199 –
Quote from: Larson on
It happens with 88.1 and 96 khz 24 bit files; no problem at all with 44,1 and 48khz/ 24 bit ones.

Fixed in the latest update. Actually the cause was a samplerate; not a bit depth.

Quote from: holyrevenger on
But could you explain how did you re-produce the issue & solve it?

There was a guy who told me how to reproduce the problem on my Japanese environment.