"Disons" = deezohn; "disions" = deezyohn If you go to Google Translate, you can put each word in the box and hit the Listen icon and it will say it for you.
Update June2020: Some of the links in the discussion below are out of date.
Ivona is now found here:
Acapela is still there, but now includes a rather annoying background jangle of sound that, I presume, is there as a kind of watermark.
Forvo is now my preferred go-to:
And for those wanting to know how to access the Google version, you can just type [translate "nous disions"] into Google and it will come up. BTW do notice that the actual translation is wrong. But the audio is good. Ha.
Trained ear or not the pronunciation is plain wrong. The IPA /j/ sound is entirely missing. Reported. FWIW. The text to speech engine is the weakest link in Duo. They should allow you to use the Google one (That one is not perfect but much better than the current TTS used by Duo). Aug 2014.
Actually, I do hear the /j/ in this one, although I grant that it's fleeting. You will find it's often the same when you hear real people talk.
Reporting is worth doing. I've had many email messages from Duo, saying that something I reported has been fixed. And I've had things accepted by Duo that I know, from reading the comments, were once rejected. That said, when it comes to the audio examples, I'm told that changing them is difficult and expensive, so there will likely be a delay.
OK, I reported it, from you comments, it confirms that it is not really possible to "fix" the pronunciation of an individual word, but rather the TTS engine might need to be upgraded. (Compare the many times that someone indicates that "I will add/fix that translation" vs. anyone indicating a pronunciation would be fixed).
With the ivona app, you do not need to be connected to the Internet to hear the speech in your phone/tablet: https://play.google.com/store/apps/details?id=com.ivona.tts&hl=en (Google translate can do that too, but Ivona usually works better). acapla app can do that too but if you purchase the app (The acapela app demo requires connection to their server)
What I meant about "allowing" other TTS engines, it that, the Duo app should have some setting that would let you choose a TTS engine already in your phone/table, instead of forcing Duo's own.
"Were we saying?" doesn't make sense in English. We might ask "Were we speaking?" or "Were we talking?", but not "Were we saying?" The sentence is incomplete. "Were we saying that?" is ok.
"We were saying?" is a colloquial shortening of "What were we saying?" (e.g., after an interruption)
It isn't a nonsensical sentence at all. "We were saying?" would be perfectly understood by English natives. However, I can see where it would be confusing to second-(or more) language English speakers since the question mark does usually change the order of the sentence in English.
It is not gibberish. As explained waaayyyy up at the top of this discussion, it would be perfectly accepted, after an interruption, to turn back to a conversation with, "We were saying?" It is probably more common to use "you" as a prompt to whomever was last speaking, or to ask, "where were we" but it is not gibberish as written.