Search by Text Search Results: "defragment" Found "defragment" 2 times here: Product: Q series Product: mQ series Q: What can I do when "Reorganizing Memory" appears? A: What can I do when "Reorganizing Memory" appears? 1. When dumping data from MIDI: the dump where the message appeared and some later dumps (if it was a complete soundset) were not received correctly. Stop and rewind the sequence a bit and resume when the message is gone from the Q's display. 2. When storing from the Q itself: the last store could not be completed due to fragmented memory. Try to store again right after the message has vanished from the display. You may have to repeat this procedure a number of times. Why do I get this message? Data is stored in so-called Flash memory. Data in Flash can't be overwritten directly. The Flash must first be erased, however the erase will affect a large block or sector of data at once. That sector can then be written over once with new data. When the Q needs to save data, it looks for already erased space of sufficient size. If it finds space, it writes the data to it and then invalidates the data at the old location, creating a fragment. If it can't find space, it has to collect all valid data in one or more sectors, erase these sectors, write the valid data back (defragmenting it on the way) and check if enough space has been freed by the procedure. This takes some time during which you see the message "Reorganizing Memory". The propensity of the memory to need reorganization is roughly proportional to the number of store operations and the amount of memory in use. You can not delete memory once you've started using it, except for erasing all user memory. For instance if you ever stored data to C100, that slot will always take up memory, even when it is later initialized. If there is not enough space to temporarily save the valid data of sectors to be erased, you get the message "Flash hopeless full". It may go away after a power cycle, but usually the only thing you can do at this point is to back up the Q and erase the whole memory. How can I avoid this message? 1. Avoid fragmentation: Store intermediate edits to QCard or to a seqeuncer instead of directly to the Q. Also try to use always the same slots for edit and use a consecutive range at the end of memory. This helps to keep fragmentation to as few sectors as possible. 2. Keep lots of empty memory: use as few slots in memory as possible. After erasing memory, do not send a complete sound set. For instance if you don't use the sequencer, leave out the patterns. Send only the sounds you plan to use, try using single sounds sent to edit buffers to find out which are the ones you need. 3. Power cycle your Q occassionaly during prolonged edit sessions. The Q checks and reorganizes the memory during boot when fragmentation is over a certain limit. By keeping the number of edits between reboots sufficiently low, the Q is able to keep enough non-fragmented free space around. How can I defragment memory? When fragmentation exceeds a certain limit, the Q is unable to reorganize the memory sufficiently well and you'll get this message more and more often. To recover, back up all user data ("Dump All" Sound, Multi, DrumMap, Pattern and Global) first. If you've just edited a handful of slots and the rest is straight from the factory set, you could also save these as single dumps. Make sure your backup is received by the Q when sent back and note the setting of DevID in Global Menu. Then cycle power and press the Multi (not Multimode) button during boot. You will be asked if it's OK to erase the DATA Flash. Press Play/OK to confirm. You have to set the DevID to the value you've noted. Send back the Global data backup now to get the rest of the global setup right. Now the difficult part: you should not send the complete backup as it is, but only those dumps that you are going to use! Otherwise you end up using more memory then before. Usually you would want to use all sounds, so this backup can be sent right away to fill all slots from A001 to C100. For Multis, Drum Maps and Patterns only the first few slots in each bank are used. One solution is to stop the sequencer after sending the first few entries. The better solution is to use a bank manager like SoundDiver and just send the entries that are of interest. You can also edit the event list in your sequencer and delete the superfluous dumps. If you've backed up single dumps, re-load the appropriate factory soundset (skipping any unnecessary slots) and then send each of your backups back to the Q and store them by hand. [ Home ] 10.05.2024 07:33:55 Waldorf Time