- Last Active
- No Roles
Dont know if the shift button has a backlight? If it does, double tap to arm shift and turn on the light, and double tap to unarm and turn the light off.
In song mode I use much more often instant mute, in track mode I prefer to enter sound edit via the direct access via pads (UI had to change a bit to allow selecting another param while shift is armed). The shift button will be the first to wear out I fear.
I want to see velocity without looking up the value.
Steps are colored based on their pitch. 64 RGB values are used to fill 128 slots. Pitch coloring looks nice. But it doesnt give me much information.
A configuration option or a shortcut to switch between pitch mode and velocity mode would be cool.
In velocity mode all notes are colored based on their velocity value, cool if shift&up/down for changing the base color would still work. A bit different for Kit Track view but i guess i could work the same.
Hold SYNTH/KIT and turn Select knob to change synth and kit banks.
A synth or kit bank is a folder on the SD card located in the preset folders.
When saving a preset allow to change the folder.
- group synth presets: bass, lead, arp, ..
- easily add user banks
- pain free file browser navigation when there are loads of files
Just want to share a test I did to evaluate sync stability or "tightness" for live usage.
Got a very good impression, hope Deluge gets added here http://innerclocksystems.com/New ICS Litmus.html, I suspect Deluge would look very good.
Did this test with every hardware sequencer I got:
Slave sync is the tough part. Usually master sync is not a problem. So I set up an external hardware sequencer (Cirklon) to slave Deluge. Both seqs play a 808 kick pattern (so I get 2 sounds). If the sync is tight it sounds like one kick drum with a flanger effect. Drifts are audible very quickly. Now, the hard part for sequencers seems to be to ensure perfect slave sync in any situation (busy cpu, io, fast tempo, ..), most of my hardware sequencers cant provide stable slave sync all the time (old Akais and Cirklon do). For example Analog Rytm is likely to drift if I change patterns quickly.
Did not notice any sync problem, very cool! Tested with switching sections, loading songs, etc. Likely there are situations where Deluge would loose sync, maybe if you slice a large sample .. However, stoked about the result!
cool if we could control stutter with pads, much like the (for now discarded) velocity pad mode.
so u could jump to different best division directly and generate rhythmical mashup.
Adding new exciting features is much more fun than debugging existing code - believe me, i known what i'm talking about, being a soft- and hardware developer for more than 30 years now.
But - this is a comercial product, lots of people have paid for it. The crash reports on facebook are frightening, and i had a crash and lost my work recently too. A total fun killer! And nobody likes to use such a machine in a live performance. So Rohan, get a cup of coffee and debug, debug, debug... Look for critical sections, memory leaks, stack overflows and all this kind of stuff. Reliability is most important.
Thats slightly disrespectful, mate. Do you provide loads of unresolved bug reports?
You refer to one single crash u had and frightening fb reports.
What happened to you exactly? What did u loose? I am looking forwards not to be frightened by your report.
Deluge has been rock solid for me. Sure, i do a backup of the SD card now and then, but thats because SD cards (especially cheap ones) cant be trusted in general. Plus, i am very capable of loosing a SD card somewhere 😋
Yeah, I lost some Deluge work a very few times in 2 years. Due to low battery or a rare freeze. For example when slicing a long sample into many slices. Never lost more than an unsaved song. Never had a corrupt xml file.
Performing live with the Deluge is a no-brainer for me, Deluge is made for that and delivers.
always in for more fx.
what do you use as sidechain source? 808 kick drum?
step automation: there is a workaround to mute a note row, and do step automation there. notes are muted but automation events are still applied.
affect entire does not work as assumed.
"affect entire" really is a misleading naming IMHO.
you never affect more than 1 parameter. you just access another fx chain. took me a while to figure that out.
eg. if you change volume with "affect entire" on, you just change the volume on the track effect chain. the volume settings of the fx chain for the individual rows are not affected.
so, if we keep the current behavior and add changing multiple parameters at once, we have a total mess IMHO: some params would be changed for all individual samples, others change the track fx chain.
however, I wished to have that functionalty too. like setting sample mode to CUT for all samples at once.
my proposal would be to change the naming of "affect entire" to something like "track/global fx". and implement batch changing params for kit tracks in a different way. for example holding shift while turning the select knob could set the params for all samples in a kit (if a kit row has that param).