Za-Chary wrote:

sing [skibidi] at note (62 v) for (0.5) beats

Xzillox wrote:

Za-Chary wrote:

sing [skibidi] at note (62 v) for (0.5) beats

I'm assuming the “beats” input changes the speed at which it is sung? Although that isn't exactly the most musically pleasing prospect, it seems like a pretty good way to implement melody. It doesn't need to be complex because low floor and all that, plus the other music blocks aren't complex.

yadayadayadagoodbye wrote:

Xzillox wrote:

Za-Chary wrote:

sing at note (62 v) for (0.5) beats

I'm assuming the “beats” input changes the speed at which it is sung? Although that isn't exactly the most musically pleasing prospect, it seems like a pretty good way to implement melody. It doesn't need to be complex because low floor and all that, plus the other music blocks aren't complex.

Beats likely refers to a beat, as described in sheet music (which in most common cases, refers to a quarter note, but can refer to other notes such as eigth notes when the time signature is to be changed)

If this was added, a “tempo” block for the TTS would likely be required, and so would a “time signature” block (though its also viable to simply have it stay on 4/4 times)

Xzillox wrote:

yadayadayadagoodbye wrote:

snip-

yeah I know about beats and stuff lol I'm a musician.

I guess to clarify what I meant was if it would play it slower or faster for the number of beats you input.

yadayadayadagoodbye wrote:

Xzillox wrote:

yeah I know about beats and stuff lol I'm a musician.

I guess to clarify what I meant was if it would play it slower or faster for the number of beats you input.

I would assume it'd just work as straightfoward as it seems, which is, 1 beat would play for the duration of 1 beat in reference to the tempo, 0.5 beats would play for half that time, E.T.C

Za-Chary wrote:

yadayadayadagoodbye wrote:

Because you'd be singing, and you'd need to know what notes you're singing

undeterministic wrote:

Suppose I sing Hi! in the note of E flat and I sing it in the note of E sharp, they sound different. How would it know what the melody is without some sheet music. Or other solution.

So why does there need to be sheet music as opposed to a block that just says the following?

sing [skibidi] at note (62 v) for (0.5) beats

Where does the sheet music come in?

gdfsgdfsgdfg wrote:

ok which engine will it use to create a “singer” voice

yadayadayadagoodbye wrote:

Xzillox wrote:

Za-Chary wrote:

sing [skibidi] at note (62 v) for (0.5) beats

I'm assuming the “beats” input changes the speed at which it is sung? Although that isn't exactly the most musically pleasing prospect, it seems like a pretty good way to implement melody. It doesn't need to be complex because low floor and all that, plus the other music blocks aren't complex.

Beats likely refers to a beat, as described in sheet music (which in most common cases, refers to a quarter note, but can refer to other notes such as eigth notes when the time signature is to be changed)

If this was added, a “tempo” block for the TTS would likely be required, and so would a “time signature” block (though its also viable to simply have it stay on 4/4 times)

play scream (scream) for (0.25) beats

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

MythosLore wrote:

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

What if you don’t want to share your voice on Scratch, or what if your voice is a baritone and you want a soprano voice to sing your song?

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

roofogato wrote:

https://scratch.mit.edu/discuss/11/

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

Za-Chary wrote:

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

roofogato wrote:

https://scratch.mit.edu/discuss/11/

If we assume that this suggestion were implemented and worked perfectly, it would be much easier to use than either of these solutions.

Xzillox wrote:

Za-Chary wrote:

Xzillox wrote:

hang on a second-
Why not just record yourself singing? Even if you're a bad singer, it probably won't be much worse or probably better than whatever the text-to-singing comes up with.

roofogato wrote:

https://scratch.mit.edu/discuss/11/

If we assume that this suggestion were implemented and worked perfectly, it would be much easier to use than either of these solutions.

True, but that's a pretty big assumption.

1. When you run a speech block with new configurations for the first time, it takes a while before the speech is played. That's because the blocks gets the speech audio on the fly, then caches it for later. This could impose a problem for something where timing is absolutely necessary.
   We could mitigate this by getting the speeches before it's being run, but I can't imagine the amount of unused requests of speeches from this…
   
2. How would we handle multi-syllable words, that has different tones on different syllables? Do we:
   a. try to sound them:
   

   sing [day] at note (78 v) for (1) beats :: extension
   sing [zee] at note (75 v) for (1) beats :: extension // not *see, since the <s> in <Daisy> is voiced (spoken like Z)
   sing [day] at note (71 v) for (1) beats :: extension
   sing [zee] at note (66 v) for (1) beats :: extension // ditto
   sing [give] at note (68 v) for (0.333) beats :: extension
   sing [me] at note (70 v) for (0.333) beats :: extension
   sing [your] at note (71 v) for (0.333) beats :: extension
   sing [en] at note (68 v) for (0.666) beats :: extension // en [ˈɛn] is close enough to the first syllable of answer [ˈænsɚ]
   sing [sir] at note (71 v) for (0.333) beats :: extension // so is [sˈɜː]
   sing [do] at note (66 v) for (2) beats :: extension

   b. use hyphens to notate that the word is split into different syllables (this also means there's a “lookahead” between blocks)
   

   sing [dai-] at note (78 v) for (1) beats :: extension
   sing [-sy] at note (75 v) for (1) beats :: extension
   sing [dai-] at note (71 v) for (1) beats :: extension
   sing [-sy] at note (66 v) for (1) beats :: extension
   sing [give] at note (68 v) for (0.333) beats :: extension
   sing [me] at note (70 v) for (0.333) beats :: extension
   sing [your] at note (71 v) for (0.333) beats :: extension
   sing [an-] at note (68 v) for (0.666) beats :: extension
   sing [-swer] at note (71 v) for (0.333) beats :: extension
   sing [do] at note (66 v) for (2) beats :: extension

   c. Defenestrate this English spelling nonsense and use something like X-SAMPA or the IPA for the lyrics
   

   sing [d'eI] at note (78 v) for (1) beats :: extension
   sing [zi] at note (75 v) for (1) beats :: extension
   sing [d'eI] at note (71 v) for (1) beats :: extension
   sing [zi] at note (66 v) for (1) beats :: extension
   sing [g'Iv] at note (68 v) for (0.333) beats :: extension
   sing [m'i:] at note (70 v) for (0.333) beats :: extension
   sing [j'U@] at note (71 v) for (0.333) beats :: extension
   sing [\{n] at note (68 v) for (0.666) beats :: extension
   sing [s3] at note (71 v) for (0.333) beats :: extension
   sing [d'u:] at note (66 v) for (2) beats :: extension

3. How would we handle edge cases like “singing” a sentence or two over a short period of time?
   

   sing [A nutshell is the outer shell of a nut.] at note (127 v) for (0.001) beats :: extension

   Or singing for a very long time?
   

   sing [aaaaaa] at note (0 v) for (99999) beats :: extension