Mclandy

As Brad points out, amp type selection is only one parameter of the Amp Cabinet effect, which is only one possible module in a DSP chain containing up to 4 effects. But to create a tone in which you can select a particular amp, you first have to select (as part of the tone editing process) a DSP (which is not necessarily the same as Tone) that actually includes Amp Cabinet as one of its effects modules. In the Appendix document, the DSP section lists DSPs 801 through 900, and the effects modules contained in each. So you could easily find a DSP in that list which contains Amp Cabinet, and apply it to your edited Tone. Unfortunately, the appendix does not list the additional set of DSPs that are associated with built-in tones. However, a while back I created a complete list of all available DSPs (those included in built-in Tones, in addition to those in the 801-900 range). The document shows each DSP, and which specific effects modules it contains, and in which order in the effect chain. I'll include the link to the forum thread below. Not to add to the confusion, but there is also the Distortion effect module, which does contain a parameter to select between a much smaller set of amp types. But the core purpose of that effect is to add the guitar distortion sound, with the amp type being just a parameter to tweak that effect. But if what you are really looking for a Distortion guitar, you might want to choose a DSP with that effect instead of the Amp Cabinet. I don't believe there are any DSPs available which contain both Distortion and Amp Cabinet effects modules, so that's an either/or decision. So again, to experiment with Amp Cabinet sounds, you need to start with the desired Tone (most likely some Clean Guitar tone, but you can actually do this with any tone, and it doesn't really matter whether it already has a built-in DSP or not), then use the Edit button to start editing the Tone, and scroll right/left to find the DSP settings. Choose a DSP/Tone (1-900) that contains the Amp Cabinet effect, then find that specific module in the chain, and go in and change the Type (cabinet type) parameter to the desired cabinet. If you can't tell what cabinet it is from the abbreviations in the manual, refer to the document link I posted earlier which expands on all the cabinet names. As you change the cabinet Type parameter, you can play the sound on the keyboard to hear what each one sounds like. Just remember, any defined DSP can be applied to any Tone, although the chain of 1 to 4 special effects modules in each DSP definition is fixed. However, as part of Tone editing, you can select the DSP you want to apply, and change any of the parameters within those effects modules (like Amp Cabinet Type). Yes, it's a bit involved, but once you figure out how to change/edit DSPs, it becomes much easier. Here's the link to the forum thread containing the full list of DSPs available, along with their effects chains:

It sounds like you might be looking for this list that a few of us put together a while ago, associating amp names with the abbreviations in the manual. Still, keep in mind that the differences may be subtle, and these are just synthesized models. I believe I saw somewhere that they are based on Kemper amp profiler software. Also, I just realized that you may be looking at the built-in tones (like "128 Clean Guitar 2") and seeing that they have a DSP defined, with a particular amp type as a parameter in the DSP. The keyboard obviously does not provide a complete pre-defined list of built-in guitar tones for every possible type of Amp model available. So if you want to try out a particular amp type, you need to start with one of the built in tones and create your own User Tone from it, and then add (or modify) DSP settings in that User Tone to choose the amp type you want.

Typically you would start with one of the "Clean Guitar" sounds (aka, "Telecaster-like"), and then add DSP amp modeling to that. But other than that, I don't believe there is any "goes with" relationship. It just depends on the sound you're looking for.

Thanks, and let me know how you make out. If you try out the function for importing Styles, you will probably find it has a CT-X "bias" to it as well, as the mappings I've built up over time take advantage of the full range of CT-X tones and drum kits. So after doing an Import, you may find some "Undefined (bank/PC)" tones listed, as well as possibly some unassigned drum sounds. The good news is that the editor makes these fairly easy to change, plus you also have the option of adding superseding mapping definitions to the "remap.txt" file to change how the tones are converted. Aside from that, I think all the other functions (other than the disabled CTX-only ones) should work for the PX560, but let me know how it goes.

Release of new version 1.1 with enabling for non-CTX keyboard support I have just released an updated version of the program that now includes limited support capability for non-CTX keyboards which use the AC7 format. As I suggested in my last post, I have updated the Preferences dialog to allow for a 3rd mode for "Non-CTX" keyboards. When that mode is enabled, another dialog option is enabled to specify an external "alternate patch" file for other keyboards. At program startup, that file will be loaded in place of the internal CT-X Tone and Drum lists, so the program will show the Tone and Drum descriptions that are valid for the specified keyboard. This mode will also disable a couple of features that are only available on CTX keyboards (the Tone EQ settings, and Drum kit substitutions). Note that support for other keyboards than CT-X depends on the creation of these alternate "Patch" files. These are simple text files, although as you might expect, they contain a lot of information. I am not volunteering to build these for all the different Casio keyboards, but as an example and model I have created one for the PX-560 and included it in the download package. The first few lines of the file describe the content and syntax, for reference. Creating one of these might look a little intimidating at first, but they can be done with relatively little typing if you know how to copy and paste into a spreadsheet, move columns around, and export content in CSV format. Perhaps this represents a good opportunity for some community collaboration. One other change in this version is that I have decided not to list User Tones by default in the tone list in the "Tone and Mixer Settings" properties page. In general, it's not a great idea anyway to use User Tones in Rhythms (anyone who has tried this probably knows why), plus with this program's ability to access the Rhythm file's built-in settings for DSP definitions, Tone EQ controls, and Drum Substitutions, there is even less reason to consider using User Tones. So basically, including User Tones by default mostly just "clutters up" the Tone list unnecessarily. However, User Tones can still be accessed and used simply by typing "user" in the Tone list filter and clicking "Apply", which will cause them all to be listed and available for selection. Beyond these changes, this version just includes a few enhancements in operation verification (things to prevent/protect users from unintentionally doing wrong things). Link: https://sourceforge.net/projects/ac7editor/files/ Let me know if there are any questions. By the way, does anybody know if Chandler Holloway is still around, or if not, is there anyone who now fulfills a similar role? Also, I see there have been a few downloads - any feedback?

@mrmr9494, @Jokeyman123 After looking in a little more depth at the PX560 Tones and Drum kits, I see enough differences that it would probably be confusing trying to edit using the CT-X data. Sometimes the same patch numbers have slightly different names, or are even swapped from what they are on CT-X. Also, Privia has a ton more Piano tones (makes sense), which would not be accessible. There are some drum kit differences, too. I do, however, think I could find a workaround for the repetitive numbering in the Tone descriptions. I wanted to make the program as simple and self-contained as possible for CT-X users (which was the primary focus), which is why I embedded the tone and drum descriptions in the program for those keyboards. However, I used to have that data in separate files. I'm thinking about the possibility of adding a Preferences option to specify an alternative, external file for the Tone and Drum data records, which would get loaded at startup in place of the embedded ones. Perhaps that setting could also "switch off" any CT-X-only features. That's something I'll muse over while waiting for some feedback from the early users.

I just wanted to mention, as @Jokeyman123 commented, you may notice that there is a newer version (5.0) of ooREXX out there, and there is in fact a way to install that with the 4.2 ooDialog manager and get my program working with it, but that gets a bit complicated and is not worth it unless you are doing your own ooRexx development. It's much simpler to stick with the 4.2 version of ooRexx and ooDialog, especially if you are installing them just to support this program. But if anyone wants further details, let me know.

Unfortunately, I don't have any other keyboards to test on (I have a CT-X5000), so I can't be sure, but my belief is that almost all of the functions should be valid on other keyboards, except: DSP definitions - I know the CT-X supports 2 in a rhythm, some might support only 1, or none at all Tone EQ settings - I'm pretty sure those are specific to CT-X Drum remapping into another kit - I think that is also specific to CT-X Even if you were to add any of those to an AC7, I think the other keyboards would just ignore them, but would still play OK. And if the source AC7 did happen to have some of these (say, if it came from a CT-X), you can use the editor to remove them if desired. In any case, I think the resultant AC7 should always be "safe" to play on those other keyboards, so feel free to give it a try. As you point out, differences in bank/patch information is a problem, perhaps excluding some instruments and including others that won't play on the other keyboards. I tried to restrict the Tone choices to "valid" tones on the CT-X, to make it more foolproof. Even if the Tone "numbers" and/or descriptions don't exactly match, any Tones with equivalent bank/patch numbers on both keyboards should be fine. I was thinking maybe it wouldn't be too hard to add an alternate Tone set for PX-560, but taking a quick look at the PX-560 tones, I see that they re-use the same "Tone numbers" in each instrument group (that is, Tones are grouped by Pianos, Guitars, Organs, Strings, and so on, and all begin with a Tone number 001), and I know that would unfortunately be a problem as I depend on those being unique. Also, it looks like they intermix the User tones with the built-ins in each group (I guess that means the User tones in each group must be derived from that type of tone?). Very different layout. Anyway, I'd be interested to hear how you make out (and the community probably would, too). P.S. Also noticed that the drum kits are very similar, but do have some differences, especially with regards to which notes default back to Standard Kit 1.

I am announcing the availability of a program that I've written, which provides a set of functions for editing AC7 files, most specifically for CT-X model keyboards. The program is hosted and available on the SourceForge web site as an open-source project. Here is a summary list of the functions it provides, several of which go beyond what is available on the keyboard itself: Change the Tones (voices) used, and the mixer settings Apply EQ filters to the Tones Shift notes in tracks up or down in octave increments Add new notes that mirror the existing ones, at octave offsets Change all instances of a drum note to a different drum note Map a drum note to a different drum note in another drum kit Shift note velocity ranges in tracks Change Breakpoint settings in tracks Set upper and lower note transposition limits in tracks Create and edit rhythm-based DSPs (up to 2) to apply to Tones in the rhythm Export from an AC7 with 4 variations/fills (CT-X3000/5000) to one with 2 (CT-X700/800) Import from a Style file to an AC7 (*) Browse folders containing AC7s, with the list showing some internal AC7 data for each Show a detailed summary of all the tracks in an AC7 Unlock ‘Fixed” tracks in an AC7 so they can be edited on the keyboard (within limitations) Create fade-in or fade-out Intros and Endings * Importing from Style to AC7 is far from an exact science, especially for Style files from newer top-of-the-line keyboards which have more features that have no equivalent on the CT-X. Poorly-formed Style files from 3rd party sources can also be very problematic. So this is only a “best-can-do” with no guarantees, but it works in many cases. Note that this program is not a MIDI editor or player, nor does it convert random MIDI files into an AC7 (MIDI files by themselves actually do not contain nearly enough information to do that). Also, at this time it only runs on Windows, and the only supported language is English. The best place to start is with the Wiki information on the project page, which is available under the Wiki tab. Please read it first!! The package is simply a downloadable zip file, and can be found on the Files tab. The project page also includes some screen shots, and can be found here: https://sourceforge.net/projects/ac7editor/ Important: The program is written in a language called ooRexx, and requires the installation of a runtime environment along with a Windows Dialog add-on package called ooDialog. These are fairly small, lightweight packages, and are also hosted on SourceForge. See the Wiki documentation for direct links to the install packages, and important information about installing them and the program. This should be a bit self-evident, but this program does modify AC7 files, and just like any editor it allows you to save those modifications to the existing file. So it's best to have a "working" folder to which you can copy AC7 files for experimentation, while keeping a safe copy of the originals somewhere else. While most of the edit changes are reversible, a few are not, so make sure you have a backup. I will try to respond to questions and problems regarding the program as much as I can, but with limited time for support I will probably focus primarily on specific problem reports like crashes or incorrect behavior, and may not respond to things like additional feature requests, or basic questions relating to information that can be easily found in the Wiki, the keyboard manual, or on the internet. Lastly I would like to acknowledge @mrmr9494 and thank him for his assistance and for blazing the trail on Casio data format analysis. Have fun!

That's exactly right, you use a USB printer cable (Type A connector on one end, Type B on the other) to connect your Casio to a computer. Get a good quality one if you need more than 10 feet of length.

Of course, the other option is to record an Ending variation of the accompaniment in which all the parts fade out.

How about this: https://archive.org/details/manual_CTK1000_OM_CASIO_EN Note: If you download the "PDF with Text" version, you can do text searches in the PDF; otherwise, I believe the PDF just contains non-searchable page images.

Unfortunately, .MRF files cannot be converted to MIDI. Not only are they in a Casio proprietary format with no converter, but they don't include all the data that would be needed for the conversion (they depend on mechanisms in the keyboard to reproduce). Primarily they are intended just for backing up and restoring songs between the keyboard and a computer. The higher-end CT-X keyboards do offer the option to save recorded songs to a USB drive as MIDI files, and that is one of their added values. P.S. As an alternative, you can record the song as MIDI by using MIDI software of your choice on your computer, and having it record when you have the keyboard play the song (causing MIDI events to be sent to the computer). How to do that depends a lot on which software you use.

When you go to save the recorded song to your flash drive, select the "MltR SMF" option instead of the MltRec option. That will save the song as a Standard MIDI File (SMF) with a .MID extension. The .MRF files are a proprietary Casio format, mainly just intended for backup and restore. There is no converter for .MRF files that I'm aware of -- besides which, MRF files don't necessarily contain all the data needed to play back a song, they are heavily dependent on mechanisms in the keyboard.

Sie können der CT-X keine neuen Töne hinzufügen, aber Sie können einen der vorhandenen eingebetteten Töne bearbeiten (seine Eigenschaften ändern) und ihn als "User Tone" in den Slots 801 bis 900 speichern. Um einen Ton zu bearbeiten, wählen Sie ihn zuerst aus und drücken Sie dann lange auf die Schaltfläche "Function" (Edit). Ein bearbeiteter "User Tone" kann wie jeder andere Ton verwendet werden (z.B. in einer Begleitung oder Registrierung)