All Activity

This stream auto-updates   

  1. Past Hour
  2. MIDI Implemtation for EUCON

    Hello. Thorsten Sure, i understand entirely. I suggested this particular solution for people who may be frustrated with the limitations of the Mackie Control protocol. Although to be honest, i may not have a full understanding of what can be done using the Mackie Control etc. I also understand the legal implications, although you may understand that i have less respect now for big global corps haven had a number of innovative designs concepts stolen from me a number of years ago, after i contacted several pro audio companies  with a ground breaking idea, for the exchange of a few bits of equipment to start up a small charity based recording studio  But alas, all the companies knocked back the idea, but then 1 year later, all of them and more had designs based on my concept but what was even more ironic, is that they missed out a few really important elements to the design which i didn't tell them about so they released designs that weren't as good as they could be. Still, a number of the mixers based on my concept that they stole won big design awards. and i didn't even get even a mention. That's how these people work. nothing is below them.  So. me having to rev eng one of their badly designed devices so i can build my own well designed device is what i am resulted to But never mind, this is the way of the world and even more so in the entertainment industry.  sure. no problem. i will not publish any copy write work that i do not have the permission to use even if half the industry has plagiarized my ideas.... but that's their transgressions I guess that is generally what happens to innovative people, i.e. Joe Meek etc. but nevermind. live long be happy. Thanks for your platform. You are very kind to give this to people.!      
  3. MCAN

    We could reserve a bootloader location to make this basic_node number configurable without touching the source code. Similar the way I did for other "permanent" flags & values. Best Regards, Thorsten.
  4. Today
  5. MIDI Implemtation for EUCON

    Reverse engineering a protocol for private purposes is one thing, publishing the information another. In any case: please don't publish any specific information about this protocol in this forum, this could bring me (as the forum owner) into serious legal issues! Best Regards, Thorsten. P.S.: I haven't looked into this protocol because I don't like the license. Anything which can't be openly published isn't interesting for my projects.
  6. MIDI Implemtation for EUCON

    hello thanks for your advice, although, to be honest mate. i am not talking here about manufacturing but simply making a hobbyist control surface that uses their protocol. From a MIDIbox mindset, i see EUCON as having massive potential. I also realise that other people out there may also see the potential when its pointed out, and there are people in this world who do things only for personal gain, and do not want anyone else to gain. Not saying that you are such a person, but there are people who do.   Anyway i could see that developing a control surface that mimicked the other manufacturers control surfaces wouldn't be that hard to create especially as Cubase now has this Remote Control Editor feature which allows any control surface that is compatible to e mapped to practically any parameter  in cubase.   So all a person need to do is get hold of one or more of the official control surfaces (Which includes Avid's Artist Series) and simply sniff the midi data from the devices and then program their own device to send the same data, As the drivers are given with the original devices, you don't even have to write software to run on PC as long as your hard ware device outputs data that is the same in nature as the compatible desks   I highly doubt that Avid or any one else will investigate or prosecute a hobbyist who make 1 single control surface that uses their driver as it would likely be bad for PR but also not be particularly cost effective.           
  7. New eurorack modules from midiphy - preview

    @latigid on   I didnt get that far.  The TI parts good and proven (all the MI stuff, OC, Performer etc) so I wanted to use those parts.  They would need a driver for sure but again, given all the STM based hardware out there using them, I figured they would be a good choice since those could be used as a guide
  8. JU60

    Salut Bruno ! Yes you'r right, that also my conclusion since I post this But I personally don't like the idea to swap the MCU I will probably go for the CHD solution http://www.chd-el.cz/index.php?id=468&lngid=en Hooked at a midibox core (via J11) to have USB midi and 16 ch Ain/Aout (J19) to read/write analog pot and automate all parameters If only I have time and code skill, I'll design a full midibox HW and SW solution for Juno60 retrofit... Best Zam  
  9. MIDI Implemtation for EUCON

    Hello EUCON is proprietary and AVID (who buy it from Euphonix) don't let anyone manufacturing compatible HW controller. Even industry big name that offer digitally controlled desk with at least five 0 on the bill can't implement eucon... IIRC the only access is for soft dev that want to implement the protocol for they app, DAW or plugins (to be controlled by HW) I suppose you need a confirmed company to have access to SDK, and sign restrictive NDA. So my suggestion is... forget it Best Zam    
  10. Troubleshooting midiphy SEQ v4+

    Hi Pat, Good that the other issues are sorted. For the multiple LEDs, load up _NG again and look at the DIN events (set debug on) when you push the buttons. Probably you get just one switch event per press/per depress. If the LED events are back to normal perhaps the HW config file is mis-configured? I'm a bit surprised that not all of the bottom row is on. Maybe SW17 has its LED in backwards? In fact, check all LEDs for correct polarity. Check whether pins of R1/R2 are shorted together.  Check whether any of the cathodes are shorted together. For this, test for continuity between the top-left pads (as viewed from the front of the MEC switches. As usual, pictures of the soldering would be useful for diagnostics.    
  11. 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?
  12. Yesterday
  13. 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          
  14. 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  
  15. ST Electronics Nucleo 144 boards

    https://www.st.com/en/evaluation-tools/stm32-nucleo-boards.html  
  16. 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
  17. Troubleshooting midiphy SEQ v4+

    thanks, nice info - will do it when i figured out whats wrong at the moment :(
  18. 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  
  19. 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?  
  20. 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.
  21. 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?
  22. 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...
  23. 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)
  24. 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.?
  25. 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?  
  26. 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).      
  27. 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
  28. 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  
  29. Load more activity