Behringer UB-Xa and UB-Xa D update 2.0 - a brief overview
Вставка
- Опубліковано 28 вер 2024
- Hi, in this video I want to share some informations about the firmware update 2.0 and also about some workflow improvements.
You can check my other tutorial as well which was using the original release firmware.
• Behringer UB-Xa Walktr...
I didn't cover every detail, however here are some additional informations about the update (possibly not complete):
New modulation sources in the matrix:
- Drift1 (VCO1 drift, a randomised per voice drift factor applied to VCO1)
- Drift2 (VCO2 drift, a randomised per voice drift factor applied to VCO2)
- DriftF (VCF drift amount, a randomised per voice drift factor applied to VCF)
New destinations:
- FiltDriftA (VCF tuning drift amount)
- FiltDriftS (VCF tuning drift speed)
- OscDriftA (VCO tuning drift amount)
- OscDriftS (VCO tuning drift speed)
- In LFO sync mode, dotted notes are now resetting correctly.
Fixed:
- "thumping issue"
- A reset all controllers message was resetting the mod wheel to 0, meaning maximum performance LFO modulation instead of no modulation.
- After resetting factory patches the routine will read back and verify that the patches have indeed been written to flash.
- After resetting factory patches, the patch names cache is invalidated in the select encoder menu. Correct patch names should now be shown immediately.
- Fixed channel pressure messages not sending if selected as the 'Aftertouch Out' and forwarding ArpSeqSel is deselected in MIDI Forwarding menu.
- Fixed impossible to start Arpeggiator or Sequencer when local control is off and sync mode is set to internal.
- Fixed behaviour of CC in dual mode
Synthtribe now contains a basic librarian to store and organize patch banks.
Hi, in this video I want to share some informations about the firmware update 2.0 and also about some workflow improvements. You can check my other tutorial as well which was using the original release firmware.
• Behringer UB-Xa Walktrough & Tutorial ua-cam.com/video/DgQslX6uupM/v-deo.html
Thankyou Tom for a thorough and informative video. This update has really improved an already excellent synth. It seems “we hear you” isn’t just a slogan.
@ionian8606 sometimes they hear you. Other times, they release the Space FX.
PLEASE. How do I find this update? I don't see it on their site. Or do I have to download the latest version of SynthTribe? The only download I can find is a PDF describing the new features. Link? Thanks in advance!
I wish they'd update that horrific red backlight on the screen. The desktop has changed to a much less violent grey-blue that looks so much nicer.
@@decimal1815 I assume that will be changed at some point in the production run later. The first desktop units are also delivered with that red one. Only the rendered pic has the other color yet.
Any ideas why Synthtribe (V2.8.1) might still be telling me that I'm up to date with Firmware V0.3.117?
@@ionian8606 That’s the correct version number for what Behringer calls 2.0
@@tomnoise23 thanks for explaining. B’s numbering is a little counterintuitive!
@@ionian8606 that’s a very diplomatic description 😉
Great video! Could you share a list of the new Mod Sources & Destinations?
Sure! The new mod sources are: Drift1, Drift2 and DriftF. The new destinations: FiltDriftA, FiltDriftS, OscDriftA, OscDriftS
@@tomnoise23 Thanks!
@@SamLibman you're welcome. Added to the description as well.
A great update to this fantastic synth and thanks Tom for the walk through video! Is there any information on the ‘improved polyphonic AT and dual midi messaging. Have you tried it out? Cheers
Thanks for your comment. I think this affects the midi out behaviour. With the older firmware there was this issue, that you could not send out Poly AT to midi, if the parameter "ArpSeqSel" was not activated. Also this contains a few bugfixes when the unit is in dual mode, so it's more reliable and you have less unexpected results. Just for instance, with the older version there were some issues here and there while editing patches in dual mode, when using local off with a DAW.
@@tomnoise23 thanks for your reply Tom. From watching the Behringer 2.0 promo video it sounded like there was a bit more was going on with how the key pressure response affects the tone. I look forward to trying it out when I receive my replacement UB-Xa as the first one I received only last Friday had an issue with some of the keys sticking. Unfortunately this problem did not go away even after playing it for some time over the weekend so I’m getting it replaced.
@@reubenhumphreys6039 That’s possible, but I don’t use Poly AT a lot. My keyboard playing skills are not really great, so I’m not sure if it’s much different than before.
Good luck with your replacement unit!
1:04 "Less parameters in the atrophy settings...and also a new few ones."
Does that mean that patches done under the older firmware - as a result - will sound a bit "differently" under the new firmware (in case that some of the old atrophy parameters were edited globally for details)? Or are the missing atrophy parameters still secretly available somewhere in a hidden "back office" of the instrument (maybe via Synthtribe App?) to make sure that old patches - which made use of these parameters - will still sound the same?
(And yes, I'm totally aware of the fact the patches as such did NOT contain any of these settings yet when saving them....but that doesn't mean that users haven't make use of them nonetheless in addition.That's why I'm asking.)
I could imagine that the chips have a limited amount of memory space...and that Behringer needed some of it for new functionalities...and therefore decided to sacrifice some parameters "for the greater good". (I might be wrong. It's just a theory of mine.)
Yes, it might be a niche topic (that doesn't even affect about 95% of the users), but it would still be nice to know. Thanks in advance. 🙂
@@sauermusicDE right- I think I was not specific enough so it’s leading to misunderstandings. The „missing“ Parameters are now editable directly from the buttons. Means, the workflow is different now, but the parameters are still available at other places.
@@tomnoise23 Ahhhh....ok. 👍
Hello Tom, and thank you very much for your effort! If Behringer can't manage to send users documentation about the update. But I still have a big question mark about the atrophy settings. It's all well and good that you can now save individual settings with the patch... but what about the global atrophy setting? SHIFT + Vintage, these profiles are applied globally and are NOT saved with the patch. So in plain language, the Global Atrophy Profile can always change my Patch Atrophy settings...unfortunately I don't understand that at all :-( Maybe you can shed some light on this. Thanks for that :-)
Ah, I see - sorry I should have added a short explanation of this to the video.
So if you open the voice menu, by tapping shift&voice, you can set the save location to "Current Patch" and make your desired changes to the Atrophy settings. When you scroll further down in the voice menu, then you have the option to copy any existing Profile, too, which is also handy as a starting point for your own settings.
If you write that Patch, then it will always load with the Atrophy settings that you have assigned to that patch.
When you have a patch loaded, which was saved with particular Atrophy settings, then pressing shift&Vintage will show "Atrophy Profile: patch".
The globally selected Atrophy setting will stay for every patch that has the save location set to "Atrophy profile."
Hope that makes sense?
@@tomnoise23 Thx a lot! :-)
Q: So do I want to change the atrophy setting that I want saved with the individual patch before or after I change the save location? I mean, first change globally within the patch I want to save, then change the save location to patch, then save the patch, then go back to global settings and put it back where I want the rest of the patches set? I'm so confused for some reason.
@@TheJrwalker77 Yeah seems confusing but it’s quite simple: Start with changing the save location to „current patch“, then apply your changes or copy any existing profile and then save the patch. The global vintage setting is not affected.
@@tomnoise23sorry for continued questions, but did you notice that the firmware # changed in the global settings? Mine didn't, but the firmware on the updater software says 2.8.1. Also, I am finding that I DO have to go back and change the atrophy settings, as changing them continues to change it globally. Once saved as you described, the atrophy setting will remain as saved per individual patch. Weird. Great synth though! Thanks so much for your help! 🎉❤
Nice demonstration with a lot of improvements! I assume max LFO rate of 20 Hz can still not be increased to 50 Hz even thru multiple mod entries or has that also changed meanwhile?
@@Gerald_Daniel thanks. Atrophy settings 32/33 are for setting the mod and performance LFOs limits. They both can go up to 60 Hz.
@@tomnoise23 Thank you so much!!! I'd not expected that. A dream came true! Now I could almost fully mimic OB8 & go way beyond that (after having aquired a unit). Obviously behringer has giant ears!
@@Gerald_Daniel You‘re welcome. Though this was possible with the older firmware as well. The upper speed limits didn’t change.
OK, then my LFO question (I guess) last fall was a slight misunderstanding. Nonetheless, very happy (if not strongly impressed) that the instrument experiences significant improvements.
Thanks for this most useful information. I cant seem to find any information about it on the Behringer download page?
@@kevanbarrett7411 the new firmware is online and will be updated using the Synthtribe app. Seems that they didn’t update the documentation yet.
Thanks. I’m not familiar with Synthtribe but I can see a version for windows for the desktop version only. Is there a keyboard version that I need?
@@kevanbarrett7411 if you download Synthtribe 2.80 and open it, it should offer an update if you’re synth is connected via usb. It’s an universal app that works for many Behringer synths
Ok thanks I’ll try it tomorrow. 😊
@@tomnoise23 Thanks . All sorted now.
These new envelope modes are very buggy. Why is Retrigger there at all, since that is the default behavior? Setting it has no effect. It is also mutually exclusive with Legato. Inverting the loudness envelope is also a bit weird since inverting the VCAs on the voices makes all voices play when no key is held. Maybe useful in Unison which will leave the last pressed note playing. I've noticed bizarre behavior with these modes. They just don't work right sometimes.
@@mwdiersFirst I was confused about some things, too but some of these functions only start to make sense (and have an immediate effect) in unison mode and with a certain playing style.
Those functions are all per Voice. For instance if you think about it, on a polyphonic synthesizer it is to be expected, that all voices are audible at their actual pitches if the VCA opens up.
If Retrigger it’s off, the Attack will pick up the level of the envelope from the actual release level, if this voice is played again. It has an obvious effect in unison mode or if many voices are playing, like in double mode with full chords and longer release times.
Excellent!
Hi, is Sostenuto working on your UB-Xa?
@@ingostromitzky497 Sorry, I don’t know- don’t have a pedal connected at my UB-Xa.
@@tomnoise23 ok thanks 🙏
@@ingostromitzky497 Oh, just wondering why you where asking: Are you aware that the hold pedal works different than usual on an OB-Xa and also on the UB-Xa? It will add a soft release to the sound, instead of holding the tone. But it can be configured as hold pedal in one of the menus (can't recall in which one right now).
@@tomnoise23 thanks, I know that but on my UB-Xa the Sostenuto works exactly like Sustain, I will double check the manual😊👍
@@ingostromitzky497 cool, good luck. Some features are in unexpected places on that synth.
I just can't get this to work, most definitely updated firmware, but I can't get the steps down to save the vintage/atrophy setting specific to the patch. I've written BEHRINGER over a week ago and never got a reply. I need steps, what order to do things. Change the vintage first, then the voice profile to save to patch? Everytime I change the Voice/AT profile to save to patch, it reverts to the default global. If I change the the Voice/AT save to patch, then change the atrophy, then save, it does not remain at the vintage setting. Why am I not getting this right? Feel like a noob! 😂😢 Do I save the patch settings last? HELP!
@@TheJrwalker77 please See my answer to the comment from user Kallewalle.
Thank you kind sir for your reply, I have read through this thoroughly, not sure why I still have trouble. I will upload a video of my problem., perhaps you can comment on my order of operations! I will send the link soon!
ua-cam.com/video/PfA28c9DXEM/v-deo.htmlsi=fNWhRaAtrbi-Wbt9
@@TheJrwalker77 I will upload a short tutorial of the procedure soon, too.
🎉🎉🎉🎉🎉 Thank you!
Thanks for the update; I had no idea a new firmware was out. Really nice that they added patch-specific atrophy settings!
Thank you for doing this!
Thank you! ✌🏻😎🎹🌴🌞
Tom, would I need to do a factory restore after the download? Or, can I simply do the download and my own sounds will still be in their locations?
I'm probably not the only person with this question, so this could help others as well.
Great video, and thanks for any help.
@@Marky8864 The update went smoothly and it didn’t delete any patches. But it will reset the global settings. Of course, It’s never wrong to make a SysEx dump as a backup of all patch banks before updating. Just in case, if something goes wrong.
Great video, Tom! Thanks a lot.
@@Bernd_Bruening thank you too!
I'm seriously considering getting the desktop version of this synth. Are there multiple voice panning options or voice pan spread options for this synth like there are on the OB-X8? Also, can these voice pan settings be saved with the patch now with the new firmware update?
Thank you.
@@kvmoore1 The panning can be set for each voice individually as a part of the Atrophy profile. Means: yes, now it can be stored with each patch.
@@tomnoise23 That's absolutely wonderful and exactly what I wanted to know. Thank you very much!
Brilliant. Thanks so much for taking the time for showing the new features. I really appreciate it.
Thanks for making this video!
How do you like the Poly-Aftertouch and keyboard in general?
I think it's okay, but very light action. Personally I prefer the NI Kontrol S MK3. Other than that, I didn't have any issues with the UB-Xa Keyboard so far. But I'm not a live player.
@@tomnoise23 OK. I may go for Hydrasynth for poly aftertouch then. I still can't believe we are in 2024 and most companies do not impliment poly aftertouch. (Roger Linn frowning.)
@@tomnoise23 What about using the native Instruments as the controller for the UBXA, is it worth it for just the feeling of better aftertouch?😄
@@markslandingsandaviationvi3123 I don’t get the point. Did I say that? 😆 But seriously, UB-Xa D plus your favorite controller could be an option, no?
@@tomnoise23 My bad😄 My point is if the midi makes any difference to how Poly Aftertouch feels/works. Many use the Hydrasynth as the preferred controller for Poly Aftertouch.
Sheesh! Behringer is already putting out updates, and we can't even buy one in Canada yet. Way to go Behringer! Nice work Tom, I'm just grumbling (not at you).
@@michielklarenbeek3909 whoa… I can relate to that. On the other hand you’ll initially get all the improvements too! 🙃
Shame that canadian stores are not able to deliver yet! But I’m wondering: Wouldn’t be stores like sweetwater be an option for you?
Oh yeah, and Reverb too. I saw a listing from a store in New York that had it $300 cheaper (even after exchange). But......we get whip sawed on duty. That's on our end. I've ordered modulars, and had the duty be as much as what I paid for the module
@@michielklarenbeek3909 ouch. Gotcha 🙂↕️
@@michielklarenbeek3909 "Oh Canada, of tax and duties grand"