Firmware Update

[turbo_kev]

Hi Terry

yep tried that and still no joy

but at least I now know that changing a patch also changes the midi channel

BTW  I notice when I change the mdi channel on mini v  it puts a little star next to the patch name ?

and I am right in thinking that you have to stop using mini v to be able to use MCC
and that you can only use 1 synth at a time in stand alone mode.  this is a right pain in the backside
I was having a read up  and found out you need a special driver of some sort to share the midi data ?

I shouldn't moan coz everything works just great in Cubase
but sometimes you just get the urge to load up a couple of stand alone synths and play

BUt defo  I cant change the midi channel  and cant use more than 1 synth or MCC without turning one of them of first

cheers
kev

[turbo_kev]

Terry

I just tried analog lab  stand alone and that works fine.  so I tried a couple of other synths from the v collection
and so far the only one that don't work is mini v   perhaps its a bug, I will try the rest in the collection and report back

cheers
kev

[elastic]

This may sound stupid - but how on do you update the firmware?

i am on a mac.

thanks

[Dav1d]

I think this should be relevant
==> http://arturia.com/evolution/kb/?View=entry&EntryID=196

[elastic]

thanks david, done it now. thanks for your help

[alandiaco]

I just updated my firmware and now Ableton Live won't detect it, it seems. I can see the BeatStep on the MIDI tab on Preferences, but it won't show up in the dropdown for midi inputs on the tracks. Did something change regarding configuration using DAWs?


EDIT: Ok, now it seems Live will only detect it if I don't have MIDI Control Center opened... But if I don't open the MCC before opening Live, I can't sync. Is it normal that you can't open both at the same time?

[teceem]

Is it normal that you can't open both at the same time?

In Windows it is normal, yes. (OSX: no idea)

But it shouldn't! Arturia should make a multi-client driver! 

[elastic]

Can anyone tell me how to sequence the filter cutoff of a plugin synth please?

Is it possible to sequence the filter cutoff AND the synth notes at the same time?

[teceem]

Can anyone tell me how to sequence the filter cutoff of a plugin synth please?

Is it possible to sequence the filter cutoff AND the synth notes at the same time?

Easy in FL Studio: https://www.image-line.com/support/FLHelp/html/plugins/Fruity%20Keyboard%20Controller.htm
I have no idea how to do it in your DAW, since you don't mention which one you're using. And maybe you should make a topic about it - because it has nothing to do with a firmware update. 

[elastic]

I have made a topic about it. But nobody replies.

I'm using ableton

[teceem]

Search/read the Ableton manual...
or
Try this:
http://www.thepiz.org/plugins/?p=pizmidi
midiNotesToCC
Windows VST: http://www.thepiz.org/pizmidi/pizmidi.zip
Windows x64 VST: http://www.thepiz.org/pizmidi/pizmidi_x64.zip
Mac OS X VST: http://www.thepiz.org/pizmidi/pizmidi.dmg

[foehnjerome]

I need to update my Arturia Beatstep but I am running Mac 10.6? How I can update to the latest version? is there any Midi Control center running on 10.6?

[teceem]

I need to update my Arturia Beatstep but I am running Mac 10.6? How I can update to the latest version? is there any Midi Control center running on 10.6?

Did you try installing the latest Midi Control Center?
If it doesn't work, it's because of this:
http://www.arturia.com/evolution/en/products/BeatStep/specs.html

PLATFORM SPECIFICATIONS:
Windows: Seven / Eight
Mac OS X: 10.7 or higher

[pironio]

I've plug in my Beatstep to my late 2013 macbook pro and Audio Midi Setup Does not recognize it. But when I plug it into my old macbook pro 2010 it comes up just fine and I am able to use MCC 1.1.0 and updated my Beatstep. But when I go back to my new mac I get the same problem. 

So my guess is ether Mac or Arturia has a problem with the other when using usb 3.0

*Update after I restarted my computer everything seems to work perfect.

[Funtmaster]

I have fixed it (for me at least).

I was mystified as to why the MCC stated no Firmware version at all. So after trying all the suggestions in this thread, I downloaded the previous Firmware version and installed that successfully and then upgraded to the latest version. In my case, it seems it needed an earlier version installed first and recognised BEFORE it could do the upgrade. Makes some kind of sense to me.......

I hope it works for others.