Have you seen their normal wireless MIDIbeam device?
Nope, thanks for the heads up!
[Oh wait, I have seen that; yeah, it would be nice to have something Bluetooth that my iPad etc could talk to directly]
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
Have you seen their normal wireless MIDIbeam device?
I also had problems updating firmware via the MC8 (though I never tried it within the editor). In any case, barring any bugs, that is the last ever firmware update that the FI will get.Just wanted to share my experience updating the FI to the newest version with my Mac (Catalina). I did have some problems doing so through the chrome browser. I was using my Morningstar Mc6 MKII as my midi interface, set it up correctly in the Audio/midi utility on the mac, and also had the Firmware update page in chrome set to allow midi communication.
I went through the firmware process via chrome, midi interface recognized, FI flashing fast ready for the update, but when I clicked update, it would just hang there for a long time, several minutes, and never updated. I tried this several times through Chrome with the same result. Just a never ending flashing of update with never completing the process.
I decided to try the firmware update through the editor. Set up my midi interface in the preferences, put my FI in firmware update mode, clicked firmware update in the editor, and it worked like a charm.
By the time I was all done I was tired and never got to really try it out. It was past my bedtime haha. Just figure I'd share my experience. If the browser doesn't work or just stalls, perhaps try updating through the editor.
Great job on the updated manual @Quatschmacher !!
Did you update from pre-v3 to v3.60? If so, my guess is that you didn’t write the v3.50 factory bank to the pedal immediately after the firmware update. This is an essential step to flush out any old v2 data. Not doing so can cause exactly the sort of problems you describe.Wow. Devastated here. Updated FI, no problems. Updated editor no issues. Love the manager. I spent several days getting all the sounds that I wanted to use. Everything went as planned until I did my final upload from manager to FI. When I went to try out the pedal on my board all the synth sounds were gone. all I get is some straight bass sounds or bass and effects. The rest are blank. I re-updated and tried to reload default sounds only to have the same issue. I looked inside and nothing seems out of place or burnt so I'm at a loss as to what happened.
That’s nothing I’ve ever encountered.No. I did it right the first time. I was able to work with it, without any issues for several days. Today when I added a few sounds from v1 that I liked I saved them into the manager then uploaded into the FI that's when everything disappeared. I did do another update as you suggested carefully following the directions but the result is the same. All my files are backed up but it's just not accepting anything. Not even the default v3.60 sound updates.
Honestly, that sounds like what I was describing where the v2 patches haven’t been flushed correctly.Windows 10 using chrome
Steinberg UR22
Yes, midi in and out connected correctly.
The weird things is I'm able to scroll thru the patches on the editor and they read correctly. But All I get is the guitar/ effects portion of the patch no synths what so ever. And any patches with pure synths are blank.
You’re welcome. Glad it was an easy fix. You shouldn’t have any more trouble if you wrote the whole sound set. (It needs to be done as the file structures of v3 differ slightly so some parameters have moved position in the code, which is why you get weird behaviour of old files are still present in the memory. Once flushed, it’ll be fine.)Thanks Quatschmacher. That 3rd reboot seems to have brought it back to life. I'll try reloading some of your patches that I enjoy as well as a few off v1 sound set again. Thank you for your help and expertise.
Are you using a Beta release on the MC6 and Chrome? I was using an older beta release and had a similar issue. I had to update my firmware to the most recent MC6 beta firmware and make a couple updates in the editor to get the issue to stop. Sorry I can’t be more detailed, I ran through a slew of attempts to get it to work and didn’t note my steps. Hope in some way this helps.Not sure if this is an FI bug or a MC6 bug or a me bug. I have been trying to get my MC6 up to scroll programs and its just not working.
Even using the Midi Dictionary on the MC6 doesnt seem to help.
CC 88 value 64 - 127 - after I press the footswitch on the MC6 it scrolls up AND keeps scrolling. There is nothing I can do to stop it from scrolling. I have to shut the power off. With a value of 63 or less nothing happens.
I can toggle the FI on and off no problem and I can send PC messages to get to specific programs / presets but I cant get the scroll up or down to work like it should. Im sure someone else is doing this without issue and Im missing something. I havent even tried scrolling banks yet. To frustrated.
It’s normal. You need to set a release message on the same button to a value of 0 for the same CC to stop the scrolling.Not sure if this is an FI bug or a MC6 bug or a me bug. I have been trying to get my MC6 up to scroll programs and its just not working.
Even using the Midi Dictionary on the MC6 doesnt seem to help.
CC 88 value 64 - 127 - after I press the footswitch on the MC6 it scrolls up AND keeps scrolling. There is nothing I can do to stop it from scrolling. I have to shut the power off. With a value of 63 or less nothing happens.
I can toggle the FI on and off no problem and I can send PC messages to get to specific programs / presets but I cant get the scroll up or down to work like it should. Im sure someone else is doing this without issue and Im missing something. I havent even tried scrolling banks yet. To frustrated.
Listen to @QuatschmacherNot sure if this is an FI bug or a MC6 bug or a me bug. I have been trying to get my MC6 up to scroll programs and its just not working.
Even using the Midi Dictionary on the MC6 doesnt seem to help.
CC 88 value 64 - 127 - after I press the footswitch on the MC6 it scrolls up AND keeps scrolling. There is nothing I can do to stop it from scrolling. I have to shut the power off. With a value of 63 or less nothing happens.
I can toggle the FI on and off no problem and I can send PC messages to get to specific programs / presets but I cant get the scroll up or down to work like it should. Im sure someone else is doing this without issue and Im missing something. I havent even tried scrolling banks yet. To frustrated.
Very cool. Do you have to reset the counter at each startup on the MC6 (and FI I guess too)?Actually got it working with the PC Scroll and I have a counter. Works great . Have Up And Down.
View attachment 4394788