Hi Christian, > > I really prefer if we have an open source solution available to > > everybody for the SBC conformance testing. If sbctester.c is not good > > enough than we have to write one. > > Sbctester.c is perfect for the decoder. For the encoder, we might also take > it or write something better to replace PEAQ. I am all for that since we need to be able to pass SBC conformance with pure open source tools. Otherwise it becomes painful for some people. > BTW; then I will have spent 6000 EUR on buying one PEAQ license in vain ;-) I know multiple better ways of spending that money ;) > > I also don't mind using the reference > > encoder/decoder and the reference files. Using wine is not optimal, but > > I don't really mind it. > > Fine. But can it be added to the repository? Or shall a description be given > on how to download it from the Bluetooth SIG web page. No we can't add it. I would have to write something up on how to download it and how testing is suppose to work. > > Another question that I have is how you use the sbc_enc_test_01.wav and > > sbc_enc_test_02.wav files with Windows reference encoder? It turns into > > a busy loop for me. > > Which file do are you referring too? I usually compress the original.wav > file (on the top of the second table). Which line options do you use for the > encoder? The official files from the Bluetooth SIG and I don't know which options would make them encode correctly. Just calling the reference encoder with the filename makes it run into a busy loop. With wine and natively running on Windows XP. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
