Search the Community

Showing results for tags 'midibox'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 98 results

  1. Berlin Trip, System Checkup

    Hi you all!   Doing some gear setup checking before traveling to berlin came out with this little 5 minutes jam.   This Jam was recorded using Midibox SeqV4 using 8 tracks, Inversed Shuffle for all tracks with 16% of intensity for all of them. 1 pattern loop only.   https://soundcloud.com/midilab/berlin-system-checkup   Gears list: 8 Channels Virtual Analog Mixer Harrison Mixbus (Running on a miniitx PC headless and armless, controlled via MIDI used as main mixer, effects and emulations). MIDI Sequencer MIDIBOX Seqv4 4 voice analog synthesizer Davesmith Tetr4 Emulated 303 and 808 - VB303 and TS808 2 Channel Sampler loop machine Controllers - UC33 and Nanocontrol
  2. Drum notes not saving? bug?

    I seem to have discovered a bug with drum tracks...   I have turned Group 1 Track 4 into a drum type (2*32/128)   most of the default midi notes work with my volca (BD=C1, SD=D1 etc) and these work fine   BUT the ones that I have to change (PH from G#1 to G1 for instance) are being accepted initially (ie I can set them up and then sequence the notes correctly) BUT upon erasing the track they always go back to their defaults (G1 in this case) ...even if I have gone into presets and logged these changes as a new preset (I created a kit called BEATS in this case with all the notes mapped correctly)   How can I get these changed notes to just "be" the notes, even after I erase the track, or is this a bug?   thanks   Phill
  3. #1 front

    From the album My #1 MIDIbox SEQ

    What shall I say, I'm just proudly showing off.

    © WTF Public License

  4. Hallo und Guten Abend,   erstmal großes Lob an alle, die hier mitarbeiten und entwickeln und testen und auch bauen! Das letzte Mal habe ich mir vor ca 5 Jahren das MIDIbox Projekt angeschaut und ich bin echt beeindruckt, wie gut es weiterentwickelt wurde! :)     Ich habe mir in den letzten Tagen einen kurzen Entwurf für einen Midicontroller gemacht und wollte mal hier fragen: - ist das Konzept an sicht mit der Midibox NG (STM32F4 oder LTP17??) möglich? (9TouchFader, 8RE mit Schalter, 8-9 OLEDS/LCDs, Buttons,LEDs,...nichts außergewöhnliches oder?) - wo könnte es Schwierigkeiten geben, bzw was ist Hardware- oder Softwaretechnisch nicht möglich?     Im Anhang ist ein Ãœbersicht wie die Oberfläche aufgebaut sein soll. Wie einigen vielleicht auffällt, ist das Design sehr stark an Cubase orientiert.   Beim Hardwareaufbau und auch bei der Software sehe ist nicht so das Problem, allerdings stehe ich etwas auf dem Schlauch was die Kommunikation zwischen Controller und DAW angeht.   Kurz gefasst: Kann der Controller so vollständig mit Cubase funktionieren?   Länger: - Cubase bieten den Generischen Controller an, allerdings lassen sich damit viele Funktionen nicht umsetzen (es scheitert schon am fest zugewiesenen Masterfader) - demnach müsste man z.B. auf das Mackie Protokoll umsteigen, dazu habe ich auch eine schöne Dokumentation gefunden? Hat da jemand Erfahrung, funktioniert das damit? Speziell die 8 LCDs/OLEDs?     Eine generelle Frage, zu der ich bisher noch keine Antwort gefunden habe: Lassen sich mit sysex-Befehlen theoretisch (notfalls durch ausprobieren) jede Funktion einer DAW steuern, die irgendwie durch einen anderen MIDI-Controller gesteuert werden kann?  Damit könnte man ja dann z.B. "fehlende" Funktionen des Mackie Protokolls beheben?     Danke schon mal im Vorraus :)
  5. Screenshot 24.07.2014 23:49:22

    From the album MB LC

    Ðе определилÑÑ Ñ Ñнкодерами и кнопками, поÑтому плата оÑталаÑÑŒ не завершена.

    © testlab c-a

  6. Screenshot 24.07.2014 23:48:58

    From the album MB LC

    Ðе определилÑÑ Ñ Ñнкодерами и кнопками, поÑтому плата оÑталаÑÑŒ не завершена.

    © testlab c-a

  7. Extended Routing

    Hi everybody,   finally I found the time to start a project on my new LPC17 core. I want to replace my current MIDI router (PIC-based) with the MIDIbox NG application. I have MIDI devices connected to both IN/OUT ports and a computer via USB. All MIDI channels are used and need to be routed/duplicated to different ports.   Here's my problem: MIDIbox NG offers only 16 router nodes, but I need at least 32 to route my channels properly. Is it somehow possible to increase the number of nodes? A different solution would be to offer a range of filtered source channels instead of single ones. E.g. could we somehow group these 5 nodes into a single one (without using "All")?   ROUTER n= 1   src_port=IN1  src_chn=5   dst_port=OUT2  dst_chn=17 ROUTER n= 2   src_port=IN1  src_chn=6   dst_port=OUT2  dst_chn=17 ROUTER n= 3   src_port=IN1  src_chn=7   dst_port=OUT2  dst_chn=17 ROUTER n= 4   src_port=IN1  src_chn=8   dst_port=OUT2  dst_chn=17 ROUTER n= 5   src_port=IN1  src_chn=9   dst_port=OUT2  dst_chn=17   That would help me a lot....   Best, Sebastian
  8. Midibox NG inside

    From the album Midibox seq_v4 und MbNg_cv_fm

    On the left side you see the STM32F4 core with its shield and the DINX /DOUT Modules. On the right side you see the new residing of my old midibox FM, the midibox CV and a switched power supply which delivers +5V +/-12V with any notebook PS. Despite the setup with two LM2576 and a MC34063, it is very low on noise.
  9. Midibox Seq_v4

    From the album Midibox seq_v4 und MbNg_cv_fm

    © Midibox Seq_v4

  10. [WTB] Any Midibox SID

    Looking for any old Midibox SIDS you have moved on from. If you have one sleeping in dust, get at me with some info and price. Some pics would be nice too. Thanks.
  11. sammichSID for sale

    Hey all, I have one of my two sammichSIDs up for sale. It's complete and comes with an Australian plugpack. I'm downsizing my setup and getting rid of a few things that are excessive. It's got green LEDs and 2x 6582a SIDs (I think, will double check). It has only been used in my home studio and has not been gigged or around smoke etc. Am looking for $250AUD for the lot.   Get in touch here if you're interested. Will try and post a photo or two when I get home.    
  12. Hi there, I have just taken ownership of a Midibox Seq V4 from a builder on the forum.   the machine is beautiful and I am loving the whole concept , I just wondered if I could ask a few polite questions that some of you who know more than me may be able to answer.   1. Is there any way to use the F1, F2, F3, F4 buttons for accessing different pages than their defaults? basically I would LOVE to bring the following functions to the top level of themenu hierachy as I am using this unit in realtime performance ..   1. Realtime record 2. the FX page ( as I change scales on the fly extensively) 3. length page    I would then keep F4 as a means to quick access the other main menu page (not got the unit with me at the moment but I am sure one of the F keys already does this).     is this something that could be rewritten and then uploaded into the unit?   2.. is there a quick way to clear all notes and start again from settings that I like to have as default? the reasoning behind this is simple, I like to know my 4 parts are set to certain lengths and forced to scale, but beyond that I do amm my pattern entry live from a blank canvas...then at the end of the song , I need ot be able to quickly erase all the data and star the next song...so far I have only been able to either do this by removing the staps manually or unplugging and replugging the unit...I am sure Im missing something?   thanks in advance for your replies, I look forward to becoming an active member in the group.   Phill MyOneManBand 
  13. Analog Mind

    Hola,   it has been a busy year already, but finally found the time to hit the keys, this time focussing on the Alesis Andromeda (only accompanied by the FS1R and the Machinedrum) - copter footage filmed in Fuerteventura - hope you enjoy! :-)   http://youtu.be/V_fToovFZ_Q   Thanks for watching, listening and your comments! :-) Many greets, Peter
  14. #1 back

    From the album My #1 MIDIbox SEQ

    © WTF Public License

  15. ...now to debug

    From the album nextSteps

    My new synth. Lots of work still to go
  16. i'm finally continuing my work on using liveapi to integrate mios32 and ableton live. this works by giving programmers a large set of functions they can call to manipulate damn near anything in live. another set of functions are automatically called by live, allowing you to track whatever is going on. this will let users play a live set without ever looking at a computer screen. the possibilities can be a lot more than that. to do this, i've made a protocol that works over midi and allows a midibox to seamlessly communicate with a liveapi script. on the programmer's side of it, you just have a simple set of functions to play with. look at it as a midibox API for LiveAPI, extending mios into live, and vice versa. currently this is being developed for live 7.0.14. i'm fairly confident that most of the code will work for live 8, and i'll try to get a new version going once this is complete. for a teaser, here are some of the functions at your disposal. keep in mind i haven't gotten to the clips, tracks, or track devices yet, but eventually you'll be able to go as far as bring clip or plugin parameter names into the midibox, and of course monitor what is going on with all of it. this list is growing by the day. functions you can call from mios: void MBLIVE_SONG_SetTransport(u8 state); void MBLIVE_SONG_GetTransport(); void MBLIVE_SONG_SetRecord(u8 state); void MBLIVE_SONG_GetRecord(); void MBLIVE_SONG_SetOverdub(u8 state); void MBLIVE_SONG_GetOverdub(); void MBLIVE_SONG_SetFollow(u8 state); void MBLIVE_SONG_GetFollow(); void MBLIVE_SONG_SetBackToArrangement(u8 state); void MBLIVE_SONG_GetBackToArrangement(); void MBLIVE_SONG_SetDrawMode(u8 state); void MBLIVE_SONG_GetDrawMode(); void MBLIVE_SONG_SetArrangementPosition(u8 mode, u16 val); void MBLIVE_SONG_GetArrangementPosition(); void MBLIVE_SONG_SetTriggerQuantization(u8 state); void MBLIVE_SONG_GetTriggerQuantization(); void MBLIVE_SONG_SetTempo(u8 mode, u16 value); void MBLIVE_SONG_GetTempo(); void MBLIVE_SONG_SetTempoNudgeDown(); void MBLIVE_SONG_SetTempoNudgeUp(); void MBLIVE_SONG_SetTimeSignatureNumerator(u8 mode); void MBLIVE_SONG_SetTimeSignatureDenominator(u8 mode); void MBLIVE_SONG_GetTimeSignature(); void MBLIVE_SONG_SetGrooveAmount(u8 mode); void MBLIVE_SONG_GetGrooveAmount(); void MBLIVE_SONG_SetMetronome(u8 state); void MBLIVE_SONG_GetMetronome(); void MBLIVE_SONG_SetLoopStart(u8 mode, u16 val); void MBLIVE_SONG_GetLoopStart(); void MBLIVE_SONG_SetLoopLength(u8 mode, u16 val); void MBLIVE_SONG_GetLoopLength(); void MBLIVE_SONG_SetPunchIn(u8 state); void MBLIVE_SONG_GetPunchIn(); void MBLIVE_SONG_SetPunchOut(u8 state); void MBLIVE_SONG_GetPunchOut(); void MBLIVE_SONG_SetSessionArrangementView(u8 state); void MBLIVE_SONG_GetSessionArrangementView(); void MBLIVE_SONG_SetClipDeviceView(u8 state); void MBLIVE_SONG_GetClipDeviceView(); void MBLIVE_SONG_SetBrowserView(u8 state); void MBLIVE_SONG_GetBrowserView(); void MBLIVE_SONG_SetDetailView(u8 state); void MBLIVE_SONG_GetDetailView(); void MBLIVE_SONG_GetTrackCount(); void MBLIVE_SONG_SetSelectedTrack(u8 track); void MBLIVE_SONG_GetSelectedTrack(); void MBLIVE_SONG_GetSceneCount(); void MBLIVE_SONG_SetSelectedScene(u8 scene); void MBLIVE_SONG_GetSelectedScene(); functions called by live: void MBLIVE_SONG_NotifyTransportChanged(u8 state); void MBLIVE_SONG_NotifyRecordChanged(u8 state); void MBLIVE_SONG_NotifyOverdubChanged(u8 state); void MBLIVE_SONG_NotifyFollowChanged(u8 state); void MBLIVE_SONG_NotifyBackToArrangementChanged(u8 state); void MBLIVE_SONG_NotifyDrawModeChanged(u8 state); void MBLIVE_SONG_NotifyArrangementPositionChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyTriggerQuantizationChanged(u8 state); void MBLIVE_SONG_NotifyTempoChanged(u16 value); void MBLIVE_SONG_NotifyTimeSignatureChanged(u8 val0, u8 val1); void MBLIVE_SONG_NotifyGrooveAmountChanged(u8 value); void MBLIVE_SONG_NotifyMetronomeChanged(u8 state); void MBLIVE_SONG_NotifyLoopStartChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyLoopLengthChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyPunchInChanged(u8 state); void MBLIVE_SONG_NotifyPunchOutChanged(u8 state); void MBLIVE_SONG_NotifySessionArrangementViewChanged(u8 state); void MBLIVE_SONG_NotifyClipDeviceViewChanged(u8 state); void MBLIVE_SONG_NotifyBrowserViewChanged(u8 state); void MBLIVE_SONG_NotifyDetailViewChanged(u8 state); void MBLIVE_SONG_NotifyTrackCountChanged(u8 trackCount, u8 returnTrackCount); void MBLIVE_SONG_NotifySelectedTrackChanged(u8 track); void MBLIVE_SONG_NotifySceneCountChanged(u8 count); void MBLIVE_SONG_NotifySelectedSceneChanged(u8 scene);
  17. Bonjour,   Je souhaite améliorer une table de mixage pour que les fader puisse contrôler mon logiciel de son (tout en concevant leur fonction première). Donc 32 potards réel reliés à 32 virtuels via une Midibox en USB.   Je ne sais pas exactement ce qu'il me faut comme matériel, un CORE et une carte USB  c'est sûr mais pour le reste je ne sait pas si j'aurai besoin de LCD et des autres cartes.   Si quelqu'un qui a réalisé un projet similaire (ou pas) pouvait me donner quelques conseils ce serai super!!!
  18. Hola,   a new track live from the studio using the MIDIbox SEQ, an Alesis A6 and the MB6582 (and some aerial footage :-)) I tried to re-record this one in cubase, but it would sound far worse than the original take, so the original it is :-).   Needless to say, i am really thankful for the MIDIbox hardware - fantastic and so much better than software for me :-)   Many greets and thanks for watching and listening! Peter  
  19. Hallo, ich bin neu bei MIDIbox und wollte eine MIDIbox SID V2 bauen. Jedoch finde ich keine konkrete Liste von Teilen die ich beim Bau einer ganzen Midibox Sid V2 brauche. (preis ? ca 200€ ? ) Das einzige was ich fand waren listen für die Minimal Version oder der sammichSID version / mb_6582 Version. Ich will jedoch diese Version Bauen    Ich kann gut Löten und hab auch ein einigermaßen gutes Grundwissen über Elektronik.   Versteh ich etwas falsch oder warum finde ich keine Details? (Suche seit 1 Woche auf den Seiten)   -Steffen    
  20. midibox Cv V2 CS 04b

    From the album imp`s Zeug

  21. Hi all,   I am wisefire. I was kind of active on here a long time ago, and I promised that one day i'll be back to complete (and document) my Midibox SID. Well the time has come to build it.   I have the version of wilbas MB6582 core board directly from wilba. The idea back when I bought it was to build my own control surface around it, to be honest if I could make that choice right now I wouldn't be so sure, but i've got all the buttons and stuff for it already so let's start this adventure!   Soldering the resistors was first, here is a timelapse.   The next evening came the capacitors.   i'll keep you guys posted!  
  22. bonjour a tous , j'ai récupéré une sammichSID dérniérement et je viens de me rendre compte en lisant le manuel que j'ai quelques problémes. Alors dans un 1er temps dans le menu clock je n'ai que sid, bpm et mod d'affiché, il me manque out, je comprends pas pourquoi je ne l'ai pas. Ensuite l'autre probléme que j'ai remarqué est assez étrange, cela concerne toujours l'affichage mais ce coup ci c'est lorsque je suis dans la fonction sid il y a affiché 1 puis 3 étoiles aprés le 1, alors que dans le manuel on voit écrit 1 suivi de 3 petits traits et lorsque justement je veux séléctionner une des deux sid ça ne bouge pas, c'est toujours pareil 1 suivi de 3 étoiles. Je tiens à préciser aussi que lorsque j'ai récupéré la sammichSID je l'ai ouverte pour regarder dedans et j'ai bien fait car la j'ai été outré de voir une des pattes de la 2éme puces qui n'été pas rentré dans la socket, cette patte était complétement pliée!!! Du coup j'ai sortie la 6581 et éssayé de la redrésser correctement j'ai réussi, j'ai remis la 6581 dans sa socket mais toujours le même affichage au niveau de la selection de la puce sid je me demande si ma sammich ne marche pas sur une seule sid ? Je remercie d'avance toutes personnes pouvant m'aider! Merci    Coordialement damien
  23. Calibrate

    From the album Antix MidiBox SID

    Testing the DACs
  24. hello, I'm trying to compile my own setup.asm file (J5 enabled+encoder+aout NG) in mplab 7.4 (pc version)   here is the result on my screen :   Clean: Deleting intermediary and output files. Clean: Done. Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p18F452 "setup TORB.asm" /l"setup TORB.lst" /e"setup TORB.err" Error[108]   C:\MIDICV\SETUP TORB.ASM 2 : Illegal character ( ) Error[129]   C:\MIDICV\SETUP TORB.ASM 4 : Expected (END) Halting build on first failure as requested. BUILD FAILED: Wed Jan 09 04:28:51 2002     I don't understand why I've two errors. The Expexted END is not in the original .asm file downloaded on UCAPPS....   Any idea to help me compiling my config ? my midibox CV is ready to start ....but before I need to update and make and .hex file     thank you by advance for helping me :-)   W
  25. midibox fm

    From the album MIDIBOX FM