amiaopensource / cable-bible Goto Github PK

Analog Video:

• Composite
• Component YPbPr
• S-Video
• RGBS
• RGBVH

Digital Video:

• SDI
• FireWire
• DVI
• DisplayPort
• HDMI

Integrated Analog/Digital Video:

• DVI-I

Analog Audio:

• Balanced wiring
• Unbalanced wiring

Digital Audio:

• AES-3
• S/PDIF
  • optical wiring
• MIDI
• TDIF
• ADAT

Parallel Data:

• PATA
• Parallel SCSI
• IEEE 1284 Parallel Port

Serial Data:

• RS-232
• RS-422
• SAS (Serial SCSI)
• SATA
• Apple Desktop Bus
• PS/2
• USB
  • USB 2.0
  • USB 3.0
  • USB 3.1
• FireWire
  • FireWire 400
  • FireWire 800
• ThunderBolt
  • ThunderBolt 1 and 2
  • ThunderBolt 3
• HDBaseT

per this thread on Twitter:
https://twitter.com/clairefox/status/1329841271028985858

I used the "cork/bottle" terminology when putting all this together instead of "male/female" for connector types and enforced that in the file image naming convention. Not a big deal but there should be a note in the README/contribution instructions that we (I) will continue to enforce gender-neutral language if anyone contributes relevant images/edits/descriptions

see: https://twitter.com/bitsgalore/status/1004333430350536705

update README with instructions for installing via homebrew/linuxbrew and running locally

A long-lingering result of the switch to ffmprovisr's codebase is that the internal linking from any module to its relevant connector/protocol pinout in pinouts.md is broken: in the online version, browsers just want to download the pinouts.md file. Offline, pinout images are live-linked to pinouts.ru so don't display even if opened properly with a browser with markdown viewing.

options:

• upload all pinout images to the repo to enhance stability/remove reliance on pinouts.ru hosting (should be done no matter what, to match in-repo connector images)
• re-structure pinouts.md to an HTML page and re-establish internal links
• hold off for dynamic restructure of entire site, a la this ffmprovisr discussion, to allow for more modular addition and linking of pinouts

Figure out how to create internal links for headings that appear multiple times in TOC (e.g. "digital," "analog") in markdown

Hi there maintainer(s), I would like to cite this project in academic research, and wondering if you'd be willing to attach a DOI to one of the releases.
There are two services that I've found that can do this, lmk if you need a hand:
http://mozillascience.github.io/code-research-object/
and Zenodo:
https://guides.github.com/activities/citable-code/

Thanks!

I've never seen a cable like this and I didn't see it in the cable bible! Whatcha think?

This is what it is attached to, something that plays Pong. It seems to be Turkish and transmits a PAL signal. We also think a feature is that it is supposed to be playable without being plugged into a television, so it might be meant to transmit a very short broadcast signal.

I love this resource very much. Is this licensed under Creative Commons, MIT, other...?

technically MIDI isn't an audio signal per se, so should probably be under "Data"

there's also a bunch more connectors besides the older/standard 5-pin DIN, which might actually help clarify the signal type and when/what/why MIDI comes into play (e.g. USB/FireWire/ethernet jacks)

see: https://en.wikipedia.org/wiki/MIDI#Alternative_hardware_transports

• analog video
• digital video
• analog audio
• digital audio
• parallel data
• serial data

At the moment, there is only the 3-pin variant. I would suggest to add the other XLR connectors as well: from 4-pin to 7-pin. For example, the 4-pin was the standard power connector for film cameras for many years (pin 1 is negative and pin 4 is positive).

hi,
feel free to disregard, but I was recently asked about alternatives to "male/female" language when referring to cables, and while I knew this had been addressed in the cable bible, it took me a minute to realize that the gender inclusive note was added only to the README and not the website proper. any chance you'd be willing/interested in adding this? from my perspective, redundancy would be good here.
thanks!
ben

Found this cable as part of the Cortical S Systematics Micro-pod technology and thought it might be worthy of inclusion

sony brand name vdc-5 ; 7-pin; Y/c-688

will send relevant links...

Digital Video:

• SDI
• FireWire
• DVI
• DisplayPort
• HDMI

Integrated Analog/Digital Video:

• DVI-I

Analog Audio:

• Balanced wiring
• Unbalanced wiring

Digital Audio:

• AES-3
• S/PDIF
  • optical wiring
• MIDI
• TDIF
• ADAT

Parallel Data:

• PATA
• Parallel SCSI
• IEEE 1284 Parallel Port

Serial Data:

• RS-232
• RS-422
• SAS (Serial SCSI)
• SATA
• Apple Desktop Bus
• PS/2
• USB
  • USB 2.0
  • USB 3.0
  • USB 3.1
• FireWire
  • FireWire 400
  • FireWire 800
• ThunderBolt
  • ThunderBolt 1 and 2
  • ThunderBolt 3
• HDBaseT

Could adding the speakON connector type be considered?

using "%" sign in file names for images breaks markdown links. find different way to mark images in need of attribution vs public domain

Under TDIF, the Bible states: "The Tascam Digital Interface Format is a proprietary protocol and connector, therefore seen exclusively with Tascam devices...."

Tascam licenses this format to many other manufacturers. In fact, if you click on the image for the DB-25 connector shown, TDIF can clearly be seen on a Yamaha device.

link out to wikipedia or other cited sources

This way, any time

brew update
brew upgrade

is run, also cable-bible will be updated to the lastest release, if needed.

@nkrabben reported:

After I brew install cable-bible, I try to run it cable-bible. I then receive an error.

LSCopyApplicationURLsForBundleIdentifier() failed while trying to determine the application with bundle identifier 193-    },.

Searching hasn't yielded anything that helps me understand what the issue is.

This allows to provide releases and use the app also locally, without access to the Internet.

Casual research indicates that because of the differences in electrical impedance, one could safely use digital AES-3 cables with XLR connectors to make analog connections, but not use analog XLR cables to make digital AES/EBU connections (at least not without introducing extra noise/fuzziness into the digital audio).

This is a crucial difference to know - so if one comes across a random XLR cable, how does one identify that it is analog or AES-3?

Digital Video:

• SDI
• FireWire
• DVI
• DisplayPort
• HDMI

Integrated Analog/Digital Video:

• DVI-I

Analog Audio:

• Balanced wiring
• Unbalanced wiring

Digital Audio:

• AES-3
• S/PDIF
  • optical wiring
• MIDI
• TDIF
• ADAT

Parallel Data:

• PATA
• Parallel SCSI
• IEEE 1284 Parallel Port

Serial Data:

• RS-232
• RS-422
• SAS (Serial SCSI)
• SATA
• Apple Desktop Bus
• PS/2
• USB
  • USB 2.0
  • USB 3.0
  • USB 3.1
• FireWire
  • FireWire 400
  • FireWire 800
• ThunderBolt
  • ThunderBolt 1 and 2
  • ThunderBolt 3
• HDBaseT

• Type A
• Type B
• Type C
• Type D
• Type E
• Type F
• Type G
• Type H
• Type I
• Type J
• Type K
• Type L
• Type M
• Type N

Not sure if we need to list them here, but a link to the IEC website would be useful: http://www.iec.ch/worldplugs/

Perhaps you should specifically note in the SDI section that even though SDI cables have BNC connectors on the ends, SDI requires coaxial cables that are different from those used for sending composite and component video.

This is something that people who might be reading the Cable Bible may not know.