Jump to content

BEBDigitalAudio

Members
  • Content Count

    120
  • Joined

  • Last visited

  • Days Won

    3

BEBDigitalAudio last won the day on January 13 2016

BEBDigitalAudio had the most liked content!

Community Reputation

3 Neutral

About BEBDigitalAudio

  • Rank
    MIDIbox Addict

Recent Profile Visitors

2,132 profile views
  1. Hello nlate, sorry I did not see your post here, but I answered to your private message... (I just saw the notification from this post when I clicked "Submit" for your answer) Don't hesitate to share my answer if you think it can help Benoit
  2. Hi Benoit

    I just sent you some questions related to the KissBox RTP-MIDI OEM Module. It would be nice if you could answer some of them.

    Thanks in advance and best regards!

    Jo

  3. 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 g
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  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
  11. 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 Win
  12. 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
  13. 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
  14. 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
  15. 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
×
×
  • Create New...