Jokeyman123 Posted November 26, 2019 Author Share Posted November 26, 2019 I will try. Just out of computer curiosity-any idea why that will work, and the other slots don't? Sounds like a memory addressing issue. As when windows OS tries to put code in a memory address that it isn't supposed to, you get the "blue screen of death" and is usually due to a programmer's error in writing code. Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted November 28, 2019 Author Share Posted November 28, 2019 Assigning edited kits to those memory slots works as expected, no warbling sound when recording. A rather strange bug, please let me know what causes this and if it can be corrected. I also notice a strange delay sometimes when I am editing a tone or hex layer, usually doesn't crash completely, but seems like it is going to. If I wait a minute or two, it will work again but it does happen. Quote Link to comment Share on other sites More sharing options...
Ricardo Bastianello Posted January 8, 2020 Share Posted January 8, 2020 Hello Mike, how are you doing? I'm trying to get the Moog Inspired Set sound for my Casio XW-G1. I saw you did a really great job but I don't know how to find the Moog sounds. Would you send to my e-mail please? I'd be very glad. Thanks a lot man. Email: ricardobastianello@hotmail.com or ricardobastianello@gmail.com. Quote Link to comment Share on other sites More sharing options...
Brad Saucier Posted January 8, 2020 Share Posted January 8, 2020 @Ricardo Bastianello Our downloads section has that and more.... 1 Quote Link to comment Share on other sites More sharing options...
Mike Martin Posted January 8, 2020 Share Posted January 8, 2020 On 11/20/2019 at 2:29 PM, Jokeyman123 said: Thanks much Mike. Just FYI - there is a new firmware in final quality control that fixes this issue. It will be released in the next couple weeks. 1 1 Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted January 8, 2020 Author Share Posted January 8, 2020 Wow, really! that is tremendous, thanks much Mike. Now that is real "back-end" support. Fantastic. Jokeyman happy, now me get cookie! 2 Quote Link to comment Share on other sites More sharing options...
kybdsammer Posted January 9, 2020 Share Posted January 9, 2020 That's great news. Thanks Mike! Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted January 9, 2020 Author Share Posted January 9, 2020 Mike-do you know if anything else might be updated or changed with this firmware-or is it strictly for this specific issue? I am on 1.15 ver. Quote Link to comment Share on other sites More sharing options...
Brad Saucier Posted January 9, 2020 Share Posted January 9, 2020 I'm sure they will list the changes on the download page if anything new is added. "Improving certain operation" is the default response for what we might call 'squashing bugs'. Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted January 9, 2020 Author Share Posted January 9, 2020 Yes, "improving certain operation" is always helpful.............or maybe better...certainly improving operations.....I'd prefer to stay out of the operating room myself.But I am grateful this bug is going to be fixed, a real plus for what I do with programming. Shows Casio does pay attention to us, very nice. Quote Link to comment Share on other sites More sharing options...
RichF Posted January 29, 2020 Share Posted January 29, 2020 Hello all, Thanks for your patience. The PX-560 version 1.16 firmware updater is now available at https://support.casio.com/en/support/download.php?cid=008&pid=2629. It corrects the issue described here. -Rich 1 Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted January 29, 2020 Author Share Posted January 29, 2020 Got it, I'll post results and if I find any other improvements in this firmware not described here. Great! Has anyone else done this yet? I have never had trouble with PX560 firmware updating, but still a little nervous after pooching my XW-P1 which fortunately Casio was very generous in restoring for no charge, saved my bacon there! Off I go.... Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted January 29, 2020 Author Share Posted January 29, 2020 OK so far-I don't see any additional features in any of the settings or menus. Every function I tested is working correctly so far-but haven't gone into great depth-into editing DSPs, tones or hex layers yet-my rhythm and tone edits and multitrack recordings are working as before. I still haven't checked the "bug" discovered with my edited drumkits used for recordings that this firmware updates designed to fix-that will be next on the list. Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted February 5, 2020 Author Share Posted February 5, 2020 Happy to report-finally got around to checking this specific bug fix and it solved the problem. I substituted all my original drumkit edits-used in a multitrack recording-and every one worked without a problem. Very nice and professionally executed followup on this, thanks Casio! 4 Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted February 6, 2020 Author Share Posted February 6, 2020 Just another followup on this-the ability to edit a drumkit on the PX560 is a very handy bit of work. Pitches for individual drum tones can be shifted quite alot to make custom kits which is what I've been doing. More depth with bass drums for example-or creating the opposite-high pitched toms, changing ride and crash cymbal's apparent sizes-very nice and pretty easy to accomplish. Pick a kit as a tone from the main menu, click edit, save and done. Makes a big difference even shifting a snare up or down a bit, and the samples are good-allow for pretty long pitch changes without sounding distorted or unrealistic. another programming trick-shifting the pitch to extremes on an individual drum sound can make it sound like something entirely different for special effects, a trick I learned on my SY77 years back. some of the weirdest sounds are created on the SY77 like this-I think I can do the same with the PX560 now that tis bug has been fixed. Nice! 3 Quote Link to comment Share on other sites More sharing options...
kybdsammer Posted February 7, 2020 Share Posted February 7, 2020 Great to hear the firmware update fixed the issue. I haven't had a chance to update mine yet but hope to do so soon. Here is the reply I received from Casio America that goes beyond the "Improving certain operation" description. It confirms what we expected. Thanks to Mike and the Casio team for being so responsive. -------------------- We improved the drum sounds in the ver.1.16. There was unnatural shaking of this sound when it's recorded as MIDI. -------------------- Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted February 7, 2020 Author Share Posted February 7, 2020 That's what started all this in the first place, I know I'm the troublemaker! the drum sounds-the actual samples are the same as the factory ones, but now I can edit away, save the edited set and use this to record with the midi recorder without the "unnatural shaking". and so far so good. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.