Casio Data Editor problems

[SSMusic]

I have SEVERE Casio Data Editor problems.

It connected to my PX-5s only few times and than  stopped.

Displays "Communication Error" message.

Wether I use Preferences/"Auto search" or go manuallty to "Casio USB-MIDI"

I have Win7-64, I7-920 CPU, 12 Gig Ram.

My "Sonar" SW sends PG## to PX-5s without any problems.

 

 

[Display Name]

We were able to get this solved in the FB group but I am cross posting here for others who may need help.  This problem is still being researched, but here's what worked for this user:

Try running the data editor in Windows Vista Compatibility mode:

Right Click on the Data Editor program
Select "Properties"
Select the "Compatibility" Tab
Select the "Run this program in compatibility mode for" box
Select Windows Vista from the drop down selector
Click Apply
Close the Properties box
Run Date Editor program 


Please post back here if it works or doesn't work so we can track this issue.

Thank you! 

 


 

[jaspeter]

I was having this problem, too.  I've changed compatibility mode and I'll post if it works or not.

 

I'm having another Data Editor problem, although I'm not sure if this is a Data Editor problem or user error.  When I save my Stage Settings, my drum set on Zone 1 keeps disappearing.  Whenever I load the Stage Setting, the Inst Select boxes in Tone Z1 come up as "blank inst".  The first button in the Mixer points to the right drum set, as does the button in the blue ribbon at the top of the Tone Z1 page.  If I then load the drum set file individually from disk, it works just fine.  The drum set is also loaded onto the instrument in the location that the stage setting points (U:20).

Should I be saving a package every time I change a stage setting if it is to include a drum set?  The end goal is simply to store set lists and drag&drop them over to the instrument.  I hope this doesn't include reloading the drum set in each setting.  I'm leaning toward user ignorance/error, because it seems this should be handled pretty gracefully by the system.

 

UPDATE:  I just found out that if I drag and drop the ZPF file, it seems to transfer OK as long as I don't load it into the editor first.

 

UPDATE 2:  Changing the compatibility mode didn't really do anything.  I am still able to recycle the data connection in the Preference menu by pressing the reset button on the far right of the MIDI box, so it isn't a real big problem.

[BelgianChocolates]

Hi there, I couldn't find another topic then this one to ask a question concerning the lack of support for Windows Vista 64 bit with the Editor ? I don't want to mess up things so has anyone tried to install the Editor on a Windows Vista 64 bit version ?

[Brad Saucier]

I suspect Casio didn't make a 64bit editor in order to maximize compatibility.  In other words, it's not really needed.  64 bit operating systems like Vista can run 32 bit programs.  It's the other way around that doesn't work.  I'm currently running the PX-5s Data Editor on 64 bit Windows 8 with no problem.  

[Cass]

Here's how I "solved" this croppy editor problem on vista 32:

Every single time when startup the editor, PX5S must be Disconnected! otherwise the editor gets stuck and crashed.

 

Run editor (takes a minute as it tries to make connection with PX5S USB! even with disabled AutoSearch!).

Then disable AutoSearch in Preference, now connect PX to USB and select manually in the editor Preferences MIDI in/out to "CASIO USB-MIDI".

And close any MIDI USB app. before running the editor as it don't tolerate parallel PX MIDI USB use!

 

---

Any change of an UPDATE FIX for this Editor to stop the autosearch! and able for parallel midi usb use and a VST Editor is welcome!?

[Brad Saucier]

I am running Vista SP2 32 bit and the PX-5s data editor works flawless.  Check for driver conflicts with other midi software before starting the data editor. 

[Jokeyman123]

Cass-I posted something about this for another Casio data editor-I think it was IDES 4.0 for older Casios but is also true for the XW-P1 data editor.

 

Casio describes the correct sequence for these editors as 1) power up computer first, 2) turn on keyboard next but DO NOT CONNECT IT TO COMPUTER YET (sorry for the capital letters but doing for emphasis not shouting). 3) Start up data editor, let it completely starrt up. 4) Now connect the keyboard while it is turned on, to the computer.

 

This is what you are correctly describing in your post, and whenever I've tried doing it another way, like you, the data editor will freeze, crash or just not see my Casio keyboard, so thanks for posting as this is what seems to solve alot of connection problems. I think this is because the Casio USB driver cannot run if another USB driver is running-and Windows doesn't always disconnect another USB driver even if you think it is-I always have to check Windows task manager to see what is still running (processes/services) in Windows to be sure nothing else is conflicting. If there is another USB driver still running in the background, I have to "kill" it in task manager to get the data editors to work right.

[Cass]

Oh Yes, Don't forget the Windows Bug XP/vista/7 max. first 10 Midi drivers Limit, Only the first midi0 to midi9 devices in the midi drivers list will be recognized by any Midi Programs. Any installed midi drivers in/from position midi10 etc. are useless!

 

Lucky there's the KORG MIDI Driver Uninstall Utility (393kB) to delete any midi drivers from that midi list very easily, just point and click to make room. Otherwise you'll need to dig into windows registery.