Roland: MC-303 (Used ONLY as a MIDI Sequencer)

- A friend of mine uses his MC303 for sequencing and he frequently comments that it is a piece of crap. Memory problems, timing problems, sync problems, the lot. I've seen it in action running internal sequences and also running external keys (Ensoniq sampler and a Yamaha DX7) and it's bad. Really bad.

Why can't you get good timing out of Cubase? I use Logic and it's rock solid - better than any hardware sequencer I've ever used.

| to pump | top of page |

Nido.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (20-Feb-02 06:55PM )

- I have a friend that owns an mc-303 and its really not very good for midi sequencing. Thats actually one of the major complaints about the machine, that the midi capabilities aren't very good at all.

I own an MC-505 and use it to sequence internal stuff, one sampler and an evenfall minimodular and it works fine. I've owned it for over two years and its never crashed on me once.

However, if you are just looking for sequencing, the 505 is way overpriced and underfeatured in the sequencing area. What makes it great is how it all works together seamlessly, although no individual part is truly outstanding.

I would agree that the mmt8 is a good way to go, orbital and autechre used to use them a lot back in the day. It works very similarly to the mc-505 sequencer only costs less. It has mute buttons for the different tracks and whatnot.

Also, the sequencing capabilities on the rm1x are supposed to be really good, with lots of editing features and stuff. I haven't had the chance to try one although I'd really like to.

Nido

| to pump | top of page |

House de Kris.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (20-Feb-02 09:17PM )

- I have an MC-303 that I used as the main sequencer of my setup for years. I've never 'gotten' what people complain about it with respect to its MIDI timing. I have asked for specifics from others in the past to go beyond "it sucks" but was unsuccessful.

For sequencing basic things like note on/off, it is just fine. You can't record CC# data, but perhaps that is beyond basic. I've used it as a MIDI master clock (most of the time) and as a MIDI slave (sometimes). Never had any problem synching it up.

If you are only using it for note on/off, then memory limitations really aren't too bad. Recording knob movements take up a bunch of memory. But since it doesn't transmit knob movement data, there is no reason to record it for basic sequencer use.

There are ways to maximize your available memory as well. If you edit your sequences a lot, this will eat lots of memory. This is because it never deletes old data, it just keeps adding to it. But, when done editing, if you copy the edited part back onto itself it will then write only the data that is used to make sounds and ditch all of the old data that is using up space. I've been able to free up about a third of my memory by doing that.

I also have an MMT-8. It is a better sequencer in most all respects. But I do like somethings of the 303 better, like the mute buttons. Also, the sub-part mute on the drum track is great on the 303. Can't really duplicate that feature on an MMT-8. All in all, I think an MMT-8 would be better than the MC-303 for straight sequencing.

House de Kris

| to pump | top of page |

reactor303.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (21-Feb-02 01:12AM )

- the timing is fine, i never noticed any problems with it.. if it wasnt for the lack of memory i would call it an ok peice for the price (still nothing i would ever get again though) BUT running out of memory in the middle of something (which happened all the time, and i only used it for note on/off) and having it ruin everything you have done is incredibly frustrating to say the least.

reactor303

| to pump | top of page |

Silver Droid.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (21-Feb-02 08:30PM )

- When I installed Windows XP onto a fresh 7200 RPM hard drive, I had no problems for a while. But as time progressed my TB-303 starting lagging to the clock signal coming out of Cubase, same with the rest of my analogues.

I haven't played around with the setup much recently, and I recently defragged so it could be a defrag issue.

I need to be able to effectively run MIDI sequences in Cubase while synching my analogues....all while recording the main mix into Cool Edit Pro.

This is why I was starting to consider a cheap hardware piece to take the place of Cubase.

Link: http://www.mp3.com/silverdroid

Silver Droid

| to pump | top of page |

House de Kris.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (22-Feb-02 02:19PM )

- Interesting story Silver Droid. It boggles the mind how the two (computer and TB-303) can get out of synch with each other. Cubase should be sending out a constant System Real-Time Message of Timing Clock which should force whatever is connected to it to behave properly. What sort of box do you use to create the DIN Sync clock required by the TB-303? Perhaps something is screwing up there and changing to a hardware sequencer won't help. Then again, perhaps the computer MIDI port skips some MIDI clocks with high density note data.

Have you tried anything super simple yet? Like make a Cubase sequence with just a kick drum at the start of the measure, nothing else. Sync the TB-303 to that and let 'em rip for a few hours and see if they've drifted.

In my experience, computer MIDI ports can have screwy MIDI clocks with higher BPMs. I've got two computers I used for comparison. One is a 486DXII/66MHz w/W95 and the other is a PIII/500MHz w/W2kPro. The 486 runs Cakewalk 3 and the PIII runs Cakewalk 8 (or somesuch). Interestingly, they BOTH start to miss MIDI clocks at around 123BPM and become totally unusable at 160BPM (as far as sending a reliable MIDI clock). In this case, an MC-303 is far superior to a computer.

House de Kris

| to pump | top of page |

nubilee.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (22-Feb-02 05:27PM )

- Get this the more pattents/sequencing you do the more fucked your patterns timing gets. The MC303's sequencer has a mind of it's own, and really limited sequencing capacity, I mean really limited. The midi timing as a whole just sucks, as does the UI. It's ok for a general scratch pad (I keep mine on the night table next to my bed) for waking dream recording sessions (the most creative times for me). Otherwise it doesn't get used.

I'll sell mine, minty with original box, packing, manuals, receipt, warranty etc. for a mere $200

nubilee

| to pump | top of page |

Silver Droid.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (22-Feb-02 06:32PM )

- I'm using a Doepfer MSY-2 synch converter. It synchs my TB-303 and TR-808. There's nothing wrong with my Doepfer because it synchs fine to my TR-909 and my Korg ER-1 (when I used to have it). So it seems like it's really the computer causing the problem.

I run very simple MIDI sequences, I have nothing complicated going on. No CC's, no audio, just MIDI notes.

I need to test the system after being defragged, gonna test it this weekend.

Link: http://www.mp3.com/silverdroid

Silver Droid

| to pump | top of page |

nubilee.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (23-Feb-02 04:32PM )

- Yeah my OS is likely older than yours, I got one of the first 303's available, and have never updated the ROM/UI.

nubilee

| to pump | top of page |

ssscientist.... Re:MC-303 (Used ONLY as a MIDI Sequencer) (24-Feb-02 11:12AM )

- My two cents worth - the MMT8 has squishy buttons, relatively small memory and complete lack of convenient backup.

Why not look for something like a Roland MC500 mkII or a Kawai Q-80 EX on the used market? Both are quality machines, both have disc drives and both offer the track muting capabilities --- mute any track at any time --- that Orbital is so fond of.

If you are new to hardware sequencing, you WILL need to find alternative manuals-- I recently bought an MC500 mk II for $120 in mint shape; when I tried to read the manual I realized WHY it was in such good shape --

ssscientist

| to pump | top of page |

Subscribe to this thread-> RSS
You'll not be able to post until you login