Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Here you can submit bugreports
Post Reply
veks
Posts: 84
Joined: Fri Oct 25, 2019 6:51 am

Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by veks »

Hi!

I'm trying to extract all audio tracks from MP4 file.
I know that this video has 8 audio tracks with 2 channels on each.
I'd like to extract them all in separate files.
I've did this:
https://prnt.sc/rbfdks

And I always get the same error whatever I do:

Code: Select all

Expected number for ar:a:0 but found: Same.
Thanks!
ThomasM
Site Admin
Posts: 231
Joined: Wed Feb 22, 2017 6:36 am

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by ThomasM »

Hi Veks,

First - sorry, I am afraid I can´t help you but...
I´ve tried your settings and in fact it is funny when you uncheck "Skip Naming Convention" The Option "Total Channels" first greys out and when re-opening the Node the box is empty like in the picture in your Link above [ I checked in Version 1.0.0.2 ].

So I have to check my workflows with this node again to see if there is something unecpected...

So long,
tom
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by admin »

hi veks,

Thanks for reporting :-) I have found the bug and it will be corrected.

-steinar
veks
Posts: 84
Joined: Fri Oct 25, 2019 6:51 am

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by veks »

admin wrote: Wed Mar 04, 2020 9:08 pm hi veks,

Thanks for reporting :-) I have found the bug and it will be corrected.

-steinar
Awesome! I like how fast you guys are! :) :ugeek:

Thanks!
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by admin »

And thanks to your report I also found a couple of other issues while testing the audio node. So thanks again for reporting issues and bugs! :-)

Can you please try this new processors.a3x file?

-steinar
Attachments
processors.a3x
(737.49 KiB) Downloaded 448 times
ThomasM
Site Admin
Posts: 231
Joined: Wed Feb 22, 2017 6:36 am

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by ThomasM »

Hi all,

Just my litle test:
I replaced the processors.a3x with the above version. I tried several encoding-options in the AudioExtraction-Node but most of my test returned Error-Messages. The only Format that worked with my test was an WAV-input. I tried with the test files from here: https://www2.iis.fraunhofer.de/AAC/multichannel.html
so you can cross-check my experience. I also added the respective Log (I hope this is the right one this time... ;-) )

I did not have troubles using this Node as I only used WAV-Files as input so far.

regards,
tom
Attachments
20200306-0822-2404-3489-719d3c41b40e.zip
(7.68 KiB) Downloaded 433 times
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Audio extraction - Expected number for ar:a:0 but found: Same. - v1.0.0.2

Post by admin »

Hi,

The input formats and their audio layout should not really matter as long as it's valid and readable by ffmpeg. However, "Same as source" may not always work when you go from a layout and/or format combination that's not supported by the output format. For example, if you have 192KHz audio and you select same as source on sample frequency, it will fail if the output does not support 192KHz.

I also found an anomalie in your workflow where your audio node had some illegal parameters. Don't know how they got there but just opening and saving it again fixed it. Although I DID find a bug with it so I'm sending you a new processors.a3x for you to try. But before you do, just open the node and click ok again, the save.

-steinar
Attachments
processors.a3x
(737.24 KiB) Downloaded 464 times
Post Reply