I could not do any session work last night even though I have quite a backlog of work. I am working on final mixes for a live recording event that I did late last year. I am working through another set of final mixes for a project which has been running on now for almost 18 months. I am also in the midst of basics for another project and I still insist on being active on live sound as well as guitar/bass performance.
I love doing all this work. I hate the dentist.
Let me rephrase that. My dentist is a wonderful human being. I just hate the whole process of going to the dentist. I had a filling that went loose and it fractured nearly half a back molar. My own fault really. I had been experiencing some pain and discomfort with that tooth for a while. I just didn’t see the need to go to the dentist right away. So time passed. Funny thing though… I had booked an appointment to check out the pain and before I could get there the filling and most of the tooth gave way.
I spent three hours last night in the dentist’s chair. Thank goodness for nitrous oxide.
Going, going, gone
A pretty busy week ahead in the studio. I am trying to get one project completed. Some projects have a natural start and end. Other projects never really end… they just stop. I think this project falls into that category but it has not stopped yet. Losing momentum in a project is really tough. I have been working on this one project since September of 2002 and things got stalled for a period of about six months. The producer and artist are both tremendous people. I really enjoy working with them. We are doing a few retakes tomorrow night. They are bringing in an upright bassist for the session. I may try a few different techniques
How to record upright bass
Get a mic, get a pre, patch and press record. I must admit that I often take the easy path with electric bass. I usually patch the instrument through a high quality DI, add a bit of compression, and straight to tape. Sometimes I will patch into a 1272 outboard. The results are predictable although much of the magic really comes from the bass player. A good player is clean and consistent and produces much of the sonic textures from the fingers. As a recordist I try to stay out of the way and let the player work the magic. A poor player… well that often requires major surgery. Fortunately we don’t get too many poor players in the studio.
Upright bass is different and much of the hard work around this instrument depends on a variety of factors: bow versus fingers, dry versus ambient, style, presence. There are many different sound areas and I always find it an interesting challenge to discover the sweet spot. There is a bow area, bridge, soundboard and soundhole. Plucked jazz bassists present the greatest challenge.
The traditional approach is to use a large capsule condenser like a U87 or U49 set about 2″ – 4″ from the bridge with another condenser aimed at the sound hole. I have used a number of different mics with varying degrees of success at the sound hole but more often than not I am looking to capture more warmth and lower frequencies with this microphone. I have worked with a few jazz bassists that do have electric pickups on their acoustic bass and I will always take a feed just in case it comes in handy later on. There is often good presence from the electric pickups.
I might use some limited eq and compression on tracking although my preference is to get a good sound from microphone selection and placement first. It is not unusual for me to consider a low end rolloff around 80Hz and maybe cut low mids around 200Hz.
I have a lot of technology in the studio. I am always looking for ways to use technology effectively to solve audio engineering problems. One problem that I used to face was how to remote control Pro Tools. In the past I used to set up in the control room and try to manage guitar, console, transport control, monitors, keyboards and mice with varying degrees of success and frustration. All that changed when I discovered remote desktop.
I use a notebook computer on the wireless LAN that connects to the Pro Tools workstation through remote desktop. The notebook then becomes the Pro Tools workstation. The monitor and keyboard on the notebook controls Pro Tools remotely. This allows me to set up in one of the talent rooms and control my studio remotely via the notebook. Very cool. Except something happened. I tried to connect to my network and I received a “network not accessible” error. Thus began a prolonged and strange battle with technology.
My first step was to search Google to see if anyone else had this experience. Turns out that most of the world has run into it if they network more than one computer. I found a Microsoft article on the issue here. This knowledge base article precisely described the symptoms I was experiencing: I could not browse other computers in the workgroup, I could not access shared folders or files, I received the dreaded error message: “Workgroup Name is not accessible. You may not have permission to use this network resource”.
The cause was due to NetBIOS over TCP/IP not being turned on and the computer browser service not being started. The resolution is to turn on NetBIOS and to ensure the computer browser service is started. So I tried the resolution.
Didn’t work. Nada. Zip. Still got the same error message.
I crawled on the web for several hours last night and avoided some much needed sleep in the process. Dozens of suggested actions to resolve the problem were discovered and all of them failed. I don’t know why the notebook would no longer see my network. It worked fine for almost a year.
And then I found the answer.
Most networks provision an address for each machine on a network. This address, known as an IP address, is often provisioned through a DHCP service. Some networks operate as broadcast networks and some operate as point-to-point. If you happen to connect a notebook computer to a different network, one that uses point-to-point, then the DHCP service might make a small change in your computer’s registery file.
If a parameter is *optionally* set by *some* DHCP server then that parameter will persist in the registry regardless of any other actions you might try. The parameter is “DhcpNodeType”. Not all DHCP servers set this parameter. I obviously had the misfortune of connecting to another network, which I often do when I travel, where the DHCP service changed this parameter. My network’s DHCP server does not change the parameter and that is why the notebook failed to join the workgroup and gave the error message. This is because my network is set up using the default “broadcast” node type and the persisting DhcpNodeType parameter continued to tell the malfunctioning machine to be a “point-to-point” node. The two types do not talk to each other.
The Solution: check the registry for the DhcpNodeType parameter. If the value is 2 then change it to 1 and reboot. Optionally one may choose the value 4 or 8 to have a computer work in both environments.
Value Type: REG_DWORD – Number
Valid Range: 1,2,4,8 (B -node, P-node, M-node, H-node)
Default: 1 or 8 based on the WINS server configuration
Description: This optional parameter specifies the NBT node type. It is written by the DHCP client service, if enabled. This parameter determines what methods NetBT uses to register and resolve names. A B-node system uses broadcasts. A P -node system uses only point- to-point name queries to a name server (WINS). An M -node system broadcasts first, and then queries the name server. An H -node system queries the name server first, and then broadcasts. Resolution through LMHOSTS and/or DNS, if enabled, follows these methods. If this key is not present, the system defaults to B -node if there are no WINS servers configured for the network. The system defaults to H -node if there is at least one WINS server configured.
By the way, there is another optional parameter at the same registry location that one may add which will override any DHCP server value placed in the DhcpNodeType.
Value Type: REG_DWORD – Number
Valid Range: 1 – 8
Description: This parameter specifies the NBT node type. It is an optional parameter that, if present, will override the DhcpNodeType parameter.
I weep for Microsoft. What a sad journey to make to ensure that your computer connects easily to a peer-to-peer network. “Hey”, tech support asks, “Didja happen to check whether you are B-node or P-node?”
This journal is now online. You may find a couple of broken links on these pages as I am still working on the blog. Be patient. I should have it finished real soon. This blog will be a bit different from the session logs off of my studio website. I will be capturing interesting aspects of my journey through life as well as items of interest to the audio engineer particularly those engineers who work in the contemporary christian music field. My studio website pretty much documents my biography to date so if you are interested in learning a little more about my background you can take a look there. I also welcome any email that comes my way and I will try to answer questions and comments from my friends and colleagues.