Corrupted project in eXT 1.4

[Optomadic]

BTW guys heres where the coordinates where for the windows x 1239784 y 376875116. I'm thinking you'd need a screen about this big to view it

[dacaumodo]

Just got back to my computer now and downloading the fix right now.


Thanks a lot Opto! Would this work for any file that's corrupted in this manner? Because it appears like that's what saving eXT projcts from inside Reaper does...

[dacaumodo]

Man you're a genius!! It works perfectly. I'd say this will be useful to a lot of people. I'll post something about it on the Reaper forum too I guess, if it is okay with you

(perhaps something as useful as this it would be a good idea to upload to the Reaper resources site since that's how the problem showed up in the first place).

Brilliant! Many many thanks mate.

d

[Optomadic]

Thanks a lot Opto! Would this work for any file that's corrupted in this manner? Because it appears like that's what saving eXT projcts from inside Reaper does...
I'll post something about it on the Reaper forum too I guess, if it is okay with you...
...it would be a good idea to upload to the Reaper resources site...

Glad to be of help mate but you should also thank InsertPizHere . If not for the insight I never would have thought to dig deeper and try to find a missing window. It just looked like the command was not firing.

The fix will work on any active window that was last opened and off the visible screen (ANY window at all). As I'm not a Reaper user I'm not 100% about this but you may be able to run the fix directly on the eXT Clip window from within Reaper. Actually if you could try this and report back that would be great!

Yes go ahead and post it to their forums also. Please post the link here.
I will try to get on there later and post the fix directly. If I have a problem you can go ahead and post it yourself.

I think I might put together one without the nag screen or even one that will run the fix automatically once the missing window is detected ..

Also I will gey the messages and window properties/info from WinspectorU. Perhaps this will give a clue as to what Reaper is doing to the window and they can fix the bug!

[Optomadic]

Ok I'm all registered over at Cockos. Let me know where to find the thread.

Thanks

[DarkStar]

I think that this might fix this:
http://forum.cockos.com/showthread.php?t=25161

I reckon that dacaumodo was referring to this thread.

If I looked at a corrupted eXT project using a binary Editor where would I find the corrupted MIDI Editor window co-ordinates?

[djsubject]

great tool!

thanks

Subz

[Optomadic]

If I looked at a corrupted eXT project using a binary Editor where would I find the corrupted MIDI Editor window co-ordinates?

Um that would be 1 a scary proposition. I would think that the amount of garbeldy goop you'd have to search through would be tremendous at best.

2 its very dangerous as eXT files do not like to be saved outside of eXT itself (from my experience).

Heres an HTML report of exactly what happens when the popup window opens.

Can you recommend me a bin editor and I will try to find the lines?

edit:

I just realized that even if you were able to find the coords in an editor and fix them you'd be overlooking the fact that Reaper is the culprit behind the issue not eXT. Once you save the project in Reaper the problem would just reoccur .

[Optomadic]

Also I forgot to mention that each time a window is open it generates a new ident number and its class name is generic and duplicate to the parent window(s) (sequencer, dock, main windows) making it virtually impossible to discern it from its parents.

[DarkStar]

If I looked at a corrupted eXT project using a binary Editor where would I find the corrupted MIDI Editor window co-ordinates?

Um that would be 1 a scary proposition. I would think that the amount of garbeldy goop you'd have to search through would be tremendous at best.

2 its very dangerous as eXT files do not like to be saved outside of eXT itself (from my experience).

Heres an HTML report of exactly what happens when the popup window opens.

Can you recommend me a bin editor and I will try to find the lines?

edit:

I just realized that even if you were able to find the coords in an editor and fix them you'd be overlooking the fact that Reaper is the culprit behind the issue not eXT. Once you save the project in Reaper the problem would just reoccur .

asseca pointed me at this one some time ago:
http://www.chmaas.handshake.de/delphi/f ... /xvi32.htm

It's proved very useful for all sorts of diagnostics

[DarkStar]

Those New York? coordinates should be more like tihs:


http://img224.imageshack.us/img224/839/dscoordsat3.png

[Optomadic]

asseca pointed me at this one some time ago:
http://www.chmaas.handshake.de/delphi/f ... /xvi32.htm

It's proved very useful for all sorts of diagnostics

Ahh ok Yea I have that. Its a HEX editor. I STRONGLY suggest against editing ANYTHING in that ..

edit:

Should not this thread title be changed to Reaper corrupts eXT files. I hate giving eXT a bad name ..

[DarkStar]

Nope, as it's not just Reaper.

[insertpizhere]

out of curiosity, i figured this out... with the hex editor you can search for EditPosAndSize in the .ext file.

the next four bytes should be: 10 00 00 00 (this means that EditPosAndSize consists of 16 bytes).

after that, you have the coordinates: x, y, width, height; four bytes each (32-bit signed integers).

there is one of these entries for each sequencer in the project.

of course if you really want to edit .ext files directly, don't do it, and make a backup first...

[Optomadic]

i figured this out... with the hex editor

Can you please explain how?

Thanks