httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
[FAILED]
I committed the line and the same thing happened on the next line.
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
On Fri, 2006-11-24 at 16:37 -0500, linuxmaillists@charter.net wrote:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
[FAILED]
I committed the line and the same thing happened on the next line.
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
FC6 has no mod_access.so nor does that appear in the httpd.conf file. The correct version of httpd on FC6 is something like htppd-2.2.3-5
When you run: rpm -qa |grep httpd what is returned? -- ======================================================================= It's all in the mind, ya know. ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Friday 24 November 2006 18:45, Aaron Konstam wrote:
On Fri, 2006-11-24 at 16:37 -0500,
linuxmaillists@charter.net wrote:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
[FAILED]
I committed the line and the same thing happened on the next line.
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
FC6 has no mod_access.so nor does that appear in the httpd.conf file. The correct version of httpd on FC6 is something like htppd-2.2.3-5
When you run: rpm -qa |grep httpd what is returned?
system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5 httpd-2.2.3-5
On Friday 24 November 2006 23:16, linuxmaillists@charter.net wrote:
On Friday 24 November 2006 18:45, Aaron Konstam wrote:
On Fri, 2006-11-24 at 16:37 -0500,
linuxmaillists@charter.net wrote:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
[FAILED]
I committed the line and the same thing happened on the next line.
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
FC6 has no mod_access.so nor does that appear in the httpd.conf file. The correct version of httpd on FC6 is something like htppd-2.2.3-5
When you run: rpm -qa |grep httpd what is returned?
system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5 httpd-2.2.3-5
Many Thanks for the trigger message that I should check it as it doesn't start here either. Its not a majorly used item here however.
I have all that above: [root@coyote sa]# rpm -qa |grep httpd system-config-httpd-1.3.3-1.1.1 httpd-2.2.3-5 httpd-manual-2.2.3-5
But httpd is still a non-starter. Next suggestion?
TIA
On Friday 24 November 2006 16:37, linuxmaillists@charter.net wrote:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
[FAILED]
I committed the line and the same thing happened on the next line.
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
This was a fresh install complete with reformat of the hdd and not an upgrade. I had to commit out about 17 or 18 lines between 4 files before the httpd would start. How is it that these conf files would be wrong coming from the iso image burned to the CDs?
On Fri, 2006-11-24 at 23:16 -0500, linuxmaillists@charter.net wrote:
Someone said that mod_access.so does not exist from FC5 on so why is this in the conf file if that is correct?
I don't know what else to check to get httpd to start.
Any help will be appreciated, Jack
FC6 has no mod_access.so nor does that appear in the httpd.conf file. The correct version of httpd on FC6 is something like htppd-2.2.3-5
When you run: rpm -qa |grep httpd what is returned?
system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5 httpd-2.2.3-5
Then things are really confused since I have the same version and mod_access.so does not appear in my httpd.conf file. -- ======================================================================= I used to think that the brain was the most wonderful organ in my body. Then I realized who was telling me this. -- Emo Phillips ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
linuxmaillists@charter.net:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
Not here. Works fine, as installed. Though I've run the yum updater since the initial installation, and never modified this installations httpd.conf file. My line 170 is not mod_access.so.
Have you run "yum update", or updated in another way, since installation?
On Saturday 16 December 2006, Tim wrote:
linuxmaillists@charter.net:
httpd fails at boot with no message as to why it failed.
I run
]# service httpd start
and get
Starting httpd: httpd: Syntax error on line 170 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory
Not here. Works fine, as installed. Though I've run the yum updater since the initial installation, and never modified this installations httpd.conf file. My line 170 is not mod_access.so.
Have you run "yum update", or updated in another way, since installation?
I hate to wake up this old thread again, but I also have this problem and a search of my list archive doesn't seem to indicate a solution being offered.
This was an install on a fresh disk when I installed FC6 in November 2006. httpd has never been able to start, but with vz blocking port 80, I didn't see it as being something to worry about. Last night vz assured me they are not blocking any ports, so I thought I'd set up a server so I could call them a liar.
I've used smart to remove httpd and the mod_friends, including the service-config-http utility, and then re-install them. After the re-install I had to run the system-config-http utility else it couldn't bind to address 0.0.0.0:80, and after I had allowed system-config-http to overwrite the conf file, then I got the above error. Looking at /etc/httpd/conf/httpd.conf with vim, I found a bunch of blank line trash at the start of the file, that when removed, reset the error address above to line 156, but it is still the same error.
This is what was re-installed by smart: [root@coyote conf]# rpm -qa |grep http httpd-2.2.3-5 jakarta-commons-httpclient-3.0-7jpp.1 system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5
No idea where that jakarta stuff came from, but the grep caught it.
What has been the resolution to this problem for FC5-6?
On Wed, 2007-02-21 at 13:03 -0500, Gene Heskett wrote:
I hate to wake up this old thread again, but I also have this problem and a search of my list archive doesn't seem to indicate a solution being offered.
This was an install on a fresh disk when I installed FC6 in November 2006. httpd has never been able to start
With fresh installs, plus their own updates, on both FC5 and FC6, Apache works for me. But I don't use the GUI tool for configuring Apache, I've never thought much of it, and I seem to recall someone mentioning it as the culprit for some of the recent "Apache won't start" problems.
Others have had problems when they've updated between Fedora releases, or have copied their Apache configuration files across, a few things changed in Apache between releases.
I've used smart to remove httpd and the mod_friends, including the service-config-http utility, and then re-install them.
Though, any custom configuration files would probably have been left on your system, and re-used with subsequent installations. Did you check for that?
You could move the current configuration files out of the way, and extract pristine ones from the RPM.
After the re-install I had to run the system-config-http utility else it couldn't bind to address 0.0.0.0:80,
My original httpd.conf file has just the following in the "Listen" section. It worked out of the box.
# # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78:80 Listen 80
This is what was re-installed by smart: [root@coyote conf]# rpm -qa |grep http httpd-2.2.3-5 jakarta-commons-httpclient-3.0-7jpp.1 system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5
No idea where that jakarta stuff came from, but the grep caught it.
It's not something that I have installed. You could try yum removing it, and seeing what else tags along for the ride.
On Wednesday 21 February 2007, Tim wrote:
On Wed, 2007-02-21 at 13:03 -0500, Gene Heskett wrote:
I hate to wake up this old thread again, but I also have this problem and a search of my list archive doesn't seem to indicate a solution being offered.
This was an install on a fresh disk when I installed FC6 in November 2006. httpd has never been able to start
With fresh installs, plus their own updates, on both FC5 and FC6, Apache works for me. But I don't use the GUI tool for configuring Apache, I've never thought much of it, and I seem to recall someone mentioning it as the culprit for some of the recent "Apache won't start" problems.
Others have had problems when they've updated between Fedora releases, or have copied their Apache configuration files across, a few things changed in Apache between releases.
I've used smart to remove httpd and the mod_friends, including the service-config-http utility, and then re-install them.
Though, any custom configuration files would probably have been left on your system, and re-used with subsequent installations. Did you check for that?
You could move the current configuration files out of the way, and extract pristine ones from the RPM.
After the re-install I had to run the system-config-http utility else it couldn't bind to address 0.0.0.0:80,
My original httpd.conf file has just the following in the "Listen" section. It worked out of the box.
# # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78:80 Listen 80
I did find the problem I believe.
1. For some reason the system-config-httpd archive also contains an httpd.conf, but its for httpd-2.0, not the 2.2.3-5 being shipped. WTF *were* they thinking?
I had removed httpd and all its friends several times but I was always putting it back in at the same time as its friends. Talking to a webmaster & IT savvy person at the tv station an hour ago, I got the hunch that I should try installing httpd all by itself, so I did. Then I set up a port forward in my dd-wrt router to a port verizon *isn't* blocking (and yes, they silently block port 80), set that port into the httpd.conf at line 134 and started it. My test page pops up instantly 10 miles away if they use the address:port syntax. Now all I have to do is actually setup the page. In fact IIRC, I have my old amiga pages around here someplace yet, which would be a bit more complex than the test page apache throws up. But I haven't written any html in quite a few years, so it'll be slow.
This is what was re-installed by smart: [root@coyote conf]# rpm -qa |grep http httpd-2.2.3-5 jakarta-commons-httpclient-3.0-7jpp.1 system-config-httpd-1.3.3-1.1.1 httpd-manual-2.2.3-5
No idea where that jakarta stuff came from, but the grep caught it.
It's not something that I have installed. You could try yum removing it, and seeing what else tags along for the ride.
Using smart now, I had to leave a couple pieces of it else it would have removed azureas too, but its clearing 222 megs of stuff now. I just found a couple pieces of livna that could go so they did.
Thanks for the hand holding Tim, I appreciate it.
On Wed, 2007-02-21 at 22:17 -0500, Gene Heskett wrote:
I did find the problem I believe.
- For some reason the system-config-httpd archive also contains an
httpd.conf, but its for httpd-2.0, not the 2.2.3-5 being shipped. WTF *were* they thinking?
I seem to recall someone mentioning the default file having problems, but I didn't experience that, myself. Perhaps because I never tried to use Apache until after I'd done a yum update.
I set up a port forward in my dd-wrt router to a port verizon *isn't* blocking (and yes, they silently block port 80), set that port into the httpd.conf at line 134 and started it. My test page pops up instantly 10 miles away if they use the address:port syntax. Now all I have to do is actually setup the page. In fact IIRC, I have my old amiga pages around here someplace yet, which would be a bit more complex than the test page apache throws up. But I haven't written any html in quite a few years, so it'll be slow.
I was pleased to find out that Fedora has the Amiga Fast File System pre-compiled in, the other day. I had to grab a file that I hadn't seen for 13 years, and could do so without much in the way of drama. Unlike the last time I tried that, I spent ages trying to compile a module. It borked a bit at listing a directory, but tab-completion worked within, so I could find the file I wanted. Go figure...
I dislike arbitrary port blocking. Sure, I can see some value in blocking SMB traffic, by default. That's rarely ever meant to go outside of a LAN. But if I've managed to install myself a webserver, I ought to be able to reach it from the outside world without a headache.
Thanks for the hand holding Tim, I appreciate it.
You're welcome. I'll bet you'll appreciate what I was doing yesterday, we seem to work in similar circles: I got called around to a place to get a couple of Sony BVH-2000 PS 1" C format VTRs working. They only had one time base corrector, which had a dud memory board, but actually manages to work fine without it (they didn't know about that). He had a good laugh when I pulled the board out, and there was "U/S" written on it in texta in huge writing (meaning unservicable, for anyone reading this who's not heard that abbreviation before). There was this strange ticking noise while one of them was running, and I was trying to work out if there was a relay clicking in and out because some servo was unhappy. Nope, they hadn't locked the supply reel on the hub, so the little keys of metal that pop out to help hold the spool on were floating around ('twas vertically mounted, not diagonally, just to tempt fate even further).
For my efforts I got some cash, a meal, and went home with a bit of history: A Tektronics type RM 529 waveform monitor, mod 158E. A scrubbing brush and soap later, it doesn't look like the plumber kept it in his truck for ten years. It needs a bit of work to sort out a dodgy mode switch or two, and I've got to work out what voltage bulbs are used to light the graticule (the darn things are labelled with a part number, not a voltage, and my multimeter probe's point just broke off, so I can't measure it without delicately poking wires in). It's mostly valve based, with a few transistors, and looks at least thirty years old. I presume it's out of a 2" quad, it looks it. Although it's 19" rack mount, it has a couple of quarter-turn latches, not the usual screw holes. Just the thing to go along with a couple of Philips LDH1s I've got here.
On Thursday 22 February 2007, Tim wrote:
On Wed, 2007-02-21 at 22:17 -0500, Gene Heskett wrote:
I did find the problem I believe.
- For some reason the system-config-httpd archive also contains an
httpd.conf, but its for httpd-2.0, not the 2.2.3-5 being shipped. WTF *were* they thinking?
I seem to recall someone mentioning the default file having problems, but I didn't experience that, myself. Perhaps because I never tried to use Apache until after I'd done a yum update.
I set up a port forward in my dd-wrt router to a port verizon *isn't* blocking (and yes, they silently block port 80), set that port into the httpd.conf at line 134 and started it. My test page pops up instantly 10 miles away if they use the address:port syntax. Now all I have to do is actually setup the page. In fact IIRC, I have my old amiga pages around here someplace yet, which would be a bit more complex than the test page apache throws up. But I haven't written any html in quite a few years, so it'll be slow.
I was pleased to find out that Fedora has the Amiga Fast File System pre-compiled in, the other day. I had to grab a file that I hadn't seen for 13 years, and could do so without much in the way of drama. Unlike the last time I tried that, I spent ages trying to compile a module. It borked a bit at listing a directory, but tab-completion worked within, so I could find the file I wanted. Go figure...
I dislike arbitrary port blocking. Sure, I can see some value in blocking SMB traffic, by default. That's rarely ever meant to go outside of a LAN. But if I've managed to install myself a webserver, I ought to be able to reach it from the outside world without a headache.
Thanks for the hand holding Tim, I appreciate it.
You're welcome. I'll bet you'll appreciate what I was doing yesterday, we seem to work in similar circles: I got called around to a place to get a couple of Sony BVH-2000 PS 1" C format VTRs working.
Wow, those are almost as much a dinosaur as a 2" quadruplex.
They only had one time base corrector, which had a dud memory board, but actually manages to work fine without it (they didn't know about that). He had a good laugh when I pulled the board out, and there was "U/S" written on it in texta in huge writing (meaning unservicable, for anyone reading this who's not heard that abbreviation before).
Yup, and if Sony has one of those boards, bring in 2 or 3 little red wagonloads of small bills neatly bundled please.
There was this strange ticking noise while one of them was running, and I was trying to work out if there was a relay clicking in and out because some servo was unhappy. Nope, they hadn't locked the supply reel on the hub, so the little keys of metal that pop out to help hold the spool on were floating around ('twas vertically mounted, not diagonally, just to tempt fate even further).
Chuckle, I've seen the hubs eat out so bad they wouldn't drive the reels anymore, spin like crazy on the startup. Then the motor gets throttled and it catches up.
For my efforts I got some cash, a meal, and went home with a bit of history: A Tektronics type RM 529 waveform monitor, mod 158E. A scrubbing brush and soap later, it doesn't look like the plumber kept it in his truck for ten years. It needs a bit of work to sort out a dodgy mode switch or two, and I've got to work out what voltage bulbs are used to light the graticule (the darn things are labelled with a part number, not a voltage, and my multimeter probe's point just broke off, so I can't measure it without delicately poking wires in). It's mostly valve based, with a few transistors, and looks at least thirty years old. I presume it's out of a 2" quad, it looks it. Although it's 19" rack mount, it has a couple of quarter-turn latches, not the usual screw holes. Just the thing to go along with a couple of Philips LDH1s I've got here.
If that thing isn't too badly fried, I sure could use it here. I have docs & all that as we have one of those still sorta working. But if the hi voltage coil is gone, tek hasn't had any of those in 20 years.
Give me an off list address & maybe we can dicker a little.
On Thu, 2007-02-22 at 01:33 -0500, Gene Heskett wrote:
If that thing isn't too badly fried, I sure could use it here. I have docs & all that as we have one of those still sorta working.
Get your own toys... ;-)
Give me an off list address & maybe we can dicker a little.
Done, have a look for a mail about "ye olde video gear..." from an e-mail address with the word "television" as part of the address.
On Thu February 22 2007, Gene Heskett wrote:
Chuckle, I've seen the hubs eat out so bad they wouldn't drive the reels anymore, spin like crazy on the startup. Then the motor gets throttled and it catches up.
I could use one of you guys for a day! I've got an archive of old 1" tapes I've been wanting to transfer to a modern format. I've got a Sony BVH*** (don't have it handy) deck that fires up, but won't lock up and only puts out B&W. We've got the TBC, but I'm not sure how to get it all working...
For my efforts I got some cash, a meal, and went home with a bit of history: A Tektronics type RM 529 waveform monitor, mod 158E. A scrubbing brush and soap later, it doesn't look like the plumber kept it in his truck for ten years. It needs a bit of work to sort out a dodgy mode switch or two, and I've got to work out what voltage bulbs are used to light the graticule (the darn things are labelled with a part number, not a voltage, and my multimeter probe's point just broke off, so I can't measure it without delicately poking wires in). It's mostly valve based, with a few transistors, and looks at least thirty years old. I presume it's out of a 2" quad, it looks it. Although it's 19" rack mount, it has a couple of quarter-turn latches, not the usual screw holes. Just the thing to go along with a couple of Philips LDH1s I've got here.
If that thing isn't too badly fried, I sure could use it here. I have docs & all that as we have one of those still sorta working. But if the hi voltage coil is gone, tek hasn't had any of those in 20 years.
Give me an off list address & maybe we can dicker a little.
RM 529 - got one in my rack. It's got a fading tube or something, and sometimes displays the signal all squished on the "A" side, but the "B" channel still works. I've got to pull it and send it in one of these days. There are several shops in the U.S. that specialize in keeping those old scopes going.
On Thu, 2007-02-22 at 10:11 -0500, Claude Jones wrote:
I could use one of you guys for a day! I've got an archive of old 1" tapes I've been wanting to transfer to a modern format. I've got a Sony BVH*** (don't have it handy) deck that fires up, but won't lock up and only puts out B&W. We've got the TBC, but I'm not sure how to get it all working...
The two most obvious questions, and easiest to resolve remotely, is do you know how to hook the two together, and do you have the multicore?
After that, you're in the realms of having to get repairs done.
On Thu February 22 2007, Tim wrote:
On Thu, 2007-02-22 at 10:11 -0500, Claude Jones wrote:
I could use one of you guys for a day! I've got an archive of old 1" tapes I've been wanting to transfer to a modern format. I've got a Sony BVH*** (don't have it handy) deck that fires up, but won't lock up and only puts out B&W. We've got the TBC, but I'm not sure how to get it all working...
The two most obvious questions, and easiest to resolve remotely, is do you know how to hook the two together,
That's a pretty general question - what I don't fully understand is sync, and where that's supposed to be fed from, and what some of the sync connector labels mean - don't have the machine handy right now, so I can't refer to it, so I'm doing this reply from memory
and do you have the multicore?
I do.
After that, you're in the realms of having to get repairs done.
Probably not going to happen. Finding someone who'd work on it, and getting this behemoth to them would be daunting, and probably not worth it
Tim:
The two most obvious questions, and easiest to resolve remotely, is do you know how to hook the two together,
Claude Jones:
That's a pretty general question - what I don't fully understand is sync, and where that's supposed to be fed from, and what some of the sync connector labels mean - don't have the machine handy right now, so I can't refer to it, so I'm doing this reply from memory
They come from your house sync pulse generator, if you're integrating the machine into a system. The TBC will run entirely on internal sync, if you want to use just the VTR and TBC together.
Compostite video reference is what's commonly known as a black burst signal. Essentially a black video signal, the same as you'd get from the video out of a camera with the lens cap on. Black video signal, with colour burst. The TBC can use this signal, alone, as its reference source.
The composite sync connectors use 4 Volt peak-to-peak combined horizontal and vertical sync signals.
I can't recall what else was on the back, there were four connectors on the one I played with the other day, and it'll depend on the model and local video system.
In general, for Australian PAL, we also have things like PAL pulse, which is a square wave that inverts on every other horizontal line; and colour framing, which is a pulse on every fourth field (it takes four fields for the colour sub-carrier to return to the same phase). NTSC would be different - it wouldn't have the PAL pulse, I don't recall how their colour framing works.
and do you have the multicore?
I do.
For a simple stand-alone playback machine, that may go to just a monitor, or any other recorder:
* Connect the multicore between TBC and VTR. * Connect advanced sync (probably abbreviated to ADV SYNC) from the TBC to a sync or reference input on the VTR. This is a 4 Volt composite sync signal. * Connect video out from the TBC to whatever other device you're feeding to.
The other inputs around the multi-core are for when you use a VTR that doesn't have a multi-core, such as Umatic (though we found that TBC was awful at handling the BVU deck we had at hand). Video in's rather obvious, you've got two choices for drop-out compensation - monitoring the RF from the video heads, or paying attention to a drop-out signal from the VTR (a simple enough RF / not-enough RF signal).
You might also want to connect the TBC video out back to the VTR's video monitor TBC input, and the local video monitor to the video monitor output. That lets you use the VTR's front panel controls to switch between monitoring input, raw VTR output (demod), TBC output, and a spare video source.
If you were integrating that VTR into other video systems for playback, you'd also connect your house sync references to the TBC reference inputs. Depending on the particular equipment models involved, and your requirements, that might be just a blackburst video signal (essentially the same as a capped-off video camera output), or might also include other separately-cabled sync signals.
The other outputs on the timebase correct don't need to be used. You've got several video outputs, two of them are composite, one of them lets you switch off sync insertion, and a sub-carrier signal for feeding to some things like *some* Umatic recorders which have a sub-carrier input. If there's a reference out, it's probably another composite sync output, rather than blackburst (I can't recall). The advanced sync is for the player it's correcting (because of delays involved in time base correcting, the player video needs to be a bit ahead of the output video).
On Thursday 22 February 2007, Claude Jones wrote:
On Thu February 22 2007, Gene Heskett wrote:
Chuckle, I've seen the hubs eat out so bad they wouldn't drive the reels anymore, spin like crazy on the startup. Then the motor gets throttled and it catches up.
I could use one of you guys for a day! I've got an archive of old 1" tapes I've been wanting to transfer to a modern format. I've got a Sony BVH*** (don't have it handy) deck that fires up, but won't lock up and only puts out B&W. We've got the TBC, but I'm not sure how to get it all working...
Sorry, without accurate docs, I'd be pretty lost when it comes to servo problems, Claude.
RM 529 - got one in my rack. It's got a fading tube or something, and sometimes displays the signal all squished on the "A" side, but the "B" channel still works. I've got to pull it and send it in one of these days. There are several shops in the U.S. that specialize in keeping those old scopes going.
That's a tired 12at7, or a bad connection in the channel selector switch.
On Thursday 22 February 2007, Tim wrote:
On Thu, 2007-02-22 at 01:33 -0500, Gene Heskett wrote:
If that thing isn't too badly fried, I sure could use it here. I have docs & all that as we have one of those still sorta working.
Get your own toys... ;-)
Give me an off list address & maybe we can dicker a little.
Done, have a look for a mail about "ye olde video gear..." from an e-mail address with the word "television" as part of the address.
I haven't see it yet, Tim. 11:05pm EST.
On Thu February 22 2007, Tim wrote:
Tim:
The two most obvious questions, and easiest to resolve remotely, is do you know how to hook the two together,
Claude Jones:
That's a pretty general question - what I don't fully understand is sync, and where that's supposed to be fed from, and what some of the sync connector labels mean - don't have the machine handy right now, so I can't refer to it, so I'm doing this reply from memory
They come from your house sync pulse generator, if you're integrating the machine into a system. The TBC will run entirely on internal sync, if you want to use just the VTR and TBC together.
Compostite video reference is what's commonly known as a black burst signal. Essentially a black video signal, the same as you'd get from the video out of a camera with the lens cap on. Black video signal, with colour burst. The TBC can use this signal, alone, as its reference source.
The composite sync connectors use 4 Volt peak-to-peak combined horizontal and vertical sync signals.
I can't recall what else was on the back, there were four connectors on the one I played with the other day, and it'll depend on the model and local video system.
In general, for Australian PAL, we also have things like PAL pulse, which is a square wave that inverts on every other horizontal line; and colour framing, which is a pulse on every fourth field (it takes four fields for the colour sub-carrier to return to the same phase). NTSC would be different - it wouldn't have the PAL pulse, I don't recall how their colour framing works.
and do you have the multicore?
I do.
For a simple stand-alone playback machine, that may go to just a monitor, or any other recorder:
* Connect the multicore between TBC and VTR. * Connect advanced sync (probably abbreviated to ADV SYNC) from the TBC to a sync or reference input on the VTR. This is a 4 Volt composite sync signal. * Connect video out from the TBC to whatever other device you're feeding to.
The other inputs around the multi-core are for when you use a VTR that doesn't have a multi-core, such as Umatic (though we found that TBC was awful at handling the BVU deck we had at hand). Video in's rather obvious, you've got two choices for drop-out compensation - monitoring the RF from the video heads, or paying attention to a drop-out signal from the VTR (a simple enough RF / not-enough RF signal).
You might also want to connect the TBC video out back to the VTR's video monitor TBC input, and the local video monitor to the video monitor output. That lets you use the VTR's front panel controls to switch between monitoring input, raw VTR output (demod), TBC output, and a spare video source.
If you were integrating that VTR into other video systems for playback, you'd also connect your house sync references to the TBC reference inputs. Depending on the particular equipment models involved, and your requirements, that might be just a blackburst video signal (essentially the same as a capped-off video camera output), or might also include other separately-cabled sync signals.
The other outputs on the timebase correct don't need to be used. You've got several video outputs, two of them are composite, one of them lets you switch off sync insertion, and a sub-carrier signal for feeding to some things like *some* Umatic recorders which have a sub-carrier input. If there's a reference out, it's probably another composite sync output, rather than blackburst (I can't recall). The advanced sync is for the player it's correcting (because of delays involved in time base correcting, the player video needs to be a bit ahead of the output video).
Why don't you send me a message, if you don't mind, and I'll reply to this privately. This is getting way off subject/topic.
On Fri, 2007-02-23 at 00:07 -0500, Claude Jones wrote:
Why don't you send me a message, if you don't mind, and I'll reply to this privately. This is getting way off subject/topic.
Okay, doing that in a moment, have a look out for an e-mail from someone with the word television in the address, and time base corrector in the subject. But why not install Fedora and Apache on it? Then we can stay on topic. ;-) Though being serious, I'd like to see some Linux software that could do RS422 based linear editing.