Ok, I'm sending a support ticket today. Anyway, it is a bit of a shame that the community has to push in order to persuade Arturia to correct well known bugs (audio mods bugs, sequencer bugs, and so on and so forth)! Knowing that, in a year or so since the latest update, (to me at least it's pretty obvious) nothing has been done on the software part and that the team isn't actively working on that, is not tolerable!
I am not - as other users did - thinking about selling my matrix BUT I paid (as many others did) 2000euros which is more than I have paid for my car. Given that Arturia is raising the prices, I hope the will consider justifying the expense of 2300 euros giving the users a full up to date piece of gear. And I am not talking aout implementing new features: even if that would be great, I think that - at this point - a simple bugfix would be warmly appreciated. ::)
And again no news about nothing......
They just tell us to send emails so we don’t pollute the forum here for other potential customers to read.
Really I think we can forget about an update.
Arturia is being run as a cash cow now and nothing else.
They just focus on hat makes most money in the shortest of time.
Instead the f keeping developing little things thy should make good and come with a good update for the flagship product.
But I’m nearly sure it will never happen.
The MB is a great synth but it could be so much more....
I’m sure behind the screen now they are working on a Polybrute and then will milk that for a year once it’s out and then once people start to ask about significant updates they will fast starting making another product to push for a year and on and on.....
Sad but nearly sure this is the Arturia philosophy....
And again no news about nothing......
They just tell us to send emails so we don’t pollute the forum here for other potential customers to read.
Really I think we can forget about an update.
Arturia is being run as a cash cow now and nothing else.
They just focus on hat makes most money in the shortest of time.
Instead the f keeping developing little things thy should make good and come with a good update for the flagship product.
But I’m nearly sure it will never happen.
The MB is a great synth but it could be so much more....
I’m sure behind the screen now they are working on a Polybrute and then will milk that for a year once it’s out and then once people start to ask about significant updates they will fast starting making another product to push for a year and on and on.....
Sad but nearly sure this is the Arturia philosophy....
Like most users i am also desperately waiting for news,
but negative theories on why and what should be kept down til a statement from Arturias side.
But it would be great if Arturia is asked by sonicstate or similar why they do not care more about their flagship synth.
Hello Everyone.
We haven't let the MatrixBrute down.
Work on an update just needs time and ressources.
We are these days trying to gather:
- Your feature requests
- Your bug reports
- Etc...
This will help define priorities and prepare an update that could at the same time bring bug fixes and improvements on the MatrixBrute workflow.
We will of course check the forum, but the best would be to contact the support to send us an official request: https://www.arturia.com/support/askforhelp/issues (https://www.arturia.com/support/askforhelp/issues)
One request per ticket would be great to easily keep a track of each ticket per feature / bug.
This will definitely have an influence on the update.
I can't give any day at the moment, as we need to define what will contain the update first.
Kind regards
Edouard
Posted by: fede bts
« on: April 10, 2018, 03:02:36 pm » INSERT QUOTE
Thanks Edouard, this post is very very much appreciated!
1. It shouldn't need tickets for you to realize bugs.
2. Why no constant bug fixes, why "one update with bug fixes and improvements"?
3. No ticket does not mean, a user does not have a useful idea. So no ticket, and an idea will not be put on your list? Seriously?
4. Why this forum then? You got so many contributions here - and now you say,
they are not good enough for you? Sorry, but that is rather not so nice...
I don't know any other manufacturer who demands tickets to pick up suggestions.
I don't know any other manufacturer who demands tickets to pick up suggestions.We are trying to officialise customer requests, maybe other manufacturers don't.
Sorry for "more pressure", but still i ( and i guess others too) do not understand, why 1 man companies can fix bugs immediately and constantly for example,
while Arturia does not.
Also, i really would appreciate an answer, if a patch memory expansion is technically possible.
The first Voyager also only had one or two banks and was expanded then to 8.
Technically I would say yes. But depending of what will contain the update, it will be or not. Can't say...
One request per ticket would be great to easily keep a track of each ticket per feature / bug.
This will definitely have an influence on the update.
Community boards can be a great asset for steering product direction, as their customers can vote on what features or capability they need in a product. IMO, having bugs reported to support tickets is the right workflow but feature requests should have more transparency with their customer base.
Visited their booth at Superbooth, but none of the ones I talked to could give me any useful information about the missing updates.
some are technically impossible, such as repeating envelopesHi HUBA,
It's technically possible in the firmware (old coder here, not easily fooled ;)). However, I think the problem is how to expose this feature in the user interface so that it doesn't become too cryptic (same for some other requested features). Some features might be squeezed in e.g. by chording some buttons, maybe blinking a LED as an indicator, but for the envelopes there are no such things available directly or related in a clear way.some are technically impossible, such as repeating envelopesHi HUBA,
by "repeating envelopes" you mean looping envelopes, right? I have been sending it as a feature request as well, but I wasn't told it was impossible. Such a pity! Well, I am glad something is moving: I'm not rushing, yet I would really like to know more aout what's happening with the developing 8) Let's cross our fingers and hope for the best
Even so, I think it might possible to use the matrix and the LED displays to expose a set of parameters like that, and also using some other buttons (chorded or held for N seconds) to enter a mode to access these parameters. It would be a little contrived and goes somewhat against the one button per function ethos, and it may not be too popular for design-cleanliness reasons. Would open up new possibilities though.
+1Exactly. I've submitted "Editing of the system parameters on the synth itself, with no dependency on the MCC software" as one of the most important feature requests. I want to still be able to make full use of my MxB in the old folks home, long after the MCC software is obsolete (I don't think it will run on my quantum computer's AI OS in the year 2045 ;D).
in fact, i assume the matrix could be used to replace the annoying need for a computer editor foe most duties.
The Matrixbrute is no longer on the front page at www.arturia.com...In all fairness, the front page changes all the time - they use it for the latest news items. The MxB is the very first thing on their product page and it appears on the news page whenever there's a related event or release.
Will not buy any other Arturia product. Ever. Great work Arturia!
We all have different needs and preferences. :) I didn't know about these issues when buying it.
What annoys me is that functions that do not work as Arturia intended (i.e bugs) aren't fixed. Bugs should be dealt with asap imo.
New features would be nice, and I would even pay for upgrades that added something I really wanted.
In all fairness, the front page changes all the time - they use it for the latest news items. The MxB is the very first thing on their product page and it appears on the news page whenever there's a related event or release.
If the complaint is just a symptom of the frustration of waiting for an update, I can understand that. From what I know, they're working on a quite extensive update, so even if it has taken its time, we're not forgotten. And now that the update is apparently being worked on, I'd rather want a solid and substantial one than a rushed and minimal one.
So many negative Nancys...
...To me it doesn't make sense to buy a synth that doesn't have certain features and then get mad that there's no update to implement those features.
Bugs should be dealt with asap imo.
New features would be nice, and I would even pay for upgrades that added something I really wanted.
Another 3 months and no news...
... - this firmware update won't probably be ready before 2019....Just to be sure, was that part stated explicitly by Arturia?
... - this firmware update won't probably be ready before 2019....Just to be sure, was that part stated explicitly by Arturia?
Hi,
Yes, the update is on the specification pipeline and yes it will be a major update. Don't ask me for a date because I have no idea. Once again I can only ask you to be patient. It tooks time for BeaStep Pro to go 2.0 but in the end it was worth the wait. I'm sure it will be the same story for our MatrixBrute.
Regards,
Matthieu
Yes, the update is on the specification pipeline and yes it will be a major update. Don't ask me for a date because I have no idea. Once again I can only ask you to be patient.
The Matrixbrute is no longer on the front page at www.arturia.com...
Will not buy any other Arturia product. Ever. Great work Arturia!
My statment wasn't (just) about the front page, but the lack of feedback from Arturia.
ARTURIA - Looking forward to the update. Just my $0.10 as someone who recently purchased this synth brand new last month.
Well if you guys just bought it you can have plenty of patience for the update lol
let's contact some magazines, if they could ask ARTURIA why they treat their flagship synth and its users like "that":
sonicstate:
https://sonicstate.com/about/contact.cfm
amazona (german):
https://www.amazona.de/kontakt/
musotalk (german):
http://www.musotalk.de/kontakt/
i cannot read french, but here's audiofanzine fr:
https://fr.audiofanzine.com
On one hand you are right. On the other Hand
- Arturia profits from positive Feedback in Forums, so they also have to live with the negative
- DSI did something after a petition and some magazine contacts
- at least the bugs should have been fixed long time ago
- one man SYNTHSTROM does wonders.
- at no point i left a doubt that i regard the MB as high as an EMS synth which is max praise from my side for a monosynth
- and yes, ARTURIA said, they are working on something. Still they cannot give Details on what and when. And i think it would be good for them
if there are some more detailled announcements
i thought about all that before and i did not want to damage them in any way. But if you Google "customer service" and Arturia,
then you might discover there is some air for improvements on their side.
And last but not least - since i had the "entitlement" discussion many times on elektronauts:
i think, we, the customers have a right for the best possible software (including enough program space).
I think it usually is nonsense to ask for hardware improvements (although often in synth history users were very happy
about one or the other), but software has to be top notch. period.
Not sure that airing frustrations is really going to speed things up.I absolutely agree with you on this. Even if I am one of the first users who repeatedly asked for this update to happen, I don't think that isnsulting Arturia will ever bring us anywhere. Just send a support ticket to Arturia asking for more details about a possible release date or features and kindly ask Arturia ask to report it in the official forum thread. The last time I did it, I got an answer in like 1 or 2 days and a guy of the staff kindly reported his thoughts in this thread. Then, if someone wants to contact SonicState or whatever webzine, it can be a good idea ... But - first of all - we have to stop insulting the developing team just because a bunch of users (how many? 10? 15?) are waiting for a (ABSOLUTELY NECESSARY, don't get me wrong) firrmware revision
I suspect energy better directed contacting Arturia directly and making wishes known...
...repeatedly if need be ;)
... Or else, people will probably end up ... contacting webzines.
sorry to bother you with an old question. Lately, there has been a huge debate regarding the future Matrixbrute Firmware Update, in the "General Discussions" section of your official forum. While I have been professing calm and comprehension, there are many frustrated Matrixbrute owners out there (and I can't blame them). We've been told that an update was in the specification pipeline, but - still - we have no clue on which specifications will it contain, when it's going to be delivered, if you're actively working on that, if it's still happening at all. It is more than disrespectful on your behalf letting people pay 2000 bucks for an instrument that needs bugfixes and promising a "Major update" that - after a year and a half - is still lacking. At this point I think you owe us an OFFICIAL STATEMENT (in the forums, and through your social networks), providing us further details. Or else, people will probably end up selling their matrix or contacting webzines.
Hello Federico.
Thanks for contacting us.
We are indeed aware of our users expectations about this update.
First, let me clarify things, the update is planned and will happen.
I saw people saying that we will not be doing it, don't worry, this is not the case.
We are dedicated to update this synthesiser as soon as we can.
The Brute team is very small, and has many other ongoing works to handle.
The person who made the MatrixBrute firmware will roll back to the MatrixBrute firmware as soon as he finished his ongoing projects.
Moreover, it also involves tons of additional work from other teams, like the test team, who also need this update to fit in their schedule.
Consequently, the MatrixBrute update is plaanned for the first half of 2019. (We initially thought it could be done earlier, but unfortunately, plannings got delayed)
Out of bringing bug fixes, we do want to improve the MatrixBrute capabilities and the sequencer workflow.
We will do our best to implement features and improvements that makes sense and will make the MatrixBrute a better instrument.
I can't give any further details about what will be implemented or not, as these changes require to be confronted to the developper plus all the constraints involved in their implementation, and we do not want to bring disappointments.
But be aware that we listened to the users suggestions with attention.
The only detail I can let you know is that we won't implement new features that can't fit clearly the UI. One of the biggest pleasure in the MatrixBrute is it's straightforward synthesis UI.
This will not be changed.
Let me know if you have any further question.
Kind regards, and thank you for your attention.
Bonjour.
...The only detail I can let you know is that we won't implement new features that can't fit clearly the UI. One of the biggest pleasure in the MatrixBrute is it's straightforward synthesis UI.
This will not be changed.
...
Consequently, the MatrixBrute update is plaanned for the first half of 2019. (We initially thought it could be done earlier, but unfortunately, plannings got delayed)...
Besides that: to run a feature request thread, ask to send in support tickets and THEN say
" we don't care about your wishes" seems really strange to me.
We will see... i relly like my MB a lot, i bought it very early new in a smaller shop which i like to support whenever i can,
but i start to get the feeling that ARTURIA just does not take their customers seriously - and who would like that feeling?
Complaints about Arturia's customer service are not exactly new - and i count not happening OS updates to "bad customer service" -
but i thought things had bettered. And really: looking at the DELUGE alone (and i met one of the guys before it even came out, so i know quite well
how supportive they are and how much they involve customers) really makes me mad. The MB could be much more creative and i am beginning
to feel bad about those poor promises...
Quote...the MatrixBrute update is plaanned for the first half of 2019. (We initially thought it could be done earlier, but unfortunately, plannings got delayed)...
So once again, sorry for this delay.
We do want to make things right, but it's not just as easy as it appear from an external point of view. We are still a growing reasonably sized company, but are all passionated people waking up each morning to bring cool and affordable instruments to the world.
As a MatrixBrute owner, I'm like you guys, very eager to see this update coming, and I wish it could have been done earlier.
Kind regards
Edouard
10.000 clicks soon ...
(https://i.ytimg.com/vi/bNiuH4tj8fc/hqdefault.jpg?v=56870627)
although in my opinion MATRIXBRUTE users should have gotten PIGMENT cheaper than any other former ARTURIA product userAssuming you got the same $69 offer that V Collection owners got, then no, you shouldn't.
although in my opinion MATRIXBRUTE users should have gotten PIGMENT cheaper than any other former ARTURIA product userAssuming you got the same $69 offer that V Collection owners got, then no, you shouldn't.
Fair enough, I agree you should have the $69 option.although in my opinion MATRIXBRUTE users should have gotten PIGMENT cheaper than any other former ARTURIA product userAssuming you got the same $69 offer that V Collection owners got, then no, you shouldn't.
No, MB users had to pay 99 not 69
that's what i say, we bought the most expensive product, are waiting so long for updates because of the development of for example PIGMENT,
but then wen pay more then Vcoll6 users.
it's not about 30 bucks. it's about being treated equally.
VAU, I don't know why you would even bother buying an Arturia product until they make good on their current responsibilities. I'm not meaning to attack you in any way, I just don't get it.
I've looked through their downloads page under the support section, and I don't see a lot of firmware updating on any of their hardware products. The matrixbrute is a much more complex instrument than most of their other hardware and, due to inexperience (maybe over confidence too) they did not budget enough resources for needed updates to fix bugs and upgrade features as user conect with their product. A huge misstep in my opinion. Now we all have a bad tast in our mouths.
That said, they have promised a huge update in 2019. It's literally in this thread in writing a few pages back.
Hi
As a new MB user ( xmas present ) can you give me a list of the bugs people have found
so I don't get confused and think my unit is faulty
cheers
kev
I really hope Arturia is not going to reveal Matrixbrute MK2 at this NAMM :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X :-X
Just wanted to remind the MB user forum community that Arturia is planning to release an firmware upgrade and we should expect it around mid-2019 as shared by Edouard; reference https://forum.arturia.com/index.php?topic=92467.msg151590#msg151590 (https://forum.arturia.com/index.php?topic=92467.msg151590#msg151590). This isn't new news but just a courtisy to those in the community who hadn't seen it.
It would be grand if Arturia would share the list of defects and enhancements the update will include.
Do you really think, just to announce a bug fix makes it better ... if the bug fixing is announced to happen in 1,5 years?
If you buy a car and something is wrong with the board computer, would you be happy if the company tells you: "Don't worry, we will fix it in about 1,5 years!"
???
Quote
Do you really think, just to announce a bug fix makes it better ... if the bug fixing is announced to happen in 1,5 years?
If you buy a car and something is wrong with the board computer, would you be happy if the company tells you: "Don't worry, we will fix it in about 1,5 years!"
???
I hear your frustration and I too am in the same boat as you and all other MB owners. Don't take your frustration out on me because I happened to repost a timeline committment from an Arturia representative to address issues. My post is not an announcement. I am merely a customer just like most of us here, I do not have any affiliations, business alliance or ties with Arturia to make any such "announcements".
No one is attacking you Endreola.
We're all in this together. I just don't want to give them an out to what they have a responsibility to do for us as high paying customers.
Just wanted to remind the MB user forum community that Arturia is planning to release an firmware upgrade and we should expect it around mid-2019 as shared by Edouard; reference https://forum.arturia.com/index.php?topic=92467.msg151590#msg151590 (https://forum.arturia.com/index.php?topic=92467.msg151590#msg151590).
... though i would have preferred if they discuss all ideas here with the users.
Some of you on this forum are much more forgiving than me.
The point about the spamming noted above: customers complained, their response was to continue, as it paid off financially for them= complete disrespect for their customers.
I am interested in is my DAW to be able to sync the Matrixbrute, which, as you all know too well. This synth doesn't work correctly because of the firmware.
I've never been able to get accurate sync. I'm sending midiclock ftom an Expert Sleepers USAMO, which is sample accurate and jitter free (converts audio to midi)
My brute always drifts up an down 2bpm. It's close enough for most things, but it is not 100% and causes issues with layering and arranging long passages.
Tonytoot- the MIDI direct from you CPU will inherently have jitter, that is not a problem with the Matrixbrute. If you have s known stable source of MIDIclock and it still forms not sync, that is all the Matrixbrute's fault; which is my case.
FYI- MIDIsync SHOULD be engaged.
Ps- how is your karma -139? LolTo be fair, Karma is a joke on this forum, just like it is on most forums. Disagree with someone and they're about ten billion times more likely to 'smite' you than any of the people you've helped hitting the 'applaud' button. Exhibit A: user LBH, one of this forum's most prolific posters and helpers with nearly 2000 posts to his name, has a whopping Karma of...51.
Ps- I just gave you an applaud because I feel bad for your story. Lol.God bless you my friend, reciprocated :-)
Ps- I just gave you an applaud because I feel bad for your story. Lol.
Did you open a support ticket Tony?
Most of my clock syncing is to Squarp Pyramid and get best results after setting Midi clock to 1ppq within MCC. These devices (and others) are connected using Midi DIN through iConnectivity mio10.
I have no syncing issues when using Logic. In fact this is the best MIDI sync I have ever used! 48PPQ.
Was really shocked that when I recorded a test sequence into Logic the attack transients are bob on the beat. Really
accurate indeed for a MIDI sync.
in case you missed it, firmware update 2.0 will be released Spring 2019. It is not Spring yet...
8)Difference is your daughter will arrive round about on time as promised, not some vague time between March and June or perhaps even later.
I have a daughter on the way this spring and, between you and I, I'm almost as excited about this. :o
Come through on this Arturia!
Aren't most of their products very good/excellent? Even my nag nag thread here does in the end prove one thing: most of the users here regard the Matrixbrute as one of the best monosynths ever made.It probably depends who you ask. I've always been reasonably content with their software, other than when they try to take the p*ss with the upgrade prices. But you don't have to look too far in this forum to find buyers of Arturia hardware who feel a bit abandoned, some who have hinted (or explicitly stated in some cases) that they wouldn't buy Arturia products again.
Here's a timer counting down the remaining days of Spring 2019 https://howmanydaystill.com/its/summer-2068 (https://howmanydaystill.com/its/summer-2068), just saying...According to your timer it's 70 days til Summer, which as of today gives 30th May. Sorry to disappoint you but Summer doesn't start on 30 May, it starts on 21st June :)
Or at least make it fully functional!
I am very excited about it. I am only wondering when it will be released ;)
This is in the current Arturia newsletter (https://www.arturia.com/images/newsletters/2019-03-15-blast-matrixcase-available/2019-03-15-blast-matrixcase-available.html):
"We've been listening to your feedback and compiling feature requests, and we'd like to let you know that our development team is currently working on a firmware update for MatrixBrute. Keep an eye on our newsletters for more updates in the future."
This is in the current Arturia newsletter (https://www.arturia.com/images/newsletters/2019-03-15-blast-matrixcase-available/2019-03-15-blast-matrixcase-available.html):
"We've been listening to your feedback and compiling feature requests, and we'd like to let you know that our development team is currently working on a firmware update for MatrixBrute. Keep an eye on our newsletters for more updates in the future."
i'm afraid that this means: sorry, we need another 6 months
Hi,
Unfortunately there is nothing I can say at the moment... But if you want your voice to be heard, please, contact the support services. The more people will do that, the more impact you'll have and the update will happen.
Regards,
Matthieu
@Arturia, when it comes to new features, why not use magnetic labels for the front panel where needed to update or add text or images.Arturia are very aware of the option to use magnetic label plates, they have been including them with the KeyLab mkII since launch.
I found that custom magnetic labels cost nothing these days, even in low quantities, e.g. here (https://www.stickersinternational.co.uk/engine-specify-magnetic-signs/confirm/?s=rectangle&w=100&h=8&wu=mm&c=3&cu=mm&q=100&v=16).
Arturia are very aware of the option to use magnetic label plates, they have been including them with the KeyLab mkII since launch.Great! :)
And again no news about nothing......
They just tell us to send emails so we don’t pollute the forum here for other potential customers to read.
Really I think we can forget about an update.
Arturia is being run as a cash cow now and nothing else.
They just focus on hat makes most money in the shortest of time.
Instead the f keeping developing little things thy should make good and come with a good update for the flagship product.
But I’m nearly sure it will never happen.
The MB is a great synth but it could be so much more....
I’m sure behind the screen now they are working on a Polybrute and then will milk that for a year once it’s out and then once people start to ask about significant updates they will fast starting making another product to push for a year and on and on.....
Sad but nearly sure this is the Arturia philosophy....
Hi,
Unfortunately there is nothing I can say at the moment... But if you want your voice to be heard, please, contact the support services. The more people will do that, the more impact you'll have and the update will happen.
Regards,
Matthieu
and the update will happen.
Are the Matrixbrute problems going to be fixed, as promised, before the summer?
'Updates' are secondary. Are you going to fix the long-standing problems with the synth?
A staff member saying 'if you do this, we may deliver' isn't good enough. It is an insult. You are angering your paying customers.
Hello.
The Matrixbrute developer is working full time on the MatrixBrute update.
> Bugs are being addressed
> New features are being implemented
We are still aiming at the beginning of summer, hoping that the test/beta-test will not dig out bugs that could delay the release.
Cheers
Edouard
I'm sure most of us would prefer the update to be thorough and a bit late rather than rushed and incomplete; as long as we are being made aware of the situation.
Thanks Edouard!
I'm sure most of us would prefer the update to be thorough and a bit late rather than rushed and incomplete; as long as we are being made aware of the situation.
QuoteI'm sure most of us would prefer the update to be thorough and a bit late rather than rushed and incomplete; as long as we are being made aware of the situation.
Thanks Edouard!
This.
Hello.Hello.
The Matrixbrute developer is working full time on the MatrixBrute update.I don't expect anything less, given I/we are paying his and your wage.
> New features are being implementedIf bug fixes were delivered in a timely manner, you could probably have sold updates as add-on packs. I'd have paid for them (if bugs had been addressed). This is potentially a missed business opportunity.
> Bugs are being addressedHopefully fully dealt with, and fixed entirely.
We are still aiming at the beginning of summerWait - I thought it was Spring?
hoping that the test/beta-test will not dig out bugs that could delay the release.Given your developer has been working on this for 2 years, I'm sure it'll be bombproof.
CheersSlightly casual for my taste when you have thousands of my money in your bank account and I have an instrument (instruments, given I have more than one Matrixbrute) that partly doesn't do what I was told it would do, but I'll go along with your tone for now:
23 days left til end of spring 2019...Last post from Arturia (03 May) it's now going to be summer.
(https://s.wincalendar.net/img/en/days/june-21-2019.png)
Two years is an epic amount of time to fix some bugs and add some features. Can anybody enlighten me as to why this is taking soooo long?
Someone probably already mentioned this in this or another thread, but is it possible Arturia knows it cannot quash some of these bugs without some hardware changes, so they are working on both firmware and hardware changes simultaneously?I don't know of any "bugs" that's tied to the hardware. AFAIK the hardware is solid.
He did say beginning of Summer which to be fair is the end of Spring. So only two weeks to go!
Arturia your deadline is 21/06/2019...Nope. ETA has been moved right to "beginning of Summer", see post from Edouard_Arturia, page 18, d/d 03 May.
Thats this Friday coming.
“We’ll do our best to make it happen.”
Great.. so the eta now went from spring to end of spring to:
“We’ll do our best to make it happen.” With no timeline at all.
Feels quite discouraging.
One thing I really really hope they put into the update, which seems like it would be simple and a no-brainer and very useful, is to be able to send midi control messages from all knobs and sliders...It does this already, ref. user manual section 6.1. You need to have "MIDI param send" and "MIDI param receive" set to "On", using the MIDI Control Center (they're on as default). You can also set "Enable 14.bit automation" to "On" in the MCC to get many of the knobs to use higher resolution (than the usual 7 bits) for the CCs.
One thing I really really hope they put into the update, which seems like it would be simple and a no-brainer and very useful, is to be able to send midi control messages from all knobs and sliders...It does this already, ref. user manual section 6.1. You need to have "MIDI param send" and "MIDI param receive" set to "On", using the MIDI Control Center (they're on as default). You can also set "Enable 14.bit automation" to "On" in the MCC to get many of the knobs to use higher resolution (than the usual 7 bits) for the CCs.
No they're not wrong in saying that "some knobs and buttons don’t send MIDI yet". You can see in the manual section 6.1 which knobs send and receive MIDI (almost all of them), and that no buttons send MIDI. What it has is still enough to use it as a MIDI controller, and to make automation tools (if you run Cubase or Ableton there are already community made MIDI device definitions for those).
I wonder why Spectrasonics is saying they are waiting for this from Arturia then. Do they mean they are waiting for something else? This is what they sent to me in response to my request that that they add the MatrixBrute to their list of hardware integration synths for Omnisphere: "Regarding the Matrixbrute – we are actually waiting on Arturia to release a firmware update that allows the front panel of the Matrixbrute to send MIDI data. As of now, the majority of buttons and knobs don’t send MIDI data making it impossible to create a hardware profile for it." And in a follow up email after I suggested this functionality was at least partially available, they said this: "As mentioned – some knobs and buttons don’t send MIDI yet which is why we’re still waiting on a firmware update." Are they just wrong, or am I missing something? I hope they are communicating with each other directly, so Spectrasonics can get whatever they need to add the MB to their list of hardware integration with Omnisphere.
If they could just be honest with us that would be a start. Some communication with clear facts about what is happening would stop angry people like me making posts like this ^.
Some communication with clear facts
...the slew of people getting bricked DOA Microfreaks....Where are you seeing this? Google can't find it for me...
I tried to post from time to time, but yes, I haven't posted "facts"
I can show you this as a proof that things are moving on.
I won't tell you what it is, but some of you may guess...
(https://i.imgur.com/VQksMgE.png)
Best regards
Edouard
... Looks like it may be ratcheting implementation in the picture, or some sequencer updates?!
I'm vibrating with excitement!
Hello everyone.
Sadly, we are not able to deliver the update today.
Even though my colleague is doing his best to deliver this right on time, the firmware update is not ready yet.
Unfortunately, to make things right, more time is required.
One thing I noticed is that, in the picture, all the lights of lfo2 are turned on. Could be because of a sort of debug mode, but, if this picture is lfo-related, I would rather speculate on a sort of customizable lfo waveform which you can draw using the mod matrix! Otherwise, if sequencer-related, it could be a new way to draw automations.
Even though my colleague is doing his best to deliver this right on time, the firmware update is not ready yet.
Edouard
Also, none of the retrig lights are on ;)
My take is that the MB is worth keeping as it is, with a few bugs and the potential for better implementation of Midi, Sequencing and Mod routing a possibility, but for now not a reality. So, in reality, if there never is a firmware update, although that will be a shame, I think I will still be happy with my MB. I could say the same kinds of things about my Minilogue and my Kronos--both of which still have limitations that Korg has not decided to expand upon or fix. Yet, I am fine with both as they are, despite these limitations.
With all due respect Micheal, and I will add that you obviously have a right to your opinion, but your comparisons are a bit silly:
The Korg Kronos is on version 3 of its firmware and being continuously updated to fix bugs and add features while the Matrixbrute had one update upon release and has been ignored since.
The Minilogue, seriously?! You're comparing a less than $500.00 synth with the matrixbrute?!
The biggest surprise to me in the email today from Arturia is the acknowledgment that there is only one single person working on the firmware update, which might explain why it is taking so long. If true, though, it also might make it more likely that the update will have its own issues. At least if there were a team, there might be some doing the updating, and some doing the checking on the updates.
I can show you this as a proof that things are moving on.
I won't tell you what it is, but some of you may guess...
(https://i.imgur.com/VQksMgE.png)
Best regards
Edouard
I can show you this as a proof that things are moving on.
I won't tell you what it is, but some of you may guess...
(https://i.imgur.com/VQksMgE.png)
Best regards
Edouard
Hello everyone.Thanks for the update and confirming that we haven't been forgotten.QuoteIf they could just be honest with us that would be a start. Some communication with clear facts about what is happening would stop angry people like me making posts like this ^.
Indeed today is the summer solstice.
Sadly, we are not able to deliver the update today.
Even though my colleague is doing his best to deliver this right on time, the firmware update is not ready yet.
Still, things are moving forward, and we are committed to deliver a great update.
Unfortunately, to make things right, more time is required.QuoteSome communication with clear facts
I tried to post from time to time, but yes, I haven't posted "facts"
I can show you this as a proof that things are moving on.
I won't tell you what it is, but some of you may guess...
(https://i.imgur.com/VQksMgE.png)
Best regards
Edouard
I'm going to guess it's an easier way to draw in and edit MOD automation. I don't think it's a custom LFO creator, just based on how there's a final blue LED lit up on the 16th step.
Having more than a single lane of MOD automation available for the MatrixBrute would be fantastic. Not sure if that would be possible given the rest of the workflow, but one can dream :)
...I Wonder what's @DrJustice opinion!Heh... well, your guess is as good as mine :)
Hello everyone.
Indeed today is the summer solstice.
Sadly, we are not able to deliver the update today.
Even though my colleague is doing his best to deliver this right on time, the firmware update is not ready yet.
(https://i.imgur.com/VQksMgE.png)
Best regards
Edouard
Great.. so the eta now went from spring to end of spring to:
“We’ll do our best to make it happen.” With no timeline at all.
Feels quite discouraging.
Although I have no way to know this, and it is true I haven't been "waiting" for a firmware update for very long, I don't read this one sentence as an indication of a change in direction, policy or prediction from Alturia from the other statements that an upgrade is in the works and nearly done. (e.g. should be out by beginning of summer). You can tell from the entire email that this person was doing his best to be encouraging and supportive, but without providing specifics, and doing so with English as his non-primary language. Seeing the email from that lens, I took it as simply more of the same. I probably shouldn't have even posted it since it doesn't really add anything to the equation.
This may likely be the last attention that the brute ever receives from Arturia regarding firmware. I'd prefer they take the time they need to make it as right as possible (as long as we're being kept abreast of the development)
This may likely be the last attention that the brute ever receives from Arturia regarding firmware.
So this is what's happening! :o
https://www.captiongenerator.com/1450312/Arturia-Matrixbrute
So this is what's happening! :o
https://www.captiongenerator.com/1450312/Arturia-Matrixbrute
Sadly, we are not able to deliver the update today.
Even though my colleague is doing his best to deliver this right on time, the firmware update is not ready yet.
Still, things are moving forward, and we are committed to deliver a great update.
Unfortunately, to make things right, more time is required.
Hello everyoneThe bugfixes workstrand and the new features workstrand should have been separate. People are happy to wait for additional new features, but they do however have a right for the product to work as described, and if it doesn't, to have its bugs patched quickly. That should have been focussed on as a priority. Years ago.
I can't provide a precise date, as many factors can influence the release date.
(Bugs harder to fix than expected, new features workflow fine tuning, test and beta test)
Basically we should start a first round of beta test pretty soon, to test a part of the new features and bugfixes that are already implemented.
Another round of beta will then be necessary to test the rest and make sure the update is pristine before release.
In case some of you are part of the beta test team, you should receive a mail from Ben soon.
Additionally, in case some of you want to be part of the beta, you can drop me a PM.
Kind regards
Edouard
Hello everyone
I can't provide a precise date, as many factors can influence the release date.
(Bugs harder to fix than expected, new features workflow fine tuning, test and beta test)
Basically we should start a first round of beta test pretty soon, to test a part of the new features and bugfixes that are already implemented.
Another round of beta will then be necessary to test the rest and make sure the update is pristine before release.
In case some of you are part of the beta test team, you should receive a mail from Ben soon.
Additionally, in case some of you want to be part of the beta, you can drop me a PM, Ben is maybe looking for additional/specific profiles and setups.
Kind regards
Edouard
With your number of followers you could actually influence Arturia to follow through with their commitments Kris.
Thanks man!
...Main other issue that annoys me is the Audio Mod Noise-VCO1 knob that sometimes acts weirdly carrying across the centre point if moved quickly from VCF1.That's is a registered bug which will surely be fixed in the update.
...when you go to the left of the detent, then exactly to the detent, then to the left of the detent again ... This can be cancelled by going once to the right of the detent, then to the left of the detent...
Sounds like a combination lock sequence, that will open up some hidden Easter egg feature. ::)
It was more than 2 weeks ago. In the message he said beta would be released to testers the following week. No beta to testers yet as far as I can tell. Is a tester reading this to confirm either way.
Cheers.
Their programmer has just finished the KeyStep firmware update which myself and some other KS users have been waiting of for three years, so I have some confidence that you guys are indeed next in the pecking order.
Edouard has OK'ed letting it be known that the beta has started. It's installed and running on my MxB ;D
There's some rather good content in this update that will make MxB users happy. Sorry no details yet (NDA) ;)
Edouard has OK'ed letting it be known that the beta has started. It's installed and running on my MxB ;D
There's some rather good content in this update that will make MxB users happy. Sorry no details yet (NDA) ;)
I agree matrixbrute update is long past due... but I'd rather it right than rushed.On a large open space which was once a 'green belt' area near where I live, 250 houses have been built along with a nursery and a primary school, and a community has moved in, all in the same time it's taken Arturia to release a firmware update for a synthesizer. One thing it certainly hasn't been is rushed.
Edouard has OK'ed letting it be known that the beta has started. It's installed and running on my MxB ;D
There's some rather good content in this update that will make MxB users happy. Sorry no details yet (NDA) ;)
A NDA for a software update? ???
So first ARTURIA does not discuss the update features here, then they take ages to get things going,
and now they NDA the beta testers?
Can we expect some kind of world wonder then?
Or what could be the reason for a NDA here?
...No they don't. That was my example scenario of what might happen if there was no NDA. As I said, it's a general NDA, pretty much standard in R&D businesses, whether formal or informal. This is a non issue IMO.
but now do NDA with the beta testers because of possible "complaints and outrage".
so why didn't more of you take up the offer
I cant say any more apart from a lot of people will be very happy
Edouard has OK'ed letting it be known that the beta has started. It's installed and running on my MxB ;D
There's some rather good content in this update that will make MxB users happy. Sorry no details yet (NDA) ;)
Well, I am delighted, as we all are, I guess, but I will still not buy Arturia stuff again. There is just too many other companies out there, who are doing this right.
Well, who knows, if this update just blows us all out of the water and comes with some sincere statement by some real person... Hope always dies last.
But nah, Arturia just lost that personal small company feeling entirely for me. In my mind they became just another evil corporation. Am I overreacting? Probably.
But there are so many awesome synthmakers out there who will really seriously take care of me, so I am in the beautiful position to choose a better team 8)
Any word on a release date for this? ???
Any word on a release date for this? ???
Something is telling me you're new around here ;D
Any word on a release date for this? ???
Something is telling me you're new around here ;D
Perhaps I should have said any NEW word on this? :P Been watching this thread for over a year now, and like many others are anxiously awaiting the update. Would have signed up to be a beta tester (in which case I'd already have the update), but I honestly don't have the time to give it the proper attention. In the meantime, it's a bit disconcerting to see lots of cool new product announcements (including a Korg update release on their Prologue synth after just 18 months since its' intro), while we wait, wait, wait for Arturia to finally get around to giving their flagship instrument some love.
I hope the volunteer beta testers are at least getting paid.
I follow Arturia on FB. They put a post up last week promoting MicroLab, their new 25-key midi controller. I saw someone post on it about frustrated MXB owners who have been waiting 2+ years for bugfixes to the firmware on Arturia's flagship product while all they seem bothered about is launching new kit 'every couple of lunar cycles'. Don't know if that was someone actually on this forum but it pretty much nailed the problem.
Yes I know we all have been waiting a long timeThanks for the reassurances Kev! Hoping that a new soundbank will also be released that shows off the new features. Wondering about backwards compatibility with existing patches, too. Questions, questions...
but rest assured the wait will have been worth it
cheers
Kev
Well, I am delighted, as we all are, I guess, but I will still not buy Arturia stuff again. There is just too many other companies out there, who are doing this right.
Well, who knows, if this update just blows us all out of the water and comes with some sincere statement by some real person... Hope always dies last.
But nah, Arturia just lost that personal small company feeling entirely for me. In my mind they became just another evil corporation. Am I overreacting? Probably.
But there are so many awesome synthmakers out there who will really seriously take care of me, so I am in the beautiful position to choose a better team 8)
In part I agree with you.
I still won't be purchasing another Arturia product until Arturia show they can be trusted.
I keep referring to it, but it is important: Frederic said himself 2 years ago on Inside Synthesis' Matrixbrute review that support is now good, and a lot of effort and resources have been put into this domain. Frederic - I'd like to know exactly what constitutes these new efforts and resources, as it certainly isn't reflected in your handling/delivery of this update. If you read your own forums with open, objective eyes, the reality is very different.
Frederic - you also added that Arturia are a company we can trust over time. How much time is needed, and how can we trust you when your own engineers fail to keep their word RE delivery date? You shouldn't make promises you can't keep, as this is the very thing that will destroy trust.
Again - if you said the update delivery was December, I'd have been indifferent. But I'd have expected the update delivery in December.
As it is, you gave a date and failed to meet your own schedule. From a business perspective, this is terrible handling of an already fragile situation - especially given the reputation of your company with respect customer feedback etc was already a sore point (hence your own addressing/mentioning of this issue) - not to mention the flagship update, for many, already being a year or so late.
PS I trust beta testers are being paid for their efforts. Or, at the very worst, being offered software as recompense. You are asking them to provide a skilled service - but not only that: in order to provide this service, they require having purchased a product that costs in the region of $2k - and their understanding of this product. This should be recompensed - not only for the skill of the testers, but for their time/investment. Testers - I trust you have given this some thought, as it could be argued that if there is no recompense aside from the update, you are willingly allowing yourselves to be exploited. The update is Arturia's responsibility - and if they want testers/the provision of a service, this should be recompensed accordingly. Given the process isn't yet complete, testers should genuinely give thought to this. We all want an update - but be very weary of allowing an unfair system to continue to exist when it could be dealt with at this very moment.
I won't be purchasing another Arturia product until Frederic very openly addresses the above issues.
But I will congratulate Arturia when the update is delivered.
Kris
Thanks for the reassurances Kev! Hoping that a new soundbank will also be released that shows off the new features. Wondering about backwards compatibility with existing patches, too. Questions, questions...
Hello everyone.
I'm dropping a little line to give you a little bit of vision on the update release.
The update is feature complete since the early August, with a great bunch of exciting features that definitely improve the MatrixBrute sound design potential, and workflow.
About the bugs, last week we almost had a release candidate, but it appeared that we need to spend a little bit more time on the Sync to make it right.
Once the sync will be OK, I think we will be good for a release candidate after the last few quirks that arose from the beta are resolved.
Kind regards
Edouard
I would be so happy to have more patch memory, not just 256 patches.
I appreciate the update Edouard. Exciting times for Matrixbrute owners!
QuoteThanks for the reassurances Kev! Hoping that a new soundbank will also be released that shows off the new features. Wondering about backwards compatibility with existing patches, too. Questions, questions...
Hello !
I can answer these questions !
Preset compatibility: The new updates adds new parameters in the synth, consequently:
- Import a V1 on a V2 MatrixBrute will automatically convert the V1 preset into a v2.
- You cannot import a v2 preset in a v1 MatrixBrute. (The MCC checks the version)
- Once a V1 preset has been converted into a V2 this preset can no longer be imported in a V1.
/!\ To play it safe, I recommend to backup your MatrixBrute preset bank before to upgrade.
Preset Bank: Victor with the help of other designers prepared a new bank with great simple but very playable presets.
Some of them are making a very smart use of the new features and can definitely be super inspiring :)
Best !
Edouard
Hello everyone.
I'm dropping a little line to give you a little bit of vision on the update release.
Hi Lunatic,
Sync is rock solid here, well about as good as MIDI clock gets. Using old fashioned MIDI cables.
Actually I am quite impressed with the sync already so great if it can be even better.
What happens in you experience? Or am I just less fussy than you?
Thank you Edouard, for some news about the Matrixbrute :) To be honest, I was thinking of selling my Matrixbrute recently, to finance another synth. I will now put that idea on hold, for a while. My biggest concern is about the lack of a sequencer editor, and a song mode for arrangements. The sound however, has never been an issue for me. The Matrixbrute is full of possibilities, and is great for sound design :)QuoteThanks for the reassurances Kev! Hoping that a new soundbank will also be released that shows off the new features. Wondering about backwards compatibility with existing patches, too. Questions, questions...
Hello !
I can answer these questions !
Preset compatibility: The new updates adds new parameters in the synth, consequently:
- Import a V1 on a V2 MatrixBrute will automatically convert the V1 preset into a v2.
- You cannot import a v2 preset in a v1 MatrixBrute. (The MCC checks the version)
- Once a V1 preset has been converted into a V2 this preset can no longer be imported in a V1.
/!\ To play it safe, I recommend to backup your MatrixBrute preset bank before to upgrade.
Preset Bank: Victor with the help of other designers prepared a new bank with great simple but very playable presets.
Some of them are making a very smart use of the new features and can definitely be super inspiring :)
Best !
Edouard
I just reread the thread and I realized, the mediocre sync is indeed not the no. 1 reason not to use the brute, that are the LFO divisions of course! ;DYou may end up with some dust on your fingers after updating, who knows...
It is a shame that people have to beg for a flagship update for years.
And then after years of waiting we do not get any information regarding the updater scope
or release date.
And now the people are still waiting and do not know when the update will be finally released.
I'm am working for an IT company, if we had an update policy like Arturia, then I would be jobless.
It is just ridiculous, Arturia is able to release new Hardware without problems but are not able to
deliver simple bug fixes.
Sorry but I don't want to wait anymore, I will sell all my Arturia gear also the Matrixbrute, and with
the money I get I will support other companies.
And it doe's not matter if the Matrixbrute sounds good, there are enough Synths on the market with similar
or better sound performance.
I don't want to support a company that treats his customers like sh##.
You may end up with some dust on your fingers after updating, who know...
The question is, is the bug you found a showstopper?We have been passing that very same message up the chain via this forum for several years, but unfortunately it has always fallen on deaf ears. It's way better for the customer experience to issue more frequent 'dot' releases which gradually and methodically improve the product, even if some of those releases are bug fixes to address bugs accidentally introduced previously. Instead Arturia opt for a big bang approach, whose release date has slipped more times than an octopus on rollerskates.
I think it is better to have sprint based releases than trying to make the software 100% bug free and never releasing.
We have been passing that very same message up the chain via this forum for several years, but unfortunately it has always fallen on deaf ears. It's way better for the customer experience to issue more frequent 'dot' releases which gradually and methodically improve their experience, even if some of those releases are bug fixes to address bugs accidentally introduced previously. Instead Arturia opt for a big bang approach, whose release date has slipped more times than an octopus on rollerskates.
But to be honest, theres something wrong with Arturias Management, because as I can
see they don't care.
(Edit just for clarity, I intend no personal criticism of Edouard: it's seems pretty obvious to me, probably to all of us, that the problems endemic in the company are not at his level)
By the way, Edouardo, I hope you don't feel personally stressed too much by all the frustration here, as it is not your fault whats happening, if I understand you correctly... So lets bring this thing to perfection as far as possible and then maybe find a new company all of us :P
I'm just teasing, thanks for being the only one available here.
Right now we have the beta 6 firmware being tested internally and to be sent in beta test tomorrow.
We were supposed to release this week, but Florian and myself found some new bugs on Monday :-\
There will be an official announcement.
At this moment, all the features will be revealed, along with a new updated manual, tutorials, and more :)
The reason a manual is really good for people like me is that I use my MatrixBrute maybe once a week, or sometimes not for two weeks (I have a very demanding job right now). I sit down and sometimes can't remember all the things I learned last time I used it. A good manual can help me get right back to what I knew last time.
Hi we are on beta 7 at the moment
just a few more bugs to iron out
its looking good, but due to NDA
I cant say any more
cheers
kev
Hi we are on beta 7 at the moment
just a few more bugs to iron out
its looking good, but due to NDA
I cant say any more
cheers
kev
Seems like we're getting to the home stretch! Who would have thought early spring would have lasted all the way to Thanksgiving ;)
Here is an incomplete list of some of the new functions.
Flaws: Sure, nothing is flawless. Even though at least triplet LFO divisions could be kinda called a bare minimum in digital LFOs for a monosynth...
Bugs? Not cool. Tight sync: A necessity.
And your Minimoog doesn´t have settings, that you will not be able to access anymore, when Windows 13 is released.
Edouard has just posted on GS that firmware 2.0 will be released this week!!!
I hope that 'more user-defined mod destinations' made it in the upgrade...always my #1 feature request. Anyways, exciting times!
Edouard has just posted on GS that firmware 2.0 will be released this week!!!Why not announce it here?
I hope that 'more user-defined mod destinations' made it in the upgrade...always my #1 feature request. Anyways, exciting times!
I will be saving my current Program bank to MCC in preparation for the FW update for sure.-Will the upgrade overwrite the current bank with the new bank Victor designed?
Question:
...
Once again, thank you everyone for your patience, and now lets play, sound design, perform, drink a beer or maybe we can do both at the same time !!!
...
Seems wonderful, addresses most requests..
funny, but not one of my requests was realized i think
see here:
https://forum.arturia.com/index.php?topic=90177.0
maybe punishment, because i started this thread;)
i have to check again, but a few years for this thin update seems rather weird to me
- LFO SLEW & SYMMETRY a double use of the LFO knobs should be an easy thing to do (?)With the custom LFOs you can program your own waveforms, with per step slew, for micro and macro slewing. It handles symmetry too, although that was always doable with the normal LFOs too - just add in a constant using a macro knob. The macro knob can of course be modulated too, which gives you modulation of the symmetry.
SLEW = soften the LFO curves ( sounds often more musical)
and SYMMETRY means you can shift the curves gradually from symmetric positive and negative values to only positive or negative values
(example: cutoff only gets opened from but not more closed from start value)
- with the AUDIO MOD knobs, allow modulation from ZERO in the matrix. Now only possible, if start value is NOT zero.This was always possible by turning the knob slightly in the direction of the modulating function you want (it's in the manual and explained mor then one time here and on GS). The 2.0 update makes it a tad easier by defaulting the right hand side of the knobs as the default modulating function.
together with unipolar LFOs (see request for LFO SLEW & SYMMETRY) this would make a lot of sense
- very helpful wold be attack / release setting (in the MCC) for the aftertouch,Well, there is a sensitivity setting there which helps. For an attack (as from the notes attack) this can be done using the mod matrix and an envelope. Not what you requested though, which BTW would be nice i itself, but oh, where in the UI would it go...
for softer fade in/out insead of sudden on/off
- track rotation = shifting tracks stepwise left / rightTrack rotation is in the update. Well, not separately for the MOD, Glide, Accent and Note lanes with separate lengths, which sounds like feature bloat to me (hard to find a workable space for all that in the UI).
you come up with a nice pattern, but then you want to start it at another step ? for this you need this feature
best case would be to to be able to shift NOTE, ARP and MOD tracks independently and if they could have different length.
(an "offset" for the different MOD track destinations might be over the top, but would allow even more rhythmical variation)
- more MOD sources ( would mean: more pages)It's in the update.
so you could for example sequence the OSCs independently. very good feature for interesting patterns
- possibility to modify all ENV stages independentelyLin/Log is doable with the added mod user assignable matrix columns and envelope feedback (could do 4 segments previously, limited by the 4 assignable columns).
(lin/log, duration 2x, 5x, 10x, etc)
I posted a bug in the tech support forum.... but then thought maybe I should ask here, in case it's just some problem on my end. The new Duo/Split Glide in 2.0 does not function correctly with the Sequencer or Matrix Arpeggiator. It was limited before, but now it doesn't do anything that it's meant to. Slide steps in the sequencer try to Glide the upper part instead of lower, for example... causing some really odd behavior. Anyone else getting this problem?I think I am seeing the same thing. However, if I turn off the Sequencer, than I can set Glide ok.
In my book, this is the very opposite of a "thin update". How about "glass half empty" if nothing else, or even a stretch to "glass half full" ? For most others I think the glass is overflowing :D
.
...From the user manual:
And lastly, dear Dr Justice, could you elaborate, what you mean by this statement of yours, answering to VAU: "This was always possible by turning the knob slightly in the direction of the modulating function you want (it's in the manual and explained mor then one time here and on GS). The 2.0 update makes it a tad easier by defaulting the right hand side of the knobs as the default modulating function."
Just the last part, as in, I would like to know, what changed.
Love you all!
Just one concern: There is no word about any Bugfixes, or am I missing that? I will be playing a really big concert with the MB next weekend and I am too scared to update right before that, so I can't check right now. But have the bugs been solved? The FM knob quirk, tap tempo in Sequencer mode, LFO retrigs?
Bugfixes
MIDI, USB and Clock Sync are now tight
Sequencer now starts on time at any tempo
LFOs are now stable when tempo-synced
Clock out is no longer reseted to 48 ppq when USB slaved
All parameters are now properly initialized when loading a preset
Various Duo-Split mode fixes (Glide, Sequencer, Legato)
Seq Mod steps can now be properly edited
Save in Panel mode is now consistent
VC01 < Noise > VCF1 knob behavior now targets the right destination
Switching Key Hold OFF doesn't silence the currently played notes
When playing with record On, Tap Tempo doensn't modify the seq length anymore
No more risk to be stuck between Preset and Panel mode
No more note OFF when note velocity value is 0
OSC3 waveform browsing is no longer inverted
CC handling improvements : Parameters are now properly sent and received
Preset, SEQ and Mod buttons are now properly responding when the sequencer is playing
Compare parameter offset no longer displays the preset page upon release
In Duo-Split lower and upper MIDI channel can now be properly adjusted
...Of course :)
I hopw you can accept, that we have different opinions here.
now, we have more structure in the whole company, more QA processes and we are able to leave more room in plannings to update our products to keep them alive and make the community happy
Hello !To be fair you can tune in a triplet by ear when the BBD is not in sync mode. But one thing that sounds absolutely mad is modulating the BBD divisions with a synced random LFO. Shame that you cant get that extra funk with the in-between odd divisions.
I wanted to implement the triplets / dotted for the delay as well, but the BBD was too limiting unfortunately.
BBD max time is very short, so in triplet / dotted, only a very few would have be available.
On the other hand, we weren't limited by the technology when implementing new time divisions on the LFOs.
Analog is great but sometimes pretty frustrating as well :)
Edouard
i really would love to know one thing:Reading between the lines I guess it's a hardware issue: there literally isn't the onboard storage space.
WHY is not possible to have more than 256 patch spaces (ideally 256x256)?
i really would love to know one thing:Reading between the lines I guess it's a hardware issue: there literally isn't the onboard storage space.
WHY is not possible to have more than 256 patch spaces (ideally 256x256)?
All I ever expected for free were bug fixes. I believe consumers do have a right to expect tech products to work as described, just like they would expect a toaster to do what it says on the box. When bugs are identified preventing the product from working as described, I also believe consumers have a right to expect the bugs to be quickly remedied with periodic dot patches, not three years down the line as part of a major release. That is my only criticism.
The fact that a lot of new functions have been thrown into this release is a huge bonus considering neither you, I, nor any other existing customer has paid a cent for the update. We should be thankful for the additional freebies, not whine about the fact that the toaster we knew only toasted four slices at once when we bought it hasn't been freely upgraded to toast 16 slices or more.
i really would love to know one thing:Reading between the lines I guess it's a hardware issue: there literally isn't the onboard storage space.
WHY is not possible to have more than 256 patch spaces (ideally 256x256)?
All I ever expected for free were bug fixes. I believe consumers do have a right to expect tech products to work as described, just like they would expect a toaster to do what it says on the box. When bugs are identified preventing the product from working as described, I also believe consumers have a right to expect the bugs to be quickly remedied with periodic dot patches, not three years down the line as part of a major release. That is my only criticism.
The fact that a lot of new functions have been thrown into this release is a huge bonus considering neither you, I, nor any other existing customer has paid a cent for the update. We should be thankful for the additional freebies, not whine about the fact that the toaster we knew only toasted four slices at once when we bought it hasn't been freely upgraded to toast 16 slices or more.
I don't think it's "whining" or entitlement to expect from an - advertised as avant garde - analog flagship in 2019 not to have to use the computer to store and organize all your patches. And if it is a hardware issue, then there should be ways to fix this with an hardware upgrade. At least that's what Rudi Linhard /LINTRONICS told me when i visited him 1,5 years ago.
LINTRONICS told me they would do the mod if ARTURIA would provide them the necessary infos.I think we can guess with some certainty that Arturia won't be doing anything like that with their premium-priced product which is still in production, no more than they will allow third parties to officially hack around with its firmware. But unofficially, any product with user-flashable firmware (such as most Arturia products, including the MxB) can be 'jailbroken' by someone with the required software skills, and thus jailbroken, can be made to do literally anything within the constraints of its hardware. You would of course in the process kiss your warranty's a** goodbye.
Hello.
We are currently testing an hot fix to resolve a few quirks induced by the 2.0 update, and add sleep/screensaver mode to increase the digital displays longevity.
About a 3.0, we already discussed this topic and though it would be cool to do it, so it is not excluded.
Kind regards
Edouard
-Midi sync bug (as described above)
-Anything else?
PLEASE, PLEASE, PLEASE enable us to sync to Midi clock the way it used to, without having to put sequencer start and stop commands into the midi stream.
I'm still a proponent for a Matrixbrute voice expander.
-problem with the Compare function (aka the "A4" bug, i.e. the Compare function seems to use Program A4 as a temporary buffer, and therefore wipes out whatever program was stored there)
-Glide function bug in Duo Split mode (glide is available on upper part as well as lower, BUT not independent)
-Midi sync bug (as described above)
Quote from: yeskeys on January 24, 2020, 01:11:12 am
PLEASE, PLEASE, PLEASE enable us to sync to Midi clock the way it used to, without having to put sequencer start and stop commands into the midi stream.
This +1000
Just bit me last night.
Would be happy to beta test!
Posted by: yeskeys
« on: January 25, 2020, 04:23:54 am »INSERT QUOTE
Quote from: aWc on January 24, 2020, 06:19:08 pm
-Midi sync bug (as described above)
-Anything else?
Yes. May I beta test??
I we don't get some action soon, I will be starting up a marketing campaign that spreads this message one synth nerd at a time - for a long time.While I feel your pain, I can't think of a time when threatening a company has succeeded in encouraging them to willingly give you a better service. Piece of advice: if your food doesn't arrive promptly in a restaurant and that really upsets you, it's probably best you just take it on the chin and don't visit the restaurant again. Because if you make the waiter's life a misery, you may well get served quicker, but it's likely he spat in your soup.
If they release a new version of the Matrixbrute before finishing the buggy first version, Arturia can fuck right off.
Is it an integrated Touché device on the left ? :o
... Hopefully by then I will have this nightmare piece of partially working near junk out of my life by then.
I firmly believe it's going to take some public shaming to get any movement, kind of like the uproar the Tempest took, what with a change.org petition or whatever happened back then. We need a headline Sythtopia article and other media outlets, like Sound on Sound, Matrixsynth, etc. etc.
Also, IMO it's a bit strong to call for fucking offs and claim utter disrespect before the potential deed is done ;)I'm not saying the Matrixbrute is useless, I enjoy it immensely. OS2.0 added a lot of functionality and fixed the sync timing issues. It also created new issues, and missed a few others. It felt like we were being listened to, albeit late, when the ver2 OS was released. Then, once again, no communication and no promised hotfix for MONTHS.
Hello everyone.
Sorry for the recent absence.
Indeed the COVID situation is not helping here.
The whole company is being reorganized to be operational even though we cannot access the headquarters, and so far all team are not fully operational because of the isolation, which implies a lot of logistic and human challenges.
We are almost done, that's why I asked if some of you were interested to join the beta.
However, the recent events were not planned, and of course, we'd rather not start a beta with two known critical bugs.
These bugs needs to be addressed first, and we are looking forward to do.
But in the current situation it is just very complicated.
Be sure that I'm looking for solutions and that I haven't forgot you guys.
My work won't be accomplished until it is out, so I'm definitely eager to get this straight.
Thank you for you understanding, and sorry again for the waiting time.
I will try to keep you posted.
Kind regards
Edouard
...THe MB would work so seamlessly in my rig if they'd just fix this goddamn midi sync. I've never seen much less owned anything that operates backwards like this. And I've been dealing with midi and music technology since DSK sync....Just think if this was open source and you could program any modules the hardware could accomodate how great it would be. PLEASE do down in history and put this into some capable hands, teams of creative euro-type guys who could fulfill so many wishes. ...
I always wondered what will happen if a beta release somehow bricks the controller. Is there a failsafe to ensure some sort of connectivity is guaranteed to be able to flash another firmware?
From all the cases I've seen, eventhe fiercest units bent the knee at some point and got updated :)
Posted by: SingleCell
« on: April 11, 2020, 09:01:41 am »
@Edouard_Arturia: When you say "We started a beta...", does that mean it went out to outside testers? ... I was hoping for an email. :/
That's a good thing to hear!
I may be a little bit late, but if it's still possible I'd like to help testing the beta. Thanks!
Are you part of the Matrix beta?
.... the new firmware Does NOT solve the midi/start command issue for the Arpeggiator and the sequencer.. ...If you don’t understand how bad this, just ask any live performer.
This could be the Matrixbrute*sad MxB noises*
This could be the Matrixbrute*sad MxB noises*
I remember to have read something about an VST from Arturia for the MxB is planned, but no statement about the timeline. Maybe with the firmware version 3.0 comes a full sysex implementation that will be fully documented.
Hello.
We should be able to release the Start / Stop fix before mid-june.
Best
Edouard
Hey.
The fix is out !
Cheers
Edouard
Hey.
The fix is out !
Cheers
Edouard
I just got the update installed, and all looks like things are working as expected.
It has been one hell of a journey over the last years trying to get Arturia to pay attention to the Matrixbrute. Thankfully, it would seem we finally have an instrument which functions as it was intended to when released.
I appreciate you coming through Arturia. That being said, this will definitely be the last time I spend money on your products. The Matrixbrute is a beautiful synthesizer. The respect and reverence it deserves from you as an instrument and tool stopped with the marketing budget allocated. I felt pretty disrespected as a purchaser of your equipment watching you release new products and firmware updates to equipment newer than the Matrixbrute for years, while the Matrixbrute sat with intolerable faults that could easily be repaired with an ounce of attention given.
So, thank you for the Matrixbrute and goodbye!