rudeog
About
- Username
- rudeog
- Joined
- Visits
- 315
- Last Active
- Roles
- Member
Comments
-
Not sure if this fix I did made it into the official FW (it's been such a long time) but look for the PCR setting in global and change it to on. I think that is the same issue.
-
Yeah its already possible as far as I remember, just send PC 1 to 8
-
What firmware version? You might just need to upgrade.
-
Yeah, the makefile stuff seems a bit less problematic for people.
-
Hi Myles, you might want to try building first with the makefiles. This thread is about mac building, but my comment gives the instructions for Windows. I think someone might have put this all in the wiki too, but not sure where right now. http://f…
-
Teddy, you are right. It looks like it's only going to record to the actively selected voice regardless of how you set up the channels. On line 1264 of MidiParser.c (in mainboard) this line of code: midiParser_noteOn(v, msg.data1, msg.data2, 0); …
-
You need to change the setting for each voice to respond to a single note (as opposed to "Any") and set them all to the same channel.
-
Nice sounds and setup, Owen.
-
This is possible right now, as I added the code to do so a long time ago. It will recognize a PC message and switch to one of the 8 patterns when the end of the bar is reached. The global midi channel (configured in the settings) is used for both se…
-
Right now CC messages are not transmitted. There was some talk of adding this, and I will probably attempt it when I get more time to write code (unless someone beats me to it).
-
Assuming this was merged as is from my fw, there is a setting on each voice that determines whether it responds only to a specific note, or responds to all notes ("Any"). If set to a specific note it will trigger only when it gets that note (and wil…
-
@Julian, Most GCC warnings can be removed. The only ones I was not able to remove were related to type or signed/unsigned conversion when using += or &=. There doesn't appear to be an elegant way of getting rid of these (unless someone else can …
-
Ok, cygwin works without any changes to the makefile (note to self, avoid mingw). So to add to the instructions... Windows Build Follow instructions 1 to 4 above Install Cygwin from http://cygwin.com/install.html During installation, add the followi…
-
I'll try cygwin. It's occurring with all files in the ARM side, and it's not related to spaces, as none of my paths have spaces. Also the command succeeds fine when run from the command line.
-
I'm having a weird problem on Windows with mingw make... It seems to generate the correct command, but arm-gcc reports that it can't find a header file (as though I had not added the -I include path). If I copy and paste the command and run it from …
-
I use mingw, so I'll test with that.
-
LXR, Kaoss Pad 3, behringer analog delay pedal, reverb pedal, proco rat distortion pedal
-
I've added these 4 makefiles to my master
-
I don't have time to test right now, but I can add these makefiles to my tree as well. I'm looking at @pld's makefile branch... are those the latest 4 makefiles? Hopefully I can get them tested on windows as well at some point.
-
Posted on MatrixSynth: http://www.matrixsynth.com/2014/05/sonic-potions-artistslxr-compilation.html
-
I'm Afrit Temple on this comp.
-
Just got done listening to the whole mix. Very impressive. Well mixed @Möbius. The songs are ordered well. There is a great deal of variety, and it sounds like everyone who participated found interesting ways of using their machines. I sent an email…
-
Cool, so it sounds like we have a successful compilation on mac.
-
np. Note that all those include directories are listed under "Include paths" under C/C++ Build - Settings - Tool Settings - Arm Windows GCC C Compiler - Directories. All the -D options are in the same place but under Preprocessor. All the -f options…
-
Yeah, you need to compile the avr project code with gcc for avr and the arm project code with gcc for arm. So once you have those separated, then we can continue to figure things out. Here is my command line for ARM (the c file will be different for…
-
I'm in favor of makefiles. For my own stuff, I'll continue to use eclipse, if only to get the context help, and the ability to easily go to errors and warnings. But the advantage to makefiles is that we don't have people struggling to get this thing…
-
@pld if you come up with Makefiles, I'd be happy to push them in my fork. Here is the command line I end up executing for that one file in the arm project (I'm on Windows, remember): arm-none-eabi-gcc -DHSE_VALUE=8000000 -DSTM32F4XX -DUSE_DEVICE_M…
-
Yes, I merged those path fixes into my branch.
-
Can you show me what avr-gcc command line gets executed before you get this error?