And 11005 MUSIC 1,2,I,0
11000 FORI=1TO12
11005 MUSIC1,2,I,0
11006 PLAY1,I,I,6
11010 NEXT
11020 PLAY0,0,0,0
11030 WAITINT(RND(1)*35+4)
11040 GOTO11000
I believe this barking is quite nice
And 11005 MUSIC 1,2,I,0
11000 FORI=1TO12
11005 MUSIC1,2,I,0
11006 PLAY1,I,I,6
11010 NEXT
11020 PLAY0,0,0,0
11030 WAITINT(RND(1)*35+4)
11040 GOTO11000
Yes but in Basic you have to set the volume to 0 so the command PLAY produces its effect...
Something like that will probably happen, but the idea was to start by something not technically ultra challenging (for me or the audience) to at least get the knack on how to do videos (duration, style, content, audio/video, rythm, etc...)
I believe that's something Jede is trying to achieve with Orix.ibisum wrote: ↑Sun Apr 22, 2018 5:42 pmWith regards to future videos, I've always wished I had the time to get some understanding of the tooling on Oric, itself (i.e. no cross-compiling tools) to do Assembly apps .. like, if the Oric was all you had, how would you go about writing a new game for it, in Assembly/Basic .. maybe thats inspiring as a topic for future videos?
Glad you like the videosNekoNoNiaow wrote: ↑Sun May 06, 2018 1:37 am If there were any points I would suggest to still improve upon:
- maybe prepare some texts or topics in advance (like, keep a list of keywords attached next to the camera) so that there are less hesitations when talking, this would help the progression to be a bit smoother to watch. In a sense, just like you polish the user experience of the game, you would have to polish the user experience of the YouTube watcher.
- often you present the results of some changes you make, followed by the corresponding modifications to the sources but it would be really nice to get the following sequence for a better rythm: expose a flaw and suggest an improvement, explain the code, modify the code, show the result.
Of course, this would require much more editing than the current system you use, so I guess that would depend on how much time you can invest in these videos.