I'm just breaking up the wordle posts a bit
-
You all love that game. :laugh: It's not my thing, but you do you. I've been messing with little boards like this ESP32-LyraT-Mini V1.2 Getting Started Guide — Audio Development Framework documentation[^] I worked over the 14th and part of yesterday getting what I thought was an ES8388 audio chip up and running. I got the code all in place, launched it, and nothing. Scanned the I2C bus, and strangely I get two device addresses, neither of which is an ES8388 address. I was so frustrated I put it down. Today I look at my reference code. It has code for several boards, among them (I thought), my board, the LyraT Mini. But it has several revisions for the full sized LyrAT (which I also own) I look at my board again, and it says 1.2 ... clearly they don't use semantic versioning on their hardware, because they made major breaking changes from what I think now was 1.0 code (due to the lack of version in the codebase). I've had other vendors audio boards that were worse, changing audio chips from build to build, same version, but it's as much a hassle here, just not *quite* as much of a minefield. So I have all this code for an ES8388 and I'm hoping my LyraT 4.3 can run it, because it's the last one I have that might have that audio chip. As far as the mini, I'm going to shelf it until I can deep dive Espressif's Audio Development Framework codebase for it, which is a multiple board and version supporting monster of a codebase. I'm feeling overwhelmed at the prospect. All this for some blips and bleeps. I haven't even ordered the board that wires to google voice services yet. I figured I'd mess with these first, but it turned out to be like pulling the dash off an old car someone did a hack job on, and then trying to find which wires go where to the point where you wish you could just replace everything. Except I can't, because I didn't build the boards. :~ I'll figure it out eventually, but the joy is bleeding out of this pursuit pretty quickly. Fortunately it's not work, which has been going pretty well on my end, though the rest of my team can't say the same, so I feel kinda bad for the hardware guys. We had some successes over the past couple of days so I'm
-
You all love that game. :laugh: It's not my thing, but you do you. I've been messing with little boards like this ESP32-LyraT-Mini V1.2 Getting Started Guide — Audio Development Framework documentation[^] I worked over the 14th and part of yesterday getting what I thought was an ES8388 audio chip up and running. I got the code all in place, launched it, and nothing. Scanned the I2C bus, and strangely I get two device addresses, neither of which is an ES8388 address. I was so frustrated I put it down. Today I look at my reference code. It has code for several boards, among them (I thought), my board, the LyraT Mini. But it has several revisions for the full sized LyrAT (which I also own) I look at my board again, and it says 1.2 ... clearly they don't use semantic versioning on their hardware, because they made major breaking changes from what I think now was 1.0 code (due to the lack of version in the codebase). I've had other vendors audio boards that were worse, changing audio chips from build to build, same version, but it's as much a hassle here, just not *quite* as much of a minefield. So I have all this code for an ES8388 and I'm hoping my LyraT 4.3 can run it, because it's the last one I have that might have that audio chip. As far as the mini, I'm going to shelf it until I can deep dive Espressif's Audio Development Framework codebase for it, which is a multiple board and version supporting monster of a codebase. I'm feeling overwhelmed at the prospect. All this for some blips and bleeps. I haven't even ordered the board that wires to google voice services yet. I figured I'd mess with these first, but it turned out to be like pulling the dash off an old car someone did a hack job on, and then trying to find which wires go where to the point where you wish you could just replace everything. Except I can't, because I didn't build the boards. :~ I'll figure it out eventually, but the joy is bleeding out of this pursuit pretty quickly. Fortunately it's not work, which has been going pretty well on my end, though the rest of my team can't say the same, so I feel kinda bad for the hardware guys. We had some successes over the past couple of days so I'm
Have been following your exploits, but I am curious (I may have missed it along the way). Your developing/designing/building hardware/software for Audio applications that Manipulate or create audio from synthetic electronic sources, digital electronic sources (keyboards, guitars, ...) analog to digital sources, microphones, ... ? excuse my ignorance as I am not familiar (other my ears) with this area of technology development.
"A little time, a little trouble, your better day" Badfinger
-
Have been following your exploits, but I am curious (I may have missed it along the way). Your developing/designing/building hardware/software for Audio applications that Manipulate or create audio from synthetic electronic sources, digital electronic sources (keyboards, guitars, ...) analog to digital sources, microphones, ... ? excuse my ignorance as I am not familiar (other my ears) with this area of technology development.
"A little time, a little trouble, your better day" Badfinger
I'm just making little audio libs people can use to do any of that stuff. And decoupling these damnable boards from the ESP-ADF monstrosity of a codebase. The ADF is hot wet garbage. In fact, upon further review of these LyraT boards, do not buy them. Timewise, I've wasted about $1600 USD and gotten nowhere with them due to bad documentation, poorly designed hardware, and ridiculous breaking changes between minor board version changes. On the LyraT 4.3 I can't even find the audio chip by scanning the bus. And that was after spending an hour trying to get it to upload and serial monitor, because it required 3 jumpers to enable that basic ALWAYS MUST HAVE feature. :mad::mad::mad:
To err is human. Fortune favors the monsters.
-
I'm just making little audio libs people can use to do any of that stuff. And decoupling these damnable boards from the ESP-ADF monstrosity of a codebase. The ADF is hot wet garbage. In fact, upon further review of these LyraT boards, do not buy them. Timewise, I've wasted about $1600 USD and gotten nowhere with them due to bad documentation, poorly designed hardware, and ridiculous breaking changes between minor board version changes. On the LyraT 4.3 I can't even find the audio chip by scanning the bus. And that was after spending an hour trying to get it to upload and serial monitor, because it required 3 jumpers to enable that basic ALWAYS MUST HAVE feature. :mad::mad::mad:
To err is human. Fortune favors the monsters.
Ah so, got it. hot wet garbage :-D Great description. You do have a way with words. Developing/modifying software for OTS hardware is a daunting task at best. wish I could offer help, but outside my area of expertise.
"A little time, a little trouble, your better day" Badfinger
-
You all love that game. :laugh: It's not my thing, but you do you. I've been messing with little boards like this ESP32-LyraT-Mini V1.2 Getting Started Guide — Audio Development Framework documentation[^] I worked over the 14th and part of yesterday getting what I thought was an ES8388 audio chip up and running. I got the code all in place, launched it, and nothing. Scanned the I2C bus, and strangely I get two device addresses, neither of which is an ES8388 address. I was so frustrated I put it down. Today I look at my reference code. It has code for several boards, among them (I thought), my board, the LyraT Mini. But it has several revisions for the full sized LyrAT (which I also own) I look at my board again, and it says 1.2 ... clearly they don't use semantic versioning on their hardware, because they made major breaking changes from what I think now was 1.0 code (due to the lack of version in the codebase). I've had other vendors audio boards that were worse, changing audio chips from build to build, same version, but it's as much a hassle here, just not *quite* as much of a minefield. So I have all this code for an ES8388 and I'm hoping my LyraT 4.3 can run it, because it's the last one I have that might have that audio chip. As far as the mini, I'm going to shelf it until I can deep dive Espressif's Audio Development Framework codebase for it, which is a multiple board and version supporting monster of a codebase. I'm feeling overwhelmed at the prospect. All this for some blips and bleeps. I haven't even ordered the board that wires to google voice services yet. I figured I'd mess with these first, but it turned out to be like pulling the dash off an old car someone did a hack job on, and then trying to find which wires go where to the point where you wish you could just replace everything. Except I can't, because I didn't build the boards. :~ I'll figure it out eventually, but the joy is bleeding out of this pursuit pretty quickly. Fortunately it's not work, which has been going pretty well on my end, though the rest of my team can't say the same, so I feel kinda bad for the hardware guys. We had some successes over the past couple of days so I'm
Quote:
I'm just breaking up the wordle posts a bit
And I find it damn right. I do not complain about it, but it is neither my thing. Your posts are sometimes very difficult for me to follow, but they do are a very welcomed "diversion"
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
You all love that game. :laugh: It's not my thing, but you do you. I've been messing with little boards like this ESP32-LyraT-Mini V1.2 Getting Started Guide — Audio Development Framework documentation[^] I worked over the 14th and part of yesterday getting what I thought was an ES8388 audio chip up and running. I got the code all in place, launched it, and nothing. Scanned the I2C bus, and strangely I get two device addresses, neither of which is an ES8388 address. I was so frustrated I put it down. Today I look at my reference code. It has code for several boards, among them (I thought), my board, the LyraT Mini. But it has several revisions for the full sized LyrAT (which I also own) I look at my board again, and it says 1.2 ... clearly they don't use semantic versioning on their hardware, because they made major breaking changes from what I think now was 1.0 code (due to the lack of version in the codebase). I've had other vendors audio boards that were worse, changing audio chips from build to build, same version, but it's as much a hassle here, just not *quite* as much of a minefield. So I have all this code for an ES8388 and I'm hoping my LyraT 4.3 can run it, because it's the last one I have that might have that audio chip. As far as the mini, I'm going to shelf it until I can deep dive Espressif's Audio Development Framework codebase for it, which is a multiple board and version supporting monster of a codebase. I'm feeling overwhelmed at the prospect. All this for some blips and bleeps. I haven't even ordered the board that wires to google voice services yet. I figured I'd mess with these first, but it turned out to be like pulling the dash off an old car someone did a hack job on, and then trying to find which wires go where to the point where you wish you could just replace everything. Except I can't, because I didn't build the boards. :~ I'll figure it out eventually, but the joy is bleeding out of this pursuit pretty quickly. Fortunately it's not work, which has been going pretty well on my end, though the rest of my team can't say the same, so I feel kinda bad for the hardware guys. We had some successes over the past couple of days so I'm
i spent much of yesterday trying to understand why a bit of C++ code would not compile . it turns out if an aliased type is replaced w/ the original non-aliased type as specified by the template declaration it compiles fine . sent a bug report to Microsoft .