# Optimizing for a CPU-Intensive Music Visualizer

**URL:** <https://discourse.processing.org/t/optimizing-for-a-cpu-intensive-music-visualizer/22358>\
**Category:** p5.js\
**Created:** [July 3, 2020, 3:07pm UTC](https://discourse.processing.org/t/optimizing-for-a-cpu-intensive-music-visualizer/22358 "2020-07-03T15:07:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![SomeOne](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/someone/32/8639_2.png) [@SomeOne](https://discourse.processing.org/u/SomeOne)\
**Post date:** [October 30, 2020, 5:20am UTC](https://discourse.processing.org/t/optimizing-for-a-cpu-intensive-music-visualizer/22358/5 "2020-10-30T05:20:18Z")

</div>

That’s fine. Setup should be used to load files, because it may take a lot of time. Draw() cycle starts after that prep works has been done. So to get the audio in sync

- load files in setup. Do all the time consuming stuff there
- start audio in draw(). Then they’ll start at more or less same time. You can stop looping of draw()-function with [noLoop()](https://processing.org/reference/noLoop_.html)

---

_[View the full topic](https://discourse.processing.org/t/optimizing-for-a-cpu-intensive-music-visualizer/22358)._