All Activity

This stream auto-updates   

  1. Today
  2. micro-second counter?

    i set: #define RESOLUTION 10 // in uS #define TIMER_NUM 1 // TIM3 #define TIMER_PRIO MIOS32_IRQ_PRIO_HIGH which give me good timing   thx.
  3. micro-second counter?

    Hi Mike, I'm not sure but 1ms is the smallest rate you can achieve with RTOS Tasks. Use MIOS32 Timer instead, the timer can be set to a multiple of 1us Check this: Best regards Bruno
  4. Yesterday
  5. micro-second counter?

    i need a count from 0-1ms (to modulate the triggerlength for a TR606 - in order to get some velocity-like reaction from the machine) count is not the problem, more the execution of the function also to make a RTOS-Task for it - i know very well and use it a lot.... but since now i dont needet anything under 1ms Rate...   when change from (taken from tutorial 006_rtos_tasks) vTaskDelayUntil(&xLastExecutionTime, 1 / portTICK_RATE_MS); to vTaskDelayUntil(&xLastExecutionTime, 1 / 10); has it effect or is it "fixed with min 1ms" ? are there MIOS functions i can use instead which have a better call-rate?   thx 4 info
  6. ok i thougt maybe there is something with the "browse-button" programming and Linux Mint Mate19? in context with PATH-grammatic (/) so i readout the Path of the hex file with: t@t:~/Downloads$ readlink -f project.hex /home/t/Downloads/project.hex i then paste the result directly into the Browser-Field of the MIOS-Stock-Built and Mios_Studio i built on this machine (today-after installing all the librarys) and it F***ing Works!!! the browser Button, is not in function with Linux Mint Mate 19!   Version Linux Mint 19 Tara 64-bit Kernel Linux 4.15.0-38-generic x86_64 Version Linux Mint 19 Tara 64-bit    
  7. i then built a Mios_Studio on this Linux Mint Mate19 Machine, but the build give me the same error when loading a hex file: t@t:~/midibox/mios32/trunk/tools/mios_studio/Builds/Linux$ mios_mate19-2 JUCE v2.0.38 JUCE Assertion failure in juce_File.cpp:149 [1]+ Angehalten mios_mate19-2 t@t:~/midibox/mios32/trunk/tools/mios_studio/Builds/Linux$ aha.... i then searched again for "juce_File.cpp" and i found it under: /home/t/midibox/mios32/trunk/tools/juce/modules/juce_core/files which now exist because i had to unpack the juce files in order to make a BUILT so line 149 says: jasserfalse - which i think is a break command in this ELSE if... which has something to do with Absulute Pathes and "/" (((dont know what that mean))) -by the way i searched the .hex-file with the "browse-button" since a drag and drop of hex never worked on Linux anyway (in this case it of course also not worked!) jassertfalse; else if (! path.startsWithChar (separator)) { #if JUCE_DEBUG || JUCE_LOG_ASSERTIONS if (! (path.startsWith ("./") || path.startsWith ("../"))) { /* When you supply a raw string to the File object constructor, it must be an absolute path. If you're trying to parse a string that may be either a relative path or an absolute path, you MUST provide a context against which the partial path can be evaluated - you can do this by simply using File::getChildFile() instead of the File constructor. E.g. saying "File::getCurrentWorkingDirectory().getChildFile (myUnknownPath)" would return an absolute path if that's what was supplied, or would evaluate a partial path relative to the CWD. */ jassertfalse; #if JUCE_LOG_ASSERTIONS Logger::writeToLog ("Illegal absolute path: " + path); #endif } #endif when clicking in the mios-studio browser-adress-bar i get this for example: /home/t/Gtk-Message: 17:35:54.994: GtkDialog mapped without a transient parent. This is discouraged. /home/t/Schreibtisch/project.hex the rapid hole getting deeper, and i even dont know "i am in the right hole?"
  8. i then tryed to install: sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install multiarch-support sudo apt-get install gcc-multilib what changed nothing (stock offically linux built, and my own built - no change off error picture then i installed 430mb of libarys done with: apt-get install ia32-libs-multiarch which changed nothing...
  9. i also tried a on my own compiled version of mios studio - and it fries when try to open a hex file t@t:~$ mios_msi JUCE v2.0.38 JUCE Assertion failure in juce_File.cpp:149 [1]+ Angehalten mios_msi t@t:~$ since i dont found juce_file.cpp in the mios_studio binaries... i only found juce_file.cpp in for example: /home/t/midibox/mios32/trunk/apps/synthesizers/midibox_sid_v3/juce/JuceLibraryCode/modules/juce_core/files but there is no Line 149 (it is but it is a comment only...)   have no idea, whats happening, maybe there are more i386-librarys that are what needet - but to bad they make no error - so i cant find out which one left, or is there a other problem
  10. running but not workgin: when trying to open bootloader.hex (for my lpc17) it says: Reading project.hex ERROR: File doesn't exist! (but it exist!:/home/t/Downloads/mios32_bootloader_v1_018/MBHP_CORE_LPC1769/project.hex)   the linux terminal give no error messages --- the error only comes from Mios Studio 2.4.6 itself   puuuh... bad
  11. i have a 64bit Linux Mint Mate 19   mios_studio is not running: meen when i double click, nothing happens, when i open it with Command-Line i get error messages like: "Error while loading shared libraries: libfreetype.so.6" and others... this things are installed on my system, when i then manually install the i386 library of it - i get it running. for example: sudo apt-get install libx11-6:i386 sudo apt install libxext6:i386 sudo apt install libfreetype6:i386 sudo apt-get install libasound2-plugins:i386 after that mios_studio is running.
  12. Last week
  13. Starting MB6582 build

    thanks - that's useful to know on the barrel jack, was wavering a bit towards the din plug anyway for neatness tbh.
  14. I made a small batch of custom MB-6582 panels a couple years back. They’re black with white print, have a little “MB•6582” logo on them, and have a trippy graphic behind the mod matrix. I sent out four sets of panels to forum members for their own builds. Just curious if anyone ever got theirs put together. I want to see my babies out in the wild ;)
  15. Starting MB6582 build

    Also: Pictures are working now, looks good! Those filter caps are a little hilariously big, lol. And I love the rainbow knobs on the other synth! Reminds me of the original C64 marketing logos. I wanted to do something similar, but it’s relegated to just the feedback knobs around back.
  16. Starting MB6582 build

    I had originally planned on a standard barrel jack for power. I ended up going with the 7-pin DIN for a few reasons. Probably the main reason is that the header pads for a panel-mounted power jack are close enough to the edge of the board that they kind of interfere with placing a panelmount jack at the same location. You might be able to get around this by placing the jack higher up on the rear panel or elsewhere on the panel altogether, by using angled headers instead of straight, or by simply wiring the jack directly to the board (though this list option will make servicing in the future more difficult). The above hurdle could have probably been surmounted, but lo and behold, a 7-pin DIN connector randomly fell into my lap. I had been asking around for a source on the OG power switch, and a kind forum member hacked off a piece of original C64 PCB for me that contained both the DIN jack and the switch. Obviously this won’t be the case for y’all, but having the part in hand made the decision a bit tougher. Other, minor reasons I went with the DIN jack: no need to redesign that part of the panel (I had custom panels made but I didn’t want to change any more than I had to), and no possibility of using the wrong voltage/polarity power adapter ever. Attaching the new jack to a power adapter was really easy; don’t let that be the only reason you shy away from the DIN connector. That all said, if the part hadn’t magically appeared for me like that, I’d have probably figured out how to use a barrel jack. I’m afraid I can’t advise on how to adapt the DIN sized hole to a barrel jack though, that’s a tough one. I had planned on custom panels from the beginning.
  17. Starting MB6582 build

    thanks, and thank you for the control surface tutorial, really does make it so much easier and answers so many questions! I was still VERY nervous the JB Weld stage would mess up, was pleasantly surprised when it all seemed to be solidly glued in place! I think my front panel is very slightly bent though, which is going to make getting all the leds through it in one piece quite interesting. Hoping I may be able to screw the screen in and only have to do it once..... 
  18. Starting MB6582 build

    Both are looking great! It is always good to see new MB6582s in the world and that there are still people not hopping on the VST bandwagon! :) Many greets and enjoy your builds! Peter  
  19. 6N137 on MIDI8 and MIDI-IO Boards

    yup, good info! very nice!
  20. Starting MB6582 build

    Pictures looking good now! I'm going to try the colour change LEDs... and cross my fingers it's not totally stupid once it's finished! Glad the knobs look OK.. they cost a few quid ;) I was planning on a standard barrel jack too - but I'm wavering a bit now. It feels like either way needs a bit of a bodge, although I guess the barrel jack at least means you can use any spare wall wart, rather than having to solder a new one. My plan was originally to laser cut an 19mm disc with a 2mm lip and a hole in the centre for a panel mounted jack and glue that into the panel. I in theory at least have access to a laser cutter at my local makerspace... haven't actually cut anything yet though!
  21. Starting MB6582 build

    Pictures working now? No worries about using the thread. As you wrote; since we're both building. I did PSU option E, which seems to be working well so far. All the guides found here has been super useful! I'm planing to use a standard 2.1 jack. The only problem is that my panels have the big 17mm hole for the DIN-jack. Has anybody found a nice solution for this? The disc-solution came to mind for me as well. But I haven't looked in to it further. I like the multi-coloured-legos kind of look to the knobs! Are you going to do those colour changing LEDs as well?  
  22. 6N137 on MIDI8 and MIDI-IO Boards

    thanks for that!
  23. Starting MB6582 build

    also - @HybrisBehemoth - what solution are you going with to power it? I am pretty sure option E "one PSU" is the right choice, but I can't decide if it makes sense to fool around with a 7 pin DIN and cutting the lead off a 12V PSU..... or maybe laser cutting some kind of acrylic disc for the case so it can just be a normal barrel jack plug and can use a normal PSU.......  
  24. Starting MB6582 build

    not for me either actually p.s. sorry for the thread hijacking, but it seemed easier to keep it in one place while we're both building! I actually started with the control surface... which I think is probably the "wrong" way round... but seemed easier.  Just need to get the LEDs in now and will be finished with that board.     
  25. Starting MB6582 build

    Pictures not working for me
  26. Starting MB6582 build

    Working along slowly but surely here. Soon finished with the main board. Passed all the tests without any major setbacks so far. Just managed to get some first sounds out of the SID. :D The 10 uF electrolytic caps I got were way too big and the film caps are a bit bulky (as you can see). Luckily I had some electrolytics lying around.    
  27. It's about 6N137 optocoupler as replacemant for 6N138 on MIDI8 and MIDI-IO Boards. Differences is that the 6N137 is a CMOS level output. More than that the 6N137 will allow you to significantly increase the speed between two MIDIbox. From datasheet maximum speed is 10 MBaud/s instead of 100KBaud/s for the 138. On the MIDI board you just have to remove the 4K7 resistor and replace 1K pull-up for a 10K. Done! Best regards Bruno  
  28. Load more activity