Talk:FreeFieldDirectivityTF: Difference between revisions

From Sofaconventions
Jump to navigation Jump to search
Content deleted Content added
Created page with "TuningFrequency:LongName: not required, because TuningFrequency is always frequency. TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always...."
 
m Isfmiho moved page Talk:SimpleFreeFieldDirectivityTF to Talk:FreeFieldDirectivityTF over redirect: FreeFieldDirectivityTF is not going to be "simple" anymore; now it is also according to standard
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
changes:
TuningFrequency:LongName: not required, because TuningFrequency is always frequency.
TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always.
* TuningFrequency:LongName: not required, because TuningFrequency is always frequency.
* TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always.

ListenerView/Up: added because required to define the orientation of the microphone array
* ListenerView/Up: added because required to define the orientation of the microphone array
SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same.
* SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same.
* EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore.

EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore.
* EmitterDescription: renamed to MIDINoteDescription because it describes a note.
* GLOBAL:MusicianPosition: renamed to GLOBAL:Musician
EmitterDescription: renamed to MIDINoteDescription because it describes a note.

GLOBAL:MusicianPosition: renamed to GLOBAL:Musician




To be discussed:
To be discussed:
* MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex...
* MIDINote (and MIDINoteDescription) '''or''' Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex...
* Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments.

Latest revision as of 11:38, 20 January 2021

changes:

  • TuningFrequency:LongName: not required, because TuningFrequency is always frequency.
  • TuningFrequency:Unit: not required because TuningFrequency should be in Hz (IS) always.
  • ListenerView/Up: added because required to define the orientation of the microphone array
  • SourcePosition:Definition renamed to SourcePosition:Reference because they provide the narrative description of the spatial reference. SourceView/Up:Definition: the same.
  • EmitterMidiNote: renamed to MIDINote because we don't use emitters anymore.
  • EmitterDescription: renamed to MIDINoteDescription because it describes a note.
  • GLOBAL:MusicianPosition: renamed to GLOBAL:Musician


To be discussed:

  • MIDINote (and MIDINoteDescription) or Note, Note:Long, Note:Unit = MIDI, NoteDescription ??? The latter has the advantage of being more general. But more complex...
  • Conventions name: if we want to keep it simple, we could ignore the room (the usual case when talking about directivity). Then, the convention could be called FreeFieldDirectivityX, with X={TF|FIR}. Note that I skipped the "MusicalInstrument" because this is limiting and we consider directivity of loudspeakers and singers already now, i.e., more than just instruments.