evangipson / midio Goto Github PK

Or something like that anyway. Would probably be cool!

LFO

• Knob -> Rate (frequency)
• Knob -> Depth (gain of gainNode on lfoNode)
• Slider -> Probability (0 - 100, 5% intervals)

Mood

• Possible X/Y Input -> Scale
  • So abstract... this will be a challenge
  • Maybe dropdown
  • Changes background gradient perhaps
• Knob -> Volume
  • Changes gainNode's gain

Control still needed:

• Choosing main wave type
• Choosing how many notes play
• Choosing how many pad notes play vs. sharper notes vs. chords vs. arps

getArpeggio = getChord w/ some delay
getMelody = get notes close to eachother and make sure they are tonal

It's really just bad UX, and not that great for UI, either.

Check this out: http://blog.chrislowis.co.uk/2013/06/17/synthesis-web-audio-api-envelopes.html

• Doublesine
• Triplesine
• Doublesquare
• etc.

Do this by creating two oscillators instead of one for the oscillator class IFF you are a "multiosc" wave

Instead of forcing triangle.

The new logic should be "if i'm a wave control, and there is only 1 active wave control and my value is 0, my value is 1." instead of "force triangle" as the action.

I see waves of weird types here: http://scw.sheetsofsound.com/editor.html

They used Web Audio API. Look into how they got other waves. Perhaps combining oscillators?

I have a hunch this is because the note is being created, but with such low volume that drawNoteWithVolumeOpacity or whatever isn't passing some threshold.

• Probably either All Rights Reserved or AGPL 3.0.
  • If ARR - maybe offer money for contributions?

Expected Behavior

When a user comes to midio, they should always be served the freshest copy of "production ready" (or on master) javascript & css.

Actual Behavior

Users get cached JS or CSS sometimes, because I'm not setting any caching stuff on my end as far as I know. This would be through bluehost. Apparently I can use an .htaccess file... but I feel like that will be a lot of work.

Steps to Reproduce the Problem

1. Load up midio
2. Leave your session open for 2 days
3. Load up midio again without a cache refresh
4. Notice the old JS and CSS

Specifications

• Midio Version: current
• Operating System: Windows 10
• Node Version: v0.10.25

example: sine waves can be circles, triangle waves can be triangles, and square waves can be squares.

also pad notes should get different timing because of their large attack & release

Also maybe have the notes be able to be arpeggiated?

Expected Behavior

midio needs to link out to it's source code, and probably my home page in case people are curious about me or my projects. also the UI i set up currently was always meant to be a test UI and i can't believe it survived this long!

Actual Behavior

midio just plays music and gives you control of synthesizer properties.

Screenshots

midio looks like this at the time of creating this issue:

First draft of version 1 of the front end:

Specifications

• Midio Version: current
• Operating System: Windows 10
• Node Version: v0.10.25

Right now their values are just loose-leaf timings, in seconds.

I'm going to need to incorporate a "tempo" slider probably.

Expected Behavior

Your keywords "midio" generative and whatever else you want should be link text for links to midio from this github project.

Actual Behavior

The only link to the midio page has no link text.

Suggested Solution

Add your usual link text to the read me and project description.

Specifications

• Midio Version:
• Related Pull Request:

Expected Behavior

Whenever I click I get the feeling that midio isn't "responsive" when really it's probably generating a melody centered around that note in the initial click. I should be able to create melodies by touching the visualizer multiple times.

This is also responsible for a lot of the "clicking not working" bugs I was finding. The clicking is working just fine, but melodies might take awhile to play out.

Actual Behavior

When I touch the visualizer, sometimes I don't see the note for like 3-5 seconds because it's part of a larger melody.

Steps to Reproduce the Problem

1. Open up midio
2. Click on the visualizer
3. Notice how if you click a bunch, you'll get lots of contrasting melodies and nothing really coherent.

Screenshots

(none)

Specifications

• Midio Version: current/master
• Operating System: Windows 10
• Node Version: v0.10.25

Expected Behavior

You'd never hear popping or crackling in the audio, and never notice a slowdown no matter how long you let midio run.

Actual Behavior

CRACK beautiful noises POPPLE POP POP gorgeous airy chord CRAAAAAAckckkckKCkkKKk

Solutions

1. the <span>s that i'm creating for the piano key effects might not be getting cleaned up correctly? i am using .removeChild and not assigning it to a variable... so it should just go away. Maybe i could only allow X number of spans to be created??
2. performance of many oscillators being created at a time with many filters each oscillator. i don't think this is the problem because if i load up midio and click a bunch it's fine and doesn't start clicking/crackling/slowing down til after a bunch of clicking. it's like the problem always takes around a minute to show up- and sometimes it never shows up at all.. .which leads me to my third theory
3. some filter being applied to some oscillator at some volume level sometimes. this might be due to any number of calculations in the code for ADSR, pretty much anytime i'm doing any filter or gain adjustments on any filter or oscillator- which is kind of a lot. i believe this is my strongest lead.

Steps to Reproduce the Problem

1. Load up midio
2. Click a bunch
3. Notice how you don't get crackling/popping/slow down all of the time
4. Reload midio
5. Let it run for 1-5 minutes
6. See if you hear crackling

Screenshots

Specifications

• Midio Version: current
• Operating System: Windows 10
• Node Version: v0.10.25

To make the generative radio a bit more ... generative!

Noise shouldn't be too hard, I should just be able to use a ConvolverNode.

Oscillators on the other hand... are going to be a challenge. Going to need to get creative.

This happens with LFO on low attack notes. I think upping the attack might fix the issue after some googling: https://www.reddit.com/r/edmproduction/comments/1f0cya/how_can_you_avoid_that_click_when_using_side_chain/

Expected Behavior

When I'm listening to midio, I expect certain melodies and chords to be "remembered" and played again later, perhaps with very small variants. This shouldn't happen all the time, but people should be able to recognize melodies.

Actual Behavior

I get lots of single shot, unrelated melodies.

Steps to Reproduce the Problem

1. Start midio
2. Hit F12 and go to developer console
3. Watch for melodies being created
4. Notice how melodies don't repeat or slightly change, there are just always net new melodies

Screenshots

(none)

Specifications

• Midio Version: master/current
• Operating System: Windows 10
• Node Version: v0.10.25

Should this be a constant wave in the background being modified by the current LFO? that sounds like a cool toggle perhaps... But i'd also like to include noise waves in the mix of possible oscillators that the composer can pick from.

Make this turn on and off composer.

Gonna have to remove how composer turns off if you shut autoplay off now that it has it's own toggle.

Currently it doesn't and I'm not sure why. Need to debug. Probably some type issue.