For 11 years networking was my profession with a specialized focus on proactive and reactive performance analysis. More recently I have embraced the AWS platform. This blog reflects my experience both past and present.
The Nord Stage 2 has four audio outputs as shown here:
You can send the various sections (synth engines) of the Stage 2 to the different outputs. This allows for more control over the mix and EQ at your output whether it be a recording bus, personal monitor, or live sound board. It’s a rather simple process.
Shift -> System Use Program Page buttons to go to Synth Outputs Scroll to change to the desired output
Having over 12 years of keyboarding experience I’ve played on numerous boards and have come to realize the various differences and nuances between the types. There are formal definitions out there and this list is probably not exhaustive, but it reflects my personal opinion. If you are reading this and are unfamiliar with keyboards this is a good place to start.
Midi controllers: Make no sounds on their own. Plug them into another device such as a keyboard or laptop to generate sounds.
It’s important to know your limits. In this case study we find a situation stemming from SMTP being throttled. This is part of the packet capture I received:
The top lines show the previous conversation ending. SMTP successfully sent 3 messages. After the 3rd message the mail server stopped responding and retransmits began. This pattern was repeatable. More than that it was repeatable from other EC2 instances. The only thing between the EC2 instances and the mail server was a router and a firewall.
If you refer to this post, you’ll see that one of my objectives for this year was to develop an Alexa app for my kids. Well, I am happy to report this objective as completed. The cover art and the image below show the high level architecture. The app idea actually started based on something I was doing for my kids that they really took a liking to. Unfortunately, for this post it might be an idea that I could actually publish and potentially monetize.
Being that I recently took the plunge to a static site hosted on AWS S3 I thought I would create a post outlining the high-level process for future reference. There are quite a few blogs in the interwebs outining this process, but if this helps someone else too then it’s a win-win. If you are curious as to WHY I migrated, you can find a short bit about that in this post.
This is old news, but I recently found out that Jeff Bezos considered “Relentless” as a possible name for his company instead of Amazon. If this is news to you as well, you can read a short article about it from Business Insider here.
Webster Dictionary defines “relentless” this way:
showing or promising no abatement of severity, intensity, strength, or pace
For some reason this word has stuck with me the past couple of weeks.
CloudShark released a new packet capture challenge for this Christmas season! Unfortunately, I don’t have the time to participate right now, but I wanted to reshare this for those of you that do. I also wanted this to serve as a reminder for me to come back to it later. Good luck!
Moving to S3 I’m currently in the process of moving my blog to Amazon S3. I’m not the first to do this and I won’t be the last. My reasons for this are similar to everyone else. Wordpress is an excellent blogging and site platform. I have really enjoyed working with it and getting to know its innards. As I continuously evaluate the purpose of my site though, I have to keep the technology behind it in sync.
Well, Tom and the team at CloudShark have put together an excellent packet capture challenge on their blog once again. It has actually been awhile since I’ve dug into a capture due to my recent shift in focus to Amazon Web Services, so this was a lot of fun for me. I feel like once you’re a “packet junkie” you are always one!
<span style="color: #ff0000;">*SPOILER ALERT*</span> The rest of this post describes the challenge and the process I followed for solving the challenge.