Home | ER-101 | ER-102 | ER-301 | Wiki | Contact

V0.3.x Firmware Workout: Better late than never

feedback

#700

I wholeheartedly second this. Seamless loops = :heart_eyes:

And of course, so amazing to have a pedal looper in the 301.


#701

I think there is a bug with “slice on onset” in the newest firmware. i was trying it with a file that has lots of clear pauses and the slice markers weren’t corresponding with those parts at all.

i took another look at some drum breaks which I’ve used slice on onset with successfully and the new firmware’s results look kind of random by comparison.


#702

+1 for trails mode


#703

+2 :+1:


#704

Yes ++

Also, I’m wondering if this could somehow be accomplished using the middle layer SDK that Brian released. Looked at the Pedal Looper lua code for a few minutes, but it’s just slight beyond my understanding and the overdub functionality doesn’t seem to be listed there. I was looking for “description = ‘Overdub’” or something of that nature and state changes, but didn’t find it.


#705

I can believe it. Onsets doesn’t really equate to pauses. The onset detection algorithm currently uses spectral flux (changes) to detect onsets, not loudness. As usual, it is a work-in-progress :wink:


#706

I implemented all of the state changes for the Pedal Looper on the C++ side. Lua code is never executed in the DSP thread. For this reason, you should only consider the Middle Layer as a more flexible patching environment.


#707

Yes, +1. I find myself always “double-clicking” to mimic this behavior, would be cool if it’s standard, or an option.


#708

+1 seemless loops


#709

Alrighty. No more votes for this are necessary :wink:


Pedal Looper
#710

damn, just when I was about to cast my vote. :frowning:

Democracy is at risk! :smiley:


#711

Just upgraded to this and it really feels like a step forward. Found it much easier to navigate around, so thanks @odevices.


#712

experienced 2 ‘Oops’ crashes , I’m afraid I was pushing it :slight_smile: Here’s the log:

—CRASH REPORT BEGIN
Time Since Boot: 4951.958s
Version: 0.3.13 (unstable)
Boot Count: 78
Mount Count: 2
Error Message:
X:/Persist/serpent.lua:90: not enough memory for buffer allocation
stack traceback:
[C]: in function 'table.concat’
X:/Persist/serpent.lua:90: in upvalue 'val2str’
X:/Persist/serpent.lua:85: in local 'val2str’
X:/Persist/serpent.lua:105: in function ‘Persist.serpent.serialize’
(…tail calls…)
X:/Persist/Serialization.lua:11: in function 'Persist.Serialization.encode’
X:/Persist/Serialization.lua:40: in function 'Persist.writeTable’
X:/Persist/Preset.lua:18: in function 'Persist.UnitPreset.write’
X:/Persist/init.lua:652: in function 'Persist.quickSave’
X:/Persist/QuickSaver.lua:207: in function ‘Persist.QuickSaver.save’
(…tail calls…)
X:/Persist/QuickSaver.lua:151: in local 'handler’
X:/Base/Widget.lua:151: in function 'SourceChooser.ExpandedHeader.sendUpHelper’
X:/Base/Widget.lua:141: in function 'SourceChooser.ExpandedHeader.sendUp’
X:/Context.lua:192: in function 'Context.notify’
X:/Application.lua:142: in upvalue 'notify’
X:/Application.lua:243: in upvalue 'dispatch’
X:/Application.lua:317: in function 'Application.loop’
x:/startup/start.lua:54: in function <x:/startup/start.lua:47>
[C]: in function 'xpcall’
x:/startup/start.lua:57: in main chunk
[C]: in function ‘dofile’
[string “dofile(‘x:/startup/start.lua’)”]:1: in main chunk
Recent Log Messages:
—CRASH REPORT END
—CRASH REPORT BEGIN
Time Since Boot: 688.974s
Version: 0.3.13 (unstable)
Boot Count: 79
Mount Count: 1
Error Message:
X:/Persist/serpent.lua:90: not enough memory for buffer allocation
stack traceback:
[C]: in function 'table.concat’
X:/Persist/serpent.lua:90: in upvalue 'val2str’
X:/Persist/serpent.lua:85: in upvalue 'val2str’
X:/Persist/serpent.lua:85: in upvalue 'val2str’
X:/Persist/serpent.lua:85: in local 'val2str’
X:/Persist/serpent.lua:105: in function ‘Persist.serpent.serialize’
(…tail calls…)
X:/Persist/Serialization.lua:11: in function 'Persist.Serialization.encode’
X:/Persist/Serialization.lua:40: in function 'Persist.writeTable’
X:/Persist/Preset.lua:18: in function 'Persist.UnitPreset.write’
X:/Persist/init.lua:652: in function ‘Persist.quickSave’

X:/Base/Widget.lua:151: in function 'SourceChooser.ExpandedHeader.sendUpHelper’
X:/Base/Widget.lua:141: in function 'SourceChooser.ExpandedHeader.sendUp’
X:/Context.lua:192: in function 'Context.notify’
X:/Application.lua:142: in upvalue 'notify’
X:/Application.lua:243: in upvalue 'dispatch’
X:/Application.lua:317: in function 'Application.loop’
x:/startup/start.lua:54: in function <x:/startup/start.lua:47>
[C]: in function 'xpcall’
x:/startup/start.lua:57: in main chunk
[C]: in function ‘dofile’
[string “dofile(‘x:/startup/start.lua’)”]:1: in main chunk
Recent Log Messages:
—CRASH REPORT END


#713

Functionality/UI idea: optional tool-tip mode wherein momentary shift+Mx produces a tool-tip message for that parameter in the contextual display. Could be enabled/disabled in admin.


#714

Unfortunately, I think that will interfere with quicksaves (SHIFT+M1).


#715

Looks like it just ran out of memory.

Edit: Sorry, I don’t mean to just state what might appear to be the obvious problem. I only mentioned it because you said you were pushing the 301, and it is possible that instead of this being a bug, you simply pushed it too far; memory wise I mean.

2d


#716

Is it possible to actually see the figures/number changing when there is an external modulation? ( at the moment we can only see the slider moving) Thanks!


#717

Yes. A setting for this was added in v0.3.09:

ENHANCED: Unit Controls > Digital readouts on the modulate-able controls can now show the post-modulation value (instead of the bias value). Just go over to Admin > System Settings to enable the new behavior.


#718

Sorry missed that…!


#719

I just wanted to say that I really appreciate the ease of updating the firmware on the ER-301.
I’ve just been through the rather tedious process of updating the firmware on my Intellijel Shapeshifter and the Rainmaker. I love my Intellijel modules, but updating the firmware on them is a real pain for a non-genius like myself. A process involving two different types of usb cables, two different apps, one of them Windows only and borrowing a Windows-laptop and finding a usb driver.
Thanks.