Chewie5150
Fractal Fanatic
beers on me! thanks voes.
Hey guys, recently upgraded my FCB with an uno chip and I've been having some issues. First of all: I went through all of the steps in voes' guide to extend the memory and put it in stompbox mode. I then dumped the sample axe fx sysex file. I then went through the axe's I/O>CTRL menu and changed all the values.
My problem is this: although the top row of pedals now behave like stompboxes, they are not actually turning any effects on or off...I'm wondering what I may have missed here.
The second problem: after upgrading, it doesn't seem as though I'm able to connect to axe-edit anymore. I keep getting "hardware busy" even though I'm using the same connection as before.
My setup is:
Behringer out > Axe fx in
Axe fx out > Midisport 2x2 in
Midisport 2x2 out > Behringer in
Any help or feedback you can give would be much appreciated.
I believe that you can't use Axe-Edit and the FCB at the same time unless you get a MIDI Merge box.
So how would you hook up the 3 devices: FBC - Axe - MIDI Interface?
Yes he will."Behringer out > Axe fx in
Axe fx out > Midisport 2x2 in
Midisport 2x2 out > Behringer in"
In this hookup the MIDI data that the Behringer is transmitting will be terminated at the Axe-FX and will not make it into the MIDISport's MIDI In.
This *will* allow him to use the FCB to trigger the Axe while using Axe-Edit to edit the Axe, but he *won't* be able to use any FCB editing software at the same time.
That would explain stuff. Is the midi led on the Axe-FX showing when you edit with Axe-EDit? I'm surprised you are getting leds on the in, though. Anyway, are you sure all the ports are connected correctly in the prgrams? Also Midi-cables have been known to fail unexpectedly. Sometimes more than one at the same time... Hardware busy just means it doesn't receive the answer to the question it asks. "knock knock?" "..."Well yeah, it was working prior to the upgrade. Which is why I'm so stumped that I'm getting "Hardware Busy (?)" messages now.
Looking at the Midisport 2x2, it looks as though there is a problem with the output signal. The "in" light is flashing, but nothing on the "out" light.
So if you have Ripwerx ask the FCB to send a system dump back to the PC it will not receive it.
Hi guys literally just got fcb, havent hooked anything up, windows vista 64bit, does the fcb1010 pc editor NOT work with this setup? i installed, click on the icon, installed update but just get mcv60dll missing file, please install again blahblah?
I can do patch dumps from the FCB to Ripwerx with AxeEdit running while controlling the AxeFX via editor and foot controller and whatever else you can want to do with these things.That's the drawback that I meant to describe.
I.e. With this hookup there is no way for the FCB to send data to the PC, but the PC can send data to the FCB.
Sorry I wasn't clear enough.
Thanks for clearing it up.
I also have to say that from my experiences trying to work this way at one time, I found that it wasn't worth it because too many unexpected things tended to happen.
Of course that was with earlier versions of Axe-Edit.
It might be better to work this nowadays.
Is the latest JAVA version correctly installed ?