Jack will definitely be added. It just might be another couple of weeks.
My 6N138's finally came in, now I just have to wait for the resistors I ordered to finally show up.

I hate living here, there's nowhere in town I can buy this stuff from and shipping always takes forever.

After some requests from some people at the MiSTer project, I'm announcing full support with that project is coming soon as well. Probably going to piggyback off of BBond007's MIDI work and tunnel everything through 3.3v tty. I haven't worked out the audio mixing yet, but it should be fairly simple once Jack integration is finished. (ALSA can already do this with certain interfaces)
More details to come soon, but I still more research on what needs to be changed before I can announce any official plans.

t9999clint wrote:

The only pins on a wavetable header are for audio, power and midi data out. I'm not sure what your asking is possible.

It has also already been done using the Serial port.

appiah4 wrote:

t9999clint wrote:

"Maybe we can use the Waveblaster header to give vintage PCs WiFi capabilities...?"
The only pins on a wavetable header are for audio, power and midi data out. I'm not sure what your asking is possible.

It has also already been done using the Serial port.

I found a different schematic of the wavetable header, it actually DOES have a midi in port. So in theory you could cram extra data through that, it'd just be a really bad Idea.

Yeah using a serial port or Ethernet card and attaching that to the Pi would work better for this than trying to cram it all through the soundcard.
That being said, there's no reason why the wavepi can't do both. If it's a Rasp Pi 3 or better it should have more than enough grunt.
The project is open source, so if someone wants to pre-configure a WIFI-TTY software setup on this they can go ahead, but it's pretty low priority for me at the moment. I'd rather spend time trying to get SC-55 emulation working using Mame first.

I finished the testing for the instructions and documentation. Looks like it'll reliably build the software I need on a clean raspbian lite install.
Made sure that the first post also mentions that installation instructions are available.

got some resistors from a friend. I finished wiring up everything according to the diagram I made on the first page of this thread, however it doesn't appear to be receiving valid MIDI data.
I'm a totally newb when it comes to this stuff, can someone familiar with this stuff take a look over my diagram and see If I missed something?

EDIT: I managed to find the error. The one of the ground connections on the 6n138 needed to be connected to the midi -data line (Midi pin 5). I need to figure out which pin this corresponds to on the wavetable header. I guess it's time to pull my 486 out of storage... (my AWE64 Gold doesn't have a wavetable header)
This also means that TTYMidi is working now. ( I still need to add a config option for it though)

My rough breadboard prototype is testing and working (and ready for some Tenticle Grape 😈 ). Github was updated to include the tty scripts. This should also in theory work with the softmpu program when configured for serial out.
I'll be sure to update the wiring schematics to include the fixes I've made to the design when I get back from LTX (next week)

Looks like I BARELY met my deadline for getting this working by then. I honestly didn't think I'd be able to get it all done in time. 😊 😊 😊
I'll be at Dreamhack with a big computer with DOOM spraypainted on the side, in the row next to the stage. If your going to LTX as well be sure to say hi!

Congratulations. Will there be an opensource diy board schematic, bom and code for this project? I would love to try it.

t9999clint wrote:

That being said, there's no reason why the wavepi can't do both. If it's a Rasp Pi 3 or better it should have more than enough grunt.
The project is open source, so if someone wants to pre-configure a WIFI-TTY software setup on this they can go ahead, but it's pretty low priority for me at the moment. I'd rather spend time trying to get SC-55 emulation working using Mame first.

Could call it the "Radio Wave Blaster" 😜

appiah4 wrote:

Congratulations. Will there be an opensource diy board schematic, bom and code for this project? I would love to try it.

It's all already on the GitHub.
I mean it's not done, but the PCB, the code, and BOM are all there.

The PCB hasn't been tested at all yet, and I know there's at least one wiring error. The code however has been tested a few times on a rasp pi 3b+ and seems to work fine on there.

Next update I'll be doing next week is TTYMIDI support (all that's left is more testing) then after that I'll start on a premade Rasbian image.

Came back from Vancouver (LTX 2019) to find that Shaw cut off my internet. So I was without internet for about a week.
Anyways I'm back now and am back working on the WavePi project.
I'm working on a P2P CDN solution for my website so I can share a few raspbian pi images. So that should be up soon.
This raspbian image is probably the only way I can reliably add Jack support, as I can't think of a clean way to add that to a script. The same goes for a WebUI

Also several other soundfont makers are probably also gonna be using this service as well. (STGiga, Strix, etc...)
I'll be sure to add a script or something to download some configs that will auto install their soundfonts to the wave pi.

Hey,

I just came across your project and I really like it. I wanted to build something like this as well. I thought about using the WaveBlaster header but as I want to primarily use Munt I was not sure if it is possible. I looked into the datasheet of my Soundcard (ESS1868F) and if I read correctly the MIDI interface on the WaveBlaster header does not support MPU-401. That's why I used the GamePort instead. But I'm not 100% sure. Did you try the WaveBlaster header yet?

I use the GamePort and connected it via a voltage divider to the Raspberry UART RX pin and I use ttymidi to connect it to Munt. I had the problem that ttymidi does not support SysEx messages. But they are crucial for Munt as otherwise it will not sound right. I modified ttymidi so it will now recognize SysEx messages. I suggest you use this version instead: https://github.com/ElBartoME/ttymidi/

I connect a 16x2 LCD via I2C to the Pi. I wrote a Python script to sniff the MIDI data and show stuff on the LCD just like the MT-32. Now I came across your scripts and I would like to use it instead. Do you plan to implement LCD support? I would probably extend the code myself if that's okay for you.

The WB header is connected to the MPU-401 interface.

This is a really cool project, thank you!

Yes I plan on implementing LCD support. I don't have the hardware right now to test that with so it'll be a while before I do it. Everything is on GitHub, feel free to add the code on there, or just post it here on the forum if that's easier. (I also have a discord)
I have integrated ttymidi into my project already, just not into the stable build yet.
I have tested it with the wave table header and it does work. It's connected to the same lines as mpu401 just as gdjacobs has mentioned.

Cool, I have to try the header. I would like a completely internal solution.

I had a look at your code and have a suggestion regarding your problem with aconnect and the midi numbers. You can use the name of the midi device instead of the number. So instead of "aconnect 129:0 14:0" you can use "aconnect 'ttymidi':0 'Midi Through':0". That should make it easier in case the numbers are not always the same.

I forked your repository and want to start working on implementing some LCD code for now.

ElBartoME wrote:

I had a look at your code and have a suggestion regarding your problem with aconnect and the midi numbers. You can use the name of the midi device instead of the number. So instead of "aconnect 129:0 14:0" you can use "aconnect 'ttymidi':0 'Midi Through':0". That should make it easier in case the numbers are not always the same.

I forked your repository and want to start working on implementing some LCD code for now.

Neat, I didn't know that. That'll make thing's much simpler. I am looking forward to your progress. 😀

Small steps. 😀

https://www.youtube.com/watch?v=ye8hCD7b2yk

nice work! I tried making it easy to parse the code and the status for others that wanted to contribute code.
what lcd are you using? Is it using i2c?

You did a great job. It is not that hard to read your code. I expanded your midi-listerner.py with a lot of code. Also some other things. You can see that in my repo.

I use a standard I2C 16x2 LCD. It uses the 'PCF8574' chip for I2C. The display shows the current config on the top and the midi channels on the bottom. It also displays SysEx messages for the LCD of the MT-32. But I'm far from done. Code needs to be optimized and I want more features. If you or anybody has some ideas on what to implement feel free to comment. 😀