Jump to content

guanche

Members
  • Posts

    8
  • Joined

  • Last visited

guanche's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

4

Reputation

  1. That's great news! I won't generally consider purchasing a new keyboard until I see that someone has demonstrated that it's worth putting in all the work necessary to get the instrument configuration file up and running with at least one of the mainstream DAWs! So yes, having the file available as a download would make these new keyboards real contenders!
  2. Has everyone already forgotten Casio´s own Mike Martin´s YouTube video, posted in 2015? It includes a great demonstration of Tone parameter tweaks and controller setup with an expression pedal - probably the best controller for a wah wah pedal, though you could at a pinch repurpose the modulation wheel with the set up knowledge he shares on the video. Precisely the sound Carlos seems to be after...
  3. Yes, immediacy is key for a good sequencing work-flow. Still miss my Ensoniq ESQ1 for precisely that reason, using on-board tones in conjunction with external synth modules - Yamaha, Roland. Back then only used external sequencers like the Yahama C1 with pre-Cakewalk Voyetra for post-production, or Atari for collaboration with other musicians, there was less of a dependency on the computer for the basic sound libraries. PX 560M still seems a good compromise. I'm not fully convinced by what I've read so far on the sequencing capabilities of Novation's LS mk iii, or its Ableton lock-in - though I'd love to get my hands back on the after-touch I used to have on my old Roland keyboard - and Novation seem to have made a conscious decision to do away with their user forum, which is not a good sign. Using an extra pedal for expressivity is not a bad substitute for after-touch, and Casio has come through with the goods on a number of key issues in response to user feed-back - long may it continue that way!
  4. Glad to hear you've found another way to skin the Casio cat. It certainly seems to be the case that the Px560m handles SMF1 files differently. Though I was initially concerned by Brad Saucier's announcement of the new default GM-on policy, in practice I haven't had to bother with switching GM mode off in the midi file - with an SMF1 file the header rewrite operation just saves Mixer changes as it should. Thanks for the heads-up. I still miss those old lean and mean pre-DAW sequencers with their full sysEx editing features. Does your old PowerTracks Pro still work on Windows 10? Happy mixing!
  5. Here's a demo of the method just described in my previous post with Dave's uploaded files: atrainF1.mid and brandyF1.mid are SMF1 versions of his files as converted by Cakewalk. ATRNF1M.MID and BRNDYF1M.MID are files saved from the PX560M onto USB media after tweaking a few parameters and selecting internal PX 560M tones for each part/track. atrainF1.mid ATRNF1M.MID BrandyF1.mid BRNDYF1M.MID
  6. Been investigating this problem of the immutable GM voicings, which I had a feeling were being exacerbated by the SMF0 midi file format, which basically stores data from all tracks into one single super-track, unlike the SMF1 format, which stores each track's data separately. I discovered that if you load an SMF1 format version of your third-party General Midi files, the PX 560M handles matters in a much more civilized fashion - changes to tracks in the Mixer - at least on the 1.16 firmware - are persisted as they should be when you hit the STORE/Midi play button combination. (For background on this header rewrite feature added in October 2016, check out https://www.casiomusicforums.com/index.php?/topic/8147-mixing-with-the-mixer/). To save changes in tempo, however, you'll have to record at least a couple of measures of the System track, (or perhaps a new empty track will do the trick if you've got an unrepeatably brilliant performance captured on your System track) So how can you convert an SMF0 format file to an SMF1 file? Dissection of a few modern SMF0 and SMF1 midi files were sufficient to persuade me that my days of hacking raw midi files are happily and hopefully behind me, but I did find, after testing a load of trial versions of Windows 10 DAW solutions, few of which provide flexible export options, that the best solution turns out to be free! Bandlab.com's Cakewalk (find it under the Apps menu header) does the job in a minute: create a new empty project, import your midi file, and immediately save your project as a simple SMF1 midi file. That's it - you can exit Cakewalk, and find your converted midi file in whatever folder you specified on project save. Copy it to your Casio USB media, and if my dozen or so tests constitute a representative sample, then you should be in business to tweak - and persist - your midi imports in the Mixer to your heart's content.
  7. Thanks for a great response - useful info on song header contents. Unfortunately suggestion didn't work - after recording bender wheel and notes to a new track mixer changes are lost in the same way as described in post. Furthermore, I discovered a previously unknown requirement for my work-around to work - a count-in of 1 or 2 bars must be specified, otherwise the mixer changes are overwritten as usual with pre-existing parameters from the song header, or perhaps a separate track header. I rechecked my assumption that it was necessary to re-record each track whose parameters you tweak in the Mixer and it proved correct: changes made to parameters to other tracks were not saved, only those specific to the re-recorded track are saved. Perhaps this suggests the structure of the song and component is slightly different on the PX 560 with respect to previous models?
  8. Had a chance to build up few test songs with the Midi Recorder, and would like to use the Mixer to adjust the settings of each song's component tracks once they have been laid down. Changes made in the Mixer work fine in real-time, controller-style, but these changes only last till the song stops playing or is restarted. When playing, say, in a loop, all tweaked settings are reset to their initial values as soon as the first bar is replayed. Changes are not propagated to the recording itself, and in the Mixer view itself values that have been changed get overwritten with each track's original settings as soon as the song restarts. Absent any mention of the issue in the manual, so far the only way I have found to ensure persistence of Mixer tweaks is to stop play-back before the song loops back to the beginning, and then laboriously re-record the first beat of the first bar of each track using Punch-in. This ensures that the desired Mixer values get written out to the Midi files, and consequently reflected in the Mixer view each time the song starts. Surely there must be a simpler way to persist Mixer adjustments, hopefully just a button-press or screen-tap away: any new owners or Casio engineers got any answers out there?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.