Ah, there should be a file named "g2editorfmx.xml" in directory 'C:\Users\<user>\AppData\Roaming\'. Try to find it and delete it.

It's what in Delphi is defined as GetHomePath, because of the different platforms. Maybe it's better that I put it somewhere more easy to find and also to add some checks preventing the thing you encountered...

and it starts again. What was wrong with c:\ for the value? ... before I nuke it again

I always prefer to have the settings file in the application folder ... which probably will not work for all platforms (including windows when you want to install into program files ... which I stopped using for that reason)._________________Jan

Don't know, I search the directories using the tried and tested FindFirst/FindNext/FindClose functions and filter out the prf2 and pch2 files.

Maybe a bug in the TTreeview Object when too many nodes are added. I'll test some more.

Blue Hell wrote:

I always prefer to have the settings file in the application folder ... which probably will not work for all platforms (including windows when you want to install into program files ... which I stopped using for that reason).

It may also be that findnext will get into a cycle following windows hard links .. or what was the windows word for that again ... the directory structure is a bit messy since XP ..._________________Jan

- Cleaner and faster termination of the USB connection on closing of the application. This bugged me a long time, but solved this by just sending a reset command to the usb interface on closing.

- Changed the location of the ini file “g2editorfmx.xml”. On windows this will be in the application folder, on Osx this will be in the documents folder.

- Added functionality “Auto assign midi to knobs”. This is for engine owners who want to use an external midi controller.

I tried to make this before on the previous editor by making an extra midi connection to the editor, but I wasn't really happy with it, because you basically had to run the editor all the time, and also the midi connection wasn't very stable.

Now I've implemented it differently, you can assign midi cc's to the buttons and sliders on parameter pages that are stored in the ini file, see picture below.
On the application settings there is a knob "Auto assign midi". If you enable that knob, the controllers are automatically assigned to the parameters associated to the buttons and sliders on patch load.

This means that the "in memory patch" will be modified, because midi controllers are stored in the patch.

- Changed the patch file browsing tree. Sub directories are only read if you expand a directory in the tree, so the application won't freeze if you accidently enter C: as your root patch folder

Thank you again for that incredible work, and congratulations.
It works fine on OSx Mountain Lion.
The only thing I couldn't understand is : how can one change morph range? I couldn't do it with Ctrl click.
I really LOVE all the new functions you implemented and the fact this editor is compatible with so many OS.

If you have an Adnroid tablet supporting USB Host mode, you can give the application a try. You can download an experimental version over here http://www.bverhue.nl/g2dev/?p=108 and read some instructions how to install and use it.

It's not much more than a controller at the moment, and it may crash now and then, but has some potential.

The problem of the usb interface is mostly tackled, at least, on my acer a1-810. The crashing happens mostly when sending a lot of parameter messages to the g2, for example by moving a slider up and down with high speed, so I had to put a limit of 20ms on that, which in turn causes latency. So that's something that remains to be solved.

Another problem is how to implement a complex patching interface on a small screen and a slow processor.

Waw, on a tablet? Great.
I have a dream : a tablet G2 editor with a pedal. When you select a parameter (touching the screen) you could change its value with the pedal. There is a gap between real controllers and display (like for example touch osc). It's funnier to tweak real buttons or pedals than virtual sliders on a tablet. So with that tablet editor with a pedal, it could be easy to edit with one foot on the pedal, one hand on the screen, and the other (hand ) on the keyboard of the G2.
Your editor running on a tablet seems to be the first (and hardest) part of my dream.

Hi, after some recovery time i am back in the studio now and switched my g2 on again.. Nice progress with the open source project.. Just trying the 0.35 fmx beta and want to try the hidden modules now since i found them most promissing on my last try..

The fmx editor opens on osx 10.8.5 and connects fine with my G2.. but.. i cant load patches from the disk..and when i try to safe a patch i get the error message in the attachment. Access violation at adress 0074183A, accessing address FFFFFFFE.

I didn't know about that error. I'm on 10.8.5 also and haven't seen that error message.

What have you put in the "Applications settings" "Patch directory" edit box? See image below.

The idea is that you put the root directory of your patch files in that edit box, then if you press "Refresh" on the Patch tab, the directory tree and files should appear. Seems to work o.k. here...

And Xav about your dream, the best thing I can think of is to build some function into the tablet application by which you can easily switch the foot controller between patch parameters. Are you using one foot controller or multiple?

Waw Brunov, it would be great!
For the moment, I only use one pedal, plugged in control pedal input.
Maybe the best way to do that would be to propose to choose a Midi CC for this purpose (pedal, wheel or midi incoming data).
Thank you very much to take that idea in consideration.

I posted this video because it may give you good ideas (interaction from the editor with an android/iphone tablet).

The editor works on my android (a very small phone) with Remote Desktop. I noticed that the only one who often speaks of this alternative is jksuperstar. I know this is not ideal on a stage/live.

In my case I use this alternative since the late 90s in several circumstances.
I remember the first time I was fishing on a lake in the middle of nowhere and I was playing with my g2 (YES! with sound!).

I tested several remote applications in the past. How to move around the screen works really well with Remote Desktop. In the video I play with some functions in the editor and I created a small patch. No problem to connect the wires!

You can have even better. I decrease the display resolution because I increased audio resolution. I can get a much smoother image. I also had a little difficulty because the camera was 10 inches from my phone and was suspended on 2 glasses. Under normal conditions, this is happiness!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum

Please support our site. If you click through and buy from our affiliate partners, we earn a small commission.