rich.o

Members
  • Content count

    5
  • Joined

  • Last visited

  • Days Won

    1
  1. Hey Casio, any update on this? Is this an unsolvable hardware problem, or a firmware fix?
  2. Exactly what I have been seeing. This is a recode for Casio. Gotta manage those subtle volume increases without jumping. Pretty much kills the thought of recording anything with CC:11 set to expression.
  3. Problem: PX-560 | CC doesn't provide smooth volume control when pedal is assigned to CC11:Expression I bought the M-Audio EX-P expression pedal. Calibrated and assigned it to CC 11 controller so I could control volume with my foot. I returned it back because it seemed to be causing a very noticeable volume jump just as the layer fades in. I was expecting the expression pedal to increase the volume smoothly, just like when you use the keyboard's master volume knob, but that's not what happened. Initially, the sound jumps from off to some low level; and it's definitely a jump and nothing like a fade in. As I further depress the pedal, it's not smooth at all in the first ~25-33% of travel. Once I'm past that first third of the travel, the pedal seems to operate smoothly. But it really kills anything subtle you're trying to do at lower volume levels. So I bought the Moog ACCEP003 EP3 expression pedal. Plugged it in; calibrated it, and same thing - volume jumping at initial fade-in and then along the first 25 - 33% of travel. Kind of like a detented pot, if you know what I mean by that. It's looking like my PX-560 is the problem. Now it could be just my keyboard, but I'm thinking that people just haven't noticed it yet because they're fading in a sound while another sound is already playing so the problem would be masked. That other sound could be coming from their own keyboard or their band mates' instruments. Either way, it probably wouldn't be noticeable. Took a while before I caught it. Anyway, I'm assuming this problem exists for all PX-560's. I'm guessing it's a firmware issue where the code/function that interprets and translates the pedal's variable resistance/impedance at its lowest levels is not granular enough to produce a smooth continuous controller response over the entire range of travel on the pedal. Maybe it's a problem having to do with the characteristics of the pedal's potentiometer, but I'm betting that routine could be written that notices when jump in db is about to happen and branch off to a subroutine that smooths out that volume level transition over time. You'd have to have to play with the timing so that is sounds natural/believable/reponsive, or as close to it as possible, but I bet could be done. Thoughts? Thanks!
  4. I agree. I've got the old Excel sheet thing going, and that's nice for what it is, but come on. There's a big ol' display right there in the middle of my keyboard. Right at the top where it says 'MAIN'. Plenty of room there...
  5. On the PX-560, if you tweak a performance setting - maybe you've un-split the keyboard, or maybe you've made some deeper edits - the blue lit bank button goes out. I can look to the LCD to see what bank I'm using, but no longer know if it's button 1, 2, 3, or 4. I assume that's Casio's way of letting us know the setting has been modified. Can't tell you how much I wish it would not do that. To me, it makes it harder to keep track of what you're editing, or just to know what performance setting you've been using. Any chance of a firmware fix for this? Thanks!! **I originally posted this in the Facebook group (permalink here) and got affirmation on the issue. Someone suggested I repost here. Hope that's OK. Basically, I and some others are asking for a firmware fix for what we've feel is an annoying issue. The fix would involve making the registration bank button blink when you've make a change to a performance setting rather than having the button light (blue) go out completely. This is a big problem if you've made an edit that you now wish to write but lost track of the setting you were editing because none of the buttons (1, 2, 3, or 4) are lit. A blinking light would solve the issue. Thanks for reading!