• 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 freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Future Impact now available!! WAS: deep impact reissue!!! interested?

Ah! Brilliant. :/ Can't believe I missed that in the drop down menu..


Focusrite Scarlett 2i4

From the manual:

Focusrite Scarlett 2i4 Does not work for firmware updates or writing all 99 sounds at once. Works for everything else but with intermittent errors.

I'm guessing this is where you're having trouble.
 
  • Like
Reactions: Quatschmacher
Ah! Brilliant. :/ Can't believe I missed that in the drop down menu..


Focusrite Scarlett 2i4
As I’ve been saying. It’s worth reading the manual. The 2i4 does not work well at all and this is clearly mentioned in the list of compatible interfaces in the appendix of the manual. I have a 2i4 myself and used it during the beta testing - it’s really temperamental. I use my Roland UM-One MK2 instead and have no problems. I’d suggest you get one.
 
As I’ve been saying. It’s worth reading the manual. The 2i4 does not work well at all and this is clearly mentioned in the list of compatible interfaces in the appendix of the manual. I have a 2i4 myself and used it during the beta testing - it’s really temperamental. I use my Roland UM-One MK2 instead and have no problems. I’d suggest you get one.

This is the one I have too. At the time I bought it, it seemed the cheapest that also had a good track record.
 
As I’ve been saying. It’s worth reading the manual.
Baaaa. Well color me sheepish! I'm usually the first to say "read the manual" and this time I did not read it myself. My bad.
Bummer too, I previously used a Roland UM-3G when I first got the FI, but then bought the 2i4 specifically because it has MIDI I/O. Again unfortunately, Roland stopped releasing updated drivers for the UM-3G, so looks like the UM-One mk2 might be solution there.

Curious now, as I never ever previously (FI V2 and earlier) had problems with the 2i4, are you saying that it is the new firmware/software that is now causing the 2i4 to be problematic?

All interface issues and solutions aside, I am more concerned about the future compatibility with the Editor and Mac OS's. Acknowledging the fact that PandaAudio is a small company and many of us are aware the years it took for V3 to be released, I am not expecting a resolution before 2020. But it would be VERY comforting to hear an official acknowledgment of the OS Catalina incompatibility and a plan or time-line for an update resolving the issue.
 
Baaaa. Well color me sheepish! I'm usually the first to say "read the manual" and this time I did not read it myself. My bad.
Bummer too, I previously used a Roland UM-3G when I first got the FI, but then bought the 2i4 specifically because it has MIDI I/O. Again unfortunately, Roland stopped releasing updated drivers for the UM-3G, so looks like the UM-One mk2 might be solution there.

Curious now, as I never ever previously (FI V2 and earlier) had problems with the 2i4, are you saying that it is the new firmware/software that is now causing the 2i4 to be problematic?

All interface issues and solutions aside, I am more concerned about the future compatibility with the Editor and Mac OS's. Acknowledging the fact that PandaAudio is a small company and many of us are aware the years it took for V3 to be released, I am not expecting a resolution before 2020. But it would be VERY comforting to hear an official acknowledgment of the OS Catalina incompatibility and a plan or time-line for an update resolving the issue.

Panda are aware of the issues people are having with Catalina; I emailed about it. A fix will happen. I can’t give you a timeline as it’s not my remit.

I too got the 2i4 due to the midi. I’m glad I hadn’t sold my UM-One! Not sure if the Focusrite worked with v2 as I bought it partway through beta-testing v3.
 
  • Like
Reactions: JimboP and mr2xbass
Interesting. Yeah, I used my 2i4 for the update and to batch write all 99 new sounds.

I never had a problem with the MIDI I/O on the 2i4 with FI V2 or any MIDI-able device I use (Pigtronix Infinity, Akai samplers/drum machines, Korg KP3+, Roland synths). I do not know enough about software writing to understand why or how the 2i4 interface would previously work flawlessly but now be glitchy with new FI firmware/software, as nothing changed in the 2i4. Maybe this is also a bug to be fixed in future updates? To lose compatibility with a previous compatible device seems like an oversight. But what do I know; I'm a musician, not a software developer.

Also, Quatschmacher, thank you so much for fielding all these to-be-expected issues that happen with any major update! You should be on the PA payroll if you are not already. ;)
 
  • Like
Reactions: Quatschmacher
Interesting. Yeah, I used my 2i4 for the update and to batch write all 99 new sounds.

I never had a problem with the MIDI I/O on the 2i4 with FI V2 or any MIDI-able device I use (Pigtronix Infinity, Akai samplers/drum machines, Korg KP3+, Roland synths). I do not know enough about software writing to understand why or how the 2i4 interface would previously work flawlessly but now be glitchy with new FI firmware/software, as nothing changed in the 2i4. Maybe this is also a bug to be fixed in future updates? To lose compatibility with a previous compatible device seems like an oversight. But what do I know; I'm a musician, not a software developer.

Also, Quatschmacher, thank you so much for fielding all these to-be-expected issues that happen with any major update! You should be on the PA payroll if you are not already. ;)
The fault lies with the interface rather than the FI. There’s a note about this in the manual under the Firmware Update section. It’s to do with it not coping with large amounts of data.

You’re welcome about the help.

I would encourage everyone to read the manual as it does cover lots of the stuff being asked on here - I included an FAQ section (which I may expand in any future version) which covers a reasonable amount of stuff too.
 
The fault lies with the interface rather than the FI. There’s a note about this in the manual under the Firmware Update section. It’s to do with it not coping with large amounts of data.

You’re welcome about the help.

I would encourage everyone to read the manual as it does cover lots of the stuff being asked on here - I included an FAQ section (which I may expand in any future version) which covers a reasonable amount of stuff too.

It also came up earlier in this thread with someone who was having trouble bulk/batching out patches. That's why I thought to ask.
 
  • Like
Reactions: Quatschmacher
It's finally here, V3 update and new housing! WOOHOO, it's gold Jerry, GOLD!
IMG_20191030_181429.jpg
 
Does anyone else seem to have problems with the Roland UM-One? Here's what happens for me. When I used the browser updater, it wouldn't recognize it at the "select the MIDI inputs and outputs" stage. What (I think?) worked was to open up the FI editor, go to preferences, the UM-One was already selected. I turned both input and output to "off," hit "apply," then opened the preferences up again to select the UM-One again. Then the browser updater recognized it.

Does anyone else have this experience?
 
Does anyone else seem to have problems with the Roland UM-One? Here's what happens for me. When I used the browser updater, it wouldn't recognize it at the "select the MIDI inputs and outputs" stage. What (I think?) worked was to open up the FI editor, go to preferences, the UM-One was already selected. I turned both input and output to "off," hit "apply," then opened the preferences up again to select the UM-One again. Then the browser updater recognized it.

Does anyone else have this experience?
Did you plug in the UM-One before or after launching the browser?