[Instrument aout trouble v1.4]

Hi all.

I am having trouble assigning Instruments to different aout channels. i always get the values from Inst.1 on the aouts.

By changing the Inst. in the aout menu nothing changes.

Can someone conform that.

Is this a bug or am i to stupid. I am using v1.4 and the Pic 18f4685.

Thanks

Chriss.

[MIDIbox of the Week (MIDIbox SID of Chriss)]

Hi,

Still don't understand it 100%. How did you do white over black?

just take a white paper and print everthing black exept the labeling. You can do this easily in a layout app (mine is still freehand). just make on layer black and the letters and drilling holes white. And then print.

It will not work the first time. But after some tests with the right paper and printer settings you can build your own custom front every time you want in 5 minutes.

And of course don´t forget the lacquer to finish..

chriss

[MIDIbox of the Week (MIDIbox SID of Chriss)]

hi euphoricgrey,

Curious... did you use a premade box oo? Also.. how did you mount the wood sides

no i first did a 3d model in rhino and then went to a lokal metall company. The main front is just a bend aluminium plate where the angels of the front and back are exactly taken from the rhino model. Bending just cost 5 euro. And the wood sides are just mounted with "metall rightangels" to the front and back.

@Jidis

I'd like to see more about what you did there.

of course no problem, since digital cameras are in every mobilephone these days i can make more pictures when i will open it for V2. The reason for this black white label with spray glue is just because i have so much fear of getting the labeling wrong while paying 100 euro or more for www.schaeffer-apparatebau.de in the end having one label wrong. Printing a b/w sheet with a laserprinter and glue it on the front cost maybe 1 euro and i could change it very fast even when there is a mistake or an update.

of course the paper won´t hold forever and when i come to very humide places you can see some waves on it but it is still is in very good condition and always impresses a lot of people.

And i have everthing prepared for upgrading to V2. I can easily change the labeling of the buttons which will change in V2.

Good work,

thanks

chriss

[MIDIbox SEQ V3.0 released]

hi,

awesome and i really like the manual, with the sound examples this is one of the best manuals i have seen. must say that i already tried build 71 but due to time reasons couldn´t test so much. but this sequencer is a must have....

thorsten,

thanks you so much for this.

chriss

[Perl Script to Copile ASM-Sources with GPASM]

thanks audiocommander for the Help,

in the meantime i found the time to test it with the FM 1.1 and that works, besides the warnings, i couldn´t test it with a real MB Core though, but i generated a hex file.

so long

christoph

[Perl Script to Copile ASM-Sources with GPASM]

hello,

first i want to say that i am happy that you work on a solution for linux, mac users.

but in my case it does not work...

here my result in the terminal, maybe it helps. Application is the MbSEQ V3 build 60

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_m_morph.inc:47:Message [305] Using default destination of 1 (file).

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:418:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

cs_menu.inc:417:Warning [202] Argument out of range. Least significant bits used.

seq_enc.inc:102:Error [113] Symbol not previously defined (SEQ_ENC_Handler_MenuPageCS_NoNewPos).

seq_enc.inc:102:Error [126] Argument out of range (-16495 not between -128 and 127)

seq_layer.inc:139:Warning [202] Argument out of range. Least significant bits used.

seq_layer.inc:154:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_chord.inc:14:Warning [202] Argument out of range. Least significant bits used.

seq_core.inc:1715:Message [305] Using default destination of 1 (file).

unfortunatly i am not able to read this, so i show it to you.

And there is no hex file generated. Is the fault in my setup?

i can send you the text after the mpasm2gpasm.pl as well..as far as i can say everthing seems to work..

thanks again for the good work

chriss

[Compile on Linux please!]

hi michael

thanks a lot for your input,

I'm not sure if macros.h is interchangeable with macros.sed... I'm totally overasked when it comes to ASM..

and i am when it comes to programing language.

when there is actually no such makros.sed file than it´s ok. i just wanted to be sure that i am not doing something wrong in the teminal or with my directions.

thanks again

chriss

[Compile on Linux please!]

hi michael

I recommend, that you load an ASM-based source (like the seq-app) and backup the pregenerated included hex file. Then try to compile the project unchanged. When you compare your fresh compiled .hex file against the backuped original .hex-file, there should be no differences.

thats exactly what i did on the last weekend, not only that the the hex file was different it was gone... and i got two files called "main.lst" and "main.cod". And i had this errors in the terminal described at the beginning of this thread.

aout.inc:61:Error [103] syntax error

aout.inc:72:Error [103] syntax error

aout.inc:155:Error [103] syntax error

aout.inc:157:Error [103] syntax error

aout.inc:183:Error [103] syntax error

aout.inc:228:Error [103] syntax error

aout.inc:239:Error [103] syntax error

aout.inc:249:Error [103] syntax error

cs_menu_timer.inc:27:Error [103] syntax error

cs_menu.inc:57:Error [103] syntax error

cs_menu.inc:65:Error [103] syntax error

cs_menu.inc:75:Error [103] syntax error

cs_menu.inc:106:Error [103] syntax error

cs_menu.inc:147:Error [103] syntax error

cs_menu.inc:178:Error [103] syntax error

cs_menu.inc:193:Error [103] syntax error

cs_menu.inc:309:Error [103] syntax error

cs_menu.inc:357:Error [103] syntax error

cs_menu.inc:415:Error [103] syntax error

cs_menu.inc:443:Error [103] syntax error

cs_menu.inc:641:Error [103] syntax error

cs_menu.inc:660:Error [103] syntax error

cs_menu.inc:669:Error [103] syntax error

cs_menu.inc:672:Error [103] syntax error

cs_menu.inc:717:Error [103] syntax error and so on ....

the problem i have is that i don´t have a C file nor a C application, instead i want to compile a plain MB asm file with gpasm.

otherwise i have to wait till i get a macbook to use mplab again  :'(

so the new thread should better call "compile MB application assembler files on OSX please"

again thanks for your help

chriss

[Compile on Linux please!]

ok

thank you for the info. didn´t thought about that.

But that means i can not compile MB applications whith gpasm right at the moment. (either v.0.13.3 nor v.0.13.4) or is it possible to write a sed file which does the same as it does with MIOS files?

And thanks for the links, although i knew them it´s always nice to get replies like that.

thanks again

chriss

[Compile on Linux please!]

hi all

this weekend i wanted to compile the Midibox SEQ application the first time under osx. usually i do this on an old PC , but always had trouble finding the right files and because its much more affort than having one maschine for all that. So first i tried to read the forum and stumbeld over Xcode2. Then i realized i don´t need that, but need gputils-0.13.4, managed to install everthing to recognize that i get a lot of error messages. looked in the forum again and found this thread... and of course the wiki. http://www.midibox.org/dokuwiki/doku.php?id=compiling_the_midibox_source_on_linux

now since i am not a linux expert and much more not a command line expert i have problems to get this sed file running.

from the wiki

To use this script, copy the following files in your mios_v_1_x_src dir:

does this mean i need to copy both into txt files and save one as "replace-macros.sed" and the other as "fix-gpasm.sh" in the dir of the MB SEQ. because if i do so it does not work. terminal gives me following messages after sh fix-gpasm.sh back:

fix-gpasm.sh: line 4: src/*.inc: No such file or directoryfix-gpasm.sh: line 4: src/*.inc_: No such file or directory

fix-gpasm.sh: line 4: src/*.asm: No such file or directory

fix-gpasm.sh: line 4: src/*.asm_: No such file or directory

fix-gpasm.sh: line 4: src/*.h: No such file or directory

fix-gpasm.sh: line 4: src/*.h_: No such file or directory

am i only in the wrong direction or do i need to do something else.

thanks for the help

chriss

[cc values when pushing a button]

Do you mean the values it sends from the MBSID MIDI Out when you push those buttons?

exactly that is what i mean.

cs_menu_cc_table.inc

i already looked there, but for me it seems that this takes care of names which are printed on the screen.

any other idea?

thanks for the help

chriss

[cc values when pushing a button]

Hi,

maybe someone familiar with the MBSID code can give me a hint where to change the values for the CC when pushing the LFO waveform button or the OSC waveform button or the filter Mode button.

My plan is to adapt the MBSID CS for a Filter in Ableton Live (At least i want to try it).

I know that i can use a midifilter which changes the values (like MidiOX) but i want to learn something about Button routines.

thanks

chriss

[slaves+aout]

Hi Thorsten,

thats perfect, very very cool.

chriss

[slaves+aout]

HI,

i have one question to the Analog extension of the MBSid

Are the slaves also able to send analog voltages through an AOUT? I mean can i hook a second Aout module to one of the slave Cores and get analog voltages out of it... for stereo effects.

thanks

chriss

[74hc165 smd Lieferant gesucht]

www.lobtron.de

habe gerade mal nachgeschaut, leider haben die den 74HC165 nicht mehr aber veilleicht kann man den ja ersetzen, kenn mich da nicht so aus. Den 74HC166 haben sie nämlich??? Den 74HC595 sowiso.

chriss

[Audio Interface and workflow?]

hi ilmenator

thanks for your suggestions.

In terms of audio quality (measured values), the Behringer DDX desk is no low quality product.

good to hear.

One thing that always is so strange for me is the price fall of behringer products (of  course not the patchbay), i mean the DDX started with 1999,. EUR and is now at 600.-. The Multiface from RME is still nearly where it started and is a little bit older.

Also, the Behringer is easy to operate. I would not buy it for its MIDI remote capabilities, though - but you wanted to build an LC anyway, right

That was one reason i started this thread.

Having two mixing consoles in a small room, one for audio and one for midi makes no sense for me.

If i will buy the DDX, i think i will not build the LC for a long time..

chriss

[Audio Interface and workflow?]

So the real answer to your question is how much money do you have?

thats exactly the point, money is always a topic and is always not enough.

a little research: (all EUR)

ECHO AUDIOFIRE 12 595.- (12 inputs, no ADAT)

RME Hammerfall-Fireface-400 850.- (8 inputs, expensive)

RME Hammerfall-Fireface-800 1249.-(8 inputs, expensive)

Behringer DDX3216 Digital Mixer 550.- (16 inputs, behringer and needs a FW ADAT)

M-audio FW1814 450.- (8 inputs+8/4 ADATs, sound qualitiy?)

So the echo would be the cheapest for the number of IOs. The DDX would be the simpelst and RME the maybe the one i have still fun in 10 years. (depends how long FW is supported)

Personally, I'd get rid of the PC and go with the DDX.

thats exactly what interrests me.

Is there a difference between pushing faders and buttons on a DDX or a LC?

(Assuming that the system audiocard-PC-software-LC runs stable).

But maybe these systems can never be as stable as a hardware mixer, and the advantage of a DDX might be that its easy to use from the beginning...and you can make some tunes without turning on the PC.

chriss

[Audio Interface and workflow?]

Hello all

i have some trouble finding out what the best solution for me concerning my studio setup.

I have about 16-20 analog Audio sources, a MIDIBOX SEQ and a MIDIBOX USB2MIDI Interface. One ibook G4 and a MIDIBOX LC is planned.

If it´s possible i would like to have them all at the same time and in realtime (no samples) in my music software.

For that i am thinking about a good FW interface (RME or echo) and control the mixer of my music software with a MIDIBOX LC.

Another solution would be a digital mixing console like the behringer DDX3216 and an ADAT FW interface, the advantage would be that i can mix more channels and maybe a better performance concerning realtime processing. Disadvantage is the pour soundquality of behringer.

I just have no experience in that and want to find a good solution in the beginning.

So what do you think about common workflows for one man sleeping room studios. How do you get your analog sources into the computer or how do you process them?

chriss

[Sequencer design for feedback]

hi stryd_one

that sounds awesome

i mean i don´t´understand alot but i am still impressed of your work

chriss

[MIDIbox of the Week (MIDIbox SID-to-go of Mesak)]

I like the picture story on the website!

thats right very very nice, could be linked to a SID tutorial.

chriss

[We need a new midibox like this one]

yeah,

i saw this at the AEC festival in Linz this sommer and asked how he did the buttons, suddenly a guy from yamaha was standing behind me...

nice people though, but this whole project is supported by yamaha, thats why it looks so professional.

chriss

[Midi toggle box]

hello thorsten,

thanks for your answer, good to hear that the SR can only deliver 80mA.

(this is not a programming specific answer, but I guess that you can excuse me, that I cannot dictate the code for all possible modifications due to time reasons...)

i can excuse this very easily, you gave so much code to us.....

my hope was that there is already an existing project or code. but i will try on my own.

thanks again

chriss

[Midi toggle box]

Hi,

my plan is to build a midibox with 64 buttons and 64 leds (beside the encoder and buttons for menu),

the leds are under the buttons, (the buttons light when they pushed, toggle state)

i already tested this with my MBSEQ and works well

so my question is:

Since 64 leds have a max. current of 20 mA x 64 = 1280 mA the box would at least need a supply with 2A.

By supporting the leds with a led martix, a lot of power could be saved right?

Is there already a application where someone implemented a ledmatrix into a MB64 or MB64e design?

If not, what would be the best hardware setup to test and program this by my own.

I think the application for the led digits is a good way to start, but i am not quite sure.

thanks

chriss

[FM Frontpanel]

thanks thorsten,

did try it with the MBsid and it works.

just put in the OPbuttons into the cs_menu_io_tables.inc and assigned the 5th DIN register to them, after setting the

;; initialize the shift registers

movlw 0x04 ; use up to 4 shift registers

to

;; initialize the shift registers

movlw 0x05 ; use up to 5 shift registers

everthing seems to work

thanks again, now i can go one building my frontpanel

chriss

[FM Frontpanel]

hi thorsten,

cool that this is possible.

as always i don´t know what to do exactly....

i just pasted the original code here:

CS_MENU_BUTTON_InsOP1

movlw 1 << 0

rgoto CS_MENU_BUTTON_InsOP_Cont

CS_MENU_BUTTON_InsOP2

movlw 1 << 1

rgoto CS_MENU_BUTTON_InsOP_Cont

CS_MENU_BUTTON_InsOP3

movlw 1 << 2

rgoto CS_MENU_BUTTON_InsOP_Cont

CS_MENU_BUTTON_InsOP4

movlw 1 << 3

;; rgoto CS_MENU_BUTTON_InsOP_Cont

CS_MENU_BUTTON_InsOP_Cont

movwf TMP1

;; pointer to _FLAGS register which should be modified in FSR0

lfsr FSR0, CS_MENU_SELECTED_INS_FLAGS

btfsc CS_MENU_MODE, CS_MENU_MODE_INS_OP

lfsr FSR0, CS_MENU_SELECTED_OP_FLAGS

and now i would put in four extra Op_buttons like this:

CS_MENU_BUTTON_OP1 for example.

but how to set the CS_MENU_MODE_INS_OP flag there? like this?

CS_MENU_BUTTON_OP1

lfsr FSR0, CS_MENU_SELECTED_OP_FLAGS

rgoto CS_MENU_MODE_INS_OP

and how can i clear the flag within the instrument button functions? like this?

lfsr FSR0, CS_MENU_SELECTED_INS_FLAGS

btfsc CS_MENU_MODE, CS_MENU_MODE_INS_OP

when i do that i get following error:

MIDIBO_FM_V1_0 MODIFIED\MACROS.H 161 : Argument out of range (-6901 not between -1024 and 1023)

MIDIBO_FM_V1_0 MODIFIED\MACROS.H 161 : Argument out of range (-6904 not between -1024 and 1023)

MIDIBO_FM_V1_0 MODIFIED\MACROS.H 161 : Argument out of range (-6907 not between -1024 and 1023)

thanks

chriss