# Information passed from Audacity to Nyquist

**URL:** <https://forum.audacityteam.org/t/information-passed-from-audacity-to-nyquist/26230>\
**Category:** Nyquist\
**Created:** [September 10, 2012, 3:49pm UTC](https://forum.audacityteam.org/t/information-passed-from-audacity-to-nyquist/26230 "2012-09-10T15:49:47Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![steve](https://forum.audacityteam.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@steve](https://forum.audacityteam.org/u/steve)\
**Post date:** [September 11, 2012, 7:17pm UTC](https://forum.audacityteam.org/t/information-passed-from-audacity-to-nyquist/26230/3 "2012-09-11T19:17:28Z")

</div>

> [@Robert J. H.](#):
>
> nevertheless a property list for the sound variable seems to be the proper way. What do you think?

Yes I agree. I wrote something along the same lines a long time ago: [Sample Printer - #19 by steve](https://forum.audacityteam.org/t/sample-printer/14790/19)

> It would often be useful if Nyquist knew more about “s”.  
> Audacity has information about the track that is not available to Nyquist.  
> The number of samples is passed to Nyquist in the variable “LEN” and the actual audio data in “S”, but that’s all.  
> What I would like to see is additional track data passed to Nyquist, possibly as a property list, to include:
> 
> Track name,  
> Channel allocation (for mono tracks),  
> Peak Amplitude (solves the Normalising issue for some situations),  
> RMS,  
> Start time,  
> Envelope Points,  
> Bit-depth.

Those were some ideas off the top of my head, not a definitive list. It’s interesting to see that you came up with such a similar idea.  
I also like the idea of taking an incremental approach.

At some point I’ll start a more formal proposal for this feature, which you will of course be very welcome to contribute to.

---

_[View the full topic](https://forum.audacityteam.org/t/information-passed-from-audacity-to-nyquist/26230)._
