Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. ok next step... "Mute" & Solo Buttons needs some external DINX and DOUTX boards (in order to make the SRIO-Gain short)
  3. About 10 years ago, I was in a car accident after completing 90% of my MB-6582 build. The carpel tunnel like pain I'm living with after a shattered wrist left me incapable of doing tedious solder work. With Wilba's permission, I paid a member here to finish the job. Unfortunately, it was obvious that the builder was a bit of a novice. Several LEDs don't light. The sustain knob doesn't change any values. When turning the filter knob, the number readings turn into random letters. But most importantly, I only seem to be getting any audio out of the SID1 output. I dealt with it for years, because I didn't have the heart to complain since it was such a kind gesture, but lately I've been itching to get this working properly. I reached out for help many years ago, but had no luck I’ve decided to try again as I got a new itch to get this thing working properly :) Is anyone willing to help me out? I don't imagine it would take much time. I have spare LEDs to match if the dead ones are truly bad. I'm sure there have since been OS updates/but fixes as well. Let me know if anyone is willing to help. I will obviously pay for the bench time! I am in the USA, but will ship to anyone willing to assist. *I have some spare SID chips i could throw in as part of the payment if anyone is interested. Thanks in advance!
  4. Last week
  5. If I remember well display is part of the CS, so it will not initialize with the firmware you use. But maybe I'm wrong. BR Bruno
  6. Earlier
  7. Hi All, a little update. I have removed a short circuit in the display connector. Now the weird alarm sound is gone and the SID module is up and running. Unfortunately the LCD display doesn't work. Maybe I have damaged a GPIO of the PIC. B.R. Giorgio.
  8. Hi all, I'm trying to resurrect a old MIDIBOX SID that I have built for an eurorack modular synth project. My setup is composed by the following: 1 16x2 LCD display GDM1602B Xiamen ocular 1 mbhp core made by smashTV running PIC18F452 BSL V1.2B MIOS V1.9E 1 SID board made by smashTV , 8580 is installed the application is setup_8580_without_cs.hex In past the system was working perfectly but the cable connections where unstable, so I have decided to rewire It. After the rewiring I have double checked all the connections but the system doesn't work anymore. I have also checked all the voltages . the synthoms are the following: 1) the display is blank (no messages, only a solid rectangle at the system boot) 2) after the system boot the SID is generating a loop of 4 notes like an "alarm tone" 3) Sending a Query in MIOS studio stops the "alarm tone" with the following message: Operating System: MIOS8 Board: MBHP_CORE or similar Core Family: PIC18F Application is up & running 4) Sending notes in MIOS studio results only in audible "CLICKS" Have you any suggestions about? Any hint would be very appreciated. Thanks, B.R. Giorgio.
  9. @Hawkeye Thanks for providing more details and trying to fix this issue. I know what you mean by rescanning/reconnecting the Core after uploading via MIOS Studio. It's not ideal but workable. I really hope Thorsten will look into it and update the toolchain. Getting an additional computer is really a hassle. This hobby is already expensive enough. It should also help to get more people onboard with MidiBox, having lower hurdles.
  10. @tago Thorsten released the Windows toolchain - and it is working, just accessing the 64KB extra memory region of STM32F4 will crash the app, maybe it is a simple linker setting, but i investigated a while back and found no easy solution. On top, under windows, USB MIDI transfers are often very unstable, i.e. when flashing new firmware releases when developing you often have to either rescan MIDI ports or restart MIOS Studio for continuous uploads, which is really frustrating when developing. That is not necessary on a Mac, so you know my recommendation - you can get a used macbook air for ~300€ - while it's not as fast as an M1, it will do the job - imho for that price, it's not worth trying to improve the windows situation with the upper 64kb block, as the Windows USB stability situation cannot be fixed by us. Many greets, Peter
  11. Ok sorry, I've found the answer here windows_mios32_toolchain_core [MIDIbox]
  12. Hello, I'm building a Midibox Sid V1 (yes, it's been sleeping for years in a drawer ) and I don't understand how to rebuild the files. I found that I should use a make.bat file to rebuild, but it's not in the midibox_sid_v1_7303e archive. Thanks for your help.
  13. Do you mean stable USB drivers for development purposes? I'd only use a Hackintosh/Mac to be able to compile an app, not for music making, if there is no other way around it. Do you know who did the original Windows toolchain?
  14. @tagoyup, i'd either recommend a hackintosh or a cheap used mac machine, it will also give you a lot more stable USB MIDI drivers. Many greets, Peter
  15. after searching, Msys 2 will automatic convert unix/posix path style to windows (using cygpath), so if the mios32_path variable $MIOS32_PATH = /c/to/your/mios32/base the msys2 will auto convert to $MIOS32_PATH = c:/to/your/mios32/base # resulting this c:/to/your/mios32/base/Mios32/mios32/include/makefile/common.mk:143: *** multiple target patterns. Stop. this auto conversion can disabled use MSYS2_ENV_CONV_EXCL=* an then call make MSYS2_ENV_CONV_EXCL=* make but, after the unix style path correct (use /c/... instead of c:/), make still cant read common.mk $ MSYS2_ENV_CONV_EXCL=* make Makefile:55: /d/savePCB/2022Project/polyphonicSynthesizer/Program/Mios32/mios32/include/makefile/common.mk: No such file or directory mingw32-make: *** No rule to make target '/d/savePCB/2022Project/polyphonicSynthesizer/Program/Mios32/mios32/include/makefile/common.mk'. Stop. is this possible that problem come from make itself, cause my make version was build for windows 32 $ make --version GNU Make 4.3 Built for Windows32 Copyright (C) 1988-2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. any help really appreciated, thanks
  16. Thanks @Hawkeye A pity Windows is not supported anymore. I think that's makes it lesser accessible to us Windows people. Is there really no one in reach who has the chops to update the toolchain? For the love of the Midibox project. If i only had an idea about those things, i would do it. Maybe i can go the Hackintosh route, but that sounds like much work better invested in other things. So with a Hackintosh i can compile the most recent NG app? @TK. What do you think about the situation? Any chance to get it working for Windows/Linux again?
  17. @tago i switched to a Mac m1 a while ago and never looked back, it's awesome, as powerful as my 8-core i7, which cost a lot more, using a fraction of the electrical power at a higher single-core speed (a lot more responsive). You can still get a mini m1 for a bit above 600€, which is a steal for the offered package. The existing (old) toolchain/compilation works fine here, also working with 64kb "upper RAM" for the STM32F4. Upgrading the toolchain to the newest release would be some work, so i'd recommend going the established route - i had used a "free" Hackintosh before, so it's also a possibility to build e.g. MIDIbox NG on most common PC hardware, too. The MIDI implementation on Mac is also way better than anything Windows, so i did not investigate further. Best regards and enjoy! Peter
  18. interested in stm32f4 and discovery.
  19. interested in tms32f4 and 2 midi io . rest i dont need.
  20. Hi, Any tips how to optimize NG to get better velocity performance? I'm getting very few velocities. I'm getting a very coarse velocitiy resolution. I'm using a STM32F4 core and have a 5 octave keyboard plus an AINSER8 attached. No menu or displays. I'm thankful for any tips.
  21. pcb arrive, soldered 4 off them (12 channels) - the 4 others i make a nother time. (24ch in total) the display drivers from Andy work great again! the midibox code is working, the max for live patches too. (at least for this state i am happy to get automaticly the Channels names, and the Macronames!!! hell yeah!)
  22. hey, i got same problem as you, and still search for solution too i found this old threads, say this was because "UNIX style PATH" but after checking my MIOS32_PATH, its already same as TK show in that post $ echo $MIOS32_PATH /d/savePCB/2022Project/polyphonicSynthesizer/Program/Mios32/mios32 but when i run make(mingw32-make) this path change as windows path (use colon : instead of slash /), same as yours @arty D:/savePCB/2022Project/polyphonicSynthesizer/Program/Mios32/mios32/include/makefile/common.mk:143: *** multiple target patterns. Stop. is this problem cause MSYS2(i use Msys2) setting? because the midibox wiki still use MSYS version 1.0(as shown in link below), and official GNU make doc says "the path need not to contain colon", but how to setting it? http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core thanks for any help
  23. Something you can do is using the shield as ground, some recent machines doesn't provide GND on Midi out pin 2, there's a chance shield is connected, this cable adaptation needs the GND to work properly. There's some explanation about it above in the thread.
  24. How much do you ask for the stm32F4 discovery board?
  25. Ah, no complains from here! Thanks for caring. Seems like there exist a bunch of standard midi implementations. Just ordered the Conduit - hope that works. Best, Tim
  26. On my side it works with a MOTU fastlane or both MTPAV(old and USB model) I think there's no rule, here I tried to find a workaround to avoid commercial boxes, I never said it will work without exception ;) Still better to buy or build one of this active boxes, with optocoupler inside. BR Bruno
  27. Hey there, I have a Meris Ottobit jr. I´d like to control. First I used an Elektron Cycles which has 3.5mm Midi I/O. Using a TRS cable TX works (CC & PC). For being able to TX/RX, I built the cable (as described by Bruno, with Pin 4 bridged). Plugging that to my RME Fireface UC I get RX (from Pedal) but cannot TX! Using a Behringer BFCF000 I can TX but get no RX!! So I got myself an iConnectivity mioXL today - neither RX nor TX!!! Taking the Elektron again for testing both RX/TX work with the built cable (but can´t use this as an interface). Any ideas on that? ...or is it just chance? Thanks, best Tim
  1. Load more activity
×
×
  • Create New...