Audacity Forum

I'm not sure what you are asking. Is your question the same as: "Why doesn't Audacity support high dpi displays?"

You need to calibrate your system to automatically correct the delay. It's called "latency correction". See: http://manual.audacityteam.org/man/latency_test.html

1) Generate the first 6 mins,

2) then press the "End" key to move the cursor to the end of the track (or: "Select menu > Region > Cursor to Track End")

3)then generate the next 6 mins
...

By default, Audacity's Effect menu lists built-in effects first, then plug-in effects. The Limiter is a plug-in effect. Scroll down the list below "Wah Wah".

You could try setting the Windows "system locale".
Alternatively, if you have the "host" setting in the device toolbar set to "WASAPI", try setting it to "MME".

Donutsfritos wrote:Does anyone know if it's possible to modify the extra track colors we got with the last update?

No, not yet.

steve wrote:I guess we may never know for sure unless someone finds a Oberheim spec sheet.

Seems that Paul White found one (last item on the page: http://www.electrongate.com/dmxfiles/images.html)

A bit more information from a Google search: μ-Law is a general companding algorithm with the formula: y = F(x) = sign(x)*Vmax*(ln(1+(ux/Vmax)) / ln(1+u)) where -Vmax <= x <= Vmax and u is the 'mu' of the law. or as Wikipedia describes : F(x) = sgn(x) * ( ln(1 + |x|) / ln(1 + u) ) where -1 <= y <= 1...

Some clues about the format: It is clearly some sort of logarithmic encoding (you can see that by looking at the waveforms, and u255law appears to be close even if not exact). The minimum absolute hex value in the BIN files is (unsigned) 0x00 The maximum absolute hex value in the BIN files is (unsig...

I imagine I can use Audacity's sample data export to get numbers Nyquist can use The "numbers" in the data dumps are 8-bit values, so whether you use Sample Data Export or a Hex editor on the BIN files, you will just get hex values in the range 00 to FF. Without either a format specificat...