« Previous day | Index | Today | Next day » Channels | Search | Join
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
00:21 | satellit_e <satellit_e!~satellit![]() |
|
02:49 | satellit_e has quit IRC | |
02:49 | satellit_e <satellit_e!~satellit![]() |
|
10:14 | bernie_ has quit IRC | |
10:14 | bernie_ <bernie_!bernie![]() |
|
11:10 | meeting <meeting!~sugaroid![]() |
|
11:38 | satellit_e has quit IRC | |
15:54 | hemant_kasat <hemant_kasat!uid149360![]() |
|
16:01 | pikurasa <pikurasa!~Thunderbi![]() |
|
16:01 | pikurasa | hi hemant_kasat |
16:01 | hemant_kasat | hi pikurasa |
16:02 | how are you ? | |
16:02 | pikurasa | good, how are you? |
16:02 | hemant_kasat | I am also fine |
16:03 | pikurasa | Did you make any new commits I should look at before we get started? |
16:03 | (I asked if Walter can join us already) | |
16:03 | (he will be here in a sec) | |
16:04 | hemant_kasat | I made a commit but I think I have mailed about it |
16:04 | walterbender <walterbender!~walter![]() |
|
16:04 | walterbender | hi |
16:04 | pikurasa | hi |
16:04 | hemant_kasat | hi walterbende |
16:04 | *walterbender | |
16:04 | walterbender | I have been working on the timing aspects of the tempo widget |
16:05 | pikurasa | walterbender: thanks |
16:05 | walterbender | It is pretty broken (more so since I started hacking on it) |
16:05 | hemant_kasat | yeah that is problem with tempo widget, any hint what can be the problem ? |
16:05 | walterbender | hemant_kasat, I don't understand the calculation you use for determining dx |
16:05 | so I am revisiting the calculation | |
16:06 | seems it should simply be the canvas width / 200 * BPM / 60 since we have 200 steps per second | |
16:06 | hemant_kasat | actually the calculation I was doing were not able to get us good result so I changed it by hit and trail only |
16:07 | I talked to you about this previously also | |
16:07 | You saw the latest commit on Pitchslider branch ? | |
16:08 | walterbender | hemant_kasat, OK. Here is my approach: |
16:08 | I calculate what should be the actual dx | |
16:08 | then I determine how far behind we are due to any delays in processing | |
16:09 | and then calculate an offset into the next pass to make up for the difference | |
16:09 | hemant_kasat | how to calculate the delay in processing |
16:09 | walterbender | so if we fall behind by 100 milliseconds then we start 20 * dx over from the edge for the next beat. |
16:09 | make sense? | |
16:10 | I don't have it working quite right yet :( | |
16:10 | pikurasa | (meanwhile, I am checking out hemant's latest pitch slider commit) |
16:11 | hemant_kasat | yeah that totally makes sense, we have to compensate the delay at the edges |
16:11 | walterbender | I keep track of the timing by (current time - starting time) - (number of beats * 60 / BPM) |
16:12 | (all the calcs are done in msecs | |
16:14 | i will hopefully have something wotking soon and pass it along for testing | |
16:14 | hemant_kasat | I think i also tried this, current time and starting time to get the delay , but I wasn't able to do this |
16:14 | walterbender | has not tested the pitchslider code in a few days |
16:15 | hemant_kasat | is waiting for feedback |
16:16 | pikurasa | Can we get on the same page for design before moving forward? |
16:16 | hemant_kasat | yes !! |
16:17 | pikurasa | I think what was unclear about what I asked for was that the user relies on constant aural feedback. |
16:18 | Otherwise the user is just "hunt and peck" for notes. | |
16:18 | And THAT would be very random. | |
16:18 | Even if done visually. | |
16:19 | hemant_kasat | But then what if user keeps the cursor at the same location for so much time , don't we stop the sound after some limit |
16:20 | pikurasa | It is a small area on the screen. However, that would be fine if the mouse is completely stopped. |
16:20 | ...so I think that is a good idea hemant_kasat | |
16:21 | hemant_kasat: What was the takeaway for you from seeing how the android app works? | |
16:22 | hemant_kasat | we can decide the time limit until then if user doesn't move mouse we stop the sound. |
16:23 | pikurasa | something like 2-3 seconds is fine. |
16:24 | hemant_kasat | in android app in the video sound is making continuously so I thought whenever the pitch is changing we can make a sound so I implemented that |
16:24 | pikurasa | hemant_kasat: I prefer that the sound be activated just by the presence of the mouse position without need for scrolling |
16:24 | walterbender | hemant_kasat, if you play a sequence of very short duration then you don't have a problem with playing a note for a long time |
16:24 | pikurasa | hemant_kasat: I just tested, but did not notice that feature... |
16:25 | walterbender: "a sequence"??? | |
16:26 | walterbender | pikurasa, essentially we are in a tight loop where we play a frequency based on the mouse position but the duration of the note we play should be very short |
16:26 | so that the change can be observed. | |
16:26 | pikurasa | Yes, that is fine. |
16:26 | walterbender | we have a limit on the duration since there is always a time/frequency interdependency |
16:26 | i.e., it cannot be too short | |
16:27 | pikurasa | Okay, the beginning frequency was too low for my speakers. I hear it now. |
16:27 | hemant_kasat | pikurasa , so instead of scrolling we want to control the pitch by mouse cursor ? |
16:27 | pikurasa | hemant_kasat: My sense is that would be much better. Hard to really move freely with the scroll. |
16:28 | walterbender, hemant_kasat: What I imagined for the click button for next semi-tone was different. | |
16:28 | I think it is a good idea, but I thought that it would be a keyboard button. | |
16:29 | walterbender | just arrow up and down should be enough, I would think |
16:29 | hemant_kasat | pikurasa , I will try doing it by mouse cursor , it would be easy to implement once I am able find out at what distance the mouse cursor from the base |
16:29 | pikurasa | YES! |
16:29 | walterbender: I like up/down arrow! | |
16:30 | hemant_kasat: I do not understand... | |
16:31 | hemant_kasat: from the base of the widget? | |
16:32 | hemant_kasat | pikurasa , I will try to implement the pitch change by mouse cursor but first I have to implement a method for calculating the cursor position relative to bottom of the pitch line, after this will be easy |
16:32 | pikurasa | pitch line = bottom edge of widget? |
16:34 | (just making sure I understand you...) | |
16:35 | hemant_kasat | base of the widget means bottom line in widget for every pitch we initialized |
16:35 | from where the slider start to slide | |
16:35 | pikurasa | Okay! |
16:35 | That makes sense. | |
16:37 | hemant_kasat | And also one more thing, as we have to submit the work to gsoc site, there are some options of submitting, either giving the link to github project or giving link to branches that have been worked upon, what should I submit ? |
16:39 | pikurasa | walterbender: Do you have preference? |
16:39 | walterbender | just link to your repo |
16:40 | hemant_kasat | ok !! thanks :) |
16:41 | pikurasa | Okay, I need to leave in ten minutes. |
16:41 | Anything else? | |
16:41 | hemant_kasat | from me, for now that's it. |
16:44 | pikurasa | walterbender: ? |
16:44 | walterbender | I will report in re the tempo widget timing |
16:44 | TTYL | |
16:44 | hemant_kasat | ok ttyl !! |
16:44 | pikurasa | Okay, thank you both! |
16:44 | Look forward to next commit, hemant_kasat | |
16:44 | Please ping when it is ready to test. | |
16:45 | pikurasa has quit IRC | |
16:46 | hemant_kasat | yeah, will try to do it as soon as possible |
17:47 | walterbender has quit IRC | |
18:28 | satellit_e <satellit_e!~satellit![]() |
|
19:12 | hemant_kasat has quit IRC |
« Previous day | Index | Today | Next day » Channels | Search | Join