borfo
About
- Username
- borfo
- Joined
- Visits
- 434
- Last Active
- Roles
- Member
Comments
-
The SEQ V4s are amazing sequencers, and open source and very hackable. Very much worth building one if you feel so inclined at some point.
-
If you're doing pendulum/forward/back type stuff, you might want to take a look at the MIDIbox Seq V4's "track direction" functions - see the "Track Direction Page" section here: http://www.ucapps.de/index.html?page=midibox_seq_manual_hw.html Check…
-
Triggering from external midi has been messed up for me for quite a while - worked fine in previous versions of the firmware... It started messing up when the RudeOG firmware's multichannel/multi-note midi feature was incorporated. My LXR is prett…
-
Step recording from an external source also isn't working for me - tried from the SEQ V4 and from a keyboard. I can trigger from the keyboard, but the LXR doesn't record the steps. Has something drastically changed in the LXR's implementation of e…
-
Are the old firmware images available anywhere? I'd like to see if older firmware versions have external midi triggers setups that work with the seq V4...
-
Bump. Same problem here sequenced from a midibox Seq V4. LXR firmware v.34
-
bump...
-
I built one of these a few months ago - it's a nice little polysynth with a lot of potential. Unfortunately the firmware is not open source though. As-is, the firmware is fine - the synth works, sounds good and is stable, but open sourcing the fir…
-
Switches are available with the exact same footprint, with larger plungers.
-
You would have to use different switches when building the lxr as well. Those buttons won't fit the switches that come with the lxr.
-
Hold on for a real answer from Julian or someone who knows a little more than I do, but I think the LXR actually swings the midi clock when it's master - like, it sends out a midi clock signal with swing, so all the other devices following the clock…
-
You should ask it here too: http://forum.sonic-potions.com/discussion/195
-
The switch bodies are the same size, but the square bit that holds the button cap is significantly smaller on the LXR.
-
I got as far as cleaning up the filenames and the slashes and case insensitivity in the includes, but then got boatloads of errors that seemed in part to be missing core includes. I started adding and changing includes to deal with that, and that w…
-
I'm all for breaking stuff and fixing it, but it's a big codebase for an inexperienced person to be running though and making semi-arbitrary changes to... It won't be particularly well-spent time for any of us if I can't hand you guys back a workin…
-
This may be a bigger project than expected... I might be a bit out of my depth. I've cleaned up most of the \ /s and filenames, but now I'm getting a bunch of other path errors. There are all the .mk files, which all have a shitload of bad file n…
-
Actually, there aren't all that many filenames that are messed up. I'll rename them manually. They don't all have to be lowercase, just the .c and .h files should be consistent.
-
Yeah, I think filenames and directories should change and follow a naming convention, rather than just fixing the includes - it's bound to be confusing to have stuff like /AVR/Hardware/SD/SD_routines.c and sd_routines.h ...all lower case would proba…
-
...so, digging a little further, I fixed a few spots where I replaced [\"] with [/"], and got rid of the pragma errors, but there are a lot of case sensitive filename issues - sometimes the .c file is named using a different case from the .h file - …
-
Ok, so I'm dumb - I just searched/replaced "\"s across the project and now I'm getting all kinds of "pragma takes a parenthesized string literal" errors... I imagine I wiped out "some \"escape\" characters" or something. Only useful information I …
-
For the record, a translation of Rudeog's instructions for linux people (well, Ubuntu people anyway) Step 1-7 are: Follow Rudeog's step 1 and 2. install GCC ARM, avr toolchain, build essentialsudo apt-get install gcc-arm-linux-gnueabi gcc-avr avr-li…
-
Soooooo... I'm guessing neither of you guys are linux/unix people? I'm getting a bunch of errors building, so far all related to use of windows slashes "\" in paths... Unix likes "/" - the first build errors I see are in AVR/Preset/presetManager.…
-
Moshang's caps are fairly standard - I've got a couple of hundred of them in different colours from ebay/china. But they fit standard size tact switches. The square buttoncap-holding parts on the LXR switches are just a little bit smaller than any…
-
Your code is nicely commented, btw. edit: ...except where it's german... haha.
-
Cool. Thanks, that should get me looking in the right places anyway - I'll look into this over the next couple of weeks. ...but don't let that stop anyone else from just going ahead and implementing any of this if you feel like it - I'm pretty new…
-
Julian and/or Rudeog - this might be a good project for me to start trying to figure out the LXR firmware... If either of you feel like pointing me to the sections of code that I'd have to look at to implement this, and any "hey, I'm talking to an …
-
Well, whaddya know. Using a separate power adapter fixed it - there's no hum now. I guess it was a ground loop. I didn't realize you could get a ground loop where everything was powered off the same power source... But I guess I do have a weird …
-
As long as we're talking about sync multipliers and dividers wishlist items, I use my LXR as the clock master - it'd be great to be able to output clock with different multipliers and dividers, in addition to being able to multiply/divide an externa…
-
I used the top piece of shiftr's design, it worked great.
-
There was the ER HorseDrum, but it eats a lot more than the LXR. I don't think it did too well.