AdamStrange

Forum Replies Created

Viewing 15 posts - 496 through 510 (of 648 total)
  • Author
    Posts
  • in reply to: sneak preview of new ui controls #3397

    AdamStrange
    Participant

    now with saturation allowing fine control over colors, clear color, random rotation of brushes giving very subtle effects:

    in reply to: sneak preview of new ui controls #3371

    AdamStrange
    Participant

    Lastly a bit of alpha:

    in reply to: sneak preview of new ui controls #3369

    AdamStrange
    Participant

    Creeping forward now with a basic paintpad:

    in reply to: Ted21 progress #3366

    AdamStrange
    Participant

    the concept is ok, implementation needs some work.

    What really needs to be done is to check the type of document first, then decide what extension it should have then add if needed

    I’ll look into it 😉

    in reply to: Ted21 progress #3326

    AdamStrange
    Participant

    let me know how you get on, I’ll sort out the monkey2 extensions for the next version for you 😉

    in reply to: Ted21 progress #3321

    AdamStrange
    Participant

    Ted21 can be found here:

    https://github.com/StrangeIsMyName/monkey2

    You will need V1.02 to compile ted21. it WON’T compile under V1.03!

    in reply to: Ted21 audio view #3315

    AdamStrange
    Participant

    I like the ‘Playhead’ addition, will definitely add that although I think I might use ‘SampleIndex:Int’, just a bit more descriptive I think

    mmmm. I thought about that and here’s my answer:

    Playhead is the industry standard for the position of any playing/position thingy

    if you talk about playhead to a sound engineer in reference to a sound clip they know what you mean. it is the current position of the sound that is playing.

    similarly, playhead means the current position in a song

    or in a media clip of any kind.

    You would never say “move the sample index of clip 4 to position 1423 please” You would say “Move the playhead to the middle”, etc

    Where you would use something like sample index is in talking to a computer. The computer has no concept of a playhead, but likes direct position information.

     

    Playhead, just makes sense

     

    OK, second thought

    Sample index. Monkey2 doesn’t use samples it uses sounds (they might be actual samples of sound), but they are Sounds. Sounds are played by channels.

    Using sample index is bringing in another layer of complexity. suddenly to position the playhead in a channel, I must know that a channel is playing a sound and a sound is really a sample?

     

    Now you and I both know exactly what is going on underneath the hood. You say sample index, I say playhead. But The best this we can aim for here is clarity and simplicty. If everyone knows what a playhead is, surely it make sense to call it playhead?

     

    Q “How did you make it loop like that?”

    A “I just reset the playhead to the start at this point”

    ” ah ok, makes sense”

     

    Q “How did you make it loop like that?”

    A “I made the SampleIndex 0”

    Q “The what?”

    A “the sample index… a sound is a sample and it has an index”

    etc, etc

    in reply to: Mark: Question about Audio #3312

    AdamStrange
    Participant

    mmmm, possibly. I have a lot of audio stuff here that wants to be converted over to monkey2 😉

    in reply to: Ted21 audio view #3311

    AdamStrange
    Participant

    there are actually 3 kinds of positions data:

    AL_SEC_OFFSET AL_BYTE_OFFSET and  AL_SAMPLE_OFFSET

    the first one AL_SEC_OFFSET is time based

    Glad you approve 🙂

    in reply to: Ted21 github update #3245

    AdamStrange
    Participant

    new version now on github with following:

    Mark has updated monkey to V1.03 and broke ted21, so to compile you will need V1.02

    but ted21 work fine with V1.03 so compile on V1.02 and use with both .02 and .03

    <hr />

    Big update with lots of stability and uber fixes throughout. it seems very stable now.

    new left code view rewritten from ground up. new audio document – you will need to update mojo/audio modules for this to work

    property icon changed and also changed color

    Clicking on the status bar will move you around the document (error on the left, current position on the right)

    document cursor position icons now functional and added to toolbar

    debug/stop icons on toolbar now correctly enable/dissable

    in reply to: Ted21 progress #3242

    AdamStrange
    Participant

    ok. Mark has updated monkey to V1.03 and broke ted21, so to compile you will need V1.02

    but ted21 work fine with V1.03 so compile on V1.02 and use with both .02 and .03

    <hr />

    Big update with lots of stability and uber fixes throughout. it seems very stable now.

    new left code view rewritten from ground up. new audio document – you will need to update mojo/audio modules for this to work

    property icon changed and also changed color

    Clicking on the status bar will move you around the document (error on the left, current position on the right)

    document cursor position icons now functional and added to toolbar

    debug/stop icons on toolbar now correctly enable/dissable

    in reply to: Ted21 audio view #3209

    AdamStrange
    Participant

    mmmm, That’s a really interesting question.

    You’d need to make a tiny change to mojo/audo/audio.monkey2:

    Ignoring some hard wired colors it should be good to go. I’ve done a quick comparison to the ted2 audiodocument and everything looks like it should compile – You’ll need to add the custom colors to mojo as well

    There’s a lot of repeated code – I was going to make a class to wrap it all up.

    Here’s the full source:

    in reply to: Ted21 audio view #3204

    AdamStrange
    Participant

    Just a small update here. I’ve been into the mojo source and added the ability to see where the playhead is. I’ve also coloured the pressed key in the current selection color. Playhead is always in white with black:

    in reply to: Ted21 audio view #3173

    AdamStrange
    Participant

    And the final version with everything operational.

    You can see the highlighted octave slightly darkened. the note is also shown on the piano view when pressed.

    in reply to: V103 – bloody annoyed! #3079

    AdamStrange
    Participant

    Mark:

    how do Resolve the changes you’ve made to mojo/view and  mojo/style? Basically preventing any ted21 stuff compiling.

    Whilst moving mojox into a module is (in some terms) a good idea. It was not particularly transparent to developers.

    I do feel that in the move you have taken something that was difficult and now made it substantially more difficult to find out what it does and how to extend it.

    I would really have thought that doing this would make things more transparent, not less?

    How do you suggest I continue from here?

    I really wanted this to all work well together and be something everyone could benefit from.

Viewing 15 posts - 496 through 510 (of 648 total)