- Joined
- Jan 24, 2016
- Messages
- 125
- Karma
- 21
- Gear owned
- DR-44WL
FYI, it appears there exists a bug in DR-44WL firmware v2.01 0110 (and the earlier v1.21 0102). It involves the recording level control setting. It is possible to send out-of-range values to the gain control hardware.
You should be able to reproduce the fault:
- listen with headphones, set Output Level to 15 or so
- in 4CH mode, press Record; Tracks 1/2 flash
- press Input Level; select Tracks 1/2
- advance input level on both tracks to 100
- deselect Track 2; reduce Track 1 input level to zero
- reselect Track 2; advance Track 1 input level to 100; note output level changes in headphones and Track 2 input level indication remains at 100
- decrease Track 1 input level to zero; note output level changes in headphones, and Track 2 input level indication remains at 100
- continue to decrease input level; Track 2 indication decreases from 100
- continue to decrease Track 2 input level to zero; note output level
changes in headphones
Level value handling code is at fault, I suspect allowing too large or negative values to be sent to the hardware. I reported this to Aaron at Tascam a year ago but the behavior continues in the v2.01 release.
Tom
You should be able to reproduce the fault:
- listen with headphones, set Output Level to 15 or so
- in 4CH mode, press Record; Tracks 1/2 flash
- press Input Level; select Tracks 1/2
- advance input level on both tracks to 100
- deselect Track 2; reduce Track 1 input level to zero
- reselect Track 2; advance Track 1 input level to 100; note output level changes in headphones and Track 2 input level indication remains at 100
- decrease Track 1 input level to zero; note output level changes in headphones, and Track 2 input level indication remains at 100
- continue to decrease input level; Track 2 indication decreases from 100
- continue to decrease Track 2 input level to zero; note output level
changes in headphones
Level value handling code is at fault, I suspect allowing too large or negative values to be sent to the hardware. I reported this to Aaron at Tascam a year ago but the behavior continues in the v2.01 release.
Tom
Last edited: