move AmplitudeScale effect to global effect instead of recorded input only

[GoogleCodeExporter]

AmplitudeScale will be associated with accelerometer motion

Original issue reported on code.google.com by meeshmu...@gmail.com on 9 Dec 2008 at 10:27

[GoogleCodeExporter]

Are we sure that we want the accelerometer to control the amplitude of *both* 
the
synth and the mic? We already have a control for synth amplitude; maybe we 
should
keep it just controlling the mic amplitude?

Original comment by jkooker on 10 Dec 2008 at 3:29

[GoogleCodeExporter]

Yes, I think we do.  We have no "master" volume other than the volume on the 
side of
the device which is clunky and not smooth at all.  Also, I think it's not very
intuitive to have that kind of a gesture control only part of the audio.

Original comment by meeshmu...@gmail.com on 10 Dec 2008 at 4:18

[GoogleCodeExporter]

Failure case: First-time user tries the app with iPod lying on table. User 
tries to
touch screen, no sound comes out.

I guess I don't see why we need a dynamic, real-time master volume. I think a 
slider
on the flipside would be a better fit for this.

Original comment by jkooker on 10 Dec 2008 at 4:49

[GoogleCodeExporter]

Ah. I think that's why we have confusion. If the device is lying flat on the 
table,
that represents full volume.  Vertical is 50% volume, and lying face down 
(where it's
impossible to play anyway since you can't touch the screen) is 0%.  At least, 
that's
how it's supposed to work...

Original comment by meeshmu...@gmail.com on 10 Dec 2008 at 4:52

[GoogleCodeExporter]

There is now a global amplitude scaling effect, but the integration with the
accelerometer is disabled until the accelerometer code gets moved to the 
iDiMPAppDelegate

Original comment by meeshmu...@gmail.com on 11 Dec 2008 at 1:10

[GoogleCodeExporter]

Original comment by meeshmu...@gmail.com on 11 Dec 2008 at 1:10

• Changed state: Started

[GoogleCodeExporter]

Accelerometer now controls global ("master") amplitude scaling, but only when 
in the
MainView.  For now I think that's fine.  Moving the accelerometer to the
iDiMPAppDelegate may still be a good idea, but it's low priority.

Original comment by meeshmu...@gmail.com on 11 Dec 2008 at 3:36

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Closing this issue.  The accelerometer issue is already documented in #16.

Original comment by meeshmu...@gmail.com on 11 Dec 2008 at 3:37

• Changed state: Fixed