sebiiksbcs

thanks tk! "bist a schatz!" i am using v3 indeed, and i'll try it out.

sorry to revive this post, but i can't find info how to get the dedicated button to trigger the sync feature, the way stuartm is using it on his seq...? or is it already implemented in the metronome button? thanks!

Good work! About how much will the panel cost and which material will you order?

Solved! The solution, just to conclude this thread: The problem was a combination of all those little things. The GM5's status LED seems to be broken and possibly caused some weird quasi-short circuit (?) The original pair or midi connectors didn't work for a reason, a newly soldered pair didn't work for a reason, a third newly soldered pair finally worked! My stupid Macbook's USB ports are too weak, both for the GM5 module and for my cheap Swissonic MIDI interface! No wonder I had no MIDI traffic at all. I have to connect a powered hub inbetween -- now both work fine.

Thanks! Just have to check my Core and GM5 --- again and again! :)

Thanks for the reply! I indeed didn't ground the GM5 module via the Core, cause I assumed it's already grounded via USB (since the power supply comes from USB) So probably the GM5 module got damaged that way. But my GM5 seems broken anyway, so... What I am trying now is to get back my regular MIDI connections via the Core's J12 and J13 ports. To make it clear, they are broken now for some mysterious reason, despite a different pic, with different optocouplers and different MIDI wires. Do I have to replace the whole Core now? How come? Could the diode on the Core have been damaged? test (although i tested the diode with a multimeter as well...)

Guys, sorry that I post this quite general 'MIDI does not work' topic, but with the thousands of results you get when searching 'midi problem', 'optocoupler' etc. I couldn't find if this issue happened before or if I overlooked something. History: - tried to USBify MBSEQ V 3.4f using a single GM5 module. - the GM5 module worked fine when connected to PC (before having any connections to the SEQ). - after connecting MIDI in/out to SEQ's Core v3 via J11 ("MIDI IO at TTL level") , the GM5 didn't work. (its status LED shone veeeeeery dark, looked like a typical short circuit) - while GM5 was connected, SEQ had hickups when I pressed play, later showed a message something like 'MIDI timeout' or so. - removed GM5 again, decided to stick to the regular external USB-MIDI interface, re-connected original MIDI in/out connections of the SEQ. - I realized I had an Optocoupler both on the GM5 and on the Core. Symptoms: - SEQ works, but no MIDI in/out at all now. (doesn't send any MIDI out, nor does it receive/react to MIDI in) Different PIC was tested, MIDI wires were replaced, Optocoupler was replaced. - If it's a firmware problem, I seem to have no way to re-upload mios or the application unless I upload via a second Core. Does anybody have a suggestion what could help? Thanks!

Always great to see another Midibox FM between all those SIDs! Your design is really nice, with clear colour markings. It also reminds me of Ableton's Operator...

Is there anybody who did something similar before: I'd like to simplify the EG5 feature into a common ADSR envelope generator, and then I'd like to have two of them. The critical point is probably if the PIC can cope with this performance load. Another (dream) goal is to implement an arpeggiator (probrably that of the MBSID V1) into the MBFM sound engine. Again, performance load? And the critical point for me is to understand the ASM code and the "surgery" I am trying to do.

Bruce Willis

enjoy! ;)

Right, I want the full control, especially EG5 as filter envelope. This cannot be accomplished through routing notes and CCs differently. That idea is really nice!

I kill you deadly! (but after tea time) It can all be googled easily!

I think another point is that with direct FM, operator feedback (to let an operator modulate its own frequency) would not be possible cause it would just cancel itself out or so. With PM this is possible. I read this somewhere in a Csound documentation I think, or the Csound Book.

Korea Tiger huaiting (=fighting)

I hope this is the right place to post my topic. Although I understand the AOUT option of the Midibox FM application, I am not sure about one point: Is it possible to build a standalone MBFM, then a standalone Midibox CV, and a filter box, and make them work together, so to say to let the MBFM use the MBCV to control the external filters? Or has the AOUT module to be directly connected to the MBFM's core in order to allow the direct control features (EG5>AOUT, LFO>AOUT etc.)? So if that kind of full communication between MBFM and MBCV is not possible, would a way to achieve both an MBFM and an MBCV be through: - building a 'to AOUT' output on the MBFM - building a similar 'to AOUT' output on the MBCV, which itself only has a Core, control surface, and LCD - have a standalone AOUT module in a box which either MBFM or MBCV can connect to - then control whatever through MBFM or MBCV > AOUT box Am I grasping the right idea or did I neglect something important?

As expected, it seems the wire has been too long. I cut it down to about 0.3 metres and it works fine. A minor problem was one cold soldering joint on the breadboard DINx3 (resulted in that pin's random DIN events from time to time because of bad grounding), but I think the main issue mentioned earlier was the too long wire.

Inharmonic frequency rations of course would be fantastic, but it is simply not possible with the OPL3 chip. It cannot detune single operators, and it only allows integer (except 0.5 of course) frequency multiplicators (0,5 / 1 / 2 / 3 ...). That's the OPL3 chip's limitation - and its charm.