Search the Community
Showing results for tags 'rebuild'.
Found 2 results
I've been having this problem since I bought the Helix, and blaming myself for it ("oh, maybe I skipped that step..." kind of thinking) but last night I followed every single step and yes, 2.10 is now running --- Intermission --- Let me just take a few seconds to thank and congratulate the team. I'm loving the new models, and I'll surely put the new expression pedal functionality to good use --- Back to program --- 2.10 is now running, smoothly. The thing is, what's failing is the update process. There are certain patches (six of them) that fail to rebuild or import (or export, I'm not sure). Helix doesn't rebuild them properly. One half of the DSP is missing, in some cases it's the first half (what would correspond to paths 1 and 2), and sometimes it's the second half (3 and 4). The first time I was annoyed, but I was still getting acquainted with the machine, so I didn't care too much. I went for my backed up patches (both as a bundle and separate playlists) and tried to restore them, but they were as corrupt as what Helix itself had turned the originals to. "Not a big deal, my patches are still in diapers" I thought. Next update. Same problem. Then 2.0, same problem. By then, it was the third time I had to rebuild those patches. I skipped 2.01 because I didn't want to go through it again, and I didn't really feel the need to update. So last night I went and made screenshots of everything in those patches, to be able to restore them later. Different USB cables, different computers (3 or 4 so far, I'm not sure) and different versions of the editor, drivers, firmware... everything. Any idea before I submit a ticket? Attached are screenshots of before and after
I am still getting the rebuild preset messages when I boot up the Helix with the latest firmware 1.12.0. A minor inconvenience but if you are obsessing over it or want to regain a few nanoseconds of your life you can use the grid I included below to tell you which setlist & preset you are seeing during the bootup process when you see a message like "rebuilding 501" and easily fix it. If you prefer, I designed the spreadsheet with a calculation box where you can just enter in the number you are seeing during the boot and the spreadsheet will return the setlist & preset number/letter. Just select & save that preset and the message for that preset should go away next time you reboot. Not a big deal but it is nice not to see those rebuilding messages any more. The preset numbers showing on bootup start at "0" so the grid does as well (L6 numbers the presets from 0-1023). There are 8 setlists on the Helix with "Factory 1" corresponding to "Setlist" 1, thru to "Templates" which corresponds to "Setlist" 8 in the grid. You will need to save the preset indicated by "Bank/FS" in the corresponding "Setlist". I am making it sound more complicated than it is, if you download the Excel sheet it will be self-explanatory. UPDATE: I noticed that if you modify any parameter on the "fixed" preset no matter how minutely and save it again. The crashing behavior both on startup and when you switch to the preset while using the editor is fixed. Se here is my conclusion. There is a workaround for now but this is definitely a strange bug which I hope gets addressed. Workaround: If you fix any of these presets affected by the "rebuilding..." message by saving them (which causes the rebuilding message to go away) make sure you edit at least one parameter on one of the blocks and save the preset again. It does not matter how small the change is. This will prevent the editor from either not starting or crashing when that preset is selected. Helix Preset Number To Bank Conversion (Share).xls