X-Edit version 2

Zak

Anyone know when the X-edit version 2 is due out..
Alberto mention it in the other forum but I couldnt find any mention of it
Zak :roll:

iced

sup zak...
still no info about the x-edit?
:?

aRcTuRuS

I wonder if they will fix the infamous pedal/program shutdown bug that you all talk about.

Zak

You would think with such a bug they would have announced something, Imagine buying a computer and then while you were using it, it just crashes for no reason.....
Hang on, that shit happens all the time
Damm, there goes my argument
Zak :shock:

D.Alexander

This is the most annoying bug, any word on this Digi :?:

AlbertA

I explained on the old GNX3000 forum why this might happen. I'll see if I can resurrect the post.

\AlbertA\ wrote:

No USB 1.1 is fine. It's the MIDI spec which requires a speed of 31250 bits per second. Each MIDI byte is 10 bits, so you can transmit 3125 bytes/second
Now every time you update the expression pedal a sysex message is generated. I've seen it take about 10-20 bytes.

Normally the expression pedal has a resolution of 100 steps. So one full sweep from toe bottom to toe up is = 100 X 20bytes = 2000 bytes. Now rock the pedal a few times, you'll notice it takes you less than a second right? So one full rock back and forth is about 2000 - 4000 bytes !!

But the maximum theoretical transmission with MIDI is 3125 bytes/second!!
So one solution is either reduce the resolution in the expression pedal updates (at least while transmitting or don't do anything (which is why I suspect that with the GNX4, the messages get corrupted and X-Edit crashes because of this).

If you ever updated a hardware synthesizer by sysex and wondered why it takes such a long time, well It's because of the old MIDI standard.

X-Edit communicates through MIDI sysex (wrapped in a USB stream) with the GNX4, and GNX3000.

armada1

Ok it has been long enough we the gnx4 users want x-edit 1.3 can you please put up in the download section. We want the new functions.

armada1

Bump

armada1

bump

aardvarkD

\armada1\ wrote:

Ok it has been long enough we the gnx4 users want x-edit 1.3 can you please put up in the download section. We want the new functions.

I second this. I don't even use X-Edit 1.2, it's just not worth the trouble. AlbertA, you don't have to rock the pedal back and forth to trigger the \"Comm error detected\" crash -- often merely bumping the pedal by accident will do it. And it sucks not to be able to audtion pedal assignments while running X-Edit. Like, does it sound better to assign flanger depth or flanger level to the pedal? I can't make that decision while editing presets in X-Edit, 'cause the mofo will crash as soon as I touch the pedal.

As long as I'm not actually saving a preset or doing a sysex dump, I don't even care that the \"Comm error\" occurs -- and I certainly don't want X-Edit to bother me with it and then lock up! A subtle \"Dude, there was a comm error, do you care?\" message in a status bar somewhere would be more than sufficient.

Cheers,

-- JK

AlbertA

\aardvarkD\ wrote:

\armada1\ wrote:

Ok it has been long enough we the gnx4 users want x-edit 1.3 can you please put up in the download section. We want the new functions.

I second this. I don't even use X-Edit 1.2, it's just not worth the trouble. AlbertA, you don't have to rock the pedal back and forth to trigger the \"Comm error detected\" crash -- often merely bumping the pedal by accident will do it. And it sucks not to be able to audtion pedal assignments while running X-Edit. Like, does it sound better to assign flanger depth or flanger level to the pedal? I can't make that decision while editing presets in X-Edit, 'cause the mofo will crash as soon as I touch the pedal.

As long as I'm not actually saving a preset or doing a sysex dump, I don't even care that the \"Comm error\" occurs -- and I certainly don't want X-Edit to bother me with it and then lock up! A subtle \"Dude, there was a comm error, do you care?\" message in a status bar somewhere would be more than sufficient.

Cheers,

-- JK

Yeah, the expression pedal bug is gone from 1.3 as far as I can tell.

armada1

the 1.2 is ok but why wait when something better is out already!!! I made 3 new patches with 1.2 today. Hmm come to think of it when I hit the expression pedal it did not crap out on me either.....strange. Also programed parameters for A,B and C buttons. Great tool. Thanks too some awesome tuterals by G3456!!! Yeah that guy rocks!!!

But I really want the 1.3 version please digitech give us a download.

PLEASE DIGITECH GODS realease the power of 1.3 x-eDIT!!!!@! :shock:

granitehead

It's not the official way, but Albert posted the V1.3 binaries at:
http://gnx4.org/downloads/software/?dl=software/X-Edit_1.3.zip
along with some appropriate caveats.
I saved all the V1.2 files and just dropped the new ones on top. Worked great! But, the virtual memory leak is still there (new splash screen is cool though...)
- g

bbreland

I'm not sure why, but I've got version 1.3. I was having some issues with my pedal and the drivers and while talking with tech support the guy said he would e-mail me the latest version of X-Edit, he did. Anyway, I have no problems posting it up here, (as long as it won't cause any issues from digitech?)

Let me know.

And yes,

1. There is still a memory leak.
2. The new splash screen looks cool.

Kewlpack

\AlbertA\ wrote:

Yeah, the expression pedal bug is gone from 1.3 as far as I can tell.

Ditto... I don't have any problems along these lines.

lespaulbb

i downloaded the binary and just cut and pasted it into the x-edit folder works fine..... However i cannot open patches from others site like alberta's. it crashes about half as much as its predessor.

AlbertA

\lespaulbb\ wrote:

i downloaded the binary and just cut and pasted it into the x-edit folder works fine..... However i cannot open patches from others site like alberta's. it crashes about half as much as its predessor.

Would you care to elaborate?

lespaulbb

ok,
instead of having:

[code:1]<?xml version=\"1.0\" encoding=\"utf-8\"?>
<?xml-stylesheet type=\"text/xsl\" href=\"Gnx4Preset.xsl\"?>
<Gnx4Preset SchemaVersion=\"1.1\" xmlns=\"http://www.digitech.com\">[/code:1]

as your header you have:

[code:1]<?xml version=\"1.0\" encoding=\"utf-8\"?>
<Gnx4Preset SchemaVersion=\"1.2\" xmlns=\"http://www.digitech.com\">[/code:1]

and x-edit cannot open it.

AlbertA

\lespaulbb\ wrote:

ok,
instead of having:

[code:1]<?xml version=\"1.0\" encoding=\"utf-8\"?>
<?xml-stylesheet type=\"text/xsl\" href=\"Gnx4Preset.xsl\"?>
<Gnx4Preset SchemaVersion=\"1.1\" xmlns=\"http://www.digitech.com\">[/code:1]

as your header you have:

[code:1]<?xml version=\"1.0\" encoding=\"utf-8\"?>
<Gnx4Preset SchemaVersion=\"1.2\" xmlns=\"http://www.digitech.com\">[/code:1]

and x-edit cannot open it.

But 1.3 should open it fine tough...

In any case if you use the g4pfix utility I posted it will correct that...