Discuss Scratch

edward789121
Scratcher
500+ posts

New sound block maybe?

If you can, click “add to backpack” next to the below code:
define play sound [sound]
play sound (sound)
set [sound v] to (sound)
define play sound [sound] until done
play sound (sound) until done
set [sound v] to (sound)
geekygirlepicness101
Scratcher
22 posts

New sound block maybe?

RainaERusch wrote:

I don't see how that would be useful, but neither did I see how the sensing blocks would be useful until I started using them. I support this suggestion.
well we can use it like this
play sound [next sound v]
im not sure if i did it right

Last edited by geekygirlepicness101 (July 28, 2016 05:32:47)

ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

Benur21 wrote:

Ok I found some time today but I found that this may not be really helpful for this thread.
Where would we need that block really?
If you're talking about the sound # block, then I'm not sure why you're suddenly asking that.
However, if you're talking about something else, could you please make it clearer to me as I'm not sure what you're asking about.

ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

geekygirlepicness101 wrote:

RainaERusch wrote:

I don't see how that would be useful, but neither did I see how the sensing blocks would be useful until I started using them. I support this suggestion.
well we can use it like this
play sound [next sound v]
im not sure if i did it right
The whole point of this block
(sound # :: sound)
is so that you can use it like this:-
if <(sound # :: sound) = [2]> then 


broadcast [message 1 v]

else
broadcast [message 2 v]
end

so the block
play sound [next sound v]
wouldn't work in that situation.

Last edited by ZZ9PluralZAlpha (July 28, 2016 13:13:12)

ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

ZZ9PluralZAlpha wrote:

geekygirlepicness101 wrote:

RainaERusch wrote:

I don't see how that would be useful, but neither did I see how the sensing blocks would be useful until I started using them. I support this suggestion.
well we can use it like this
play sound [next sound v]
im not sure if i did it right
The whole point of this block
(sound # :: sound)
is so that you can use it like this:-
if <(sound # :: sound) = [2]> then 


broadcast [message 1 v]

else
broadcast [message 2 v]
end

so the block
play sound [next sound v]
wouldn't work in that situation.
Because the sound # block I refer to and actually came up with will report the last sound played by the sprite it is being used in.
pvz_pro
Scratcher
500+ posts

New sound block maybe?

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
WHAT????!!!! The whole point of my new block is so that you don't need a variable! It saves you making one therefore saves you time!
Your script in your post is wrong anyway because it would look like this:-
when green flag clicked
forever
set [The sound # variable you talk about v] to (Sound # :: sound) // MY SOUND # BLOCK!!!!
end
So even there, you need my sound # block.
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
In your post, you mentioned this
set [sound v] to [sound #]
So when you wanted to know the value of your variable, it would report
(sound # :: variables)
as the value of the variable.

You should have this
set [sound v] to (sound # :: sound) // My sound # block will report the number of the last sound played to the variable
instead of this
set [sound v] to [sound #] // Here, the variable won't be set to the number of the last sound played, but to "sound #"

Last edited by ZZ9PluralZAlpha (July 28, 2016 16:48:43)

DimensionPvP
Scratcher
100+ posts

New sound block maybe?

Support even though there is some kind of workaround.

When you start to play a sound:

set [sound # v] to [The number on the thing]
play sound [pop v]

if <(sound #) = [2]> then
say [ya watevs]
end

But still, support.
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

Can we submit these ideas to the Scratch Team so they can tell us if it can be included in an update?
Benur21
Scratcher
100+ posts

New sound block maybe?

ZZ9PluralZAlpha wrote:

Can we submit these ideas to the Scratch Team so they can tell us if it can be included in an update?
I don't think much they will ever add something, but you can still try it.
LP_Play
Scratcher
1000+ posts

New sound block maybe?

No support;

when I receive [message1 v]
set [sound? v] to [true]
play sound [sound v] until done
set [sound? v] to [false]
Doing this with different variables and different broadcasts will allow for a workaround.
pvz_pro
Scratcher
500+ posts

New sound block maybe?

ZZ9PluralZAlpha wrote:

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
In your post, you mentioned this
set [sound v] to [sound #]
So when you wanted to know the value of your variable, it would report
(sound # :: variables)
as the value of the variable.

You should have this
set [sound v] to (sound # :: sound) // My sound # block will report the number of the last sound played to the variable
instead of this
set [sound v] to [sound #] // Here, the variable won't be set to the number of the last sound played, but to "sound #"
I meant something like this
set [sound v] to [1]
play sound [THIS IS SOUND ONE (don't use all caps) v]

ZZ9PluralZAlpha wrote:

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
WHAT????!!!! The whole point of my new block is so that you don't need a variable! It saves you making one therefore saves you time!
Your script in your post is wrong anyway because it would look like this:-
when green flag clicked
forever
set [The sound # variable you talk about v] to (Sound # :: sound) // MY SOUND # BLOCK!!!!
end
So even there, you need my sound # block.
I don't really need it because of the easy workaround
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

LP_Play wrote:

No support;

when I receive [message1 v]
set [sound? v] to [true]
play sound [sound v] until done
set [sound? v] to [false]
Doing this with different variables and different broadcasts will allow for a workaround.
I'm trying to save you having to make variables and it reports back the number of the last sound played, not just true or false.
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

pvz_pro wrote:

ZZ9PluralZAlpha wrote:

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
In your post, you mentioned this
set [sound v] to [sound #]
So when you wanted to know the value of your variable, it would report
(sound # :: variables)
as the value of the variable.

You should have this
set [sound v] to (sound # :: sound) // My sound # block will report the number of the last sound played to the variable
instead of this
set [sound v] to [sound #] // Here, the variable won't be set to the number of the last sound played, but to "sound #"
I meant something like this
set [sound v] to [1]
play sound [THIS IS SOUND ONE (don't use all caps) v]

ZZ9PluralZAlpha wrote:

pvz_pro wrote:

no support, has easy workaround
(sound)//new var
set [sound v] to [sound #]
play sound [sound v] until done
WHAT????!!!! The whole point of my new block is so that you don't need a variable! It saves you making one therefore saves you time!
Your script in your post is wrong anyway because it would look like this:-
when green flag clicked
forever
set [The sound # variable you talk about v] to (Sound # :: sound) // MY SOUND # BLOCK!!!!
end
So even there, you need my sound # block.
I don't really need it because of the easy workaround
Oh, that makes sense now.
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

Benur21 wrote:

ZZ9PluralZAlpha wrote:

Can we submit these ideas to the Scratch Team so they can tell us if it can be included in an update?
I don't think much they will ever add something, but you can still try it.
How do I do it? I've never seen anyone do it so I'm not sure what to do.
Sheep_maker
Scratcher
1000+ posts

New sound block maybe?

Benur21 wrote:

ZZ9PluralZAlpha wrote:

Can we submit these ideas to the Scratch Team so they can tell us if it can be included in an update?
I don't think much they will ever add something, but you can still try it.
Well since they aren't working on 2.0 anymore this is probably the best time to do so before 3.0 gets finished.
ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

Sheep_maker wrote:

Benur21 wrote:

ZZ9PluralZAlpha wrote:

Can we submit these ideas to the Scratch Team so they can tell us if it can be included in an update?
I don't think much they will ever add something, but you can still try it.
Well since they aren't working on 2.0 anymore this is probably the best time to do so before 3.0 gets finished.
Do you know how to submit this idea to the Scratch Team because at the moment it is just on this forum.

Last edited by ZZ9PluralZAlpha (July 29, 2016 09:57:22)

DownsGameClub
Scratcher
1000+ posts

New sound block maybe?

Benur21 wrote:

redgreenandblue wrote:

What if 2 sounds were playing at once?
when green flag clicked
play sound [looong music v]
play sound [looong music2 v]
set [variable v] to (sound #::sound)
Then sound # will be “1 2” like when you change a variable to a list:

LIST
1 (hello)
2 (world)

when green flag clicked
set [Variable v] to (LIST :: list)
Variable will show “hello world” separated by spaces.
That is not going to work out. It would just make the blocking system much more complicated than it really needs to be.

I will support on the
(Sound # :: sound)
block, with its function as reporting the last sound that started playing. However, the term still seems a bit ambiguous. Can we think of another name that isn't as long as “Last sound # Played”? Lets keep it simple here.

Last edited by DownsGameClub (July 29, 2016 11:23:17)

ZZ9PluralZAlpha
Scratcher
1000+ posts

New sound block maybe?

DownsGameClub wrote:

Benur21 wrote:

redgreenandblue wrote:

What if 2 sounds were playing at once?
when green flag clicked
play sound [looong music v]
play sound [looong music2 v]
set [variable v] to (sound #::sound)
Then sound # will be “1 2” like when you change a variable to a list:

LIST
1 (hello)
2 (world)

when green flag clicked
set [Variable v] to (LIST :: list)
Variable will show “hello world” separated by spaces.
That is not going to work out. It would just make the blocking system much more complicated than it really needs to be.

I will support on the
(Sound # :: sound)
block, with its function as reporting the last sound that started playing. However, the term still seems a bit ambiguous. Can we think of another name that isn't as long as “Last sound # Played”? Lets keep it simple here.
In sensing,
(sound # :: sound)
might look like this:-
([sound # v] of [Sprite1 v])
So that makes it a bit simpler anyway.

Powered by DjangoBB