• 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.

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

#5,721
@Melvin7822 have you seen and tried this?

(@Andras Szalay, for information, Zsolt may be interested in this.)

EverythingBass said:
When i try to start the 3.0 editor on MacOS Catalina i get a "The application “FIEditor” can’t be opened."

Running the 2.20 FIEditor without any problems.

Any tips? (already tried chmod +x to make it an exacutable)
Click to expand...

EverythingBass said:
Solved it!

I used another unzip program then the default mac "Archive Utility", now it works like a charm!
Click to expand...
 
#5,722
Quatschmacher said:
@Melvin7822 have you seen and tried this?

(@Andras Szalay, for information, Zsolt may be interested in this.)
Click to expand...

Yes, I have seen that and I was wondering. Others said it does not work, which is no surprise, because as far as I am informed (I am not Mac user) most (or all?) applications for previous OS do not run on Catalina without recompilation/implementation changes. Zsolt is working on that.
 
  • Like
Reactions: sillyfabe, mr2xbass, Basehead and 2 others
#5,723
I've owned a FI since the initial batch and have followed its progress on here for years now. I just want to compliment everyone at PandaMIDI and its assistants on not only a great product but amazing follow-through. This is rarely seen and even more rarely acknowledged. I thank you for this innovative version 3.0 and for now.....I'm off to make more sweet sounds with this incredible sound-sculpting machine!
 
  • Like
Reactions: Kubicki Fan, cosmicevan, Bo0tsy and 6 others
#5,724
Hi FI team, congrats on the great release of V3. Fantastic job on the new manual too.

I have been editing patches to fit my band needs all week and learning a lot about the new features. I definitely will be adding a midi cc controller setup to take advantage of the possibilities.

I want to point out a crashing bug (or perhaps a crash-causing user error). Using Windows 10 Home Edition to edit patches: If you are on preset 99 in the FIEditor and hit the plus sign (+), rather than the number starting over at 00 (or even doing nothing), the editor crashes and doesn't recall the last preset load folder or last preset used when restarted. I tested it a couple of times to make sure that was what caused the crash, and I got same result each time.

The opposite function, on preset 00, and clicking the minus sign (-), does not cause a crash. While the number stays on 00, the name in the preset window AND the preset sound decrements to the preset alphabetically last (or previous) in the LOAD-from folder last used.

This is not a major issue for me, but I thought I would bring the crashing to your attention anyway for future cleanups, especially since you have been so helpful in answering questions etc in the past. Thanks!
 
  • Like
Reactions: Quatschmacher
#5,725
used the weekend to update.
The backup of sounds and update went smooth, no troubles at.
FI was on midi channel 2 like i have it always since im using it with að switch.
Soon after i updated i just couldn´t get it to connect to the editor at all unless
i changed FI midi channel to All. Is that normal? i didn´t have to do that before the update.

The Editor crashed also a couple of times when hitting the -+ signs.
I wasn´t taking notice what i was hitting exactly when it crashed.

Like before the default 99 sounds on V3, not many usable live but you can really hear the possibilties
in soundsculping and what the update brings to table.

But is it just me or is the sound 53 on the V3 sounds the best thing yet to hit the pedal.
Not possible to play that without smiling :)
 
#5,726
Hog Branch Austin said:
Hi FI team, congrats on the great release of V3. Fantastic job on the new manual too.

I have been editing patches to fit my band needs all week and learning a lot about the new features. I definitely will be adding a midi cc controller setup to take advantage of the possibilities.

I want to point out a crashing bug (or perhaps a crash-causing user error). Using Windows 10 Home Edition to edit patches: If you are on preset 99 in the FIEditor and hit the plus sign (+), rather than the number starting over at 00 (or even doing nothing), the editor crashes and doesn't recall the last preset load folder or last preset used when restarted. I tested it a couple of times to make sure that was what caused the crash, and I got same result each time.

The opposite function, on preset 00, and clicking the minus sign (-), does not cause a crash. While the number stays on 00, the name in the preset window AND the preset sound decrements to the preset alphabetically last (or previous) in the LOAD-from folder last used.

This is not a major issue for me, but I thought I would bring the crashing to your attention anyway for future cleanups, especially since you have been so helpful in answering questions etc in the past. Thanks!
Click to expand...
Is the crashing with the +/- keys in instances where the folder doesn’t contain the number you are trying to jump to? Does the folder contain non-numbered program files too? Any chance you could make a video of the behaviour?
@Andras Szalay - we should make Zsolt aware of this.
 
#5,730
Quatschmacher said:
Also, a screenshot of the folder contents might help in case it’s to do with the file names or something.
Click to expand...
I´ll do that.
I was just going through the default V3 sound this weekend.
So that folder was likely the only active.

Another possibilty would be that i downloaded couple of sounds from the database.
And that folder also contained couple of mp3 files..
But still, i remember going through them without a problem.

But anyway.. I´ll check this better after work when i get home.
 
#5,731
Quatschmacher said:
Is the crashing with the +/- keys in instances where the folder doesn’t contain the number you are trying to jump to? Does the folder contain non-numbered program files too? Any chance you could make a video of the behaviour?
Click to expand...

Well, as I suspected, the crashing probably was user error because I do not think I had a preset 00 in the folder at the time -- I noticed that and added one later in the evening. Also, I am sure that I had several presets with un-numbered names that I was auditioning within that folder. I am at work now and cannot test this functionality or make screenshot/video; sorry I cannot be more helpful. My thanks to all you tech wizards for keeping all this information and functionality sorted out!
 
#5,732
Hog Branch Austin said:
Well, as I suspected, the crashing probably was user error because I do not think I had a preset 00 in the folder at the time -- I noticed that and added one later in the evening. Also, I am sure that I had several presets with un-numbered names that I was auditioning within that folder. I am at work now and cannot test this functionality or make screenshot/video; sorry I cannot be more helpful. My thanks to all you tech wizards for keeping all this information and functionality sorted out!
Click to expand...
You shouldn’t need to add a 00 prefix - that is simply what shows when a file has no numerical prefix. I was asking to try and get an idea of what might be causing the crashing.

I meant more if there was no 99 for instance and you were trying to scroll back from 01 to 99.
 
#5,733
I have good news for you. Zsolt Rammer, our expert for both PC and MAC programs has investigated the problem with the Catalina OS, and he found that our editor works fine under Catalina. There are just a few things you should take care of. Since I am not familiar with the MAC world, I rather cite his investigation result exactly:

I checked the editor on the latest version of Catalina (10.15.1) and everything works fine. The application is compatible with the latest macOS. But users can't run the app in the latest macOS, because the file attributes are changed in the zipped archive somehow. I think the error was caused by the wetransfer service. Because of this we are going to publish on the pandamidi web page the version that was not going through wetransfer. The new version will be available there until noon tomorrow CET.

Otherwise, Catalina users can change the file attributes manually. The solution is to use the "chmod -R 755 <filepath of FIEditor.app>" command in the console. For Catalina users, my installation advice is to change the downloaded FIEditor.app attributes to number 755 and follow the instructions in the FI user manual. Furthermore, if the editor doesn't start, delete the "FIEditor" directory under path "Users/Username/Library/Application Support". Until a new release is available, I suggest this workaround.

Andras Szalay
 
  • Like
Reactions: Highroler79 and BurningSkies
#5,734
Andras Szalay said:
The new version will be available there until noon tomorrow CET.
Click to expand...
Just for clarification for users, I’m sure you meant “by noon” rather than “until noon”. “Until” would suggest it will disappear after noon, which I’m sure is not the case. (I’m guessing that Hungarian uses the same word for both these concepts (like the German “bis”).)
 
  • Like
Reactions: Highroler79
#5,735
Quatschmacher said:
Just for clarification for users, I’m sure you meant “by noon” rather than “until noon”. “Until” would suggest it will disappear after noon, which I’m sure is not the case. (I’m guessing that Hungarian uses the same word for both these concepts (like the German “bis”).)
Click to expand...

Of course you are right.
 
#5,736
Quatschmacher said:
Also, a screenshot of the folder contents might help in case it’s to do with the file names or something.
Click to expand...
Forgot the video, but the crashing happens either when you first start the editor and press the + sign with no folder selected.
You can also cause it to crash by selecting a folder with no V3 sounds, like say your desktop for intance and press the + sign.
 
  • Like
Reactions: Hog Branch Austin and Quatschmacher
#5,737
FINALLY got around to doing a backup of my existing patches and doing a full update. No problems at all. Loaded all the new 99 sounds on since I wanted to check them out myself. Tracking has definitely improved (it wasn't bad at all before) and will be digging in to some customization this weekend. Well done, Andras and team!!!
 
  • Like
Reactions: Highroler79, Bo0tsy, DELACIUS and 5 others
#5,739
Basehead said:
FINALLY got around to doing a backup of my existing patches and doing a full update. No problems at all. Loaded all the new 99 sounds on since I wanted to check them out myself. Tracking has definitely improved (it wasn't bad at all before) and will be digging in to some customization this weekend. Well done, Andras and team!!!
Click to expand...
Just wanted to second this. Great job on the new v3 release guys, so many great new default patches, some of them are really much more reactive to your playing dynamics than previously, whilst some of the other new ones have that old school sinewave type synth phatness that I thought was occasionally lacking in the default v1 release patches. This will keep me busy for some time and I've not even dived into the new editor yet!
 
  • Like
Reactions: Basehead, Highroler79 and Quatschmacher

Latest posts

Top Bottom
Back