Not really a teensy3.2 problem except I am using a BC127 to give me bluetooth audio from a teensy3.2 sending I2S audio over bluetooth to speakers.
The BC127 is configured for interface settings, profiles and codecs by UART to match the teensy and all works with A2DP and APTX fine. The problem is latency when trying to have sounds happening at same time as events programmed in teensy. So enable APTX Low Latency in BC127, this should give latency of about 30 to 40 ms. I think this will work if the BC127 connected to teensy is source and transmit to another BC127 as sink, I havent tried it. I did try pairing the BC127 to another manufacturer APTX Low Latency module and I got broken up audio when the two were paired both using the APTX Low Latency codec. and both were using CSR chipsets but may have been different actual chip types. I just wondered it APTX etc not supposed to be a standard and should I not be able to pair any with any as long as both supported the same protocols.
Does anyone in the Teensy community have any experience of this..???
The BC127 is configured for interface settings, profiles and codecs by UART to match the teensy and all works with A2DP and APTX fine. The problem is latency when trying to have sounds happening at same time as events programmed in teensy. So enable APTX Low Latency in BC127, this should give latency of about 30 to 40 ms. I think this will work if the BC127 connected to teensy is source and transmit to another BC127 as sink, I havent tried it. I did try pairing the BC127 to another manufacturer APTX Low Latency module and I got broken up audio when the two were paired both using the APTX Low Latency codec. and both were using CSR chipsets but may have been different actual chip types. I just wondered it APTX etc not supposed to be a standard and should I not be able to pair any with any as long as both supported the same protocols.
Does anyone in the Teensy community have any experience of this..???