All Activity

This stream auto-updates   

  1. Today
  2. Troubleshooting midiphy SEQ v4+

    Thought I'd report back, the above issues are solved. They were soldering issues, some really stupid some harder to find. I still have an issue I'd like to fix, the stop, rewind, fast forward and pause buttons are constantly lit up. They function correctly when pushed, but I'm assuming this is not normal?
  3. Yesterday
  4. Cubase Quick Control Plugins controller

    Would the following do the job? CORE_STM32 Module AINSER64 (is this all i need or do i need an DIN and/or DOUT module?, as I plan to use absolute rotary encoders) MIDI_IO Module? (or can i rely on the built in USB on the STM32F4DISCOVERY) or do i need a USB GM5 Module? LCD Infos (just for added effect prior to using LED Rings) Thanks          
  5. Hello I was wondering if someone could help me with some basic advice with regards to what MIDI box modules I am going to need to get for my first learning experiment into the MIDIbox universe. For my first experiment i would like to make a controller that can be used to control a specific plug in which i use in Cubase. Lets say for example. a tape delay emulation plugin. Which i am fond of. For example. say the UAD EP 34 UAD EP 34 Which uses 6 rotary encoders (perhaps with LED rings), 1 x Fader and 6 toggle switches. Although i understand that Cubase only allows max 8 using Quick Control mapping of generic hardware to plug ins. I do not think that any more than 8 physical controllers can be mapped to plug ins used on inserts if the control surface is using the Mackie control surface protocol / driver. However perhaps i am wrong, as i am not an expert in this area. And you guys will likely know more about this. Just to clarify, i was wondering  which modules i will need to use to make a basic control surface to control the bellow plug in. I was also wondering if it is possible to connect an Ethernet output, which may be used at a later date when i can work out how to use the EUCON. Thanks I will firstly need a core module. What others modules do you recommend i need. Do i need a MIDI module for MIDI I/O or can this be done by the built in USB  I guess i need Analogue module as well? If i were to employ LCD rings, would i also need a special module for this? Although my first experiment with MDIbox, i will likely not use LED rings, so as to keep it simple, rather than make my own life hard thanks for any help  
  6. ST Electronics Nucleo 144 boards

    https://www.st.com/en/evaluation-tools/stm32-nucleo-boards.html  
  7. ST Electronics Nucleo 144 boards

    Hey, I was wondering if any one considered using the ST Electronics own Nucleo 144 boards for MIDI Box projects, as these also usually feature STM32 MCU's but also include a range of boards that are equally cheap as the STM32F407G-DISC1 but which offer extra features with regards to input output Just out of interest thanks
  8. Troubleshooting midiphy SEQ v4+

    thanks, nice info - will do it when i figured out whats wrong at the moment :(
  9. Troubleshooting midiphy SEQ v4+

    Mmmhhh cannot help further sorry :/ One last advice, Before soldering mathias switch take time to recover them with electrical tape or paint sides with a marker to avoid light bleed between them. i was really annoying with light bleed between steps. Caps are hard ( impossible ? ) to remove once placed and it took me lot of time to place tape to isolate light with caps installed. Cheers  
  10. MIDI Implemtation for EUCON

    Hello I was wondering if anyone had any information on the MIDI implementation for the EUCON protocol that is now used to connect several types of control surfaces to Cubase 10, Logic 10, Nuendo and Protools 2019.5   I think these control surfaces uses Ethernet interface, which is different to the standards used by MIDIBOX but can be used alongside Mackie Control and generic control surfaces. So think of the possibilities, although in all fairness, i do not know if any one has been able to turn their hand to getting their MIDI box to control all the parameters in  all the different plug ins at the same tume. so please forgive me for my ignorance.   I would imagine that there would be little info on this protocol, as the manufacturers would likely want to keep this a closed platform http://avid.force.com/pkb/articles/compatibility/EuControl-Compatibility   However, if someone already had a EUCON compatible control surface, I can't see why someone cant' rev engineer using basic mici sniffer apps or even MATLAB Audio Toolbox? apart from the obvious legal restrictions... but hobbyists.. may bend the rules a little for personal use?  
  11. Troubleshooting midiphy SEQ v4+

    Thanks for your input - i checked it but there seems to be no short anywhere - On the LEMEC RH PCB however i have only installed the header in the J89 slot and not the J89A because it is the last module in the chain (am I wrong there) so there isnt realy the possibility of such a short right now. So my chain right now is from JApcb J89-port to J89-port of LEMEC LH and from the J89A-port to J89 port of the LEMEC RH.
  12. Troubleshooting midiphy SEQ v4+

    Hi all, @knochenfabrik just my two cents: Did you check the last/first encoder pins are not touching the pins of the ribbon header . You can check that looking at the side of your build?
  13. Troubleshooting midiphy SEQ v4+

    OK when the LH pcb is connected to the core J89 it works fine and everything is registered so I modified the SEQ_R and tried it with the RH pcb but there is nothing - will have to measure continuity later - the pcb just seems to do nothing right now :-/. I also tried to set on/off pins individually how it is mentioned in this thread a bit earlier but it didnt realy do anything - maybe i also should try it again.   Thank you very much...
  14. Troubleshooting midiphy SEQ v4+

    Not sure. Disconnect all PCBs, connect lemec_L directly to the Core J89 (without JA) and load seq_R.ngc. You can also connect lemec_R directly to the Core, but you need the following modifications: ################################################################################ # Left Panel ################################################################################ ... # 8x8 Button/LED matrix - we emulate "normal" LED/Button functions: DOUT_MATRIX n=1 rows=8 inverted_sel=1 inverted_row=1 sr_dout_sel1=4 sr_dout_r1=5 led_emu_id_offset=1001 DIN_MATRIX n=1 rows=8 inverted_sel=1 inverted_row=0 sr_dout_sel1=4 sr_din1=2 button_emu_id_offset=1001   (i.e. offset the DOUTs by three)
  15. Troubleshooting midiphy SEQ v4+

    Thank you again for the fast response. I tried to reflow some pins and get rid of short where they seemed to be possible. Status Quo: Japcb + Les Mec LH work fine together but when Reconnected all the PCBs and loaded SEQ_L - with both les mecs  installed all the encoders still dont work (no turns and press on all of the encoders on both boards) - when i press switches on JApcb i get the following in console: "[10389.729] load seq_l [10390.157] [MBNG_LCD] no response from CLCD #1.1 [10390.157] [MBNG_LCD] no response from CLCD #2.1 [10390.157] [MBNG_FILE_C] Event Pool Number of Items: 348 [10390.157] [MBNG_FILE_C] Event Pool Allocation: 12250 of 65536 bytes (18%) [10390.178] Patch 'seq_l' loaded from SD Card! [10390.184] [MBNG_FILE_R] /seq_l.NGR (optional run script) not found [10396.484] set debug on [10396.655] Debug mode turned on [10402.023] MBNG_MATRIX_NotifyToggle(2, 34, 0) [10402.023] MBNG_DIN_NotifyToggle(3034, 0) [10402.023] [EVENT] id=BUTTON:3034 hw_id=BUTTON:3034 bank=0 fwd_id=LED:3034 type=NoteOn value=0 label= [10402.023] MBNG_DOUT_NotifyReceivedValue(3034, 127) [10402.023] MBNG_MATRIX_DOUT_NotifyReceivedValue(3, 34, 127) [10402.026] MBNG_MATRIX_NotifyToggle(2, 50, 0) [10402.026] MBNG_DIN_NotifyToggle(3050, 0) " Can i assume that failure must be on the Lemec-board (RH)? Additional question: is it possible to progress without the lemec (RH)? - install and test the OLED, MIDI8 etc.?
  16. Controlling plugins in Cubase

    Hello, Now i am a born again Cubase virgin, not haven used Cubase for 20 years. Started using Cubase 10 recently and noticed that there are some really useful features that may or may not be useful to people who make MIDIbox control surfaces to control DAW's.   Firstly, i noticed that Steinberg include features to "easily" assign 8 x physical tactile control (outputting MIDI CC messages) to various features in Cubase  which include quiet a large array of plug ins parameters. This feature is called "Quick Control". This, however limits you to only 8 controllers per track and 8 controllers globally.   Where i thought this was great and very useful, I also thought that it was very limiting. As some plug ins, or should i say quite a lot of plug ins, have more than 8 x things that need to be controlled. And in fact, if you are a pro working on a mix down, it isn't uncommon for you to want to control more than just one plug in per track. Perhaps the same plug ins on each track but which still means that you need more than 8 controllers per track.   I did notice there is another feature that is used with Quick Control, that can also be used with some high-er end control surfaces, which I believe works outside the Quick Control driver / feature.   This feature is called their remote control editor, and can be used up to 8 controls with Quick Controls but outside quick controls, can be used with control surfaces that use one of the following select platforms: Yamaha NUACE Euphonix System 5 - MC Avid Artists Series WK Audio ID  This feature has the potential to unlock a large amount of parameters in Cubase, so that potentially you can design the most interesting and useful control surfaces ever. Although, i am not a programmer or MIDI box expert, so not sure how easy it would be to work out how to rev eng their protocols or drivers so that you can then use it to expand the amount of features and parameters you can control with your own control surfaces. Anyone understand how this drivers for the control surfaces that are compatible with remote control editor works?  
  17. Troubleshooting midiphy SEQ v4+

    Maybe a short on the power rail? Or else soldering around pins 1/2/9/10? From the pictures, many of the joints look a bit "cold", where the solder forms a ball rather than a nice fillet. Try reflowing the pins. Pins 1 and 2 on 165s are the strobe/clock lines. They shouldn't be shorted together or to +5V/0V, and all 165s carry the same signals (check continuity between chips). Pin 10 is the serial input and receives serial data from the next 165 in the chain, so IC1 (pin 10) receives from IC2 (pin 9). You can compare voltages, signal traces etc. from the functional lemec_L. Also make sure that the connections between the plate PCB and le mec are correctly made (through-board headers).      
  18. JU60

    @Zam I just restore then mod a juno 60 for a friend using the juno-66 from tubbutec, it works great! The only critic is that they provide not enough length cable, I was obliged to change them to follow the existing cabling path, I did not change the MIDI I/O cable then cable is straight from cpu to old DCB position(not very good too). But this mod is great and add a lot of features to the juno-60 I highly recommend it to you, do not reinvent the wheel, they made it very well. Best regards Bruno
  19. daisy chain USB Midibox control surfaces

    Hello again Thanks to everyone for their help on my question and sure, i guess you guys are likely right with regards to 4 x Mackie control units to be used. I am new to cubase 10  and MIDI box / electronics beginner so just getting my head around it all. Used to use DAWs for long time, but previous versions and had a few years out. and things have changed. haven't used Cubase since 2000... lol. so a little learning needed. thanks again appreciate the help  
  20. OPL3 made in China

    Hello. A few years ago I also ordered 10 pieces in china which look exactly like yours. Mine worked great and were without problems to obstruct. best regards
  21. Troubleshooting midiphy SEQ v4+

    Hi guys, made some progress and mistakes so here I am again. Finished the JA and both Lemec-boards. JA-board was working find when tested with MIDIBOX_NG (with Midibox App all LEDS in the lowest row start to light after ~5 sec of powering on - the green LED doenst light up - in MIDIBOX_NG it works just fine when clicked though) So i went on to test the Encoders and Switches on the LEMEC boards. On the left board (first in chain) all of the Encoders work and One single Matias Switch doesnt work (The one in the down right corner - 2nd row, 8th column)  Had the 4148 Diode in the wrong direction - now it works perfect. On the right board (2nd in chain) none of the switches and encoders work and when everything is chained together for DIN test alle the 16 encoders dont react. I had to "air-wire" IC1 on the right board since i removed a bit of pad and traces on 3 pins of the 10 pin header (see photos attached). Tried to resolder IC17 on the 2nd board and now it seems that if its connected none of the encoders on any board work - if i only connect the first board to the JApcb it works perfectly fine. Also when i only connect the RH pcb (2nd in chain) to the JApcb the LEDS and switches on the JApcb wont work and i get this message when loading SEQ_R "[7621.268] load seq_r [7621.630] [MBNG_FILE_C:1] WARNING: unknown command:  test [7621.630] [MBNG_LCD] no response from CLCD #1.1 [7621.630] [MBNG_LCD] no response from CLCD #2.1 [7621.631] [MBNG_FILE_C] Event Pool Number of Items: 203 [7621.631] [MBNG_FILE_C] Event Pool Allocation: 7066 of 65536 bytes (10%) [7621.641] MBNG_MATRIX_DOUT_NotifyReceivedValue(1, 1, 0) [7621.641] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 1, 0) ..........................................." If anyone could give me a clue on what i should look i would be very thankful.  
  22. MCAN

    I decided to add a Basic Id field, 3 bits which will allow 8 Cores on the MCAN Bus. And remove the vman_prio field which was an optional feature. I think it's the best compromise.   struct { // extended u32 none:1; u32 is_request:1; u32 is_extended:1; u32 src_node:7; u32 dst_node:8; u32 app_type:3; // standard u32 basic_node:3; u32 cable:4; u32 type:4; // ports u8 src_port; u8 dst_port; }; } mios32_mcan_header_t; - Message types are always prioritized(type) - We keep the 16 MCAN ports (cable) - 8 chained cores max in the basic mode(basic_id), the basic_node field will not be used in extended mode and replaced by the src_node. Of course this basic_node id will have to be declared in mios32_config.h and different for each core on the buss, value from 0 to 7. Notes: the type of message is always a priority, the cable has priority over the id @TK. What do you think about? Best regards Bruno
  23. daisy chain USB Midibox control surfaces

    I still did not take the time for that... But if i remember well you already tried it ;) oh yes you need it in the NG.
  24. daisy chain USB Midibox control surfaces

    Hello I'm here I use direct midi uart coupling between core at 10x speed, not optocoupler. For this you need: Same PSU for all core (my 3 core are in a 3U rack) Short wire between core J11 connectors Routing configuration at "master" core where midi i/o (to/from slave) go to USB midi 2 to 4   My protocol emulation is MCU   Now for your specific configuration, If cubase only allow 1 HUI device to be configured, I suspect all your controllers will be mirrored, whatever chaining/connection between controllers you use... Are you sure you can't use MCU protocol which usually allow 4 units (1master+3 extanders) to be configured in most DAW   Best Zam   ps @Antichambre any news about MCAN ?
  25. daisy chain USB Midibox control surfaces

    There's an other solution, try to contact @Zam here, he's working on something similar, chaining multiple Core with one Master connected in USB. Best regards Bruno
  26. daisy chain USB Midibox control surfaces

    You can chain them via midi I/O easily.  If you want to connect multiple midiboxes via USB you would need to define different USB descriptions in the firmware which means you need to be able to compile firmwares by yourself. 
  27. Hello I was wondering if any one could help does anyone know if it is feasible to be able to daisy chain more than one Midibox control surface together also if someone was to create more than one control surface, each being different in design and then plugged each of these in independently via USB if the host DAW is cubase, and only allows one type of mackie Hui to be mapped inside cubase does this mean that each Midibox will behave the same?  
  28. Load more activity