hi, it turns out that it does connect eventually, it just takes a very very long time. the first few times, it woild open and not connect to the amp at all, although, without me changing anything that is nowanifesting as taking 4-5 minutes to load instead. once loaded, it is connected, but with other issues loke being unable to load external tsl files.
Hi Derek, I am not aware of any issues with the Katana Mk2 app, does the setting in the Preferences menu show the "KATANA" as a device ?Is it just that it won't connect even though the Katana is seen as a device ? I am happy to try and get this resolved. CheersColin. On Monday, 29 July 2024 at 08:55:52 pm NZST, Derek Church dchurch24@users.sourceforge.net wrote: Excellent! So it is - I'd just downloaded the latest. Thank you. However....is there an issue with the MKII version now? On the same machnine,...
Hi, The GO version (20240714 in the title bar, although I believe it was released today - 202450729)) crashes after a few minutes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) and crashes when trying to load .tsl files (loaded the same file fine last week) , with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7"...
Hi, The GO version (20240714 in the title bar, although I believe it was released today - 202450729)) crashes after a few minutes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) and crashes when trying to load .tsl files (loaded the same file fine last week) , with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7"...
Hi, The GO version (20240714 in the title bar, although I believe it was released today - 202450729)) crashes after a few minutes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) and crashes when trying to load .tsl files (loaded the same file fine last week) , with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7"...
Hi, The GO version (20240714 in the title bar, although I believe it was released today - 202450729)) crashes after a few minutes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) and crashes when trying to load .tsl files (loaded the same file fine last week) , with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7"...
Hi, The GO version (20240714 in the title bar) crashes after a few minutes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) and crashes when trying to load .tsl files (loaded the same file fine last week) , with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" press RESET !!! --- following this line is after...
I spoke too soon :( It works for a minute or two, then crashes with: floorBoardDisplay::autoConnect() x 1 system data received "F0411001050D1210013000003FF7" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped)
Excellent! So it is - I'd just downloaded the latest. Thank you. PS. Keep up the good work! It's a fantastic bit of software :) Thank you.
Excellent! So it is - I'd just downloaded the latest. Thank you.
Excellent! So it is - I'd just downloaded the latest. Thank you. However....is there an issue with the MKII version now? On the same machnine, it's refusing to connect to my MKII 50, whilst the GO version is working perfectly.
Hi Derek, Linux version is now updated CheersColin. On Thursday, 25 July 2024 at 08:13:29 am NZST, gumtownbassman <gumtownbassman@users.sourceforge.net> wrote: The time limited beta version is expiring, and I hope to post an updated version this weekend. Is there an issue with the Linux version? Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/fxfloorboard/discussion/585787/ To unsubscribe from further messages, please visit https://sourceforge.net/auth/subsc...
The time limited beta version is expiring, and I hope to post an updated version this weekend.
Hi, I've had the "update or else" warning now for a couple of days. I download the latest version (20240629), and run it, but it then tells me to download the latest version. Am I downloading from the wrong place? Kind regards, Derek.
Hi, I've had the "update or else" warning now for a couple of days. I download the latest version (20240629), and run it, but it then tells me to download the latest version. Am I downloading from the wrong place? Kind regards, Dave.
Hi, Something has gone a bit wobbly in the conversion from Katana Mk2 patches. I will fix that on the next release update. Cheers :-) Colin
Hi, I've noticed that some single patches designed with Sneaky Amps are still asigned to them and this also happens with every patch within the livesets. Please, find attached some examples. The Alice in Chains one is assigned to Bass Flat and the Base Metal Tones liveset contains two pathes also assigned to the Bass Flat amp.
Hi, I've noticed that some single patches designed with Sneaky Amps are still asigned to them and this also happens with every patch within the livesets. Please, find attached some examples. The Alice in Chains one is assigned to Bass Flat and the
Ok, best logical solution. By the way, since the last two or three updates, the program takes much more time to open. By the way #2, it would be great to be able to delete patches on the saved-patches folder within the program features.
Ok, best logical solution. By the way, since the last two or three updates, the program takes much more time to open.
Thank you for your reply, good to hear the patch names are now displaying correctly. Sneaky Amps do not exist in the GO (or the Katana Gen3) hardware, so any patches which use "Sneaky Amps" will be rendered to the nearest equivalent "GO" amp model.
The patches within livesets names seem correctly written with the latest 2024-06-21 update. Tx
Hi, I've noticed an annoying bug since I'm testing your Fx FloorBoard for Katana Go that stands there on each update. In most of the cases, the patch names within the liveset packs are not showing or show in one or two strange characters. I've got around five hundred patches and livesets and just a very few of them show correctly. I've tried by switching all available different languages in the Preferences > Settings menu. Also, I've opened the problematic ones with Notepad and can read all the patch...
Windows 10 Pro updated to latest version Dell T5400 Xeon Octacore 32 GB RAM Katana Go
Windows 10Pro updated to latest version Dell T5400 Xeon Octacore 32 GB RAM Katana Go
Hi, I've noticed an annoying bug since I'm testing your Fx FloorBoard for Katana Go that stands there on each update. In most of the cases, the patch names within the liveset packs are not showing or show in one or two strange characters. I've got around five hundred patches and livesets and just a very few of them show correctly. I've tried by switching all available different languages in the Preferences > Settings menu. Also, I've opened the problematic ones with Notepad and can read all the patch...
Colin, Thank you so much for the reply, and for all of your work. Makes sense now. I'm not sure that I want another piece of equipment in my already busy setup, but I do wish I had more patches, so who knows.
Hi Joe, The Katana can not physicaly store any more than the 9 patches, and the FxFloorBord Midi Patch Loader function only works while FxFloorBoard (and computer) is connected between the Katana and midi controller (the extra patches are stored in FxFloorBoard). The Midi foot controllee is connected to the computer as an additional midi device, as seen in the Preferences/Midi-USB menu, an option for midi Controller. Cheers Colin.
My setup consists of an FCB1010 controller midi out to a Roland GR-50, then midi out to my Boss Katana MK2 head. Since I need to control both units with FCB1010, and the Katana only has midi in, this is the only setup that would work for me. I managed to get the expression pedals to work for both the GR-50 and the Katana, but I cannot seem to get more than the 9 midi presets on the Katana. I set specific external midi program change numbers for every patch on my GR-50 to send to the Katana, but any...
AWESOME !!! Great to hear it is working well . Thanks for your help Cheers :-)
The best things come in threes :-) Everythings works perfectly. Thank you so much!
Fingers crossed this time version 20240603 for ME-25-Edit now up !! :-)
Hi, the "square" issue is solved. Thanks for that! However the programm is now still crashing again after a few clicks in the tree structure. That's been a bug you already fixed in the second last build, where you took care of a better ALSA support. May I ask for another "final" version, addressing this issue? I'm fine with the .tsl/.syx support, as I found a way around it. You just might keep it on the back log, as it will make other users happy.
A new 20240602 2nd June version posted, hopefully fixed that issue once and for all. The ME-25 patch structure data is different from all other Boss devices, every second byte is a "00" (zero) and when read as text show as blocky squares. The .tsl type patch files were added to the ME-25 after the initial editor release, so I will address those at a later stage.