View Full Version : GT-8FxFloorBoard editor upgrade requires testers.
gumtown
05-26-2009, 04:21 PM
The never ending FxFloorBoard project has now moved to updating the GT-8 version.
I have uploaded a windows only update (mac & linux available on request), and have added a few extras, like shortcut buttons and system editing of global data and custom pre's & distortions and wha's etc...
I am looking for some testing to be done on the system data loading part, i need some to install the patch editor, and set it to 'deBug Mode' from the Preferences>Midi menu, then set the 'connect' on, and press the 'system' or 'custom' button and see what figure the popup windows states ( {xxxx bytes received} ).
I am also requiring a bulk dump file of a GT-8 which includes the 'system' data, just so i can check a possible fireware bug in the GT-8/GT-Pro handling of system *.syx data.
You can PM me for an email address to send the bulk file, or use the address in the editor's 'about fxfloorboard' menu.
I will eagerly await for someone's reply, Thanks !!.
The latest build is made ready for windows 7.
MeMyselfAndI
05-27-2009, 02:28 AM
... I have uploaded a windows only update (mac & linux available on request)...
Im a :icon40: user. You can misuse me as a testperson. Particularly, because I found out that midi data transmission using a USB-Midi cable together with windows-GT8-tools under wine sometimes seem to be incomplete. I tip to wine, because bulk dump and load with :icon40: tools is working.
...I am also requiring a bulk dump file of a GT-8 which includes the 'system' data, just so i can check a possible fireware bug in the GT-8/GT-Pro handling of system *.syx data...
I´d like to do that for you. You only have to be a little patient, because I´m working too much for the money :icon16:
gumtown
05-27-2009, 07:30 AM
Im a :icon40: user. You can misuse me as a testperson. Particularly, because I found out that midi data transmission using a USB-Midi cable together with windows-GT8-tools under wine sometimes seem to be incomplete. I tip to wine, because bulk dump and load with :icon40: tools is working.
As requested a :icon40: version for you built on G-OS (ubuntu variant) ready for testing on :icon40:
MeMyselfAndI
05-27-2009, 10:16 AM
As requested a :icon40: version for you built on G-OS (ubuntu variant) ready for testing on :icon40:
:icon14:Thanx, Gumtown. Will test it for you asap.
gumtown
05-29-2009, 03:52 AM
Cheers!! thanks for the GT8 bulk dump, it's helped a lot, next Linux update done (version 20090529), i think this one should sort out the system editing.
gumtown
06-02-2009, 02:53 AM
Any success with this one?
gumtown
06-07-2009, 04:59 PM
another update done, added GT-10 patch file loading and a filter on the midi input, which has seen problems on the Linux version with non-midi rubbish in the data.
The midi output data rate has been slowed a little to stop the "midi offline" error from data overflow.
I am hoping the system editing is fully working and updating the display correctly now..
since i don't have the GT-8 model, some user feeback, feature requests and critisism would be appreciated..
:-)
gumtown
06-15-2009, 09:00 PM
Any interest in helping to test drive a free editor for GT-8 users?
Problem for me is i don't have access to a GT-8
brainiac7
06-24-2009, 01:24 PM
I'm new to the GT8, and I've downloaded the GT-8 editor found on this website already. In what way is your software superior? I'm not aware of there being any problem with what already exists.
Good luck with your project and please give me some reason to invest time in your software. Thanks.
gumtown
06-25-2009, 04:52 PM
Stuff i am working on recently is
The ability to edit and save/load just the system data, global setting and custom amps,wha and distortions. I don't think the other editors can do this.
Also added user text dialog, which allows patch files to have text desciptions of a patch build.
Also working on adding patch file loading/conversions from other GT models patches.
It is a bit of an on-going project where refinements are made and features added, the
project covers all COSM BOSS GT models, which has been very time consuming (6000 hours so far) for a bit of freeware software, no other editors support Mac Osx or Linux.
I will be happy to assist. It will be a few weeks before I can do much though. FWIW I am a professional programer.
gumtown
07-16-2009, 09:22 PM
Hey there Hamp, that would be fantastic !!
i hope to update the editor before then with some refinements and added features.
Maybe some of your programming skills could be handy too, what are you like at C++ and Qt framework?.
gumtown
07-24-2009, 08:14 AM
just updated all platforms to version 20090724, more improvements and tweaks, the Mac version was quite out of date.
laechelp
07-26-2009, 05:27 AM
Hi, i just download the latest version 20090724 of the GT-8 Fx FloorBoard and installed it. environment: Win XP Home Edition SP 3, M-Audio (USB-Midi) cable, Boss GT-8. I changed the preferences (Midi in: , Midi out: ) to USB-Audiogerät. Now i push the "Connect"-Button and got a message box (connection Error: "The Boss GT-8 Effects Processor was not found...").
Using the GT-8 Editor there are no problems using this configuration.
Can you please help me?
Thanks.
gumtown
07-26-2009, 06:45 PM
Hi, i just download the latest version 20090724 of the GT-8 Fx FloorBoard and installed it. environment: Win XP Home Edition SP 3, M-Audio (USB-Midi) cable, Boss GT-8. I changed the preferences (Midi in: , Midi out: ) to USB-Audiogerät. Now i push the "Connect"-Button and got a message box (connection Error: "The Boss GT-8 Effects Processor was not found...").
Using the GT-8 Editor there are no problems using this configuration.
Can you please help me?
Thanks.
Are the midi cables around the right way?
GT-8 midi out > adapter midi in,
GT-8 midi in > adapter midi out.
There may also be an issue because i have updated the midi system with the latest release,
and don't have a GT-8 for testing.
If the midi cabling is not an issue, and your midi adapter device is available in the editor's TOOLS>Preferences>Midi, then let me know, and i can adjust things to suit.
laechelp
07-27-2009, 11:54 AM
Are the midi cables around the right way?
GT-8 midi out > adapter midi in,
GT-8 midi in > adapter midi out.
There may also be an issue because i have updated the midi system with the latest release,
and don't have a GT-8 for testing.
If the midi cabling is not an issue, and your midi adapter device is available in the editor's TOOLS>Preferences>Midi, then let me know, and i can adjust things to suit.
Hi,
the midi cabling is ok. In the editor's Tools>Preferences>Midi i can choose in the combo-boxes the midi device "USB-Audiogerät" (<- German). As i wrote the midi cabling works well with the application GT8Editor. Any further idea?
Thanks.
gumtown
07-27-2009, 06:13 PM
I have found issues with different brands of midi adapter, wait timing for received data seems to be different. And with this version i may have made the time too short.
Try setting the program to "deBug Mode" from the Preferences> Midi menu, then press the editor "connect" button.
This will display some data from the GT-8 in a popup window, the message should start with 'F0' and end with 'F7'
the message should be
{F0 7E 10 06 02 41 06 02 00 00 00 00 00 00 F7}
If you could let me know what you are getting, and i can fix the problem.
Or if you get no popup window at all.
Even without the "Connect" button active, you should be alble to send patch data to the Gt-8 and do some realtime editing, with the differences being heard as you play. (should be able to turn effects on/off and see the l.e.d on the GT-8 toggle).
If you could let me know what is happening, that would be very good thanks..
laechelp
07-28-2009, 02:49 PM
Hi gumtown,
with the midi setting switched to Debug - Mode, i got the following string in the status bar: F07E000601F7, but i get no popup-Window.
Hope this helps a little bit.
Cheers!
gumtown
07-28-2009, 07:20 PM
I just uploaded a new windows version which you can download from
http://gtx.tinfoilmusic.net/
which has a few midi modifications, but the "connect" should still be working.
The fact that in deBug Mode, and doing the "connect" thing does not return a reply message in a popup window suggests two things.
1.) Something up with the external midi, but if that works with other applications....
2.) The GT-8 needs to have it's MIDI DEVICE ID set to "1" (page 80 of user manual), to allow system exclusive communication.
I tried the GT-8 program on my GT-10B, as the connect protocol is the same, and it "Connected", so i think maybe the MIDI DEVICE ID setting might be worth a look at..
If the problem persists, let me know. I do want to have things working well for all situations.
laechelp
07-29-2009, 01:07 PM
Hi,
i downloaded the actual version 20090728 (windows). But the effect was the same....
I first uninstalled the old version, then installed the new one.
I have made some screen shots pasted in an PDF-File. How can i send this file to you?
The MIDI Device ID (in the GT-8) was set to ID = 1 .
As I wrote the MIDI cabling is ok (it is an M-AUDIO MIDISport UNO, 1-in/1-out CLass-compliant USB-to-MIDI Interface).
I have installed Windows Home Edition SP 3 (a german installation).
Do you have any more idea, what can i do next?
Cheers!
gumtown
07-30-2009, 12:36 AM
Have you seen this ?
http://forums.m-audio.com/showthread.php?t=3741
Seems the UNO had a bad production run.
Are you able to try another type of midi device?
the editor does push the midi specification limits to the edge on speed, and the editor is fussy on receiving bad data (active CRC checks), and if your midi device is one with a lazy opto isolator, some midi data could be corrupted.
From your PDF images, it seems there is no midi data returning from the GT-8, could you test the midi to the GT-8, just by using the editor without the "connect" active.
Try turning a few effects on/off with the editor controls, the lights on the GT-8 effects should change state as you switch them.
Something else to try is installing MidiOx and MidiYoke http://www.midiox.com/
If you install MidiYoke first, then use MidiOx to setup the port routing (use all midi yoke devices, then disconnect all routing connections to start with)
this program does seem to slow down midi data, or you can view midi data streams to see what is happening.
laechelp
07-30-2009, 11:25 AM
Have you seen this ?
http://forums.m-audio.com/showthread.php?t=3741
Seems the UNO had a bad production run.
Are you able to try another type of midi device?
the editor does push the midi specification limits to the edge on speed, and the editor is fussy on receiving bad data (active CRC checks), and if your midi device is one with a lazy opto isolator, some midi data could be corrupted.
From your PDF images, it seems there is no midi data returning from the GT-8, could you test the midi to the GT-8, just by using the editor without the "connect" active.
Try turning a few effects on/off with the editor controls, the lights on the GT-8 effects should change state as you switch them.
Something else to try is installing MidiOx and MidiYoke http://www.midiox.com/
If you install MidiYoke first, then use MidiOx to setup the port routing (use all midi yoke devices, then disconnect all routing connections to start with)
this program does seem to slow down midi data, or you can view midi data streams to see what is happening.
!!Yippiee, it works
I made an update of the M-Audio Midi-driver, reboot and every thing is fine. I will continue testing (if its ok).
Thanks, stay tuned and keep on rockin'
lestervai
08-14-2009, 10:40 PM
hey where to download the latest version of the gt-8 floorboard?
gumtown
08-15-2009, 02:57 AM
hey where to download the latest version of the gt-8 floorboard?
Download from
http://gtx.tinfoilmusic.net/GT8-download.html
There are still a few issues to work through and iron out, so if you are able to try it and let me know if the patch loading from the GT-8 works for you (or not), by doing a "double-click" on a patch-tree patch item (loads a GT-8 patch into the editor).
Problem for me is i don't have access to a GT-8 to test a few progamming changes, and sort out issues with different brands of midi adapters.
gumtown
10-15-2009, 03:30 PM
The GT-8FxFloorBoard has just had a bit of an update, with a bit of a new look.
The chain arrangement has been reversed to left-to-right, a 4 way patch clipboard has been added and the ability to paste a single effect part of a patch into another for any of the 4 clipboards.
Added bulk file patch loading, and am currently working on bulk GT-8 backup/restore, with the ability to have the GT-Pro *.gte single or bulk patch file format as a standard for all the previous GT models, so patches will be interchangeable between GT models.
And you will be able to use the Boss GT-Pro Librarian for GT-8 patch files too.
As usual, i don't have access to a GT-8, so i need to rely on your feedback as to whether stuff is working as it should be.
gumtown
10-27-2009, 03:24 PM
i just keeps on coming, now updated with French, German and Chinese languages.
gumtown
01-07-2010, 06:43 AM
and again GT-8FxFloorBoard patch editor updated
to cope with non-compliant or awkward midi adapters.
http://gtx.tinfoilmusic.net/GT8-download.html
Windows, MacOsx, Linux versions now 20100106
some of the more recent new feature additions are..
*Bulk file backup/loading of GT-8 User patches-save in *.syx, *.mid, or *.gte (Gt-Pro) formats.
*load patch file from Bulk files, either *.syx, *.mid, or *.gte (Gt-Pro) formats.
*load single patch files from either GT-8, GT-Pro, or GT-10 formats- load *.syx, *.mid, or *.gte format patches.
*Multi language support for English, French, German, Chinese.
*4 way patch clipboard, copy, paste and edit 4 concurrent patches.
*4 way partial effect paste, copy effect parts from one patch and paste to others.
*Newer framework builds for better support of recent operating system releases.
wooddot
01-08-2010, 02:53 PM
anyone ever thanked this man. I do now!
(sadly my GT-8 is dead (costs), had the rom destroyed due to an update).
Negotiating good will get this thing back for half the costs soon!
Listen to my stuff : http://www.mutealbino.com
Buy my stuff : http://www.cdbaby.com/cd/mutealbino
titaniumslide
02-17-2010, 12:02 PM
Gumtown,
I could help you in some small way I have A GT-8, Edirol UM-1ex and a M-Audio Uno. I have noticed many errors with the M-Audio midi, I just received the Edirol and things are looking better,but there are still some issues. '
If you could tell me what you are looking for prehaps I can help.
By the way, Thank You for all you do for this community of users with your software.
Scott
gumtown
02-19-2010, 06:15 PM
Hi Scott,
Could you let me know what the specific 'issues' are please.
Your findings on the M-Audio midi device confirm my thoughts that they have some fault on the midi receive part.
The M-Audio site has a serial number list of the bad devices, and i think they may replace it.
pedroa
03-31-2010, 05:15 PM
Hi there gumtown,
First of all... Thank You Very Much for the FXfloorboard software is funtastic!!!
I am a linux user, using kubuntu with the latest kernel and let me tell you that your "little" app works great with this cheap piece of equipment I got for 5 bucks:
http://cgi.ebay.com/USB-MIDI-Cable-Converter-PC-to-Music-Keyboard-Adapter_W0QQitemZ260501435641QQcmdZViewItemQQptZKe yboards_MIDI?hash=item3ca71874f9
And it worked at the very first try, with linux!
When I open a branch it loads the patches names, when I click one patch it activates it on the GT-8, when I double click a patch it loads the definitions on your app, really really great :)
Now issues:
1) I am using a asus eeepc with a 10" screen and the text box for editing the patch description is way down the screen and I can't see the status bar (the one that says "ready"... "reading names" and that sort of stuff)
Very very minor thing really.
There is no way to maximize, or adjust the window borders? maybe make the pedals board scrollable.
The way I do it now is I move the window up a little bit, so the menu bar disapears above the screen but at least I can see the status of communications with the GT-8.
2) And this one is the most important...
Everything works fine when I start your app, it connects to BOSS GT-8 automatically, then I open a bank, it pulls the names of the 4 patches alright. Takes a little more than a sec to pull each one.
Then I open another bank, again it pulls the names alright, but... when I go and open a third bank it starts to drag and I see that on the status bar your app is trying to pull the information, and it keeps retrying and retrying and keeps giving that information.
From then on, it seems that the communication between your app and the BOSS GT-8 is choked.
If I close your app, and run it again it gets back to normal state.
Is it me, linux, the app, the cable or all at the same time?
Again thank you very much and let me know if I can give you any extra information.
I will certainly make a donation for this app... you totally deserve it...
Cheers,
Pedro A.
pedroa
03-31-2010, 05:45 PM
BTW: The link I gave is not for publicity spamming purposes, if the administrators judge it that way please remove it.
gumtown if you need a linux tester, here I am, thanks.
Pedro A.
gumtown
03-31-2010, 11:45 PM
i have exactly one of those midi adapters devices, and i can tell you there is a problem with the device design, especially with receiving large system exclusive data. It is a harware issue with these type adapters, if you use, say, an Edirol adapter, you will have no problems. the names on the patch tree should update 12 of them in about 2 seconds. The problem with this device is the same on Linux, Windows and Mac Osx.
pedroa
04-01-2010, 05:28 AM
Hi gumtown and thanks for the reply.
Well that was my first feedback on my very first experience with it, and after testing it last night a bit more I now know it was not accurate.
Well you may be right about the Edirol cable but it costs 10 times more.
I may well make a donation to you and still keep the change :)
I was not complaining on the time it takes to load the banks trees, and so that you know it may take some time more if the banks are on different parts of the tree, like a bank on Presets and another on a User bank.
No problem, it is an acceptable drawback.
Now regarding that 2) problem I mentioned...
Yesterday I pinpointed the real problem, and the problem is not in selecting or expanding bank trees, it does that alright with no choking at all.
It will only choke when I double click a patch and then expand a unexpanded bank
After I double click a patch, it loads its definitions into FXFloorBoard and then I may edit it, write it, and even select another patch, just as long as if it is from an already expanded bank.
But if I expand a bank that was not expanded yet it will choke.
I guess that will get you on the right track. Maybe some "reseting" is required before expanding any Bank?
After this choking happens I can either:
1) Close the app and open it up again, which I assume resets the device to a workable state again.
2) Click the "connect" button on FX so it disconnects, connect it again. This will make FX either say it does not recognize BOSS GT-8, or it will reload the already opened trees with wrong Patch names or with a "bad data". Then I click "connect" to disconnect and the click "connect" again and then it will be alright and working.
By the way what IDE do you use to program and compile the linux executable? I also do some coding, not much of a C++ fan though, but I know may way around. I could easily fix my window height problem at least :)
Thank you very much,
Pedro A.
pedroa
04-01-2010, 05:35 AM
Almost forgot a little suggestion:
I know you number your Bank/Patches starting by Bank 1 for User and then again Bank 1 for Preset.
It would be nice if the numbering was done acording to what is shown on the Boss GT-8 screen.
So, for example Preset 68-4 would show on FX as P68-4 instead of P33-4.
Thanks
Pedro A.
pedroa
04-01-2010, 06:37 AM
Another thing I remembered suggesting:
I noticed that when you expand more than 4 Banks, one of the already expanded Banks will collpase leaving only 4 Banks expanded.
(at least that's what I think it does)
Would it be possible to have more than 4 Banks expanded at a time? Is this to limit the amount of data retrieved from the GT-8? Could that limit be made a Preference?
Seen your http://gtx.tinfoilmusic.net/coming%20features.html
1) "EQ graphic display"... yammi :)
2) "Print/Display all settings and save to txt file"... hey I know PHP and I see that Sysex Reader was written in PHP, maybe pull the gutz out of Sysex Reader and stick it in FXFloorBoard for the Patches?
Anyway to include an Arpeggiator, Harmonizer editor to edit the scales on FX someday? :)
Need a Portuguese translation?
I hope you don't mind that I made a donation to you of the double the cable cost me. :)
Thanks again,
Pedro A.
pedroa
04-02-2010, 12:56 PM
Leaving a little linux geek developer how-to note on compiling this thing:
1) Get the source here:
http://fxfloorboard.svn.sourceforge.net/viewvc/fxfloorboard/branches/gt-8_ver-2/
Go for the "Download GNU tarball" on the lower left corner (if you are too lazy to go the Subversion way)
Uncompress the thing somewhere so you will remember where it is.
2) As IDE we will go for QT Creator, install from the command line (be sure to be the su):
apt-get install qtcreator
3) Open up QT Creator, it should be on the Development section of your window manager "Start button", or for the command line maniacs it is as simple as running with a qtcreator command.
Be sure you run it with su previleges or your Builds won't work.
So sudo qtcreator if you are not logged in as su/root
4) Open the GT-8FxFloorBoard.pro project file.
(Now is the right time for you to remember where you uncompressed that tarball file, got it?)
5) Just click Run and watch it go... or... fail spectacularly (meaning loads of fatal errors thrown at you by the compiler) ... if you... don't have the ALSA developer files installed. Namely the alsa/asoundlib
If that happens just install it with:
apt-get install libasound2-dev
... And go for it again.
Building it all takes some time and in the end it gave 51 Warning messages, almost all were about variables or parameters that were declared but never user. But it works!
Just leaving it here for future reference, for me and other lunatics that might have, like myself crawled the internet for this piece of information and didn't find it.
Going to figure out how this thing works now... and my apologies if you think that I am crazy here on this thread just talking to myself :)
Cheers,
Pedro A.
gumtown
04-02-2010, 04:50 PM
O.K. you have gotten further than most at building/compling the program yourself.
To make the program portable, the Qt framework is built as 'static' (using the Qt .configure with the -static -release switches)
each platform requires it's own multimedia/midi libraries installed, the ASLA dev files for Linux, windows MM sdk for windows, and Xcode for mac osx.
You will find by looking at the mainWindow.h & .cpp files that the main window is declared as a Widget rather than a fullsize main window, changing that will allow a full size scalable window.
To reduce the GUI size, either the actual images need to be reduced or some tricky graphics scaling is required (check out the Qt Affine example).
rhaneyjr
04-05-2010, 06:41 PM
excellent program! what would be really cool is to be able drag and drop the pedals on the screen to change the fx chain. is there a way to edit FX chain now? havent been able to find it
gumtown
04-06-2010, 12:52 AM
excellent program! what would be really cool is to be able drag and drop the pedals on the screen to change the fx chain. is there a way to edit FX chain now? havent been able to find it
Yes just hover the mouse pointer over the stompbox (except on areas with a knob or button) then hold the left mouse button while you drag the stompbox to the new chain location.
pedroa
04-06-2010, 01:45 PM
You will find by looking at the mainWindow.h & .cpp files that the main window is declared as a Widget rather than a fullsize main window, changing that will allow a full size scalable window.
To reduce the GUI size, either the actual images need to be reduced or some tricky graphics scaling is required (check out the Qt Affine example).
Yup, I just resized the floor.png file, modified some Offsets on the code too and it is sweet now :)
Already fixed the limited 4 Banks expanding.
Also changed the Bank numbering.
Just need to fix that load/expand choke issue and I am fully happy with it and my 5 bucks cable.
Thanks Colin
4x4uk
04-07-2010, 04:30 AM
i have exactly one of those midi adapters devices, and i can tell you there is a problem with the device design, especially with receiving large system exclusive data. It is a harware issue with these type adapters, if you use, say, an Edirol adapter, you will have no problems. the names on the patch tree should update 12 of them in about 2 seconds. The problem with this device is the same on Linux, Windows and Mac Osx.
I have exactly the same midi to USB adaptar and can confirm the above, it simply does not work repeatedly or reliably for large data transfers and in particular sysex dumps
MeMyselfAndI
05-06-2010, 07:04 AM
Hi Gum,
I have a stupid question:
what is the big difference between midi and sysex data?
I also realised that cheap USB-Midi-Interfaces (like mine) have difficulties with huge sysex transfer but not with midi transfer. At last I made manual bulk dump of midi data, converted it to sysex to edit it in Editors (and the other way around).
Isn´t it then better to use only midi?
gumtown
05-07-2010, 09:11 PM
Not a big difference between midi and system exclusive data, it is still all midi data. System exclusive data is a format which is native to a particular device (i.e GT-8), and does not use midi channels like midi note or continuous controller data.
All patch and system data sent or received by the GT-8 is system exclusive, the data files can be coverted between *.syx and *.mid formats, the difference being the file headers, *.syx data occupies full midi bandwidth and full speed and individual GT-8 units can be identified by Midi Device ID number 1~32 - the receiving GT-8 Unit ID must match that of the data content or the data will be ignored.
Then *.mid data speed is limited by a tempo byte in the file header and occupies one of the 16 midi channels, the GT-8 midi channel must be set to the same as the data sent.
Either format still contains the same GT-8 patch & system data.
The problem with the cheap midi devices is they can't receive patch data from the GT-8, the GT-8 sends a patch in about 32 segments/packets (one for each effect group) and the midi device can't cope with all this data at once. With a patch editor, the editor expects to receive 1010 bytes/patch of data, and if this exact amount is not found, it will display an error.
By sending to a sequencer using the same midi device may seem fine, but the sequencer does not know how much data to receive, it thinks all is fine when the data stops, and may save an incomplete dump without you knowning.
When you go to reload back to your GT-8, the sequencer saved data might not be the same as the orginal patch before saving, since the GT-8 will reject corrupted data, and you end up with only partial patch data reloaded, and the patch not sounding anything like it's orginal.
MeMyselfAndI
05-10-2010, 04:17 AM
Hi Gum ,
thanx for your answer.
... By sending to a sequencer using the same midi device may seem fine, but the sequencer does not know how much data to receive, it thinks all is fine when the data stops, and may save an incomplete dump without you knowning.
When you go to reload back to your GT-8, the sequencer saved data might not be the same as the orginal patch before saving, since the GT-8 will reject corrupted data, and you end up with only partial patch data reloaded, and the patch not sounding anything like it's orginal.
This would be one big nightmare :-{ !
Do you have some kind of midi interface compability list?
As far as I now yet, following midi interfaces doesn´t work properly:
- LogiLink USB Midi Adapter
- M-Audio Uno
virtual
05-26-2010, 03:07 AM
Hi, man!
Thanx for big work. Developing GT-8FxFloorBoard editor this is good idea. Really.
But it doesn't work in my case :-(
I tried run it on Gentoo Linux with E-mu 0404 PCI soundcard (alsa driver with/without jack-audio-connection-kit), but all attempts were unsuccessful... the transfer of data from GT-8 failed. Connection doesn't occur.
I used two MIDI-cabels to connect GT-8 to PC.
First cable: GT-8 MIDI-OUT -> EMU-0404 MIDI-IN
and second cable: EMU-0404 MIDI-OUT -> GT-8 MIDI-IN
Correctness of connection verified by MIDI-sequencer (QTractor). Data were sent from GT-8 to PC (were displayed in message window).
Maybe midi interface in EMU 0404 pci isn't compatible with GT-8FxFloorBoard?
gumtown
05-27-2010, 01:03 AM
FxFloorBoard should happily run on any Linux distro, as long as there is X-window system and ALSA midi. I have heard of problems with the EMU 4040 card in the past, they recieve smal data like midi notes/program change O.K. but can fail when moving large amounts of system exclusive data.
The FxFloorBoard source code is available if you want to compile on you Gentoo system, on the SourceForge site just search for "FxFloorBoard".
EDIT: i forgot to mention an update will be available in the next few days, with a few new features like, Text Dialog- a patch has all it's settings displayed on a list which can be saved or printed. Clipboards are now automatically saved to disk, so they are there on startup of the next session, [F1] button pulls up mouse cursor hover "Whats this" Help, patch Auditioning of Bulk Patch Files, where the patch is sent to the GT-8 temporary memory (play area) as the mouse passes over the patch. Plus the Gt-8 editor can load in GT-Pro and GT-10 patches and convert them.
hope to update this weekend.!!!
gumtown
07-12-2010, 05:19 AM
Hey !! More features added now!!
* Bulk Patch Editing - for writing a common effect's parameters over a series of patches in one quick operation.
* Patch Text Dialog - displays all the patch parameters in a text format, which can be Printed or Saved as a *.txt file.
* New Assigns layout - separate assigns editing pages which will allow Bulk Patch Writing use of individual assigns.
* GT-8 User Patch List - Text dialog of all the User patches in a list for Printing or saving to *.txt file.
current version 20100712 for Linux, Mac Osx, and Windows.
virtual
08-03-2010, 11:48 PM
Hi!
I found solution of my problem with e-mu 0404 pci soundcard.
All trouble was in card clock. ALSA don't work correctly with MIDI-data on e-mu 0404 pci if card clock not 48000hz.
Switching to 48000hz solve problem with connection and MIDI-data transfer. FxFloorBoard works perfectly!
I hope that the given information will be useful to somebody.
pedroa
08-30-2010, 11:30 AM
Thanks for the update and heads up Colin,
Your product Rocks, literally :)
Cheers,
Pedro A.
rs1909
01-06-2011, 11:20 PM
I have rebuilt the source code on Fedora 14, and it has crashed:
(gdb) bt
#0 0x00000039e41e21bb in QLayout::addChildWidget(QWidget*) () from /usr/lib64/libQtGui.so.4
#1 0x00000039e41da590 in QGridLayout::addWidget(QWidget*, int, int, int, int, QFlags<Qt::AlignmentFlag>) () from /usr/lib64/libQtGui.so.4
#2 0x00000000004619e5 in editPage::insertStackField (this=<value optimized out>, id=<value optimized out>, row=<value optimized out>,
column=<value optimized out>, rowSpan=<value optimized out>, columnSpan=<value optimized out>, alignment=...) at editPage.cpp:327
#3 0x000000000049a9b6 in menuPage_midi::setEditPages (this=0x6f87a50) at menuPage_midi.cpp:60
#4 0x00000000004b1051 in menuPage_midi::menuPage_midi (this=0x6f87a50, parent=0xacc390) at menuPage_midi.cpp:31
#5 0x000000000047092c in floorBoard::initMenuPages (this=0xacc390) at floorBoard.cpp:738
#6 0x0000000000470df0 in floorBoard::floorBoard (this=0xacc390, parent=<value optimized out>, imagePathFloor=<value optimized out>,
imagePathStompBG=<value optimized out>, imagePathInfoBar=<value optimized out>, marginStompBoxesTop=<value optimized out>,
marginStompBoxesBottom=72, marginStompBoxesWidth=25, panelBarOffset=10, borderWidth=3, pos=...) at floorBoard.cpp:104
#7 0x000000000041cefe in mainWindow::mainWindow (this=0x7fffffffd000, parent=<value optimized out>) at mainWindow.cpp:45
#8 0x0000000000415635 in main (argc=1, argv=<value optimized out>) at main.cpp:81
In order to compile I had to change incorred direct referencing of constructors like QPoint::QPoint(a,b) -> QPoint(a,b)
This produces compiler errors, e.g.:
stompBox.cpp: In member function ‘void stompBox::updatePos(int)’:
stompBox.cpp:336:56: error: cannot call constructor ‘QPoint::QPoint’ directly
stompBox.cpp:336:56: error: for a function-style cast, remove the redundant ‘::QPoint’
The prebuilt version does not work properly, it cannot connect to my GT-8, neither under linux or Mac OS X. I have an Alesis IO2 with midi in/output.
gumtown
01-07-2011, 05:17 AM
The source code needs updating to be compatible with QT 4.7.0 upwards as in your example, Qt no longer supports direct constructor calls, and the Qt library should be compiled as a static build (-static -release), and requires ALSA and X11 development libraries.
The prebuilt versions should be working fine with most midi devices, if the device driver is installed, it should show on the FxFloorBoard midi device list.
rs1909
01-07-2011, 08:18 AM
The prebuilt versions should be working fine with most midi devices, if the device driver is installed, it should show on the FxFloorBoard midi device list.
Thanks for the advice! The prebuilt version runs, but cannot connect to the GT8. I did select the proper midi in/out devices, on both OSes. When I select a patch from the combobox, sometimes it changes the patch selection on the GT8, but not always. When it does, the GT8 displays that it has lost connection. After trying to connect for some time I decided to build the software myself. You are saying 'most' midi devices, so could it be a problem with the Alesis IO2?
pedroa
01-15-2011, 07:23 PM
Hi and great year to you all,
I have just downloaded the current code from git, built it with qt 4.7.0 with no issues.
Worked great with my 5 bucks cable, right away.
To say the truth, I think it has less issues with the cable than before.
It seems that, even though it chokes like before, it chokes less.
And when I click connect a couple of times it gets back to normal.
Got a couple of questions for gumtown...
1) I seen on the git commits that you have added graphical equalizer to the GT 10 tree, will you be porting that to GT 8 someday?
2) I notice on the source code that you summon the plastique looks, but on the sourceforge binary the fonts are all tiny.
It is not an issue because when I build it from source the fonts become alright, just wanted to mention the situation though.
Thanks Colin,
Pedro A.
gumtown
01-16-2011, 01:58 AM
Hi and great year to you all,
I have just downloaded the current code from git, built it with qt 4.7.0 with no issues.
Worked great with my 5 bucks cable, right away.
To say the truth, I think it has less issues with the cable than before.
It seems that, even though it chokes like before, it chokes less.
And when I click connect a couple of times it gets back to normal.
Got a couple of questions for gumtown...
1) I seen on the git commits that you have added graphical equalizer to the GT 10 tree, will you be porting that to GT 8 someday?
2) I notice on the source code that you summon the plastique looks, but on the sourceforge binary the fonts are all tiny.
It is not an issue because when I build it from source the fonts become alright, just wanted to mention the situation though.
Thanks Colin,
Pedro A.
Hi Pedro,
The midi sub-system is always being improved, now it re-tries a few times for failed data requests, rather than calling an error first time.
So the cheap midi devices can be tollerated a bit more now.
1>) if i can finish the graphical EQ editing correctly, then the GT-8 & GT-Pro versions may use it.
2>) The Plastique look seems to get ignored by windows Vista/7, but was essential for the Linux version. Not many widgets want to comply to the forced looks anyway (most widgets are re-classed so only the stock widgets comply).
BTW: does all the functions work correctly? i don't have access to a GT=8
cheers Colin..
rancid_alika
01-19-2011, 08:32 AM
This is probably a newbie question, as I am a newbie to this forum, but anyway: I see all this amazing software for the GT-8, but I don't know what kind of cable to get to input it to my PC? Which cable should be used?
pedroa
01-19-2011, 12:28 PM
Hi Pedro,
The midi sub-system is always being improved, now it re-tries a few times for failed data requests, rather than calling an error first time.
So the cheap midi devices can be tollerated a bit more now.
1>) if i can finish the graphical EQ editing correctly, then the GT-8 & GT-Pro versions may use it.
2>) The Plastique look seems to get ignored by windows Vista/7, but was essential for the Linux version. Not many widgets want to comply to the forced looks anyway (most widgets are re-classed so only the stock widgets comply).
BTW: does all the functions work correctly? i don't have access to a GT=8
cheers Colin..
Hi Colin,
Like I said before if you reset the connection, just like when you start the application, the cheap cable actually works pretty good, I am just not sure if such a reset is possible while you are working with the application though.
1) Cool, thanks :)
2) No problem, I rather compile it myself because I get a less 10 Mb binary.
I think it works great man :)
Fantastic software.
Have some problem with some patches that come with the app, maybe they are GT 10, so some don't actually work, but those that work, are great.
Working with it manually, it controls my GT8 just fine.
Thanks a lot for your work on this fantastic, intuitive and time saving application.
Pedro A.
pedroa
01-19-2011, 02:41 PM
This is probably a newbie question, as I am a newbie to this forum, but anyway: I see all this amazing software for the GT-8, but I don't know what kind of cable to get to input it to my PC? Which cable should be used?
If you read the thread from the beggining you will find a link to the cable I am actually using to work with it.
It does not work flawlessly, but hey for that price I can live with the drawbacks.
From what I hear and read, the best cable is from Edirol which is from Roland, but it costs a lot more than the cable I am using.
Read the whole thread for more info.
Cheers,
Pedro A.
gumtown
01-19-2011, 05:30 PM
This is probably a newbie question, as I am a newbie to this forum, but anyway: I see all this amazing software for the GT-8, but I don't know what kind of cable to get to input it to my PC? Which cable should be used?
Your GT-8 and computer need to be connected with a midi device adapter, typically USB to Midi. The Midi in and Midi out are both used for full duplex data transfer between the GT-8 and computer software editor...
I recommend a good reputable brand for the best reliability and least data corruption.
although the cheepo Ebay usb/midi devices will work with a few data errors..
gumtown
01-19-2011, 05:36 PM
Hi Colin,
Like I said before if you reset the connection, just like when you start the application, the cheap cable actually works pretty good, I am just not sure if such a reset is possible while you are working with the application though.
1) Cool, thanks :)
2) No problem, I rather compile it myself because I get a less 10 Mb binary.
I think it works great man :)
Fantastic software.
Have some problem with some patches that come with the app, maybe they are GT 10, so some don't actually work, but those that work, are great.
Working with it manually, it controls my GT8 just fine.
Thanks a lot for your work on this fantastic, intuitive and time saving application.
Pedro A.
The small compiled file size would be due to the Qt libraries being shared on your system, as opposed to statically built for distribution (library files are built into the executable file).
Your shared library build will most likely not work on another computer without the Qt framework installed.
I also used to use 'UPX' to compress and encrypt the executable and libraries down to 8 Mb.
Great to hear it's working well !! :-)
mpoirier
04-22-2011, 05:55 AM
Hey Gumtown, I tried the soft again this winter but not much success keeping a connection alive with the GT-8. Kept getting sync errors.
I had flawless sync with the other more limited soft available on this board, so I guess the midi link does work.
What settings should I use to have solid communication with the GT-8 ?
Thanks !
gumtown
04-24-2011, 04:18 AM
What type of midi adapter do you have? (one type does not work well, a cheap chinese type with either/or/and a blue case, and musical clef printed on the side, driverless - this type won't shift large amounts of sysex patch data without an error - the software rejects any midi data errors).
Does the bottom left status bar give any info on "retrying data request" messages?
gumtown
06-03-2011, 07:38 PM
Just a reminder the free GT-8FxFloorBoard editor can be downloaded from
http://fxfloorboard.sourceforge.net/
It is fully functional with many advanced features, such as
Four ClipBoards for copying and pasting patches,
Each effect edit-page has a "partial paste" button for each of the four clipboards,
allowing effect parts of another patch to be pasted into the current edited patch.
Patch text Summary, which displays a patch's parameters and settings in a text format, which can be saved as a txt file or printed.
System/Global text Summary, which displays the GT-8 system and global settings in a text list format.
Patch List Summary, a tool to display a text list of all the GT-8 User patches, alligned into Banks of 4 patches.
Bulk Patch Modifier, allows you to Write your favourite effect setting or preamp, or what ever, to a User selected multiple range of patches in one operation.
Bulk Patch backup/restore, make backup copies of a selectable range of USer patches, or load in a bulk lot of downloaded patches.
System Backup/Restore and editing.
mpoirier
06-21-2011, 09:25 AM
Hello !
Sorry, forgot about this post. I just downloaded latest version "GT-8FxFloorBoard version 20110519: 19 May 2011" and it seems more solid !
I use a M-Audio MidiSport 4x4, don't know if you support this interface.
The connection works great now, the only glitch seems when I double-click Write/Sync to store patch data, the app seems to have trouble with lots of "retrying..." in the bottom status bar.
But in the end seems like it's saving the patch properly.
Will continue to play with it some more...
Thanks !
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.