I wouldn't put my faith in ChatGPT for anything that matters.
It also gave me advice on how to mic an upright bass when playing live in a room with other players. I consider its advice superior to advice I had earlier received from discussion boards. It also gave me microphone recommendations that I can research.
I also described a scenario of how my Focusrite Clarett8pre wasn't sending sounds to my headphones until I also turned on my Profile 2626, which is connected via optical ADAT cables. It told me that it sounded like the connection between the two was impeding the Focusrite's ability to route the inputs to my headphone mix, and to check Focusrite Control to see how the routing was defined. It wasn't a complete answer, but it put me on the right track.
So while before you'd simply type "my microphone is broken and I hear hissing noises" and pray Google had the answer to a more or less exact match for your question, now you type the same and ChatGPT can tell you possible causes. But then you refine your question "no, I tried this and that's not it. My mike brand is X, and it's a bit dusty. Anything else I should try?". New answer by ChatGPT. "No, I tried that and that's not it. But now I remember my dog bit it, is dog saliva bad for the mike?", and so on and so forth.
And it can do magic that Google cannot. Say you ask for a snipper of code in Java. Then you realize you want to see the solution in Python. "Please rewrite the code you just generated but in Python" -- and voilà!
Some information here : https://github.com/dair-ai/Prompt-Engineering-Guide/blob/mai...
I wondered though if it was especially effective because information on sound hardware is one of those subjects that probably has a huge corpus. Lots of people ask redundant questions about their gear, so accurate information is probably well-correlated in some sense.
In contrast, I wrote three fiction chapters about a group of people on a shared quest of sorts. I tried to get ChatGPT to read those and summarize one of the characters across the three chapters, and it hallucinated like crazy. That's probably something where I need to learn some prompt engineering, or maybe it just isn't supposed to work well.
Someone should stick a tts-and-stt converter in a rubber duck and interface it to ChatGPT, I bet it would sell like hotcakes.
Just start by telling it you want to have a conversation instead of outputting code. Otherwise it will assume you want it to output a web page and might even try to generate images about what you said.
A couple of hours ago I posted a question on Stack Overflow, relatively niche stuff. In 5 hours it got 7 views and no reactions.
After waiting for around two hours after posting it, I posted the same text into ChatGPT and got three different answers, two of them cropped due to network errors, but one through the API managed to get answered (even though the API is also having outages). It solved my issue.
> I wouldn't run anything that matters open-loop.