![]() ![]() ![]() I found myself missing blocks I wanted to select when using the mouse. Then you would be able to instantly jump to different parts of the mod with a great deal of precision. Would allow you to hit for example Left Shift + "T" Instantly play Block 11 on Deck A or Right Shift + "S" would Instantly play block 18 on Deck B. Each mod is divided in to 32 blocks, mapping each block to a keyboard location, for example : I wasn't thinking of the block loop (which would be useful though), I was thinking along these lines. Where I said slice I should have said "block" Re reading what I wrote I notice it makes almost no sense. ![]() Thanks for the feedback! And don't be sorry - the more I can polished I can get this, the better! Are you talking about the aforementioned block loop? Yet again, I think there's a control to choose the division factor, though I'm not sure if it ever worked too well.another thing to look at. ![]() Perhaps I thought nobody would want itĪutodivide, slices - not sure what you mean here. Although no.I did used to have a MIDI button assigned, as you saw in the vid, and it's just a really simple thing that - again - might just be orphaned from the controls. The retrigger - I think that's just a row scrub which I'm using to leap back to the previous row, every row, if you see what I mean. I'm using somebody else's (notoriously fiddly) GUI library for that, so I'll play around.Īuto BPM - I swear I've had that.or something similar.if it still exists in the code, it might have got orphaned from the controls, or it might just not have been written up in the docs.Īuto restart - yup, that's very easy, and would be handy. Non-transparent dropdowns - I think it's possible I'll have to check. I'd have to do a load of fiddly logic checks on incoming MODs, whereas I wonder if the block loop feature would help you here? After all, a loaded MOD is unlikely to be playing out to the room straight away, so you could bash the block loop, adjust the pattern if necessary, then depending on the song you'll probably have a 1 or 2 bar loop of its main beat. Option to load MODs with the first pattern looping - possible, but I think it'd frequently be troublesome. Move the info display to somewhere more visible gotcha. But you're right, 8 makes sense and doesn't hog too many keys/buttons. Abandoning that sort of keycontrol for users with MIDI controllers who'd prefer to dedicate the keyboard to interface stuff makes sense, though I think I'll keep the default roughly in place so that the base-level, unmodified ChipdiscoDJ can always be controlled via a laptop keyboard by someone who's only got a laptop and a few MODs.Įxtra channel mutes - yes! I think they exist, and may or may not have phantom MIDI CC values applied to them, but I was probably thinking to myself "well I'm not going to have 32.so I may as well just have 4". So, I think what your comments tell me is that I need to go back and implement something I toyed with early on and then gave up on - proper configurable controls I'd need a practical but universal way to save them, so I'll have a think about that problem.īut yes, I'd originally been using arrowkeys for patternscan and tempo, with SHIFT as a modifier to control the second deck. Sorry, only just noticed your comments - bloody shitting Wordpress has decided to relinquish its duty to email me whenever somebody's posted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |