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: Multiformat 128 kbps Listening Test (Read 275163 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Multiformat 128 kbps Listening Test

Reply #675
I think we have the 1st portable with WMA Pro support - http://www.dapreview.net/news.php. Btw. I gave my vote to WMA Pro already yesterday.

Multiformat 128 kbps Listening Test

Reply #676
Quote
I think we have the 1st portable with WMA Pro support - http://www.dapreview.net/news.php. Btw. I gave my vote to WMA Pro already yesterday.
I think not. Quote from news:
WMA9 Professional, WMA9 Lossless and copyright-protected WMA files are not supported.


Multiformat 128 kbps Listening Test

Reply #678
Quote
Quote
because the test corpus is expected to be more challenging, more complex. [a href="index.php?act=findpost&pid=346126"][{POST_SNAPBACK}][/a]

Why?

I think you make a couple of mistakes if you do that.

Firstly, who defines complex? Is it defined by looking at how high bitrate the encoders allocate for a particular part? <snip>

I meant complex casualy as tending to encode with more bits, not for a deliberate policy 'saying for test purposes that the samples should be more complex, its just that on balance, samples choosen for human listening interests will probably tend to average out higher in bitrate than those choosen entirely randomly.
Theres sure merit for choosing entirely randomly, or making sure the samples alone achieve overall the average bitrate, I could go with that, but then to be honest I dont see my listening abilities being able to perform this test myself. The decisions are up to test participants and conductors. Im interested in the result, much preferably with wma standard included. Im interested in getting people to understand the 'wma 2pass solution' which negates the previously percieved 'wma 2pass problem' So that if you want to test it you can.

JohnV said that Nero will probably use ABR for the test, that makes the unfairness of rejecting 2pass wma standard options even more stark.

And the vote is unfair, i didnt vote in it, because obviously wma standard would be too badly handicapped by using q50 (20% reduction in target bitrate) It wouldnt be handicaped or unfairly advantaged by using 2pass on the joined samples, *especialy if the samples are to target average bitrate themselves, or a larger targeting corpus is included in the encode.

But during the course of this loopy thread, wma standard has been discouraged for ultimately invalid objections to its only suitable encoding mode - thats gonna reflect poorly on the test and forums expertise for those with the insight to see the 2pass method for what it really is (an ideal automated analogue of manual bitrate targeting processes)
no conscience > no custom

Multiformat 128 kbps Listening Test

Reply #679
Quote
It wouldnt be handicaped or unfairly advantaged by using 2pass on the joined samples, *especialy if the samples are to target average bitrate themselves, or a larger targeting corpus is included in the encode.
[a href="index.php?act=findpost&pid=346238"][{POST_SNAPBACK}][/a]


No, but the distribution of WMA bits in each sample wouldn't be identical to a real world encoding of the same, full tracks at the same setting (128, 2-pass). Therefore the results of the test would be very hard to interpret, or even meaningless.
davidnaylor.org

 

Multiformat 128 kbps Listening Test

Reply #680
Quote
Quote
It wouldnt be handicaped or unfairly advantaged by using 2pass on the joined samples, *especialy if the samples are to target average bitrate themselves, or a larger targeting corpus is included in the encode.
[a href="index.php?act=findpost&pid=346238"][{POST_SNAPBACK}][/a]


No, but the distribution of WMA bits in each sample wouldn't be identical to a real world encoding of the same, full tracks at the same setting (128, 2-pass). Therefore the results of the test would be very hard to interpret, or even meaningless.
[a href="index.php?act=findpost&pid=346241"][{POST_SNAPBACK}][/a]

Neros ABR wouldnt be identical either, and other vbr encodes, depending on their encoders precise implementation wouldnt be precisely the same for encoded sample only, than in-track encodes. Theres also encoding start up differences to fuss over, each vbr individual vbr encode can have 'run-in' differences and 'run-out' differences as the small sample starts and finnishes.

And as for how different the 2pass encodes would sound from their specific settings, firstly if no identifiable advantage or disadvantages can be proposed (very difficult to propose because of the relativistic* nature of the global vbr setting within the final 2pass) particular differences will balance themselves out, helping one sample while hindering another (there are many many such variances in individual performances in a test like this) Secondly the differences, should in fact be very small when the sample corpus bitrate is normalised, or the 2pass bitrate is achieved using an added larger 'targeting corpus'

Its very easy to recognise that there will be differences, you need to look deeper, compare overall processes to rate the importance of the possible differences. As soon as you  examine and contrast the (normaly unerecogised) manual process of targeting a bitrate that is used in one way or another to specify or check all the codecs settings - with wma st. automated process, you will realise what these differences amount to in practice - nada

[span style='font-size:7pt;line-height:100%']edit: *, sorry - jargon abused. I wasnt refering to Einstiens theory there, just how the bitrate distribution tends to remain relative across time with a global vbr method even as different mean bitrates are targeted[/span]
no conscience > no custom

Multiformat 128 kbps Listening Test

Reply #681
Quote
Neros ABR wouldnt be identical either, and other vbr encodes, depending on their encoders precise implementation wouldnt be precisely the same for encoded sample only, than in-track encodes. Theres also encoding start up differences to fuss over, each vbr individual vbr encode can have 'run-in' differences and 'run-out' differences as the small sample starts and finnishes.


Didn't think about that.

Quote
And as for how different the 2pass encodes would sound from their specific settings, firstly if no identifiable advantage or disadvantages can be proposed (very difficult to propose because of the relativistic nature of the global vbr setting within the final 2pass) particular differences will balance themselves out, helping one sample while hindering another (there are many many such variances in individual performances in a test like this) Secondly the differences, should in fact be very small when the sample corpus bitrate is normalised, or the 2pass bitrate is achieved using an added larger 'targeting corpus'

Its very easy to recognise that there will be differences, you need to look deeper, compare overall processes to rate the importance of the possible differences. As soon as you  examine and contrast the (normaly unerecogised) manual process of targeting a bitrate that is used in one way or another to specify or check all the codecs settings - with wma st. automated process, you will realise what these differences amount to in practice - *nada
[a href="index.php?act=findpost&pid=346246"][{POST_SNAPBACK}][/a]


Ok. Can't quite get my mind around that, at least not right now. I'll just take your word for it.

Now - will Sebastian also take your word for it?
davidnaylor.org

Multiformat 128 kbps Listening Test

Reply #682
Quote
Now - will Sebastian also take your word for it?

If they cant visualise what Im saying (the equivalence with manual multipass targeting method that goes on explicitly or in kind) I wouldnt suggest anyone takes my word for it - a concensus from Codec Dev's would be persuasive.
no conscience > no custom

Multiformat 128 kbps Listening Test

Reply #683
run-in differences are mitigated by setting abchr-java to start playing 1 second into the sample.

If nero's abr is like lame's abr, it doesn't work the same way as wma vbr 2-pass.  That is, it would be a 1-pass abr, so there wouldn't be the same problem with encoding just short samples.

ff123

Multiformat 128 kbps Listening Test

Reply #684
Quote
Quote
Well, looks like WMA Professional is gonna win the poll for the 5th contender.
Good thing for Microsoft and WMA when the test results are out, since most people outside HA probably don't realize there's actually a significant difference between these codecs.  The other one, higher quality - almost nowhere used, other one lower quality and used very widely.
Interesting to see the results though.
[a href="index.php?act=findpost&pid=346135"][{POST_SNAPBACK}][/a]


On a sidenote: Is there a command line encoding utility for WMA Pro? I'd like to try that beast out.
[a href="index.php?act=findpost&pid=346200"][{POST_SNAPBACK}][/a]


There is WMCmd.vbs which you run with cscript.exe from a console.

Multiformat 128 kbps Listening Test

Reply #685
The fifth competitor poll can be closed now - the winner is WMA Professional Q50 9.1 which received a total of 60 votes out of 122 (49.18%).
MusePack came second with 25 votes, followed by None with 23 votes and WMA Standard Q50 with 14 votes.


Multiformat 128 kbps Listening Test

Reply #687
My foobar (0.8.3) settings:

Encoder: CSCRIPT.EXE
Extension: wma
Parameters: "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" -input %s -output %d -a_codec WMA9PRO -a_mode 2 -a_setting Q50_44_2_24
Format is: lossy
Highest BPS mode supported: 24
Tag: none
[ ] Pass floating point data
[ ] Encoder requires accurate length
Display name: WMA PRO Q50
[ ] Hide console window
[ ] Never use source file BPS

Can someone please confirm?

Edit: Original batch file command line:

CSCRIPT.EXE "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" -input %1 -output "%~dpn1" -a_codec WMA9PRO -a_mode 2 -a_setting Q50_44_2_24

Edit 2: foobar 0.9 Converter profile for WMA PRO Q50:

Encoder: Custom
Encoder: CSCRIPT.EXE
Extension: wma
Parameters: "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" -input %s -output %d -a_codec WMA9PRO -a_mode 2 -a_setting Q50_44_2_24
Format is: lossy
Highest BPS mode supported: 24
Display name: WMA PRO Q50
I'm on a horse.

Multiformat 128 kbps Listening Test

Reply #688
Quote
My foobar (0.8.3) settings:

Encoder: CSCRIPT.EXE
Extension: wma
Parameters: "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" -input %s -output %d -a_codec WMA9PRO -a_mode 2 -a_setting Q50_44_2_24
Format is: lossy
Highest BPS mode supported: 24
Tag: none
[ ] Pass floating point data
[ ] Encoder requires accurate length
Display name: WMA PRO Q50
[ ] Hide console window
[ ] Never use source file BPS

Can someone please confirm?

Edit: Original batch file command line:

CSCRIPT.EXE "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" -input %1 -output "%~dpn1" -a_codec WMA9PRO -a_mode 2 -a_setting Q50_44_2_24[a href="index.php?act=findpost&pid=346283"][{POST_SNAPBACK}][/a]


Didn't work:

Code: [Select]
INFO (foo_clienc) : CLI encoder: C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs
INFO (foo_clienc) : Destination file: file://E:\test\sweep.wma
INFO (foo_clienc) : Source file: file://E:\test\sweep.wav
INFO (foo_clienc) : 44100Hz 24bps 2ch
ERROR (foo_clienc) : Encoding failed


The command prompt window that opened shows this:

Code: [Select]
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
_


The last line is a blinking cursor, but the window is halted.

dbPowerAMP works without problems.

Multiformat 128 kbps Listening Test

Reply #689
Quote
run-in differences are mitigated by setting abchr-java to start playing 1 second into the sample.
If nero's abr is like lame's abr, it doesn't work the same way as wma vbr 2-pass.  That is, it would be a 1-pass abr, so there wouldn't be the same problem with encoding just short samples.

Neros 1pass ABR will have relatively massive run-in discrepancies with the samples encoded insitu. If wmas 2pass targeting is unnacceptable Neros ABR is definitely out of the question.

Quote
Congrats for the winner!

And now back to the samples...

The vote was really flawed -you all know it.

Now my last attempt at waving the truth in front you guys:
Suppose 3 phrases joined: A, B and C

It would be wonky for the prepass calculated vbr setting not to be global,
assuming it is, this equation would be true:
Code: [Select]
 phraseA_Bitrate*phraseA_Duration
+phraseB_Bitrate*phraseB_Duration
+phraseC_Bitrate*phraseC_Duration
=target_Bitrate*Total_Duration (=total bit allocation)

Next define Demandrate, a kind of passage complexity estimate from the encoders preferences, high for passages which would demand more bits, low for passages which would demand less.

phrase_Demandrate=phrase_Bitrate/target_Bitrate
phrase_Bitrate=phrase_Demandrate*target_Bitrate

Substituting phrase_Bitrate for its Demandrate expression in previous equation...

Code: [Select]
 (phraseA_Demandrate*target_Bitrate)*phraseA_Duration
+(phraseB_Demandrate*target_Bitrate)*phraseB_Duration
+(phraseC_Demandrate*target_Bitrate)*phraseC_Duration
=target_Bitrate*Total_Duration

devide both sides of equation by target_Bitrate to leave:
Code: [Select]
 phraseA_Demandrate*phraseA_Duration
+phraseB_Demandrate*phraseB_Duration
+phraseC_Demandrate*phraseC_Duration
=Total_Duration

That equation illustrates (by being linear) that the bitrate demands of A and B (Phrase_Demandrate*phraseDuration) remain in proportion with each other, nomatter what the demand of C. To be fair C's demand only needs to be normalised because if it is greater than (A+B)/2, A+B is deprived, if it is less A+B is boosted.
C can be normalised most easily by removing it altogether, alternatively it could be a sample of the same DemandRate as (A+B)/2
The longer C's duration, the greater its DemandRates effect on A and B's bit allocation, at 0 it ceases to have an effect.

The difference between doing the 2pass bitrate targeting on only A+B, and doing it on A+B+C where C is the clipped portion of the parent tracks is at least as transient to the test results, as the difference between the test samples used, and the tracks people will actualy encode guided by the tests results(!!)

That's me done.
Good luck
[span style='font-size:7pt;line-height:100%']edit: speling[/span]
no conscience > no custom

Multiformat 128 kbps Listening Test

Reply #690
Quote
What I wanted to know now is whether you want to decide something regarding the sample or should I create the sample set and you swallow it as-is?


Repeating myself:

What do you want to test?

Is your sample representative of the population that relates to your test question?

Are you ready to defend that sample set? Can it be validly defended?

Personally, I can live with either decision (your set or a shouting match about which samples "absolutely need" to be included)

I know that opening the sample discussion will cause another chaotic discussion and many will learn in the process.

This will take time, but the sample set might be "better" in the end (in some ways), or perhaps not better at all. At least it'll be different, that's for sure.

Now, is it worth opening this discussion?

Your call, imho. I'd be slightly more inclined to open the discussion on the sample set than take a ready-made set, but you must weigh the pros/cons as the test organizer.

At least the start of the test will be pushed further into the future, if discussion is started. I have no qualms with that, you have to think of your own schedules/time use too.

Best regards,
Halcyon

Multiformat 128 kbps Listening Test

Reply #691
Quote
Didn't work:

Code: [Select]
INFO (foo_clienc) : CLI encoder: C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs
INFO (foo_clienc) : Destination file: file://E:\test\sweep.wma
INFO (foo_clienc) : Source file: file://E:\test\sweep.wav
INFO (foo_clienc) : 44100Hz 24bps 2ch
ERROR (foo_clienc) : Encoding failed
Thanks for testing.  It works fine for me - it was more the settings that I was querying.

Maybe your "WMCmd.vbs" is not in "C:\Program Files\Windows Media Components\Encoder"?

Curious.
I'm on a horse.

Multiformat 128 kbps Listening Test

Reply #692
Quote
Code: [Select]
INFO (foo_clienc) : CLI encoder: C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs
I think you have incorrectly set "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" as the encoder, not "CSCRIPT.EXE".

If I edit the path to WMCmd.vbs to create an error I get:

Code: [Select]
INFO (foo_clienc) : CLI encoder: CSCRIPT.EXE
INFO (foo_clienc) : Destination file: file://C:\noname.wma
INFO (foo_clienc) : Source file: file://C:\noname.wav
INFO (foo_clienc) : 44100Hz 24bps 2ch
ERROR (foo_clienc) : Encoding failed

Note the "CLI encoder: CSCRIPT.EXE".

[span style='font-size:8pt;line-height:100%']Edit: spelling[/span]
I'm on a horse.

Multiformat 128 kbps Listening Test

Reply #693
Quote
Neros 1pass ABR will have relatively massive run-in discrepancies with the samples encoded insitu. [span style='font-size:7pt;line-height:100%']edit: speling[/span]
[a href="index.php?act=findpost&pid=346292"][{POST_SNAPBACK}][/a]

In short 10-20 sec hard samples our ABR may reach about 140kbps average because of the initial ABR buffer size. Full length tracks are equal or below 133kbps in almost all cases.
Juha Laaksonheimo

Multiformat 128 kbps Listening Test

Reply #694
Quote
Quote
Code: [Select]
INFO (foo_clienc) : CLI encoder: C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs
I think you have incorrectly set "C:\Program Files\Windows Media Components\Encoder\WMCmd.vbs" as the encoder, not "CSCRIPT.EXE".[{POST_SNAPBACK}][/a]

Thanks.

I had a wrong line there and I fixed it. Now it seems to start encoding, but I get this prompt when foobar sends the temp file to the encoder:
"Microsoft ® Console Based Script Host has encountered a problem and needs to close. We are sorry for the inconvenience..."

I have installed about everything related with WM encoding, but nothing separately related with scripting. (Should I install something from e.g. here: [a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnanchor/html/scriptinga.asp]MSDN / WIndows Scripting[/url]?)

Also, Windows Media Encoder itself (the GUI program) doesn't work anymore on this PC. It uses all available memory and crashes when trying to select a source file. I have tried all usual tricks e.g. uninstall/reinstall, search MS knowledgebase etc. It used to work about a year ago...

Only dbPowerAMP works.


Sorry about this being a bit OT, but it is related to a test contender and how people can use it.

[span style='font-size:7pt;line-height:100%']Edit: typo[/span]

Multiformat 128 kbps Listening Test

Reply #695
Quote
Now my last attempt at waving the truth in front you guys:
Suppose 3 phrases joined: A, B and C

[ .... ]
[a href="index.php?act=findpost&pid=346292"][{POST_SNAPBACK}][/a]



Ahem... it is SUPPOSED that  128+128+128/3 = 128 . That's not what we talked about. The target_bitrate for A,B,C, and Total are not necessarily equal, so you cannot simplify them like you did.

2-pass Encoding  is doing an encode (generally with several tools disabled to speed it up) to get an estimated demandrate for each section of the sample. Depending on the deviation from the targetbitrate, the encoder increases or decreases the target quality, and starts the second encoding (this time, a real encode), probably an ABR one, but taking the previous results in consideration.

1-pass (usual ABR) does not have this "take information" step, It just starts encoding in fragments of a delimited time (like, saying, 2 seconds), and tries to constraint the demandrate to the targetbitrate.

One cannot do a mixture of both, it is either 1-pass or 2-pass.

Multiformat 128 kbps Listening Test

Reply #696
Quote
In short 10-20 sec hard samples our ABR may reach about 140kbps average because of the initial ABR buffer size. Full length tracks are equal or below 133kbps in almost all cases.
[a href="index.php?act=findpost&pid=346317"][{POST_SNAPBACK}][/a]

And an average Kbps of 140, would mean the first section was kicking in even higher than that (and towards the end, the reverse as the ABR algorithm tries balance it out). - Certainly quite a different bitrate distribution than the sample could recieve encoded insitu.

@Jaz - leave the condescension to those who know how to read a freekin' equation

[span style='font-size:7pt;line-height:100%']edit: more seplling and grammur[/span]
no conscience > no custom

Multiformat 128 kbps Listening Test

Reply #697
Quote
@Jaz - leave the condescension to those who know how to read a freekin' equation
Could we please have proper tone...

I too fail to see the point in the formulas you present. 

Adding engineering units to the formulas might help you to see what I mean:

phrase_Demandrate kbps = phrase_Bitrate kbps / target_Bitrate kbps
phrase_Bitrate kbps = phrase_Demandrate kbps * target_Bitrate kbps

Now according to my old math book:
kbps / kbps = factor without unit
kbps * kbps = kbps²

It's like apples and pears, you are not supposed to compare them. 

Now on the other hand...

If what you meant to say was that phrase_Demandrate is not a rate but a factor, illustrating if the bitrate is above or below the target_Bitrate the formula could be rewritten:

phrase_Demandfactor = phrase_Bitrate kbps / target_Bitrate kbps
phrase_Bitrate kbps = phrase_Demandfactor * target_Bitrate kbps

Following your substitutions the resulting formula would be:
phraseA_Demandfactor * phraseA_Duration s
+ phraseB_Demandfactor * phraseB_Duration s
+ phraseC_Demandfactor * phraseC_Duration s
= Total_Duration s

Since
phraseA_Duration s
+ phraseB_Duration s
+ phraseC_Duration s
= Total_Duration s

the Demandfactor is just a representation of how much above/below the average bitrate the phrase bitrate is.

Nothing new here.

Multiformat 128 kbps Listening Test

Reply #698
Quote
@Jaz - leave the condescension to those who know how to read a freekin' equation

[span style='font-size:7pt;line-height:100%']edit: more seplling and grammur[/span]
[a href="index.php?act=findpost&pid=346420"][{POST_SNAPBACK}][/a]


You put me in need to open my Oxford Dictionary... Yet, the the verb "condescend" means "to do something that one's rank, abilites etc do not require one to do". That, of course, in the context of your sentence is clueless.

sehested said the rest.

Multiformat 128 kbps Listening Test

Reply #699
Condescend
  • To descend to the level of one considered inferior; lower oneself.
  • To deal with people in a patronizingly superior manner.
Come on - We (hopefully) just got over a load of flaming let's please not start another war. 

Edit: That's to both BTW.  And me.  And you.
I'm on a horse.