Skip to main content

Topic: QAAC: discussion, questions, feature requests, etc. (Read 381231 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • lvqcl
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1050
Try earlier versions? Or try CBR mode, maybe this will change the result.

Re: QAAC: discussion, questions, feature requests, etc.
Reply #1051
Try earlier versions? Or try CBR mode, maybe this will change the result.

I've tried TVBR, CVBR & CBR, and gotten to the same place: Nowhere! But, again, anything that I created through the latest iTunes is just totally fine. At this point, I have to wonder if QAAC, again, has a bug in it, or Apple has purposefully modified iTunes to make it so that you can't do anything with AAC, or ALAC, if it's not created in their program (Wouldn't put it past them). Who knows? In any case, I'm so pissed off right now that I want to throw my iPod 20gb in the garbage can. It's nothing more than a useless piece of crap at this point. I don't like not having control of my music.

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1052
Maybe related, or maybe not: https://hydrogenaud.io/index.php/topic,17773.0.html

m4a container written by qaac is different from the ones created by iTunes. fb2k also writes some metadata which is never written by iTunes. Therefore, there *can* be a compatibility issue regarding container. MP4 is an unnecessarily versatile, complex format for storing a single audio track. Some kind of compatibility issues are quite common in poor parser implementations, especially seen in hardware players.

However, since your ipod is able to play at least one track, I guess it's not simply because there's something in the container which iPod cannot handle properly.
There might be an issue in the sync process when files came from outside of iTunes... but I really have no idea.

Re: QAAC: discussion, questions, feature requests, etc.
Reply #1053
Maybe related, or maybe not: https://hydrogenaud.io/index.php/topic,17773.0.html

m4a container written by qaac is different from the ones created by iTunes. fb2k also writes some metadata which is never written by iTunes. Therefore, there *can* be a compatibility issue regarding container. MP4 is an unnecessarily versatile, complex format for storing a single audio track. Some kind of compatibility issues are quite common in poor parser implementations, especially seen in hardware players.

However, since your ipod is able to play at least one track, I guess it's not simply because there's something in the container which iPod cannot handle properly.
There might be an issue in the sync process when files came from outside of iTunes... but I really have no idea.


For the hell of it, I installed Rockbox on my iPod, and I ended up having no problems at all with the QAAC-based AAC files. That tells me the Apple software didn't like them. By design or on purpose? Some might say it's the former. I still think it's the latter. But at least the damn thing works now.

  • tvks
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1054
I get the same problem with my iPods (both 5G & 5.5G) just like ghostman6842's.
I encoded the QAAC files using command line "-v 256" setting, and they can be played if I select certain one of them. But when iPod starts the next track (both starting when the previous is ended and I press the NEXT button), iPod get restarting.
I tried the problem files played on different iPod models. iPod 5G & 5.5G get this problem while iPod nano 1G & iPod nano 5G do not.
BUT I have found that the files I encoded years before using QAAC 2.33 with the same setting, are played fine on all my iPods.
AND I also tried encoding some files using command line "-v 128" setting, and they are played fine.
So, I guess there may be something with the latest QAAC with “-v 256” setting?

  • Rigby
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1055
Question: Is it possible to somehow alter the chapter names QAAC generates when using the --concat option? I'm trying to make audiobooks from MP3 files; unfortunately the track names in their metadata have ridiculously long prefixes, so I can't see the track numbers in the chapter list on my phone. Ideally I'd like to have simple sequentially numbered names like "Chapter 1", "Chapter 2" and so on.

BTW, thanks to the dev! This is a really useful tool that has already saved me a ton of work. :)

  • Anakunda
  • [*][*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1056
Good news, new qaac brings alot of new features

Quote
    Support decoding FLAC in MP4.
    AAC decoder: now recognizes 6.1ch/7.1ch AAC channel config constants (11 and 12) defined in 14496-3:2009/Amd 4:2013
    Concatenating files with no title tag with --concat now creates empty chapter name (formerly file name was used).
    --start now accept negative value. using --start and --delay at the same time is not allowed now. These two options are the same in functionality-wise, except for the reversed sign (For trimming, you use positive value for ---start, and negative value for --delay).
    --adts and --concat doesn't allow concatenating files with varying sample format anymore.
    External dlls are now loaded in lazy way, which means that they are not loaded until needed.
    Increased buffering size for --play to avoid glitches on multi channel files.
    --native-resampler now always use dedicated AudioConverter.
    CAF: enabled 7.1ch rear AAC output.
    AAC in CAF: when chan chunk is not present, get channel layout from kuki chunk.
    Named pipe output is removed. I guess it has been rarely used anyway, but if you happen to want it, use https://github.com/nu774/namedpipe .


  • eahm
  • [*][*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1057
Thanks for the news and for the update.

Link here: https://sites.google.com/site/qaacpage/cabinet

Re: QAAC: discussion, questions, feature requests, etc.
Reply #1058
I am getting audio breakup when multiplexing HE-AAC encoded with QAAC.exe v2.63, and HEVC, in MeGUI. I downloaded v2.63 from two sources with the same result. I have gone back to the QAAC backup in MeGUI, which is I think v2.62, and no problems.

  • Anakunda
  • [*][*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1059
QAAC 2.64 is out.


Fixed regression of 2.63: HE-AAC frames were incorrectly multiplexed.
  • Last Edit: 19 May, 2017, 08:41:45 AM by Anakunda

  • dev
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1060
Hi

Is this normal for the encoder to put lowpass on LFE channel, or is this an error?
Or is putting higher than 120Hz frequencies on the LFE channel a mistake?

ChannelPlacement.wav
http://www6.zippyshare.com/v/KVIBROyc/file.html
ChannelPlacement.m4a
http://www6.zippyshare.com/v/czCuQqaV/file.html


thx.
dev

  • eahm
  • [*][*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1061
Different question from the previously asked in the Opus thread, will the new qaac or refalac support Opus in a CAF container since Apple will start using it? Thanks nu774.

  • kode54
  • [*][*][*][*][*]
  • Administrator
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1062
If anyone gets this up and running soon, I have handy iOS 11 devices ready to test it.

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1063
Different question from the previously asked in the Opus thread, will the new qaac or refalac support Opus in a CAF container since Apple will start using it? Thanks nu774.
Well, if new iOS supports Opus only in CAF container, "Opus in CAF" encoder may be a bit helpful... but I can't think of any other use cases.
Because I don't have iOS devices, "Opus in CAF(only)" encoder is not only completely useless for me but also looks like a stupid piece of software that's not worth the effort of implementing it.

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1064
As far as I know, iTunes (for Windows) currently doesn't support CAF files at all.
CAF is such a minor format that even Apple doesn't support in their player.
Will this change to support Opus files on iTunes 13 or something?
If iTunes will support decoding/encoding of Opus in CAF as a first class citizen, then Opus in CAF might happen to become more popular than I think.

  • eahm
  • [*][*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1065
I don't know why they always have to do shit like this, they already support straight mp3 right from the factory, why the hell don't just add opus as is? It drives me insane, they want to be Steve Jobs but he was only doing this because he was an emotional baby.

  • polemon
  • [*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1066
It seems I've been blissfully oblivious to the CAF container. Wikipedia and a quick search on Google doesn't turn up any info what sort of codecs it's able to contain, the Spec doesn't say much either.

What are the codec constraints of CAF?

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1067
What are the codec constraints of CAF?

Well, The spec is at https://developer.apple.com/library/content/documentation/MusicAudio/Reference/CAFSpec/CAF_spec/CAF_spec.html .
The spec lists up some of the currently defined values for the mFormatID field, but it is not an exhaustive list.
Also, it doesn't provide enough information about how to store each codec like this: https://wiki.xiph.org/OggOpus .

As far as I can see, the following codecs are supported by CoreAudioToolbox on Windows:
    .mp1: MPEG Layer 1
    .mp2: MPEG Layer 2
    .mp3: MPEG Layer 3
    QDM2: QDesign Music 2
    QDMC: QDesign
    Qclp: Qualcomm PureVoice™
    Qclq: Qualcomm QCELP
    aac : AAC
    aach: MPEG-4 HE AAC
    aacp: MPEG-4 HE AAC V2
    alac: Apple Lossless
    alaw: A-Law 2:1
    dvi8: DVI
    ilbc: iLBC
    ima4: IMA 4:1
    lpcm: Linear PCM
    ms\000\002: MS ADPCM
    ms\000\021: MS DVI
    ms\0001: MS GSM 6.10
    paac: MPEG-4 AAC
    qaac: MPEG-4 AAC
    qach: MPEG-4 HE AAC
    qacp: MPEG-4 HE AAC V2
    samr: AMR narrowband
    ulaw: μ-Law 2:1
    zaac: MPEG-4 AAC
    zach: MPEG-4 HE AAC
    zacp: MPEG-4 HE AAC V2

(You can see this list by running https://github.com/nu774/cafmux)

  • polemon
  • [*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1068
(You can see this list by running https://github.com/nu774/cafmux)
Thank, that's a great tip. I'd still have to work out the difference between "aac", "qaac", "zaac", etc. those don't seem to be FourCC or anything.

Problem is: I'd have to port it to Linux first. However FFmpeg is apparently able to mux and demux it.

I wonder if I can make FFmpeg print out which codecs for a given container are supported.

  • andiandi
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1069
Hi.
I've a question regarding no delay option. I read this :

This method has a danger of introducing some pops/clicks, but can reduce zeroes at beginning when decoded, and also beginning of the input can be (hopefully) more or less restored (instead of just discarding them).
Any comments?

You can try this by the attached experimental implementation:
(Attachment Link)

Since then, are those "popclicks" still there with no delay option ?

Thanks.

  • JunkieXL
  • [*][*][*][*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1070
Thank you for all of your hard work on this nu774.  I really appreciate it.
JXL

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1071
Since then, are those "popclicks" still there with no delay option ?
Actually, I'm routinely using it for encoding video soundtrack. Don't use it for music.

  • andiandi
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1072
Since then, are those "popclicks" still there with no delay option ?
Actually, I'm routinely using it for encoding video soundtrack. Don't use it for music.

Alright. Actually i'm also referring to this. So is it safe if I use nodelay for video soundtrack right now or is it better if I take care of the delay manually?

  • nu774
  • [*][*][*][*][*]
  • Developer
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1073
Nothing has changed regarding --no-delay option.
--no-delay is safe as long as the beginning (50ms or so) of input signal is digitally silent.
Moreover, even when the beginning of input signal is not silent, you won't hear any "glitches" as long as you listen to one file only.
The effect of --no-delay should become apparent only when you encode two or more gapless inputs, and you listen to the gapless transition between songs.

  • andiandi
  • [*]
Re: QAAC: discussion, questions, feature requests, etc.
Reply #1074
Nothing has changed regarding --no-delay option.
--no-delay is safe as long as the beginning (50ms or so) of input signal is digitally silent.
Moreover, even when the beginning of input signal is not silent, you won't hear any "glitches" as long as you listen to one file only.
The effect of --no-delay should become apparent only when you encode two or more gapless inputs, and you listen to the gapless transition between songs.

Alright thanks for all !
  • Last Edit: 22 September, 2017, 11:53:05 AM by andiandi