BEBDigitalAudio

Members
  • Content count

    119
  • Joined

  • Last visited

Community Reputation

3 Neutral

About BEBDigitalAudio

  • Rank
    MIDIbox Addict

Recent Profile Visitors

359 profile views
  1. The NG and the DSP...

    And after a long silence (being VERY busy with other stuff....), here are some news of the project to turn the ASX/X-Synth into an open DSP platform for music. But first of all, I have to report some of the bad news about ASX/Plugiator : Use Audio is now completely dead and silent. The website is closed. It is now handled by a company who wants to sell the domain name to the highest bidder (I hate those companies who want to make money with "well known" domain names). Since Use Audio was the only source for Prodyssey, Pro12, FMagia and Drums&Bass plugins, the ASX is little by little getting the status of abandon-ware. Moreover, we tried to get in touch with inDSP in India, and the answer we got was "all developments of the ASX/Plugiator is completely stopped" In other terms, the only available board is now the X-Synth from iCON, for which it's very hard to get a clear status. It's still existing on iCON website as an active product, and they sell it with 300USD off (see here https://www.icondigitalusa.com/shop/xsynth), but it seems out of stock. And at the same time, it can still be found on various places on the web, but with crazy prices (I saw some over 400 USD !!) Software support from iCON is simply non-existing, since the software they provide is not even branded "iCON" but "Use Audio" (the name appears on all plugins in the Manager). That means that iCON does not even probably know that there are other plugins (and does not probably even want to deal with the licensing issues with inDSP)   Now, the "good" news : after countless hours of experimentation on my ASX boards, I think I have finally found a way to inhibit the local microcontroller and be able to download DSP firmware directly from an external board through the SPI link. The process involves to solder two connectors on X-Synth boards (SV1 and SV3) and place a jumper on SV1. It's also needed to solder a wire directly on U204 (pin 11) to get access to the SPI CS line to the DSP. Soldering this wire is quite difficult by the way, and requires serious soldering skills. Apparently, inDSP has implemented a special mode in the ATMega32, probably for DSP debugging on something like that. This mode is activated by shorting pin 1 and pin 2 of SV1. But take an extreme care if you start experimenting with that : shorting the wrong pin on SV1 will activate the ICSP mode (In Circuit SPI Programming) mode of the ATMega. That means that you can format the microcontroller Flash memory through the ISP connector!! And there is NO WAY to recover the ATMega32 program in that case (in other terms, your synth board will be DEAD!!) I will post more details on the forum as soon as possible, but I think I am on a good way now. Once again, if you decide to experiment with the DSP SPI link, note that you need to know exactly what you do and you take the risk of erasing the microcontroller memory in case of any failure. In other terms : don't tell me I did not warn you about risks
  2. The NG and the DSP...

    Hi Joel, apparently, the alert system with the private message is failing (it failed for me)... but I think that you will get an alert with this message in the forum. Please check your private messages Benoit
  3. The NG and the DSP...

    I think I still have one somewhere, that I don't use. Let me check, if I find it, I will send it to you Benoit
  4. The NG and the DSP...

    Hi Jelise, as somebody was saying still recently in USA : yes, you can It's just a question of making an adapter between the two connectors. Look at picture from Pasbel, it tells how to do it. I am not at home right now, but if you need a more detailed schematics, I can send it to you (since there is a risk that I completely forget this meanwhile, don't hesitate to send me a message as a reminder) Benoit
  5. MIDIbox goes RTP-MIDI...

    Hi Zam, sorry, I completely forgot to answer to this post. You don't need 4 SPI to do that, nor you would need 4 endpoints. It would be possible to do that using the CableID to identify the session partner. Don't forget that a single endpoint in the KissBox can support multiple sessions in parallel. I would need to update the software to report the session partner using the CableID, but this is feasible (I already talked about this option with Thorsten a long time ago, but we never went further) Sharing the same endpoint between various session is the key to save a lot of memory (something that Hugo106 did not seem to understand when he said that there was not enough memory in the OEM CPU )
  6. Weird issue with MIOS Studio under Windows 10

    Hi Youpli, thank you for your proposal, but the issue has been solved (see the last message I sent). I solved this by recompiling the application from a fresh copy of the repository. I suppose the USB enumerator code was corrupted in my repository copy, and this was giving this strange issue Benoit
  7. The NG and the DSP...

    Hi Jelise, the ASX (and iCon) are very different from NeoSynth. The NeoSynth is based on DREAM chipset (DREAM is a subdivision from Atmel based in France) and is mainly a sample player (sample player followed by DCF/DAC chain). The ASX and iCon are based on SHARC DSP, and they run "virtual analog" synthesizers (not based on samples) The sound you get from each of them is then very different, since they use completely different synthesis algorithms. In my humble opinion, they complement nicely each other. Now, about the fact you can't find ASX anymore, the iCon X-Synth is exactly the same board except from the connectors used to interface with the keyboard. In other terms, you need just a an adapter (just connectors and wires, no electronic components). I can give you details about the wiring you need to make. So, if you find a X-Synth rather than ASX, do not hesitate, they do the same thing. Benoit
  8. Weird issue with MIOS Studio under Windows 10

    I finally solved the issue I just updated my SVN snapshot completely. Don't ask me which file was different, but once I got a fresh view, I just recompiled the application and it worked. And finally, there is no bug on my side, it's just something related to MIOS32 source code, like a file which was not updated on my computer to the last version (probably in the USB enumerator). Now, the application works like a charm both on XP, Win7, Win10 and Mac without changing even one line of code on my side And thank you a lot for your time and investigations, Latigid. At least, we know now what to do when we see such a behavior on Win10...
  9. Weird issue with MIOS Studio under Windows 10

    I tried the app_skeleton on Win7 : it works, the USB MIDI interface is recognized. So there is an issue in my code that blocks the Win7, I will look to that But there is also clearly a Win10 issue. If I go to configuration panel when app_skeleton is running, here is what Win10 tells me   (Ok, it's in French sorry) The MBHP does not appear as a MIDI interface but as a composite device (so, there is an enumeration issue. The MBHP is composite : MIDI + Audio, both should appear here) And the status reported below is "driver error" (while everything works fine on Win7...)  
  10. Weird issue with MIOS Studio under Windows 10

    Hi Andy, thank you for doing the test I get the same behavior under Windows 7 : the board is not recognized at all (see below) I just tried to compile the app_skeleton (the simplest possible MIOS application) : same result. Really weird... Benoit
  11. Weird issue with MIOS Studio under Windows 10

    And small update : I made a test under Mac OS (10.9) and it works too. MIOS Studio finds a "USB MIDI Peripheral" (generic name). When I check in Audio/MIDI Configuration, it is also displayed corectly (as coming from midibox.org). So the more I look in that, the more I think it's a Win10 related issue, not a MIOS32 problem itself. I will make a test today at work with a Win7 machine, just to be sure Benoit
  12. Weird issue with MIOS Studio under Windows 10

    Hi Latigid, thank you for your help forgot to say : this is a MB997C board (previous version of Discovery, not the new one). I tried to install the GM5 driver, but it fails (it says "Contact manufacturer : error 0x0006") I did not try to update the ST LINK for now, I will try later today (normally, it's not related to that, since it's not the new DISCOVERY board) I send you here the HEX file I used for the test. The application is empty, it's just the basic core (so I am sure it's not a bug crashing the board) Benoit     HorusDSPController.hex
  13. Hi all, I am facing a very, very strange problem with MIOS Studio under Windows 10. I have created an application using Eclipse with MIOS32 on my Win10 machine, but when this application is loaded in the STM32F407 via MIOS Studio, I loose the USB connection between MIOS Studio and the MBHP. I thought first it was my application, but when I upload it with MIOS Studio on a XP machine, the USB connection works Here are the steps I follow : - installation of MIOS Bootloader V1.0.18 on the MBHP using ST LINK - I start MIOS Studio 2.4.6 : the USB MIDI port appears and MIOS Studio displays the bootloader message - I select the HEX file compiled from Eclipse and upload it into the board : application is uploaded correcly. MIOS Studio looses the USB connection when the STM32 restarts (normal behavior up to now) - if I scan now the MIDI devices on the computer : no more MIOS32! I can try anything from disconnecting USB, power supply, etc... It never appears again I then reloaded the bootloader using ST LINK : USB connection to MIOS Studio works again. At this level, I thought it was an error on my side, blocking USB. I connect now the MBHP to a WinXP machine and I take the HEX file compiled on the Win10 machine. The bootloader appears as expected and I am able to upload the HEX file into the MBHP. But now, when the MBHP restarts (with the application compiled on Win10 machine), it works perfectly with MIOS Studio under XP! If I connect it to the Win10 machine again : fail! So the problem is clearly not in my code, nor in the toolchain being run under Win10. Did somebody already saw that?   Benoit
  14. Hey Latigid By the way, I just forgot to tell you : you can create as many "presets" as you want, with different toolchain configuration, just by creating as many workspaces as you want. For example, on this computer, I have one MIOS32 configuration for the "pure" MIDIBox projects (the projects presented on the website), and I have another one, located in a different directory, with its own SVN image for my HorusDSP projects (since there is a MIDIBox version of it). Each workspace has its own build environment configuration, defined in the Preferences. When you switch from one workspace to another, Eclipse takes care to point to correct source code folder and toolchain folders. If you need more help with this setup, just tell me, I can explain more in details
  15. make an line in