March 28, 2024, 02:11:09 pm
Welcome, Guest. Please login or register
News:

Arturia Forums



Author Topic: Polybrute reverting to firmware 0.2.0 and failing to switch on - FIXED  (Read 2259 times)

drfireball

  • Apprentice
  • Apprentice
  • *
  • Posts: 22
  • Karma: 2
Today my PB failed to switch on - only the Poly light lit up in the polyphony section. Fortunately this was solved by posting to a Facebook group where Jamie Morden (Geosynths) had also had this problem. Solution was to start Polybrute Connect which recognised the synth as having reverted to OS as above. It installed the new firmware and the synth restarted correctly.

DrF

SWilliam

  • Apprentice
  • *
  • Posts: 11
  • Karma: 0
Thank you soooo much for sharing this!  I thought my Polybrute was toast and just got off the phone with my local dealer to have it brought in for warranty on Monday.  I'm so relieved!!  Just updated the firmware now and it's back up and running!

mcresp

  • Apprentice
  • *
  • Posts: 12
  • Karma: 0
This has happened to me twice now !
Bit Pissed .... if this was to happen at a gig  >:(

michaeldancurtis

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
First Thankyou to the Original Poster,  I don't know if you all just got lucky or if I am below average intelligence but it took me a while to get this to work...

I will put the step by steps for others because this is SUPER usefull to know.

Bad firmware Steps to fix:

1) Close PolyBrute Connect
2) Turn off PolyBrute
3) Unplug USB
4) Turn on Polybrute - DO THIS BEFORE STARTING PolyBrute Connect
5) wait 30 seconds
6) Plug in polybrute
7) Open Polybrute Connect

If you don't see some red lettering that tells you to update firmware.... start the process over.



TheAndyMac

  • Apprentice
  • Apprentice
  • *
  • Posts: 29
  • Karma: 2
Just had the same issue today and was about to request to get it swapped for replacement (not even 3 weeks old).

A bit concerning that this is happening (to some users) so we really need Arturia to tell us:
(1) is there an underlying hardware fault in those units where it happens (seems to be a smallish number) so they probably will need replacing under warranty?
(2) or is this a firmware issue that will be addressed - and hopefully very soon?

mantrak

  • Apprentice
  • Apprentice
  • *
  • Posts: 38
  • Karma: 1
Not fixed, see other post with similar title.

 

Carbonate design by Bloc
SMF 2.0.17 | SMF © 2019, Simple Machines