Jump to content
Video Files on Forum ×

Zex

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Zex's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. What I'm trying to say, it's just a simple bug of the file saving process during recording. Nothing to do with CPU power. Imagine we have several difference registrations with its own Effects settings like DelRev1 (for registration 1) DelRev2( for registration2), etc. and Tones1 and Tones2... As everybody here knows Before playing we press Reg1 it loads up [DelRev1,Tones1] and it overwrites the current (or default) selected tones and effects if we press Reg2 it loads up [DelRev2,Tones2] above the reg1 and so on so hand playing in a timeline looks like Reg1->[DelRev1,Tones1] playing Reg2->[DelRev2,Tones2] playing Reg2->[DelRev2,Tones2] ... While we start midi recording it writes [DelRev1,Tones1] into the header of the midi file but when we press Reg1/2 it writes only Tones info, by some reason it ignores the effects settings so the timeline of the recorded file looks like this header Reg1->[DelRev1,Tones1] playing Reg2->[null,null,Tones2] playing Reg2->[null,null,Tones2].... and midi player logic replaces those null values with some default ones while playing that's an issue
  2. you're right, partially, every pressing of the reg button restarts all the effects and that's Ok, every effect processor does it, a more complex one tries to minimize the cracks and other side effects while doing so, it tries to mix the old and new effects together w/o any gaps in the sound. Unfortunately this piano cant do it w/o gaps but the main issue here it does not start new assigned effects at all it just starts some default ones. The most obvious difference can be heard in the echos. A midi file already contains all effects but only in the header and only for the very first part until a reg button is pressed, as I said in the prev. comment it does not save intermediate information about the changes in the settings, although the notes and rhythms are saved fine per every registration
  3. No problem, As I've told several times already , I want to switch between registrations during midi recording w/o loosing any effects atm it's impossible. It's that simple. I have a piano registration#1 with long delays and an orchestra registration with same delays and effects. I want to switch between them, but once I switched all affects are gone in the midi file. Any press of any reg button during recording just removes all predefined effects especially long delays (which is the most obvious) And it's not complex it's just reverb and delay(echo) that's it. There's no issues while playing so that effects are not complex (only a midi file does not record that information) It's just a bug that requires a fix, there's no solution to this unfortunately The midi files just don't' store that information correctly (only their header is OK I believe) but all intermediate changes (re effect changes) are not saved correctly (nil values) or not saved at all. and thank you for your help )
  4. I'm talking about system Effects section on the main screen (not about DSP section in the tones they are already set up correctly and saved as a User Tone with required settings, also the system effects settings are saved to Reg#11) I believe it's better to show on the video... midi_record_effects_bug.mp4
  5. I want to be able to record a midi file that saves DSP effects assigned to every registration button so that I can switch between different DSP effects while recording and later I could record that midi to a .wav w/o any additional steps. Or at least it should not reset DSP effects at all when a reg.button is pressed. At this moment it only records the current selected DSP effects, once I press any registration button during midi recording it resets all DSP effects to the default ones and not to the assigned to that button and that affects midi records only, it applies effects correctly while you just playing
  6. The mixer does not help with DSP effects, I use the system track (just in case) >> during a midi recording by pressing saved registrations Yes, that's how I try to workaround the issue while recording to wav, but this requires my presence and preparation in order to remember all the parts where I changed the registrations which takes a lot of time (I dont memorize those moments while playing) I'm composing live and the midi record is usually 999 measures. So after midi recording I need to rehearse it, get all the breakpoints and then wait and be ready during wav recording to hit the registration button to get DSP effects back into recording which is a mess and will take an hour of my time minimum. correct all the settings (including DSP) are brought in to the system midi record initially, but any new registration change does not bring new assigned DSPs, it just resets to the defaults instead. Which is I consider to be a major error/bug, because if it can save DSP settings in the first place why can't it save the new ones And this problem just ruins all my such recordings.
  7. Yes it resets the effects each time but not to the registration effects but to the default ones. And that is not correct and is not an expected behaviour because while playing live it does not reset the effects to the default settings, only midi records contain that error. A midi record should save every change of the registration (no matter the same or a different one) including its assigned effects. But atm it saves the Pressing button event but not the corresponding effects (I believe it saves null values instead) so while playing midi they are replaced with default settings
  8. I use system track and the same exact registration for recording. Also, yes it's not a wave recorder issue, it's a midi recorder issue (internal memory, own casio format, system track). No issues while playing and recording WAV simultaneously in realtime, only in recording a midi (own casio format) and "converting" it to wav later It does not matter which instrument or how many of them... you can use any single piano for reproducing Also another issue here is that the delay effects start working only after the 1st note recorded (if you started recording with the first note pressed), the very first note cracks every time, most likely because the effects settings are applied during the play of the 1st note it does not have enough time to be properly activated before the first note. (but it has a work around - don't start recording with the note you need later... just press something and wait for some time) Steps to reproduce the mane issue 1. create a piano registration with long echo delays so you can clearly hear the echo trails (3-5 long repeats should be fine). Save the registration to, for example, Bank#1 Registration#1 [#11] 2. Start a new "system" midi recording. Confirm that you can hear the trails while playing. 3. play any notes, e.g. Do,Re,Mi and press [#11]. Confirm the echo trails, should be fine 4. play other several notes, e.g. Fa, Sol, La and press [#11] continue playing 5. repeat the prev. step if you want just remember the notes you played and when you pressed [#11] 6. stop recording and press Midi Play button in order to replay your just recorded midi. The very first part of the midi should be playing fine, so Do, Re, Mi echoed 3-5 times as required Wait for the first [#11] hit and listen to Fa, Sol, La, as a result you won't hear the repeats as the previous ones same applies to all notes after next [#11] hits
  9. No you didn't understand I recorded midi, used the same bank with effect settings, during midi recording it played fine no issues when pressing the same Bank#1 button several times within several minutes... e.g. click bank#1 recording midi and playing ...effects are fine ...still recording midi and playing... click bank#1 no issues all effects are fine But then I record WAV from that recorded midi the 2nd and others (recorded) clicks on the Bank#1 button removes all effects and resets it to the default ones e.g. start wav recording / midi started and playing ...effects are fine ...still recording but once the bank#1 clicked (not manually from the midi data) right after that all effects are reset to the original...
  10. So I set all the delays, reverbs up as needed I can here it, everything sounds ok saving the registration, it's saved correctly If I record a new midi file and forget to select the bank section before recording in most cases it ignores the current effects and sets some unknown... maybe default ones. Ok that can be solved partially by pressing bank #... which is required and only then start recording. And it's better to record a new file not overwrite the existent one (it's even worse) The main problem is... I use the same bank#1 during midi recording I can press bank #1 several times to reset to its original settings because while recording I switch tones using the screen But! not the effects And everything sounds perfects while recording no effects are affected by pressing bank#1 But after that I'm trying to record that midi to audio and the first part before pressing bank#1 the 2nd time is fine all effects are correct but once I press bank#1 again it's gone all effects are set to some default or some settings and that is %%% annoying. In order to record w/o issues (or at least to fix it) I have to stay and listen during recording (it could be 30 or more minutes) and be ready to press the bank#1 button to activate the effects if missed Might be it's fixed in the latest update but I don't want' to loose AutoSleep
  11. Unfortunately not very useful in my case, I compose live usually, so I do not know what I need beforehand
  12. Hello! Found 1 major issue (FW 1.10) when recording midi it does not record/overwrite the current rhythm playing, it uses probably the one that was already set on the file selected for recording (same applies to the global effects section) so I selected a midi record that can be deleted to overwrite it with a new record, activated my bank with all the settings and rhythms... started recording played a song with different drum tracks active during performance, they sounded as required but after recording the midi plays another drums sets instead of the used ones... so it ruins the entire record. And selecting my bank before/while recording does not help, it still uses incorrect drums I cannot mute a drum track (during recording midi, it just ignores the accomp. volume settings) I there a way to edit the midi in order to update drums? 2. in arpeggios settings if I press One Touch button it automatically replaces my lower 1 tone with some VA..seq... not sue why, so If I accidentally touch that button during live performance it ruins all the performance, I dont know how to fix that one touch button thank you And I dont really want to update to 1.14-16 because there are other issues in the FWs like auto-turning off does not work, etc... also I had to save all the registrations... and not sure if the will survive the update
  13. thank you that partially solves by problem I couldn't find it either, there's only Hold1 parameter but it's just repeats the sustain pedal I have the 3 pedal unit, but the sostenuto pedal does not holds arpeggios as well, no assignable parameter exists in the controller settings...
  14. Hey! Is there a way to hold arpeggios by a pedal? I need to have arpeggios running in order to use hands for other operations atm sustain pedal just holds the pressed notes not the sequence, so arpeggios stop running if I remove fingers thanks
  15. I've assigned toggling Upper 1 and Upper 2 with the pedal. It can turn them on/off but not as logically expected. so I have U1/on and U2/off by default. I want toggle them to the opposite position U1/off and U2 /on by a single touch. Every further touch converts its current status to the opposite but not to the same values for both. At this moment at the first touch it turns U2 on, so both U1 and U2 become active, at the next pressing it just turns them all off and then turns them all on. 0. on/off (initial) 1. on/on (first pressing) 2. off/off 3. on/on .... that makes that functionality useless for my needs If the last firmware has that fixed, please let me know. thank you
×
×
  • Create New...

Important Information

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