• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: 'beats' are integers?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 'beats' are integers?


  • Subject: Re: 'beats' are integers?
  • From: Os <email@hidden>
  • Date: Tue, 12 Jul 2005 22:17:37 +0100

Hi,

no, that's not the problem. It seems that Live's sliders have some other resolution than 7 bit. (I just tried it.)

But that's not really the point - my question is a bit more philosophical: should 'beats' parameters take fractional values *ever*?

E.g. if I change my parameter's range to 0-31, which is surely a coarser resolution than the GUI slider in Live, then Live still only displays integer numbers for the parameter, while sending fractional values to my AU.

NB Live is not using my MIDI interface to set values - it's setting parameter values directly through the AU API.

It just seems wrong to me - to show the user one value, but to set the AU's parameter to a different one.


cheers, os.


On 11 Jul 2005, at 18:41, William Stewart wrote:

But wouldn't you want this range to be

0 to 127

0 to 128 actually gives you 129 steps, not 128; so I suspect that is the problem

Bill

On 10/07/2005, at 5:00 AM, Os wrote:


Hi,

I've come across a problem when using my plug-in with Ableton Live, and I wonder whose problem it is.

At the root of it is an AU parameter of type kAudioUnitParameterUnit_Beats.

I expose this to users as a float, min 0.0, max 128.0. When controlling it via MIDI, I set the value to (1+x) where x is the MIDI CC value, giving a usable range of 1-128 (integers) via MIDI.

Live exposes the parameter as a value from 0-128 (fair enough) and displays only integer values to the user. However, the value it is applying to my plug-in doesn't take integer values - I imagine it's incrementing in steps of 129/128, as it maps the range 0-128 to a 7 bit controller value.

So, who's right here? Am I wrong for allowing a 'beats' parameter to take fractional values? Or is Live wrong for showing a fractional value rounded to the nearest integer?


cheers, os.

email@hidden
http://www.collective.co.uk/

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden



--
mailto:email@hidden
tel: +1 408 974 4056
______________________________________________________________________ ____
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
______________________________________________________________________ ____




email@hidden http://www.collective.co.uk/


_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >'beats' are integers? (From: Os <email@hidden>)
 >Re: 'beats' are integers? (From: William Stewart <email@hidden>)

  • Prev by Date: Re: Logic7.1 picks the wrong plugin
  • Next by Date: Re: Logic7.1 picks the wrong plugin
  • Previous by thread: Re: 'beats' are integers?
  • Next by thread: using stereo mixer
  • Index(es):
    • Date
    • Thread