Page 2 of 3

Character Series Shotgun Case

This past month has been a wide shift of gears. I now look out the windows to new surroundings in what feels like a completely different province. Perhaps it wasn’t exactly one month, but several. Judging by the content I’ve been placing on this site lately, it’s clear to me my mind has been elsewhere!

Anyways, planting roots in a new home in a new place, my first order of business was getting a studio space set up where I could put my Pfaff to work. I have a lot of materials on hand at the moment and have been putting the word out to family and friends that I’d like to see them disappear. A couple promising projects are popping up requiring measurements, materials sourcing, design work, estimating and prototyping, but one project in particular didn’t require any waiting or decision making.

When I was asked if I could fabricate a soft takedown shotgun case, I didn’t hesitate to say yes. This is something I’ve been meaning to do for a couple years now; I was already familiar with the cases on the market, all the materials I’d needed were on hand, and I had already gained a bit of experience working with these materials across other projects. For this case to be complete, all I had to do was pattern out the design I’ve had in mind for years, grab the materials and get to work.

Here is the result:

 

A couple years ago, I’d like to think that I could have accomplished an equivalent result, but the me now, perhaps in a completely different place in my life, would be quick to identify all the little things that I hadn’t completely figured out yet.

I continue to make mistakes and see plenty of room for improvement, but also, plenty of things came to fruition with this project and I look forward to detailing them out.

Project specifications:

  • 30″ barrel 12 gauge (or smaller) shotgun (either over/under or side by side)
  • Materials
    • 16 oz waxed cotton canvas, blue
    • Heavyweight Irish wool, heather
    • 5 oz full-grain cowhide leather
    • Bonded Nylon #69 T70 thread
    • YKK zipper
    • Solid brass rivets and D-rings

Mechanic’s Toolsets in Service Manuals

I have yet to come across a service manual for a car, truck or motorcycle which includes a comprehensive list of tools required for each maintenance or repair procedure. The manuals will most definitely include Special Service Tools (SST), but when it comes to listing whether the case cover bolts require a 1/4″ ratchet and 8 mm socket, you are left on your own to determine this fact. I can easily see why technical writers and publishers would have to draw this line when creating a service manual, as it may be assumed that the manual is being read in a workshop fully stocked with all the generic tools one would hope a mechanic would have, but what if you are adventure touring on a motorbike, or privateering in the Dakar rally? Without a truck bed, trunk, or a mobile workshop following you, it’s absolutely necessary to know which tools you need specifically for the kind of maintenance and repair you plan (or don’t plan) on performing.

I’ve only been riding 4 and a half years, but I quickly had to redefine what it meant to be mechanically prepared. I had once been used to heaving a large, heavy toolbox in the back of the Land Cruiser, prepared for just about anything happening (and enjoying that nothing ever did). Then with my first Yamaha dual-sport, a small 350 cc, lacking any form of storage besides an 8″ x 6″ x 2″ tail bag, I had to learn how to pack minimally and hope for only the most basic problems to occur, if any. Riding with friends helps, when some coordination is made ahead of time to split the tools amongst each other, but it’s not always guaranteed that the tools required to remove the carburetor on one bike would allow for the same thing to be done on another bike.

This is where many people simply draw a line for themselves and sign up for roadside assistance, carry cash for a tow, or are one of those types who touch their seat, grips and footpegs and simply sell it the moment something else requires touching.

Who actually goes to this length, to determine precisely what type of tools they require, if say, a tire tube is punctured, or a spark plug needs to be removed, or the valve clearances need to be adjusted? Who has actually performed all the repairs on their bike and made note of which tools are needed for which tasks?

Happenstance Guidance

If Google were to tell you what I search the most… it would be dictionary definitions and encyclopedia articles.

From a young age, I remember being drawn to words and meaning. I’m still obsessed with understanding, and it’s for the most part why I’m so drawn to what the internet has to offer. I enjoy my silent habit of going about my day and taking a word I see or hear and casually putting it under the microscope. The most satisfying words to me are the words that are most commonly used which we happen to be least conscious of using. For example, “wiktionary this” and “wiki that“.

I wonder… how many people can say they’ve looked up “this” in a dictionary? Or noticed that the wiki page for beards rivals most Wikipedia articles for depth of content? Only Google knows, I guess. I should probably write about all the benefits this simple habit brings me one day, but what I want to specifically lead into now is this: nothing has brought me closer to understanding myself in relation to the world than by-chance looking up the noun “medium“. That may be a dramatically embellished statement… but let me try to unpack it.

Like most cases when I look up seemingly random words in the dictionary; I’m first, struck at how flexible words can be in English, and second, amazed that I take satisfaction in looking up what feels like the obvious. This is, after all, a word I’ve used countless times throughout my spoken life. But this word got me seriously thinking… Of all the detailed definitions, the two that impressed upon me most were “The means, channel, or agency by which an aim is achieved.” and “A format for communicating or presenting information.

This is precisely what I’ve been attempting to figure out for the majority of my life; what my medium is. This is why we go to school, this is why we find a job, this is what makes us individuals with purpose and how others may find value in us. This is the interface between each one of us and the world; where individuality is born. But has anybody ever actually put it this way? Does everyone realize this early enough? Do we see each other by the means which we achieve our aims or the way we communicate information? I don’t think we do consciously, but I believe it certainly defines us unconsciously.

This makes me consider my portfolio, which happens to simply be a placeholder on the website at the moment, if anyone’s actually noticed. I have delayed posting anything until I’ve determined what sort of format I want it to be; the kind of content that I wanted to include and who it is that I want to tune it for. I have kept revisiting this hesitation with the questions, “who”, “what”, “when”, “where”, “why”, and “how?”… when I believe I should instead just be defining “the medium”. What could offer myself and those who view it more guidance? What will interface with the rest of the world in a way that displays content consciously while subconsciously hints towards that unique and identifiable “me”?

Before I Say CAD, Let Me Just Say This

Continuing on from CAD Applications on Linux:

Before I chime in on what I think would make a CAD application successful on Linux… perhaps I should back it up. I’d like to clear the air on what it is I’m talking about when I say “CAD”. I believe this is the most important definition for the Linux community to grasp hold of and understand clearly.

CAD stands for Computer-Aided Design or Computer-Aided Design and Drafting (CADD), and CAD software uses computer technology to create, assist and manage a design and its documentation.

An easy question to ask yourself, if you’re wondering whether or not CAD software is required, is, “Am I creating something?” Typically, if something’s being created, it will be subject to a level of designing. And if something is to be designed, it’s likely to change. And it’s precisely the changing, which calls for the use of computer technology. Computers can manage the change of a design much more efficiently than we humans can, but for computer technology to efficiently aid us, we must consider the kind of designing we’re performing. After all, someone has to tell the computer what to do. How you design a road isn’t the same as designing a bridge. Designing a house isn’t the same as designing an automobile. It’s these differences in the type of designing we do which brings us an overwhelming amount of software applications divided by industry and tasks, targeted for specific design methods.

If categorizing CAD software by tasks, we’d recognize 2D vector (or drafting) applications, 3D modelling applications, animation applications, analysis, GIS server software, etc. If categorizing CAD software by industry, we’d recognize the architectural, engineering, construction and manufacturing industries, among others. And if you take the manufacturing industry alone, think of all the different things that could be manufactured and the specialized software that may exist because of the differences between these things. Further, not all software is tuned for just one industry or one task. Often, many tasks are utilized within an industry, or many industries rely on one or two specific tasks.

This plethora of “CAD” can be a good thing as well as a bad thing. The Good? CAD technology can be harnessed and tuned to do so many different things; affording us a quick way to build something, a way to communicate a complicated design, a way to determine whether or not something is safe or a way of proving that an idea will work in the real world, and of course managing how these ideas change along the way. The Bad?

Semantics.

People have been known to bastardize the acronym in ways such as, “I need someone to CAD this up.” or “Yeah, I do CAD.” We’re placing too much meaning on the acronym and it’s leading to too much confusion. And rightfully so! It’s easier to say “CAD” than it is to describe what finite element analysis is in the context of parametric solid modelling in the manufacturing industry. It’s easier to say “CAD” than it is to describe what grading is in the context of pattern making for the fashion industry. It’s easier to say “CAD” than it is to describe a graphics pipeline in the context of rendering for the animation industry. And really, by saying “CAD”, it is actually describing these things correctly; just very generally.

So… not so much a problem with the technology itself; more to do with humans, right?

Right. We all have this little switch in our head that flicks off the moment we become disinterested in the information we’re receiving, and it causes our ears to work less with our mind. (Here’s where I thank you if you’re still following me.) So I’ve learned that I have to tune the way I communicate what I do to the ears that are listening. The way I describe what I do to my mother isn’t going to sound the same as how I describe my craft in a job interview. And on the flip side, from an interviewer’s point of view; just because I may be an expert in 2D drafting, doesn’t necessarily mean I’d be hired as a Render Wrangler, but both applicants may be CAD Technologists.

In other words, a certain type of attention needs to be paid to the way CAD is communicated because it’s capable of being received in so many different ways; its capable of meaning so many different things. I believe the same level of attention needs to be paid within the Linux community.

What’s the context?
What is being performed?
For who?

The more effort placed in communicating precisely what form of CAD technology is being done, the greater chance there is for the Linux community to do what they do best, hopefully leading to a true suite of CAD software available on Linux.

Installing Bitwig on the openSUSE Linux Distribution

I’ve been successfully running Bitwig on openSUSE for about a year now. I have been able to successfully install upgrades for Bitwig, and have even switched from openSUSE 13.2 to openSUSE Tumbleweed successfully. Frankly, I am downright amazed by the fact that this is all working.

Bitwig is arguably a game-changer as far as digital audio workstation (DAW) software goes, and impressively, it’s available for Linux. Ubuntu Linux, that is.

So… if it is only released for the Debian-based Ubuntu Linux distribution… how was I able to install it on the RPM-based openSUSE Linux distribution?

Meet Joey Hess, and figure out how to buy him a beer. He authored the Perl script called alien which converts software packages (like a .deb package to an .rpm package!). Following me? Ensure it’s installed on your machine.

Head to Bitwig’s website and download the demo for the Ubuntu platform.

Open up your terminal and get cracking!

Switch to the root user and enter your password:

su

Run the following to convert the Debian-based software package to an RPM-based software package which openSUSE can work with:

alien -r bitwig-studio-1.x.x.deb

Depending on your machine, it may take a while. Perhaps look up Brian Bollman in the mean time. He offers a plethora of video tutorials which will get you up to speed with Bitwig quickly and confidently, regardless of your experience with digital audio workstations or audio in general.

When alien is done, you’ll see something like:

bitwig-studio-1.x.x-x.x86_64.rpm generated 

With the .rpm generated, we can check the dependencies of the package by running the following:

rpm -i --test bitwig-studio-1.x.x-x.x86_64.rpm

Now, the following is going to depend on what you already have installed on your machine. The machine I am testing on is set up in a fairly bare-bones manner, so I anticipate that the majority of people will experience the same:

error: Failed dependencies:
    libavcodec.so.53()(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavcodec.so.53(LIBAVCODEC_53)(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavcodec.so.54()(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavcodec.so.54(LIBAVCODEC_54)(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavformat.so.53()(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavformat.so.53(LIBAVFORMAT_53)(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavformat.so.54()(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libavformat.so.54(LIBAVFORMAT_54)(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libbsd.so.0()(64bit) is needed by bitwig-studio-1.x.x-x.x86_64
    libbsd.so.0(LIBBSD_0.2)(64bit) is needed by bitwig-studio-1.x.x-x.x86_64

This essentially means… for the Bitwig .rpm to install and work correctly, it’s going to depend on the above packages. So, open your YaST and look up these packages. Try searching for libavcodec, libavformat and libbsd. It’s been confirmed that they aren’t there, but maybe you’ll learn something in the process of searching.

Here’s what I found:

screenshot-from-2016-11-22-19-56-36

screenshot-from-2016-11-22-19-58-03

screenshot-from-2016-11-22-19-59-08

With a few basic searches, I learn that libavcodec and libavformat are part of the FFmpeg library, and it looks like openSUSE has a few libavcodec and libavformat packages installed, though not the same ones that Ubuntu uses which Bitwig expects. Another thing I notice is that the failed dependency error we received earlier didn’t explicitly name the package as we’d expect to see in YaST. It looks as though where we are told we require libavcodec.so.53(), when we actually need to look for a package that is named libavcodec53. Lastly, it looks like the libbsd0 package is available in our standard openSUSE repositories, so taking care of this dependency is as easy as checking the box and installing. So go ahead and do that while YaST is open… or close YaST and be explicit in your terminal:

zypper install libbsd0

Now, because I’m not interested in hosting Linux packages, and neither do I want to encourage people to blindly download and install packages from a source they’re not 100% familiar with (including my website), this is where I tell you to spread your wings and fly. Your homework is to find the libavcodec53, libavcodec54, libavformat53 and libavformat54 packages and ensure they are manually and properly installed on your machine.

After completing your homework, run:

rpm -i bitwig-studio-1.x.x-x.x86_64.rpm

And revel in the typing of your final command:

bitwig-studio

Voila!! Bitwig will load, step you through the EULA and prompt you to install any content packages, if you’re interested.

screenshot-from-2016-11-22-21-11-48

Did you experience problems finding and installing the libavcodec53, libavcodec54, libavformat53 and libavformat54 packages? No biggie. As a last resort, you could simply forget about ’em and force Bitwig to install anyways… Not recommended, but on a test machine I was able to successfully run Bitwig even without these dependencies. There are likely to be features of Bitwig which fail to work, but I wasn’t able to find them.

Run the following:

rpm -Uvh bitwig-studio-1.x.x-x.x86_64.rpm --nodeps

Then:

bitwig-studio

Merry beat-making!!

« Older posts Newer posts »

© 2018 Drew Merryman

Theme by Anders NorenUp ↑