Jidis

Thanks Kris :) I looked all over for the date of that friggin magazine and couldn't find it. I'm surprised JLC doesn't have any location details to go with those user photos. That one just had "glass console" or something. George

For what it's worth, that Cooper promo shot was on the cover of Mix, maybe last year or so. I think they had the details on it, but I'm not sure if it's available online. They (the faders) could just be an open mixer window in their host for visual ref. If I see the magazine laying around, I'll see if it says. BTW- People on another group were bragging recently about the new Novation controllers. Apparently, they create a link between the DAW app's "open" plug GUIs and the controls, so that if an editor opens onscreen for a plug you've assigned a map to, the controller automatically switches to that particular map/layout or something. On top of that, the Steinberg apps have remote (MIDI) key commands which can be assigned to the "edit" buttons of VST plug slots, so you could effectively select, open, and edit plugs, regardless of where they were in the mixer, complete with an auto-opening onscreen GUI and all the parameter names, etc. on the controller's LCD (at least I think that's what they meant ;)). I also think that having tactile control, in addition to a nice big visual reference onscreen is really nice in a lot of places (namely, many of the new EQ/dynamics plugs with graph windows). I wish they would add functions like that for the generic remotes. I'm pretty sure the Novation things are tied to some software. Right now, the generic remotes seem to only identify a "list" of parameters for each plug slot. There's no real way for a remote to identify a specific plug within the mixer. George

FWIW, I inquired about that chip to Digikey a while back and they listed a "replacement" as being a: CY7C64713-56LFXC (Digikey part# 428-1680-nd, I think) I remember looking at it and it was a totally different package or something, but maybe someone more knowledgeable here would know if it's useful for anything. George

Stryd, This has the same info in it, but it's not the source I remembered: http://www.jaycar.com.au/images_uploaded/potprimr.pdf Looks like B is just linear, and A was once linear too, but A should mean log now. It also mentions the "C" taper, which puzzled me a while back on something. Take Care

Yes, the CS10/2 had 8-channel fader modules which went with it back in the pre-motorized days, so my guess is that the Cooper outputs whatever it normally does for banks 2 thru 4 (not sure what part of the message changes there). George

Nathan, Just found the thread. It is very similar to yours (check the last reply): http://www.midibox.org/forum/index.php?topic=8084.0 George

Nathan, Yeah, it's been "built" for quite a while. I ran into a few problems with it, the last of which I never resolved. I'm pretty sure it was very similar to what you just got, but I'd have to dig up the thread. Seems like maybe Jaicen had a "plus" board working here. Good luck and let me know if you make any progress with it. George

I thought it was "A" should be audio/log, but may possibly refer to linear on some old stuff, but "B" was generally a safe bet for a linear taper. ??? I think there was a discussion a while back on it, where some site links came up with full details. Glad to say I'm fine on 10k linear pot stock here regardless. I've missed more than my share of awesome eBay part deals. ;D George

Funny, I think that's exactly what mine did. ;D George

Glad to see you got that working. :) I'm running a full sized 317 on mine and the smaller (correct) size on the 7805, but my voltages were OK. George PS- I'm in the same boat as you on the software. I'd be interested to see what options it has on that.

Thorsten "timing tested" a few a while back IIRC, and indeed it did get one of the worst ratings. I actually have one myself, which has done OK, but it usually only does controller stuff, so I can't comment on it's timing. I've also seen it disappear a few times (used to do it a lot on the Mac), but there's probably too many sources for that to blame the MIDISport drivers. Always wished there was more DIY MIDI i/o available, especially post 2K/XP. :'( George PS@ThoR- I think dj3nk may have been referring to internal connections(?). Sometimes the built-in circuits will have dual row headers inside where you can connect for stuff like MIDI/SPDIF/ or for front panel ports on your case, even though the port isn't built into the board. You could also maybe use a cheap PCI card, just for the MIDI/game port (assuming you're desktop) and disable the sound device.

That sounds right. :) You can also usually push those contact (crimp) parts out by pushing in a little metal tab on the side with a pin,etc., while you pull on the cable. That way you can rearrange the wires if need be. Also, I've burned down many an unwanted pin on those and the dual row IDCs, using belt sanders or just a sheet of sandpaper on the table. 8) Take Care, George

Slorrin, If you're only doing a couple, you can probably snip something from the front panel (LED/switches) junk inside an old PC case, or from a CDROM audio cable. The single row things are usually the type with the "inserts" that crimp around the wire and snap down into the plastic housing. Not really "re-usable" from the crimp part, but you can leave them as is, and splice the wire together to get a double ended one (tape or heatshrink, so you don't leave the joint exposed obviously). George PS- I'm guessing you're dealing with the standard (.100") pin spacing. That's what most of that stuff usually is.

Oooh. I guess that could be a problem. It barely conforms to most of the standard Windows stuff anyway. ;D When you've successfully dragged across a group, the objects should become highlighted and change color. They should change color again when you right click one to initiate the move. (some of this may depend on your color assignments, but I'm not sure) I guess there may be equivalents under the Mac interface. Someone here might use it like that and know whether it works. Worst case scenario, the overhead to run Eagle seems to be pretty low for the basic functions (I rarely use the autorouter). If you can dig up even a crappy older PC, you can probably dedicate it just to that. I run it all the time on Socket7 machines and laptops running 98SE. Take Care, George

Nathan, Most of that stuff shares the Eagle "group" command funkiness. IIRC, it's basically: - select "group" command - lasso all the stuff you want - click the "move" tool or whatever then the clincher: - *right* click on any of the objects you just grouped They should all now be floating around in move mode together. BTW, you can also usually right-click while objects are in move mode and they'll rotate 90 degrees (convenient for de-criss-crossing your airwires to find a logical layout). Hope that helps, George

Seppoman- Much Thanks! I'll remember that on my next one. :) George

Well, it looks like I'm late enough getting back that you guys have already found everything anyway. :-[ dj3nk- I'm no expert with it myself. I sort of just know how to get to the basic stuff that I need. Most of the stuff I know came from online tutorials and such, rather than Cadsoft's manual. I sent Nathan (napierzaza) a link to an older thread with some of the sites in it. http://www.midibox.org/forum/index.php?topic=7852.0 Nathan, yeah, I knew how to get to the "isolate" part. The thing I can't figure is how to keep Eagle from separating grounded component pins from the ground pour. I think it usually creates pads and connects them with a small "crosshair" looking trace, rather than just having one single hole in the pour, but it's been a while since I've done it. I don't really know enough design theory to make statements on trace width. I know I use the .016 for a lot of stuff where I can, but it's probably best to beef things up where space allows it. You can always "neck down" or whatever they call it, and reduce certain segments with the "change/width" command if you need to get through a tight area. Someone here may be able to give better pointers on trace width from the electrical angle. - Again, really thick stuff has actually given me more trouble on toner transfers than the thin traces, but the thinner ones are obviously more fragile during the etching and soldering stages. Take Care, George

Nathan, Coincidentally just dropped you an Eagle related mail. The Eagle links toward the bottom of Jaicen's thread here may help for anyone else interested http://www.midibox.org/forum/index.php?topic=7852.0 George

pilgrims1, I just replied in the thread below yours about Cubase control. It's the same way for Nuendo (which I use) and I haven't gotten any replies on it in the Nuendo forum or from them, so I'm not sure whether it's being looked into for any of the version 4 stuff. Cubase 4 appears to have the exact same documentation for the Generic Remote, so I'd guess for now, it's the same. :'( I saw you mention buttons and LEDs, so keep that in mind if you go with the generic. Take Care, George

Possibly for another reason as well- I've mentioned it a couple times here already, but there's an issue with the Steinberg Generic Remote, which doesn't provide outgoing MIDI messages for remote controlled items whose status has been changed externally (from your MIDIBox). For instance, if you've got all your Cubase solo switches mapped to MB buttons with indicator lights, and you hit a solo switch on the box, Cubase will solo it, but won't send the message to cut the light on. If you click the onscreen solo button from the computer, the light will come on. It works the same for all bi-directional items in the generic, and depending on how you plan to use the box, it could be no problem or it could totally ruin it's functionality. Good luck with it, George

Jaicen- I checked that for you at the studio tonight on my sampler's MIDI monitor. Nuendo did indeed output a stream of CC data as the fader automation was being read on the selected channel. It would also output a single value in stop mode whenever the selected channel was changed (corresponding to whatever the new channel's fader was at). Everything looks good. George

Not in front of a Nuendo machine right now, but that sounds about right. Hope this link works, but there are PDFs for Cubase3 here: http://www.steinberg.de/386_1.html The GR seems to have been pretty unchanged for a couple versions at least. The docs for it aren't actually in the "Remote Control Devices" manual, but in the main "Operations Manual" in a section called "Remote controlling the mixer". You'll probably get as much info from just playing around with it though. As I mentioned, it's pretty deep. You'll also notice certain transport functions and stuff which show up in more than one place in the editor's pull down menus (it's sort of a mess, but at least it's powerful). George PS- Make sure to export the maps as you make good ones. Building them can take quite a while, and IIRC, there are points where it won't auto save the map with the project or something, so you'll be dumped back to the defaults if you aren't careful.

Hey again. Yes, it will. :) In the GR editor, you have a column where you'd select which channel you want each controller element to map to, and there's an item for "selected" channel which will do that. All the control items you mention should be no problem as they appear to be part of the onboard channel strips. Inserts can work like that too, but you have to be careful to keep the exact same plug in the exact same insert location on your channels, because it seems to only address them as a list of control elements (it doesn't actually know what you're mapped to). So, if channel one has an EQ in slot one and you've set up a knob map for it, and channel two has a reverb in that location, your map will go to random parameters on that one. The Steinberg GR has a lot in it. It's deep enough that it could probably use a better form of GUI/editor than it has (as well as a fix for that bi-directional glitch I mentioned >:(). Can't believe you're going with no lights. ;) Take Care, George

Jaicen, Be aware that Cubase/Nuendo's generic remote has a small quirk in the handling of a two way connection for status lights and such. If you assign channel strip elements (mute/solo/rec) to note messages or whatever you're using to trigger them, the corresponding messages will only go out if the parameter is changed from the DAW. To simplify, if you had a channel strip with a "record" light and button assigned to a MIDI note, pressing the button on your controller would not cause the LED to light, whereas pressing the onscreen button in Cubase would do it. For such a small "incomplete feature", it can really screw things up for people like us. The rest of the GR implementation seems to work well for what you're after. If you assign a common channel strip to the "selected" channel in Cubase, all the correct messages will go out as you change the selected channel onscreen. Sorry if that's bad news for you (it definitely was for me). George PS- Drop them an email if you can. I'm guessing they don't see it as something worth fixing. I read the remote section of the version 4 PDF, and it looks like the same exact documentation.

Roger, Yes there are 90 degree "riser" cards (adapters actually). I've looked at them for a single board computer I've got. You can find them on eBay IIRC, and at some electronics outlets online. I think there were not only different heights available, but also left and right turn ones. They're used for short bodied (1U/2U) rackmount computers a lot, so a rack case dealer may sell them too. I think they should cost only a few bucks if you're lucky. Take Care, George PS- Obviously make sure you've got clearance for your other onboard stuff. :o