firmware 4.17 issues
- ignatius
- Super Deluxe Wiggler
- Posts: 15654
- Joined: Tue Dec 23, 2008 4:03 pm
- Location: oregon
- Contact:
firmware 4.17 issues
4.17 is buggy as hell for me. doesn't really work. crashes the module. also, doesn't allow paging through parameters. the Z knob still works but pressing it doesn't page through the parameters.
Re: firmware 4.17 issues
Could you expand on what crashes and when?
Some algorithms use Z for something else e.g. reverbs use it as freeze. You can still select parameters with S.
Some algorithms use Z for something else e.g. reverbs use it as freeze. You can still select parameters with S.
- ignatius
- Super Deluxe Wiggler
- Posts: 15654
- Joined: Tue Dec 23, 2008 4:03 pm
- Location: oregon
- Contact:
Re: firmware 4.17 issues
i was exploring the granular pitchshifter and only had access to the first parameter. couldn't page through the other parameters. i tried to change algorithms and it freaked out and would jump around in the algorithm list as i turned the knob. then all the lights in the display got brighter and it did a kind of pulsing thing and freezed up. I rebooted and tried again but got same results.
i put v4.16 back on it and it now works as it should.
edit: i should add that i did reinstall v4.17 thinking maybe something went wrong w/the install and wiping it and starting again would help but it didn't.
i put v4.16 back on it and it now works as it should.
edit: i should add that i did reinstall v4.17 thinking maybe something went wrong w/the install and wiping it and starting again would help but it didn't.
Re: firmware 4.17 issues
4.17 adds the freeze function to the granular pitch shifter, so you'll have to change parameters with S.
- ignatius
- Super Deluxe Wiggler
- Posts: 15654
- Joined: Tue Dec 23, 2008 4:03 pm
- Location: oregon
- Contact:
Re: firmware 4.17 issues
push/turn S right? well, i'll give it another go but didn't work out last time. will report back.
- ignatius
- Super Deluxe Wiggler
- Posts: 15654
- Joined: Tue Dec 23, 2008 4:03 pm
- Location: oregon
- Contact:
Re: firmware 4.17 issues
sucess this time! i think i maybe was a little impatient with the previous install and was jumping around trying to get through parameters and that caused some freaking out of the module. seems fine now that I go slower through accessing the parameters via the S knob.
tldr - user error
tldr - user error

Re: firmware 4.17 issues
the Y input seems non-responsive for the K-1 through K-5 algorithms. It will only change wavetables manually via S knob. Anything I can do to fix this?
Re: firmware 4.17 issues
Y doesn't change the wavetable - it changes the wavetable position, same as parameter 1, not parameter 0.
Is that the confusion?
Is that the confusion?
Re: firmware 4.17 issues
Perhaps, yes. Do you mean the phase position within a single wavetable?
To be clear, changing individual wavetables can only be manually controlled? If so, would it be possible in a future firmware update to use a control voltage input for changing wavetables?
Thanks!
To be clear, changing individual wavetables can only be manually controlled? If so, would it be possible in a future firmware update to use a control voltage input for changing wavetables?
Thanks!
Re: firmware 4.17 issues
> To be clear, changing individual wavetables can only be manually controlled?
Yes - or via MIDI.
Changing the wavetable is not instantaneous - it would be quite glitchy changing it via CV. Is what you want a kind of two-dimensional wavetable lookup?
Could you achieve what you want by combining your wavetables into one giant wavetable?
Yes - or via MIDI.
Changing the wavetable is not instantaneous - it would be quite glitchy changing it via CV. Is what you want a kind of two-dimensional wavetable lookup?
Could you achieve what you want by combining your wavetables into one giant wavetable?
Re: firmware 4.17 issues
Maybe I'm still misunderstanding, sorry. In your video demo for algorithm K2, wavetables (i.e. different single-cycle waveforms) are 'scanned' via LFO into Y input without glitchiness, no? I was unable to achieve this result when I tried myself. I had individual WAV files for each waveform, rather than one concatenated file.
Re: firmware 4.17 issues
In the terminology of the disting a 'wavetable' is a collection of single cycle waveforms. So Y scans through the waveforms, smoothly.
How big are your waveform WAVs? Perhaps they're too big, and the disting can only load one.
How big are your waveform WAVs? Perhaps they're too big, and the disting can only load one.
Re: firmware 4.17 issues
Okay, I thought so. All 63 WAV files in my 'wavetables' folder are 556 bytes. Should I rather include a single concatenated WAV instead of these? If so, this requires a playlist_wavetable.txt file, correct?
Thanks so much for your help with this.
Thanks so much for your help with this.
Re: firmware 4.17 issues
That should be fine - no need to concatenate or make a playlist.
They do however need to be in a folder, inside 'wavetables'. See user manual page 85.
They do however need to be in a folder, inside 'wavetables'. See user manual page 85.
Re: firmware 4.17 issues
Ah, this was the issue: I neglected to nest! I had microSD > wavetables > 00-63.WAV. I appreciate the clarification.
Re: firmware 4.17 issues
One more question: If each WAV is 533 bytes, what is the maximum number of individual single-cycle WAVs the mk4 can scan within a folder?
Re: firmware 4.17 issues
The max is 29000 samples. A 533 byte WAV probably contains about 250 samples, but you could easily check that.
Re: firmware 4.17 issues
PS there's also a 100 file limit.
Re: firmware 4.17 issues
100 file limit for each nested folder? Or for the entire microSD?