We're introducing two new transcription models in the API:
• GPT-Live-Transcribe: built for low-latency live transcription.
• GPT-Transcribe: optimized for asynchronous transcription of completed audio files and batch workloads.
Both models better understand context and deliver more accurate transcription on real world audio across accents and languages, including for short phrases, numbers, specialized terminology, and speech with loud background noise.
I received my Codex Micro today and have been using it all day. I have really enjoyed having a companion device that let's me keep tabs on my tabs. That being said, I have some loving feedback:
1. I've found myself clicking an agent button as a way of jumping into Codex, but have had to navigate to the app on my comp instead before using the pad. I would love if on any layer, clicking some buttons would navigate me to the appropriate app
2. I've used the input app to add some new layers (love this feature and will explore more) but seem to have a lot of connectivity issues. I've noticed that going to different layers seem to mess with the bluetooth discoverability? and also having to exit out of the app to ensure that I can use the Micro with Codex again.
3. I've preferred to hold the pad in my hand more than resting it on the desk. I think because it feels natural, and because I've used the pad as a way of notifying me when something needs my attention while I'm busy doing something else. That said, I find myself holding the dictate button and speaking into it (even though there's no mic) and wanting a little pager like screen to see what's going on without having to jump into the app to see exactly what it is.
4. I'm not sure yet on how to best utilise the dial and the joy stick. I appreciate the different ways of navigating information, but I haven't found the current applications that useful. I also find the joystick to be quite stiff, especially when rested on the desk. One of the main reasons why I've begun holding it more often.
Overall, I'm excited to continue tinkering with this and figure out a set up that suits me. Kudos to @work_louder for this great device. It's brought out the hobbyist in me and can see this being a tool I through in my bag.
🚨 @FabrizioRomano: “The plan at Arsenal was, from next week, to meet with Aston Villa & try to get a deal done for Morgan Rogers. Arsenal were NEVER going to offer £117m. For Arsenal, the realistic value of the player was around £90m-£100m maximum, no more than this.”
“Arsenal were in very advanced talks with Rogers. There were meetings between Arsenal & the player’s representatives - the player was also involved in some direct meetings.”
“Arsenal were going all in, in terms of contract. Personal terms were not a problem, Rogers was open to that. There was some tactical doubt on the player side, but NEVER financial. The contract was always ready & almost agreed.” ❌🏴
I think a big part that's missing, at least on the team plan, is the ability to see my team's traces and telemetry. We remain incentivised to use the team subscription, but are ultimately hamstrung by what we're unable to view in sessions. Having to resort to using opentelemetry, which is subpar
@NathanBLawrence Not sure skills are cancelled; rather people enjoy using them, but haven't found a good enough orchestration layer yet to manage versioning, changes, and determining desired outputs