Jump to content

DIAA

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by DIAA

  1. Including mixer settings as saved at Registrations memories would be another nice feature the 560M could have... Maybe on some future FW update...
  2. Please check https://support.casio.com/en/support/download.php?cid=008&pid=1263
  3. I have a mini collection studio with synths, arrangers and pianos, from vintage to new models. I play for pleasure, have reasonable experience and demanding expectations. The more I explore, the more I like the MZ's friendliness and specially its flexibility. Its potential is better found from fun, investigation and intuition than from its relatively "dry" manuals. I'd definitely buy it again.
  4. Hello there, I did update MZ's fw to current version 1.50 and I"m extremely happy to share, The above is already done! Kindly check the control labels right over K1 and K2 knobs at the new version screen below. Thank you Casio ! That was a learning to me: before dreaming for a suggested improvement, I should be optimistic, less cautious and update to the latest firmware version. I might be already there... Cheers !!!
  5. I did update MZ's firmware to Version 1.50 and I'm extremely happy to share, that's already done. Kindly check the control labels right over the corresponding knobs at the new version screen below. Thank you Casio! That was a learning to me: before dreaming for some improvement, I should be less cautious and consider updating fw to the latest version. It may be already there ! Cheers !!!
  6. Briefly touching ideas for a new hardware, I'd love to have a touch sensitive area right below the keyboard so that you might trigger something with your thumbs when you have both hands busy on the keys... That could be truly useful to trig a rhythm fill-in or advance a variation sequence step, insert a break, start a fade, etc. It could conveniently allow 2 of such features, since this touch-bar could be split into 2 areas, for convenient use of right and left thumbs. I guess it would feel more ergonomic than hitting an assignable pedal when you're standing up, while leaving the pedal free for additional demands. PS: kindly let me know if I'm not making myself understandable, here or in any other of my posts. I'll be more than happy to clarify what I meant. I'm trying to make myself short and I'm not a good communicator
  7. Still regarding just firmware changes for current hardware: imagine that when creating a new registration, you must change the split point, the chord input type, the harmonizing type and other features to those values you use/like more. Now imagine that it happens in most of the times you do that. Wouldn’t be nice to be able to tell the system: please redefine defaults for such features to "this, that and those" values? So another hint, still for the current hardware, is to add an item in the SYSTEM SETTINGS menu to allow the user to set “default” values for selected features. Factory would initialize those values with their current defaults, but users would have access to change such defaults to their best fit, so that those features would come pre-adjusted to the user taste when building a registration to be saved into the Registration Banks.
  8. Yes, Brad, that's the best thing I could hear and you're right, an update provides the upgrade you mention. That way, it definitely helps in the motivating example I gave. However, if the memory button started blink when you make a change (instead of when the SAVE button is pressed only), I'd see 2 additional benefits: - a reminder that the Registration was modified and not saved (while telling you where to save in case you want it to replace the older content); - guide you back if you'd like to return to the original registration, when you temporarily changed anything live on a performance. Just hints from my own feelings... PS: in order to avoid excessive distractions from a blinking panel, the blink rate could be sync'd with the tempo blink.
  9. I'd just like to echo 2 of BobbyC's suggestions: - Make sliders assignable: MZ's flexible architecture allows wonderful dreams around on the fly control. It would be great to widen usability of the sliders; - Give the assignable foot-switch all the parameters available on the PX-5S - one immediate hint could be control the rotary-speakers speed.
  10. Still regarding the firmware for current MZ hardware, another hint is to move the control area of the assignable knobs (K1 & K2) to the right on the screen, so that they lay above the corresponding knobs. By this move, the touch control on screen would double as LABELs, intuitively identifying the assigned function. No need for additional changes in the screen design, except rotating the Phrase control to the far left (please check attached picture). Currently, driven by the screen, I often reach the Value willing to actuate K1 (or reach K1, when willing K2). This small change would help, specially when playing in the dark.
  11. That's best thing I could hear I'll check, it's probably not up to date or I'd have noticed that. Thanks BradMZ
  12. Sticking to updating firmware only, on the current hardware , another pretty easy suggestion regards Registration Memories: assume you improve some of your Registrations and you want to save it over the older version. It would be nice to be sure which memory it was (as to avoid overwriting another good registration)... Currently, the original registration memory is lit until you modify it, turning off as soon as you change a registration element. It would be nice if it started to blink instead, indicating it was modified, so that you'll know where to save the change without mistake...
  13. I was willing to create a tread with this very same intent. I'm glad I'm not alone and there's one already!!! An improvement suggested is to move the control area of the assignable knobs (K1 & K2) to the right, so that they lay above them on the screen. By this simple move, the touch control on screen doubles as LABELs identifying the assigned function. This change requires a minimum effort in the screen design, simply moving the Phrase control to the far left (please check attached picture). Currently, driven by the screen, I often actuate the Value willing to reach K1 (or reach K1 willing K2). This small change would help, specially when paying in the dark....
  14. Yes, BradMZ, that's what happens, and it's unfortunate. Penalize non-HexLayer tones by limiting such a basic feature to hex layers is not fair, specially under such a powerful and flexible system architecture. I'm an R&D engineer myself and I feel a correction as worth and easily addressable. It's disappointing to see Casio leaving this as "a feature", as it seems to be the case. I suggest we wait and see if somebody else feels differently.
  15. Thank you BradMZ for your prompt and clarifying reply. Your 1st line already helps making envelope parameters and graphs meaningful. I must confess, I started using the instrument out of the box, going after clarification only when surprised by the issue above. In this regard, I think: a) MZX’s envelope description is not clear about such an important difference, even on searching web updated versions; the corresponding screen on the instrument should state “offset” and not “envelope”, as those are substantially different things. Your comprehensive explanation truly helps, also by raising this fundamental difference between Wave and HexLayers tones. THANK YOU ! An issue still remains, however. The Forum and your expertise are valuable help. Let me narrow my original comments above to its final part (amplitude spike). I can add screen pictures or sound files if necessary, but let try to be quicker with an example: Assume, for example, you’re layering a piano and a string (or organ or any non-decaying wave), while playing a slow passage (notes being held for longer, eventually with a sustain pedal). While the piano naturally fades down, the string keeps sounding loud (since an AMP decay to zero is not in its preset). Ironically, this is aggravated by the wonderfully large polyphony, leading to a potentially unfitting note mix - forcing you to prematurely kill it by releasing the key/pedal. In such scenario, you might wish to easily modulate the string AMP, smoothly offsetting its amplitude down during sustain. It’s not rare to expire all decays and an undesired spike will be heard when you finally release the key(s)/pedal because the offset jumps from its programmed silence (negative max) to its zero (midrange) default. Users may have noticed this in a grand finale where notes are kept sounding until they completely fade out: a spike will sound when you finally release key(s)/pedal. The same happens with the PX-560 and PX-5S pianos, where it is particularly bothering as similar layerings are beautiful and quite often used. Thanks once again.
  16. Hello there, this is so basic that either it has already been discussed (and I just can’t find where) or I’m definitely missing something in MZX’s envelope programming. I see much more flexibility than found on simple ADSR envelopes, however, in contrast to former CZ-like 8 steps rate/level programming for example, MZX’s has a different (unnatural to me) sense regarding such parameters, which is also shown in its (nice) graphical display. I understand that MZX’s envelope course has been split into negative and positive halves (those funny numbers revealing a 7-bit representation resolution). Although offering a midrange zero is interesting for pitch envelopes, I can’t understand how this benefits AMP envelopes, for example. I think that a note shouldn’t be sounding before KEY ON. Hence, I don’t undertand what the INITIAL LEVEL before ATTACK means. What worries me much more, though, is the note being forced to end at midrange ZERO value, which is not zero amplitude. A note should stop once you have KEY (and PEDAL) OFF after all decays expire. That, however, does not happen: assume a minimum (negative) sustain level, for example. If the key is held long enough to so that decay is over, a postmortem breath is heard because the envelope jumps from the minimum (negative) to midrange (zero) when the key is released… In other words, you’ll hear a short sound peaking when you release the key after decay expires… My MZ-X500 came in firmware version 1.21, I didn’t dare to update it yet. In anyway, newer versions do not mention anything about this. Since I can’t believe this is a standing bug, I'm surely misunderstanding something. Any light on this would be truly appreciated. Thanks in advance.
  17. Thanks a lot, your comments very appreciated. I'll buy it before it becomes one of those you can't find any longer :-) Cheers !
  18. Thanks for sharing!!! I'm in love and about to buy a 5S but was concerned about fast obsolescence. That's pacifying ;-)
  19. Hello, congrats by this great interaction! I'm purchasing a PX-5S: how can I check the unit's firmware version at the shop? Thanks a lot in advance!
×
×
  • Create New...

Important Information

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