Since 3.8.0 and now with 3.8.1 the meters, both the channels and the master going into the reds. I guess its related to the change: “Improved level meters to more accurately reflect audible volume.”
Using AutoGain my levels used to be around 0 now they’re showing +4 even in silent parts and clipping almost all the time which is definitely not true and renders the meters basically useless. For me it was perfect how it was before and I strongly hope for a fix.
Other than that I’m patiently waiting for pitch lock as a default setting and the option to set the playhead to the left rather than the middle. Also as a user of the 4-channel-view I’d love to see some better usage of the space there, especially with the effects open.The waveforms become really small and the information displayed there is barely worth the space that is used there. Looking forward for the next updates!
I have a similar level meter issue with my Denon Prime 4 since the update. The channel meters don’t register at all until I turn the gain past 12 o’clock then they go straight into the red. If I turn back to 12 o’clock they don’t register at all.
The VU meters in Djay still appear to be showing the correct readings for me and the audio doesn’t clip until they hit the red.
My controllers used to “almost” follow the Djay VU’s and had no major issues before the updates. They did still go into the red slightly before the Djay VU meters though.
Since the updates. The controller VU’s now go into the red when Djay is only at about 30%-50% of the level.
By the time that the Djay VU’s are just starting to blink the red/clipping level, the controller VU’s are totally solid all the way up.
1: Put it back the way it was so they are almost correct again.
2: Add a setting to allow the user calibration of individual controllers to match the Djay VU’s, as I’m sure they don’t all act in the same way. The calibration would simply ask the user when the controller’s VU meter hits the first Red/clipping led and then sync that with the djay VU meters.
Not opposite to me. Mine are doing the same as yours on my NS6ii.
I think the point I was making was that on my controller the midi VU meters are just visual, the audio is not actually clipping so turning the gains down is sending out less signal than you should be to the master out. The proof for me was by looking at the djay VU’s on the screen and turning up the gains past the red clipping on the controller which still sounded fine, until the djay VU’s went into the red, when the sound then got distorted.
My master VU’s are now usually off or don’t get past 2 bars (if I turn the gains to 100%) which is obviously wrong.
If I disconnect djay/iPad usb and change my input from pc to line in, and play the same track from my iPhone using djay into the ns6ii rca input, the VU meters work properly!
Can you test if your VU’s are now giving a wrong indication by djay sending the wrong midi out information or whether it is really clipping. My controller is currently working with the VU’s
clipping on every song, but the sound is fine so it doesn’t make sense to turn the gains down (I just don’t take any notice of the vu’s).
I guess after having a pioneer wego for a long time that didn’t have VU’s, my ears are my distortion meter. The auto gain & djay vu’s still seem to be ok for me if I ignore the controller.
Atleast we are all of the same one opinion. It changed, it’s wrong, and needs to get fixed
Yeah, same for me on the master. Completely unusable.
But the question is on the fader vu’s. The update has pushed them up into the red with the same settings as before since the updates. For me it’s just visually wrong and I don’t think it’s really clipping the output, but some people are turning the gains down to compensate when they probably don’t need to. If they are doing that they are probably then turning up the master out which may then clip the active speaker
Algorridim need to tell us if the updates are just sending higher midi levels for the VU meters or are sending a higher audio output. If it’s the former we just have to ignore the vu’s till it’s fixed, if it’s the later you do actually have to turn the gains down, which is impossible if you have auto gain turned on (unless you adjust every single track after loading which defeats the purpose).
And on the subject of auto gain. When in this mode the deck output is always higher than the sampler & microphones set to max (others have commented on this). The only way to compensate for this is to either turn off auto gain and bring the gains down (no thanks) or play with the faders pulled back and the master turned up, it’s what I do now, but not happy with it. It’s nice to be able to throw up the faders and know they will be at the rIght levels.
Please add the Serato feature that allows you to reduce or increase the max auto-gain db. That way it can be reduced to match the sampler & Mic volumes while still retaining automatic track output levels.
I’m not sure if it’s related but since the latest update, I’m randomly getting a clipping/cracking noise in my headphones whilst playing random tracks…It’s not happening all the time but is happening occasionally…This definitely wasn’t there prior to the latest update…
A note to Algoriddim,
We users trust the updates that you guys provide, and in most cases are very appreciative of them…
However there are times where the updates appear to fix problems that aren’t broken,and in some cases make things worse,the latest update with the VU levels is a perfect example…
In reading just about all the bug issues and requests issues that users are experiencing, I don’t think I have read anywhere that users were experiencing issues with the VU meters, besides Rane One users experiencing Line VU meters not working prior to Version 3.7.6.
In contrast, a lot of minor and easy fixes/upgrades get swept under the table…(ie Key Lock being on as default whenever Djay is started)
I wish there was a way to roll back the update and “downgrade” to a previous version if we are experiencing issues with the current versions…
Unfortunately this update (3.8.2) didn’t fix it for me. Hope I don’t have to wait for another month.
It honestly sucks to have no usable VU-meters on a system that’s not even capable of remembering gains. Especially considering it was perfectly doing its job before that. I can’t understand how you set priorities. Maybe focus on what people actually need to properly djay. Like we can’t even rate or tag songs and that’s just so horrible for a library. Or remember pitch lock finally. Can’t imagine this to take even half a day of development. I hate to rant but I just don’t get it at all. And please stop with the “various bug fixes and improvements”. Just list them all. That’s why people read the changelog. A few updates ago you finally fixed the isolator-eq and you didn’t even mention it. I had to check manually after every update.
There’s so much good about this app but the wasted potential here feels immense and I’ve gotten a bit frustrated over the time. Please focus on actual issues and the major missing features that are so important, they should have been added a long time ago.
Hi @frgld, Thanks for keeping us updated and sorry to hear the recent update didn’t fix the issue for you.
Could you please tell me which controller you’re using exactly? Also, are you using a customized MIDI mapping in djay for your controller? If so, you should have received a popup message in the latest update (3.8.2) letting you know an updated MIDI mapping is available. If this is the case for you, please try using the new updated default MIDI mapping provided in djay for your controller, and this should solve the issue for you.
Please keep me posted on how things go with this. Also, thanks for your additional feedback about other features you’ve been waiting for. I’ll be sure to pass this along to our team.
Yes, the app noticed me today afternoon there is a new MIDI-config file for my Mixon 4 and asked me if I want to update. Now the VU-Meters are out of the reds. Thanks for that!
I was even able to manually integrate the new midiMaxValue from the .djayMidiMapping file into my old mapping so I didn’t have to rebuild it from scratch which would have been a lot of work as it’s heavily customized.
@frgld That’s great news! Thanks for keeping us updated. I’m really happy to hear things are working properly for you now and that you didn’t have to rebuild your customized mapping from scratch either.