sebiiksbcs
-
Posts
256 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by sebiiksbcs
-
-
I'm using just some other PSU with +5/+12/-12 V that for some reason has a DIN connector. When I sleep I have nightmares where I am connecting it to one of the MIDI plugs.
-
-
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.
-
just connect the gm5 on its own, see if thats working and being picked up in the operating system. make sure the gm5 has its optocoupler in, as that will need it. also on the ucapps site is a driver for the gm5 grab that just in case you need it, dont write the gm5 off just yet.
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.
The other approach I considered was building a MB-CV and adding an additional port for a connection from the MB-SID or MB-FM core. You can pass +5V on this connector and use a simple circuit to multiplex the lines going to the AOUT module in the MB-CV. So when +5V is coming in from the MB-SID or MB-FM, the AOUT module is controlled by the MB-SID or MB-FM. When no +5V is coming in (e.g. the MB-SID or MB-FM is off or the cable is disconnected), the AOUT module is controlled by the core in MB-CV. You could also or instead add a switch to select which input goes to the AOUT module.
That idea is really nice!
-
I kill you deadly! (but after tea time)
I kill you filthy
(I bet no one will get that connection)
(I bet a beer to the first person who CAN get that connection)
It can all be googled easily!
-
The main difference between FM and PM is that a DC offset in the modulator produces a pitch shift in the carrier with FM and only a phase shift with PM. This makes a PM synth more stable.
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.
-
For example: I'd love to be able to assign an LFO to alter the finetune frequency of a single operator to create patches that start out with a harmonic relationship between the operators, then gradually drift - leading to a subtlely shifting FM texture.
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.
-
I am having a quite similar problem. I use a breadboarded DINx3, and it sends all kinds of messages only when D7 of the first DIN is triggered.
Interestingly, after exchanging the breadboarded DINx3 with spare DINx4s from SmashTV I had around, the behaviour is the same. The problem doesn't seem to be on the DIN PCBs.
The point is: I used a fairly long wire from the core to the DINxX PCB. It is about 1,5 metres! How about you? So my problem seems to be the Core-DIN connection.
-
Hi and welcome! I am not the biggest expert, but I can answer your basic questions first.
I have spec'd so far
10 x Motor Faders (8 x channels + master)
10 x Level Meters (1 per channel and + master)
Actually I don't understand why you want 10 tracks. The Master track has only one fader (you can't use two of them in some sort of stereo audio way.) Thus, 9 faders and LED meters are recommended. (MB Gurus, correct me if I am wrong.)
96 x buttons
64 x LEDs
8 x Encoders w/LED rings + 1 Shuttle/Jog Wheel
Sounds good!
(for LEDs, Buttons, Encoders, Jog Wheel, LEDring and 8 Faders)
1 x CORE
4 x DOUTx4
4 x DINx4
1 x MF
Sounds good! There is the possibility that you'll need only 3 DOUTx4's here, since you seem not to include a LED digit display (the red numbers on the MCU showing the bar/beat or minute/second stuff).
(for additional Fader, and Level Meters)
1 x CORE
2 x DOUTx4
1 x MF
I am quite sure there is no 9th level meter. You won't need (can't use) the 2 DOUTx4's.
1) Does this sound right? or am I barking up the wrong tree ???
Sounds neat! You seem to have done some 'extreme digesting' of this forum if you say you spend only days here!
2) Assuming that I will need a MIDI IN/Out for the second Core also, is it possible to integrate a 2x2 USB/Midi Interface so I would only need 1 x USB connection to my PC?
I think the two cores will be linked to each other, so you'll need only one MIDI in/out. Apart from that consideration, the USB interface (look for 'GM5') is much more convenient anyway, since you'll use the LC with your computer, and actually not expensive.
3) What PIC Header should I use?
So the first Core (the one with LCD and 8 faders etc. connected) gotta be device ID=0, the other one ID=1 I guess. This is for adressing the two PICs when you upload the application.
I hope that helps you laaa.
MB gurus, please correct anything of the above if there's something unclear! Thanks.
??
-
So what the...? A topic about selling one Ultracore about buying one Ultracore about selling one Ultracore about buying one Ultracoreabout selling one Ultracore about buying one Ultracoreabout selling one Ultracore about buying one Ultracoreabout selling one Ultracore about buying one Ultracore
So do you still have it for sale?
-
my mom said the boards arrived at home ;)
samples?
in MIDIbox FM
Posted
The MBFM is a very programmable synth, this is how aggressive it can sound (record is without effects or filter option) if it's being modulated in a creative way. I might post more sound examples of soft, moody, spherical sounds in the future