sebiiksbcs

Sure thing, just PM'd you

Want to buy one PIC18F4685 with MIOS bootloader burned on it.

Hi Riggs, which PIC is this? PIC18F4685?

Hi Scott I have two SID 8580 chips, I can check the R later, one is tested and working fine, the other worked fine the last time I used it but I can still throw it in my Midibox SID to make sure it's working.

from SEQ_CV_SendPackage in core/seq_cv.c: // if channel 1..8: set only note value on CV OUT #1..8, triggers Gate #1..8 // if channel 9..12: set note/velocity on each pin pair (CV OUT #1/2, #3/4, #5/6, #7/8), triggers Gate #1+2, #3+4, #5+6, #7+8 // if channel 13..15: set velocity/note on each pin pair (CV OUT #1/2, #3/4, #5/6), triggers Gate #1+2, #3+4, #5+6 // if channel 16: trigger the extension pins (DOUT) This is entirely new to me! Is the pairing feature only available via the actual tracks 9-15 on the Seq? So this way there already is a velocity feature implemented, which is much more desirable than accent on/off anyway! But instead of duplicating the gate signal across the paired pins, #1/2, #3/4, #5/6, #7/8, couldn't the second pin of each pair go high when velocity exceeds 100? Which would naturally also happen when the accent trig is active? This way there'd be note, velocity, accent, all in one flexible package... Or am I misunderstanding something?

My focus lies on slide and accent information, so I guess I'll answer my own question with "no" Slide (or better glide) is taken care of by the Seq itself, which leaves accent. So I am assuming that a hack is possible, e.g. output a logic high on a separate DOUT pin whenever the track step's velocity is above 100?

Apologies if this has been explained before and I simply didn't find it. See title. Correct me if I'm wrong: the SID V2 engine seems to offer the option to directly forward various information to the "gate" output pins, including gate, slide, and accent information (when using the bassline or drum mode) Is the same possible with the SEQ V4? Or are the gate outputs (I will be using a dedicated DOUT shift register) somehow hard-wired to pair up with their respective CV channels? Like gate 1 always goes with CV 1 (and outputs the gates of the track that CV 1 is assigned to)

I've been testing the CV V2 app on my Core LPC17 and I'm using the standard SCS. Is it still the case that no sequencer features are available via the SCS? Are they only available from the lemur/ipad/touch screen? Or is the LPC17 firmware not updated anymore, i.e. I'd have to get a STM32F4 to get access to more and/or newer features? Thanks

Thanks midiwanted!

I'm one of those guys with a 4x20 LCD and 10 buttons on their SID v2 (5 above, 5 below). Menu scrolling is great, just not perfectly intuitive. Right now I am diving into the code and trying to make the necessary changes to make the menu scroll 5 (or even 10) parameters at a time (which equals one full line, or a full page). I just feel like this is more intuitive than the current way of scrolling through the parameters one at a time. Even, say, on a 2-line LCD it doesn't feel optimal for me because it would feel better to know that, i.e. I can find OSC always at the first entry either in line 1&2 or 3&4, instead of having the positions just floating around arbitrarily Long story short, I'd like the menu scrolling to scroll 5 parameters at a time instead of 1. This is the passage I believe I need to edit: (found in /src/cs_menu.inc) ;; -------------------------------------------------------------------------- ;; called by cs_menu_enc.inc when the menu pos should be updated ;; item in CS_MENU_PARAMETER_L ;; -------------------------------------------------------------------------- CS_MENU_MenuPosUpdate ;; copy result to cursor pos and request display update movf CS_MENU_PARAMETER_L, W andlw 0x3f movwf CS_MENU_CURSOR_POS ;; set page offset directly movwf CS_MENU_PAGE_OFFSET ;; now request a display update so that we see the new parameter on screen bsf CS_STAT, CS_STAT_DISPLAY_UPDATE_REQ ;; clear counter so that cs_menu_timer.inc counts from zero and the menu item is marked for a short time clrf CS_CURSOR_CTR ;; clear "CS_STAT_CURSOR_FLASH" bit (see cs_menu.inc for the handling) bcf CS_STAT, CS_STAT_CURSOR_FLASH ;; thats all return I did have limited success by changing the number "3F" to values like "3E", "3D" etc. but then the binary counting the encoder works with (does it?) got messed up, meaning the page scrolled by x times 1 parameter, buy only on every x-th turn of the encoder. I also was able to indeed make the page scroll in full lines by adding values with ADDLW instead of doing the ANDLW but then obviously scrolling back didn't work. Has anyone been working on something similar and could point me in the right direction?

cool, will pm you

Hi Ilmenator, do you have 1 spare available for me? Thanks!

I think the voice CC have been changed recently, rendering the txt file on ucapps.de outdated. Are you using CC# 13-15? (See the txt file included in the firmware package.) Just to be sure..

I'm using setup_pic18f4685_mbfm_v1.asm with settings adjusted to my hardware. I left all 4685-ish settings standard, which means WAVETABLES_IN_RAM is on, and also USE_SHADOW_BUFFERS and DISPLAY_CC_ASSIGNMENT_NAMES.... I'll try it with some of these settings off. Good idea! Interesting. When I set WAVETABLES_IN_RAM to 0, I get the following error during the build: ./src\mbfm_rnd.inc:410:Error [179] Unknown opcode "MBFM_RND_GenerateWTE_Loop" ./src\macros.h:15:Error [113] Symbol not previously defined (MBFM_RND_GenerateWT E_Loop). ./src\macros.h:15:Error [126] Argument out of range (-16377 not between -1024 an d 1023) make: *** [setup_pic18f4685_mbfm_v1.hex] Error 1 Does that mean the random generator needs WAVETABLES_IN_RAM to be on?

Hey, I recently upgraded to v1.4e from v1.1. I used a PIC18F4620 I had lying around instead of the recommended PIC18F4685, and so far everything works just as well. Only the Wavetable sequencer seems to be broken. I can access and edit it in the menu, but it doesn't seem to have any effect. Could it be because I am using a PIC18F4620? Is anybody else using a an 18F4620? Any ideas?

You can find pictures here: http://www.flickr.com/photos/disgustingpie/9346930048/in/photostream/

Didn't know where MIDIBOX CV related stuff belongs so I post it here... Totally voided my warranty for my Maschine MK2 and installed a small CV interface. Why? - I wanted to integrate Maschine with my analog stuff without having to run Maschine's MIDI through an external MIDI-CV converter first. The gates and CVs now feel like a direct extension of Maschine's possibilities. Also, I had a Core8 lying around that I wanted to put to use. - 8 gate outputs (5V) - 2 CV outputs (NOT 1V/oct but 0-5V) So how does this work together with Maschine hard/software? SIMPLE: - I assign a MIDI out module to a sound (channel 1) - I go to keyboard mode on that sound and play pads 1-8. The gates correspond to those 8 pads. Done. Velocity CVs are available for pads 1 and 2. DETAILS: - The interface is a Midibox CV with one AOUT_LC module. I was surprised how much space there is available under the Maschine PCB. I could fit some other toys there, and I think the next step will be an additional 1V/oct CV interface from midimplant.com. - I've assigned the gates to MIDI notes C3, C#3,...G3 and the CVs to velocity of the first two gates. I am using gates and not triggers because you can do some great on/off sequencing stuff with them, e.g. opening/closing a filter etc. - If I want to use the CV outputs for smooth progressions, I record the respective pad with note repeat active (the highest note repeat resolution is 1/64th which works quite well for the CVs since the interface itself has a built-in slew rate that I set to 8 ms). - Technically, the CV outputs run at about 0.48 V/octave if you will, and they have a precision of 8 bit. They are meant for percussive sequencing and not playing melodies, so I'm good! The background is that the interface runs solely from Maschine's USB power (5V) anyway and I omitted the AOUT_LCs op-amp scaling and offset circuit.

By the way, I forgot to mention I wouldn't mind if the PIC in question had a Core8 attached to it. I would take the Core, too. Do you have a spare one you'd be willing to sell me then?

I just found out the Midibox FM firmware has been updated but a PIC18F4685 is required. So if you have a spare one you don't need, I'd be interested. Thanks! I am located in the heart of Europe. ;)