Thứ Tư, 20 tháng 6, 2018

Auto news on Youtube Jun 20 2018

How does Growth-Driven Design work? The Growth-Driven Design

methodology has three major stages. The first

is the strategy stage. The goal of the strategy stage is to

develop an empathetic understanding of your audience

and how the website can solve problems along their journey.

Try to imagine the world from your audience's perspective.

Who are they? What challenges are they facing? What are their

goals? And where does the website fit in as a part of

that? There are several steps you'll need to take to

complete the strategy phase. First, define the website goals

by reverse-engineering the overall business' goals and

identifying how the website will influence them. The website

goals should be SMART goals- that's specific, measurable,

attainable, relevant, and timely - to help you properly measure

the website's impact on the business. Next, to understand

your audience, you'll need to do user experience, or UX,

research. The research may be qualitative, quantitative,

observational, or a combination to uncover user insights that

guide you through the rest of the strategy stage. The next

step is called "Jobs-to- be-Done." This framework will

help you identify the underlying needs that drive your audience

and what it takes for them to switch to your company's

products and services as a solution. Following jobs-to-

be-done, you'll refine your fundamental assumptions. This

step involves boiling down what you already know about your

market, your business, and your website. You'll refine or

create new user problem statements, unique value

propositions, situational triggers, current user habits,

switching anxieties, and more. Fundamental assumptions are at

the core of the success of your users, business, and website.

The next step in the strategy stage is to develop personas

using the deep understanding of your audience that you've

gained through the previous steps. A persona is a fictional representation of your ideal

customer. Then, you'll need to do journey mapping where you map out that persona's

journey of what happens before, during, and after they interact

with your business. By mapping your persona's journey,

you'll have a direction of how to weave your website into

that journey and solve their problems along the way.

After that, you'll develop a website specific strategy. These

are probably what you're used to looking at for website redesign.

Things like: site architecture, on-site SEO, key

sections and pages, integrations, technical

requirements, and more. The last step in the strategy stage of

GDD is for you to brainstorm an initial wish list.

The wish list will contain creative and impactful

website ideas that aim to solve your user's challenges,

provide value to the user, and help your business reach its

goals. The website wish list will have anywhere between 75

and 200 different ideas, including site elements,

sections, pages, specific features and modules,

integrations and more. With a strong wish list of high-impact

ideas, you'll begin the second phase of the Growth-Driven

Design methodology, which is the launch pad website. The goal is

to quickly build a website that looks and performs better than

what you have today, but isn't a final product. Rather, your

launch pad is the foundation you'll build and optimize

upon. The main driver, for launching quickly and without

sacrificing quality, is to collect data from real users

interacting with the site. Then, you're equipped to make

better, data- driven decisions on how to improve the website.

Launching quickly also creates a quicker time-to- value versus

the six or more months of a traditional web design project where you don't see any value

from the business. How can you quickly build a launch pad?

Well, there are a few key areas you can focus on

to accelerate the launch of a remarkable and effective

website. First, find a way to customize your approach to

building the new website that maximizes acceleration while

maintaining quality. There are a number of ways to make that

happen. Each website is uniquely different and will require a mix

of approaches to make sure it's a well-performing launch

pad. This is why it can be helpful to work with an

experienced HubSpot Partner agency to guide you on the best

approach for your new launch pad. The second way you can

accelerate your launch pad website is by running design

sprints on high-impact pages and sections. A design sprint is a

short, concentrated time period focused on problem solving,

design, prototyping, and testing. Design

sprints help you use the team's collectively

share their knowledge, generate ideas, but also

come to a high-quality prototype of your new website in record

time. Next, for anyone who's built a website in the past, you

may know that developing high- quality content - including

text, images, and video - is one of the most challenging

parts of a website build and often causes huge delays. Having

an effective content development process and great content

collaboration tools can accelerate your content

production speed and increase the quality of the content you

produce. The last way you can accelerate the build of a launch

pad website is through investing in internal efficiencies.

Internal efficiencies include switching from a waterfall

process to an Agile or Scrum process, building an internal

library of pre-built templates and modules that you can reuse,

removing developer dependencies so marketers can make updates on their own, leveraging

collaboration tools, these are a few way you can invest in internal effeciencies.

Once the strategy stage has been created and your launch pad website is live, you'll move

into the continuous improvement stage of the Growth-Driven

Design methodology. The goal of the continuous improvement stage

is to start identifying the high-impact actions you can take

to grow your business based on real user data. Once you've

launched the website, it may be difficult to stay focused on

improving the highest impact items at any given time, so

you'll follow a simple yet powerful agile process: plan,

build, learn, and transfer. Let's look at each step. In

the planning step of the cycle, you'll define the most

impactful items to build or optimize at that moment in time

to drive toward your goals. This starts by determining an area of

focus that your team can rally their improvement efforts

around. Focus is key, folks. The challenge is, there are many

areas you could work on: things like messaging to layouts to building

new pages to optimizing existing ones. The wide range of options

can make it overwhelming and difficult to determine where to

best focus your time. To solve this, you'll use the website

performance roadmap. The performance roadmap is a

framework for you and your team to ensure you're spending time

and energy on improving the most impactful areas. The roadmap

helps you set clear expectations with your boss, stakeholders, or

clients on exactly what you should and should not be working

on and why. And because there are specific metrics to measure

for each focus area, you can easily measure and report on

your progress building a peak performing website. What does a

performance roadmap look like? There are three major themes:

"establish", "optimize", and "expand". The

"establish" theme revolves around the core foundational

activities you can do when you"ve built something new.

Within this theme, there are three focus areas. First, you

can focus on "harvesting low hanging fruit" or building

high impact items that are easy or quick to accomplish after you

launch the site. Secondly, there"s building an audience to collect

data and run experiments. And third, there"s confirming the

website is driving value to those users. The "optimize"

theme revolves around on improving the user experience

and business performance of existing items on the site. The

three focus areas under optimize include improving usability on

the site to ensure visitors can unlock value as quickly as

possible. Doing conversion rate optimization, or CRO, to reduce

the friction and steps in your conversion funnels on your website. And

personalization, to provide a hyper-relevant experience for

each user or user-segment to ensure they get the perfect

experience for their needs. Lastly, the "expand" theme

revolves around building new items on the website to expand

the impact the website has. The three focus areas within the

expand theme include building new digital products onto the

website, such as tools, directories, digital resources,

or interactive experiences. The second focus area is expand into developing new items

on the website to improve other areas of the customer journey

map, such as a new customer experience, customer website, or maybe an

advocate program. And the third focus area in expand is using the website to help

other teams achieve their goals and help the business grow. This

could be building items on the website to help the sales team

prospect, qualify, and close deals. It could be helping the

HR team recruit more quality candidates and retain current

employees, or helping the customer service team reduce

support tickets and inbound phone calls. There are many ways

you can use the website as a tool to help the entire company

grow. The website performance roadmap is ordered to match the

lifecycle of a particular website. After your launch your initial launch pad

website, you'll often focus on the establishing and optimizing

themes, and over time you'll progress to focusing on the

expand step. Every website is different, and it's key that

you let the performance metrics and experience guide you on where your team

should focus. Each quarter, you should reassess how to divide

your continuous improvement efforts between different focus areas

based on performance metrics. Once your quarterly focus area

is set, it's important not to shift. Shifting focus can create

a lot of motion with little on individual improvements. Once

you've determined your focus area, it's time to complete

user experience research, or UX research, to understand what

challenges or friction points your website users are running

into that's preventing their progress. Once you have a good

understanding of the challenges, your team will brainstorm all

sorts of new action items to build. These items will drive

user value while improving the performance metric of the

current focus area. All ideas should relate to your team's

current focus area. With your list of brilliant ideas, it's

now time to prioritize the list to identify the highest impact

action items you can implement to boost performance in your

focus area. Based on your workload capacity, you'll go

down the list and select the high-impact action items until

you run out of capacity. Anything after will

be re-considered in the planning step of the next cycle. With

those high-impact action items in hand for the current sprint,

you'll write out action item cards with four key elements.

One, an outline of the specific customer scenario in the form of

a "job statement." Two, a hypothesis statement about your

proposed change and the impact it will have. Three, any

research or data that will back up your hypothesis. And four, an

experimental design for how you plan on testing the hypothesis.

Now that you have a focus and prioritized action items to

implement, you can move to the second step in the continuous

improvement cycle: build. The goal of the build step is to

host a working sprint with a cross-functional team to

complete all the high-impact action items. Just like a sports

team, your team will swarm on the action items to

collaboratively tackle them with aggression. With

these action items as their focus, they'll sync schedules,

meetings, and work times. In addition to building the action

items, the team also needs to set up the experiments as

outlined in the experimental design in order to properly

measure the impact the action item has and validate or

invalidate the original hypothesis. You'll launch what

you've built and let your audience interact with your

experiments. After a period of time, which will be different

for every experiment, you'll then move on to the learn step

of the cycle. In the learn step, you'll take a step back to

review the experiments you're running to extract learnings

about what you see your users interacting with. Was your original hypothesis correct or

did you prove it wrong? If it was proven wrong, this is okay

and fairly common, especially when first starting out and

trying bold ideas. It's critical to assess the outcomes

to learn more about your audience. What did their actions

and behaviors tell you about them, and how could you

incorporate these learnings into future action items? This is

such a critical step because the more you repeat the cycle, the

more you learn about your audience. The more you learn

about your audience, the more likely you'll have success in

providing value and hitting your goal metrics. The final step of

the continuous improvement cycle is the transfer step. The goal

of the transfer step is to share your learnings and exchange

ideas throughout the entire company to improve the entire

business, not just one of the parts. Between internal

communications and meetings, you'll share your user

learnings from the experiments you performed the previous

month. You can make recommendations based on the

learnings of how other departments could improve. You

can ask questions to other departments to pull insights and

fill gaps in your user research. You can also use this time to a

consistent user experience during all interactions with

your company. You'll look for possible collaboration

opportunities with other departments and teams. This a

cycle because you'll continually repeat the steps,

building momentum each time you repeat them. Generally, the

cycle is repeated every two weeks, with new action items

being built to impact the current focus for the quarter.

Eventually, you learn and improve enough on that focus

area and meetat specific goal. Then you'll move

to a new theme or focus on the website performance roadmap to

start the cycle again. To recap, the Growth-Driven Design

methodology starts with planning and research in the strategy

phase, which concludes with the creation of a solid wishlist.

The wish list is built into the launch pad website. In this

stage, you're building a website that looks and performs

better than today but is a starting point for your website

success. Then you'll start the continuous improvement stage

where month-over- month your improving based over real user data. This process is a

great alternative to the existing nightmare of a launch,

with the "set-it- and-forget- it" process in traditional web

design. Now you're continuously improving, using

the website to help all aspects of the business grow and seeing

results each month. Of course, marketing and sales are layers

that live on top of Growth-Driven Design. Think of

Growth-Driven Design like a sports car, but you still need

gas for that sports car to go, and that's what marketing and sales are. To develop a

peak-performing growth business, you need all three working

together, as they're all interconnected and they all feed off

each other. All of the challenges associated with the

broken traditional web design process are now solved with the

new playbook, Growth-Driven Design. This is the future of

web design and the playbook for building a peak-performing

website. Hopefully you're feeling inspired to grow as an

marketer, to grow as a web designer, to grow out of the

broken, traditional web design process and to start building

peak- performing websites using Growth-Driven Design. Let's

transform the world of web design together.

For more infomation >> Website Design Tutorial: Build a Peak-Performing Website with Growth-Driven Design - Duration: 19:03.

-------------------------------------------

Bluehost Website Tutorial | How To Build A Website With Bluehost - Duration: 8:37.

Bluehost website tutorial hey guys Bryan with WP Cupid blog and in this video I'm

going be showing you how to build a website with Bluehost whether you're new

be a technology or pro this step-by-step Bluehost website tutorial on how to

build a website with Bluehost tutorial video is perfect to follow along with by

following this Bluehost website tutorial video you will have your website hosted

and started with Bluehost in as little as 10 minutes at the end of this video

you will have your Bluehost website successfully started the first step I'm

going to cover is how to choose and register your own domain name for free

with Bluehost along with providing you with a discount on their hosting step 2

is choosing the right hosting plan step 3 is getting your website set up if

you don't have time to host and start your website right this second be sure

to bookmark this video so you can come back to it later I provided a link to

Bluehost below in the description to get your free domain name in the hosting

discount I do want to mention that the leak is an affiliate link and I'll

receive a commission which helps support this channel and helps us put out more

WordPress tutorial videos some things to know about Bluehost is they host over 2

million websites worldwide and over 850 thousand blogs around the world they are

also recommended by WordPress themselves since 2005 they instantly install

WordPress for you which makes starting a site that much easier

they provide 24/7 support via chat email and phone and they have a 30-day

money-back guarantee if any reason you're unhappy you can cancel and get a

refund no questions asked within the first 30 days the first thing you want

to do is head on over to Bluehost via the link in the description if you

already have it you'll see the get started now button on the page click the

button this is where you can select your hosting plan you'll see three different

options you'll see a basic plan + plan in a prime plan I recommend going with

the basic plan and then you can always scale up whenever you like if you have

more than one website then you want to choose either the plus plan or prime

plan I'm gonna choose the basic plan for this tutorial as this is most common go

ahead and hit the select button on whichever plan you would like to use we

are now brought to a demain page where we can choose the domain name that we

want completely free or if you already have a

domain name you enter it in over on the right for the new domain you can select

if you want it to be a.com dotnet dot org etc dot-com is the most popular

domain extension so I'd recommend going with a.com if you can I'm gonna type in

a domain here and click the next button you are now brought to a create your

account page this is where you will input your information we out first name

last name the business name is optional put your country address information in

put a phone number and lastly the best email for you and you'll get emailed a

receipt of payment and a copy of your login credentials etc below that you'll

see package information you'll see account plan this is where you can

select a term for your hosting package you have 12 months 24 months and 36

months and lastly 60 months as you can see you'll save money the longer you

purchase your hosting for I'm gonna select the 12 months package setup fee

is free the domain is free you'll see site backup pro you can unselect this as

there are free backup plugins you can use for your WordPress website search

engine jumpstart you can keep unselected this isn't necessary to have site lock

security fine is security for your WordPress website it protects it from

hackers I don't select this as there are really

good free alternatives domain privacy is an add-on that I highly recommend it

will prevent telemarketers and marketers getting a hold of your personal contact

information and bugging you with their services the domain privacy will shell

Bluehost information for the site and not yours

all these add-ons are completely optional and up to you to get as you can

see you're saving a lot for this hosting package well that you will input your

payment information I'm not gonna fill this out for protection of personal

information once your information is filled in you want to select the I have

read and agreed to Bluehost privacy policy in terms of service now click the

submit button you are now brought to a page where you will choose a password

for your Bluehost account click the create your password button and put the

password you would like click the I have read and agree to Bluehost privacy

policy and terms and conditions and click the next button you'll be directed

to a congratulations page click the blue login button

along in the Bluehost Bluest is also going to at this time email your

dashboard login information to the email address you provided for the rest of

this tutorial I'm gonna show you how to build a wordpress website with Bluehost

don't want to build your website with blows no problem

Bluehost has a ton of site builders where you can quickly get your website

started and set up let's continue in our Bluehost website tutorial on how to

build a WordPress website with Bluehost now you'll now see pick your theme

Bluehost has a bunch of awesome free wordpress themes to choose from you can

select a theme now if you want to or below the themes you can click skip this

step if you choose a theme now you can always change a theme you pick without

any problem at a later date I'll be going over this in more detail later in

the video once you choose your free theme you'll be at the page here stating

all done click the button that says start building to start building your

website on WordPress once you click that and log in you'll be at the wordpress

dashboard this is what the wordpress dashboard looks like it'll ask you a few

questions as you can see if you don't need help just click that you don't need

help option once you do that you will see this page you will see blog posts

where you can add a new blog post you will see where you can add new pages to

your blog if you want to change your navigation menus you can do so easily

and if you are going to sell products on your site you could install WooCommerce

to do so let's get to know WordPress a bit on the far left you will see tabs

hover over them and get to learn them post is where you can add new post pages

is where you can add new pages the media tab is where your images will show that

you upload to your blog comments is where you can view comments people leave

on your blog appearance is where you can change the look of your theme or change

your theme to another one or a premium theme select themes when you hover over

appearance it will showcase free wordpress themes you can choose from if

you select most popular it will show you the most popular free WordPress themes

hover over a theme and click activate to make the theme your WordPress theme you

should also see add new theme on this page this is where you can add a new

theme if you got it from another site or is a premium theme the plugins tab in

the left menu click add new this is where you can add new plugins for your

site pretty much any feature customization

you would want more than likely there's a plug-in to do that in the top left of

your WordPress dashboard you will see welcome here or your site title towards

the top of the page click this to view your site to log into your WordPress

dashboard you can do so via the Bluehost cPanel or by typing in your domain name

with a slash WP dash admin here's an example it'll bring up this page here

just input your login credentials to be logged into WordPress one of the best

plugins that can make hosting your WordPress website on Bluehost easier is

a plug-in called Elementor element or page builder is a drag-and-drop editor

for WordPress Elementor is the number one WordPress page builder today in over

500,000 users use it all around the world this plug-in can save you a ton of

time and lots of headaches figuring out how to make specific customizations this

plug-in has a free version in a paid version if you want to activate this

plug-in click Elementor page builder in the search bar you'll see the plug-in

click the Install Now button and click activate to activate the plug-in I

provided a link in the description to it so you can check out their site in the

free and premium features a great place to get premium WordPress themes is theme

for us I include the link in the description below you can get already

professional made WordPress themes if you don't want to bother with designing

your site etc another great site if you need help with designing your

customizations in WordPress is fiber with fiber you can get tasks done for

just $5 Fiverr is a great place to get a logo made if you have trouble doing so

yourself you have successfully built your website

on Bluehost and that is my Bluehost website tutorial on how to build a

website with Bluehost step-by-step video if you have any questions get in touch

yes I'm here to help you with anything you need alright guys thanks for

watching give this video a thumbs up and subscribe to our channel for more

wordpress video tutorials leave us a comment we love hearing from you

For more infomation >> Bluehost Website Tutorial | How To Build A Website With Bluehost - Duration: 8:37.

-------------------------------------------

5 THINGS: Building a Hackintosh (ep302) Build & speed vs Mac Pro & iMac Pro w/ Avid, Premiere & FCPX - Duration: 23:27.

On this episode of 5 THINGS, have you ever thought about using a Hackintosh?

Wondering how they perform?

Or maybe, just maybe, you wanna build one?

Fear not my tech friends, for on this episode, we've got you covered.

Hello and welcome to another episode of 5 THINGS – a series dedicated to answering the

5 burning tech questions that you have about technologies and workflows in the media creation space.

Plus, tech stuff I dig, and how it's used.

I'm still your host Michael Kammes.

So, uhhh, I understand you like Macs.

So do I.

So much so that today we're gonna choose the parts you need, build one, and see how it

performs against current Apple computers.

Let's dive in.

Why build one?

If you spend any amount of time following Apple, you've realized that they are a consumer

technology juggernaut.

Phones, tablets, watches, headphones.

This has led some to speculate that Apple isn't paying attention to the professional market.

"'Cause Apple doesn't care about us!"

[cough]

That is, Apple isn't making computers for those of us who need a lot of horsepower for creative

applications, and expandability to make the system more powerful than what the factory

model ships with...or what Apple deems us as worthy of.

We also need to look at the cost.

The Apple logo carries a price premium, and without much exception, Apple computers are

more expensive than their Windows or Linux counterparts.

And while I concede that a ready-to-roll machine should cost more than the sum of it's parts,

Apple tends to inflate this cost more than most.

Another reason to build a Hackintosh....is, well...

"because it's there!"

Because you can.

Well, physically, anyway.

I'm not a lawyer, and debating the legalities of building a Hackintosh is not my idea of

an afternoon well spent.

However, the tech challenge in and of itself is enough for some to dig in.

Lastly, owning a Hackintosh means you'll at some point you're gonna need troubleshoot

the build due to a software update breaking things.

If you don't build it yourself, you're not gonna know where the bodies are buried, and

you'll be relying on someone else forever to fix it.

For all of these reasons, I rolled up my sleeves, grabbed some thermal paste, and went down

the road of building my very own Hackintosh.

"Look before you leap."

When building my Hackintosh, this was my cardinal rule.

See what others had done before, what hardware and software junkies had deemed as humanly

possible, and follow build guides.

Although I was willing to build it, I didn't want it to be a constant source of annoyance

due to glitches, and then no avenue to search for answers if things went south.

Part of building a Hackintosh is being prepared for things to break with software updates

– and to only update after others had found the bugs.

I wanted to keep the tinkering after the build to a minimum.

More createy, less fixey.

The main site online for a build like this is tonymacx86.com.

The site has tons of example builds, a large community on their forums, and even better,

users who have done this a lot longer than me.

A great starting point is the "Buyer's Guide" which has parts and pieces that lend themselves

to the power than many Apple machines have.

A CustoMac Mini, for example, is closely related to the horsepower and form factor you'd find

with a Mac Mini.

As I tend to ride computers out for awhile, I decided to build a machine with some longevity.

"So this is the oldest personal computer in the world. Pretty historic junk."

"But the question is, 'what do you do with it?'"

Longevity meant building a more powerful machine, and thus as close as possible to a Mac Pro.

And wouldn't you know it, there is a section called "CustoMac Pro".

The downside to a machine as powerful and expandable as a CustoMac Pro is that it's

fairly large.

After I took inventory of all of the expansion cards I'd want to use, I realized I didn't

need everything that a CustoMac Pro afforded me.

The large motherboard in the system – known as an ATX board, was simply overkill and was

too large of a footprint for my work area.

I could actually go with something a little bit smaller and still have plenty of horsepower.

So, I looked into the CustoMac mATX builds.

M stands for Micro, and the micro ATX board would be similar to a full sized ATX board, but

a bit smaller.

I'd also lose some expandability with a smaller, micro ATX motherboard, but I could use the

same processor that I would use in a full size build – in this case, a Core i7-8700K,

and still get a decent amount of RAM (64GB) and have a couple of PCIe slots for a Graphics

card and future a 10GigE card.

I then went through the process of combing through the forums to see if there were any

guides or posts pertaining to the parts outlined in the CustoMac micro ATX section.

And wouldn't you know it, there was an extremely in-depth post that outlined each step in detail.

Next, I cross referenced the parts listed with reviews online, and I also consulted

various communities and folks to get some independent opinions.

This caused me to change a few things up, like getting quieter fans, a more stylish

case, and a few minor tweaks.

At this point, I was fairly convinced the parts and accompanying guides and forum posts

were going to be enough to point the way, so I pulled the trigger and bought the parts.

As the build was going to be massively based on the work that others had done before me

I purchased the parts via the site's referral codes.

Sure, I paid a little bit more, but let's support the community, eh?

I'll post the exact specs of the machine at 5thingsseries.com, along with the prices,

as well.

Now that the parts were ordered, it was time to prep the MacOS installer.

A computer won't do much for most of us unless it has an OS.

In order to get the MacOS onto a non Apple machine, we need to prep the OS appropriately.

Step 1 is to download Sierra or High Sierra from the app store on another Apple computer.

Step 2 requires us to download a Mac app called Unibeast.

Unibeast will take the MacOS installer, and place it on a bootable USB stick along with

an app called Clover, which contains the files needed to allow the OS to install on non Apple

hardware.

For Step 3, we need to format a USB stick for the OS to be on.

Make sure it's formatted as MacOS Extended (Journaled), and make sure the partition size

is relatively small.

Unibeast recommends a 7GB partition.

Larger sizes, like newer 128GB, 256GB or even larger sticks, just won't fly – partition

them into a smaller size.

I also recommend a USB 3.0 stick, it'll make things go a little bit quicker.

Launch Unibeast for Step 4 and follow the prompts to select the USB stick, as well as

various options for install – such as the Clover EFI Boot type (which I'll go into in

a minute) and inserting legacy graphics drivers into the install if necessary.

Then, let Unibeast create your installer on your USB stick.

A note about the EFI Bootloader config: When your Hackintosh boots, it looks for an EFI

partition.

The EFI partition contains basic system drivers and options.

If your EFI folder is borked, well, so will your build.

This is where Unibeast, Clover, and your hardware need to be in sync.

As you'll see later on in the video, my EFI folder during the USB stick build was no bueno,

and caused a bunch of issues.

Now that we have our MacOS installer prepped, let's get to the hardware build.

Day 1 of the build, and I'm here at Key Code Media.

It's Saturday. No one's here. So they let me build the machine with the caveat that I tell everyone that

they do not condone the building of a Hackintosh and that Apple is a valued partner to KeyCode Media.

All right. Here's all my gear but I'm missing one thing.

Alright now that I'm caffeinated let's get to work.

First thing is to get the side and top panels off of the Corsair Air 240 case.

That way I can start installing the parts and pieces and started threading cables to the right place

so they can attach to the internal components and motherboard as easy as possible.

First thing you're probably wondering is why you don't have a blazer on, to which I would respond "It's the weekend, brah."

Second of all we've got the power supply unpacked we've got the case unpacked, and

first thing to do is install the power supply in the case. If do that first that means that can maneuver the cables around

everything else they put inside there so I traditionally do that first..so let's get that installed.

For the power supply I went with the Corsair RM750.

This power supplies a little bit overkill for the build as it stands today.

However I intend to install a 10 GigE card to the future plus some existing spinning hard drives.

I also anticipate needing to install more fans as the system grows.

The 750 has plenty of Jacks from which you can run power to all of these devices.

So now that the power supply is installed I'm going to flip the case over to the second compartment

and we're going to retrofit the fans with more quiet ones and then we'll get into the ooey gooey good stuff

of the motherboard and GPU and CPU.

So as they poured over the parts list I made a few changes namely I chose different fans.

Noctua fans are known for being exceptionally quiet and there are only a few dollars more than traditional fans.

So even at first glance you can see that these fans are completely different.

The Corsair fan right here is hard plastic. You'll see it's a bit flimsy

and to hold it to the case is actually screw holes that go through here through the fans to the case

which could cause vibration after a while.

The Noctua fans are a lot sturdier and see there's rubber on the sides and also instead of screws that go through

there are actually rubber grommet that we would put through and that of course will cut down on vibration

We've got the 120 millimeter fan installed ...the rubber grommets are kind of a pain.

Make sure you have needle nose pliers to actually pull them through the fan.

The motherboard is what I spent the most time researching.

I went with an Asus Z370 as it could take the same processor as a larger motherboard.

It also gives expendability for the future.

So right now I'm being limited by two things.

First I don't seem to have screws for the motherboard. It doesn't appear the motherboard came with screws,

they should have come with the case, but I can't seem to find the screws that came with the case.

I'm also out of coffee.

No.

No.

Too big, dammit.

No.

No.

No.

Too big.

So after a half hour of searching I found enough screws throughout the shop to get the motherboard in.

They're all kind of a mismatch of orphan screws

but it's all in there.

Okay here's the processor, the Intel Core i7-8700K.

it's their latest model and their reviews online have been great.

All right now time to put the processor in...

Now the processor is in we want to put the heat sink on so we can cool the processor down.

I went with the other Noctua part, the NH-D9L. Now I had the option to go liquid cooled.

But anyone that remembers the old Mac G5 - the leaks that happened - would never want to repeat that.

So the heat sink has a fan inside of the heat sink as opposed to over it.

So I messed up. Apparently the heat sink needs to have a backing plate which comes through these holes here...

and unfortunately these holes can't be accessed from the other side of this case.

So I have to pull up the motherboard. Put this underneath, then put them on the board back in.

So I'll be back in a bit.

Okay the motherboard is out. Now I can place the bracket through the rear of the unit.

Since the motherboard is already out I'll just finish installing everything here.

Let's put in our brackets.

We need some thermal paste between the heatsink and the processor.

Then we can screw the heatsink over the processor.

Now I can put the fan into the heatsink.

Okay so now we have RAM. I wanted to go to 128GB but going with a smaller motherboard means I had to rethink this.

So I went with 64GB which I'll install in pairs.

I'm kind of excited to try this as my boot drive. It's an M.2 NVMe.

It's essentially an SSD but instead of plugging it into a traditional SATA port

it has a faster port on the motherboard for read/write speeds in the thousands of megabytes a second.

They do however get mounted kind of funky here vertical to the motherboard.

As for the graphics card I went with the GeForce GTX 1070, as I plan on using it for CUDA acceleration in Adobe apps.

All right all the parts are in. Graphics card is in. Processor, RAM, heatsink, fan. Let's fire it up and see if it works.

Fans started.

GPU fans are going.

Rear fan is going.

"Flux capacitor...fluxxing."

No smoke... no flames.

Lights on the motherboard...

and look at that!

Looks like we're getting something on the screen.

Now here we have the Asus motherboard bios which are going to configure according to the install guide recommendations on the website.

So I've made all my changes. I've got my bootable Mac USB stick.

We'll put that in the back of the machine here...now will save the BIOS changes and we'll restart.

And now now we have the moment of truth.

The Mac USB stick is in, and it's booting...

Well that's promising.

And there we go!

With the machine built and no smoke coming out, it was now time to dig into the Mac OS.

So here we are with build day 2.

Back at Key Code for day two.

I'm reminded by a text that KeyCode does still not condone this build. So there you go.

It's day two and I'm back at it. Yesterday we got the machine to boot and today we're going to troubleshoot Mac OS issues.

Let's dive in.

Oh Shit.

That's not right.

Is that the wrong driver?

Shit.

I told the Clover installer when I built the USB stick to install Nvidia drivers...maybe chose the wrong ones.

I suppose I can download the ones from the website. Let's give that a shot.

Shit.

Looks like the Ethernet drivers weren't installed, either.

Are the wrong drivers installed?

Maybe I should have made a hackin-watch or a hackin-phone?

Is it too late to have a donut?

Is it too early for whisky?

What if C-A-T really spelled DOG?

What the Hell!?

Did I choose the wrong career?

Is this an EFI partition problem?

Did Han Shoot first?

So, is goofy a dog or isn't he? I mean he walks a dog and wears pants.

[Music-Starship "We Built This City"]

[Record Scratch]

Alexa no Jefferson Starship while building a Hackintosh.

Alexa: "I won't play any of that weak ass Starship shit any more"

If the graphics drivers aren't loading, what else isn't loading?

Microwaves are too slow.

I'll probably have to edit the Config.plist file.

Did I turn off the stove?

I should have told that driver that NO, HE was the jerk.

Is CUDA installed?

What Is the Airspeed Velocity of an Unladen Swallow?

I wonder if there was a version mismatch between Clover and Unibeast.

I should have ordered the steak.

[Hums and taps foot to "We Built This City"]

So what I think may be happening is the wrong drivers are being installed.

from the EFI partition...which just may be hosed.

So, I need to change them out with known good drivers.

What I'm going to do it utilize a script I downloaded; EFI Mounter 3.

Enter in my password...

I'm going to mount the EFI...

Alright, what I've got here is I've mounted the EFI partitions of both my USB boot stick as well as the install of Mac OS 10 on my SSD.

I'm going to copy the EFI folder from one volume to another and see if the old EFI will help this boot any quicker.

So let's open the stick and let's open the EFI...there we go.

And now I'm going to copy this EFI, and I'm going to select "Replace".

OK, now I'm going to shut down, pull out the USB stick and see if that helps.

That's a lot better!

Let's log in.

"1-2-3-4-5". Same as my luggage.

Graphics seems to be right. It's using the Web drivers I'm willing to bet. Let's take a look.

And yes it is the Nvidea web driver. I think that may have solved it.

I guess that means what was causing the issue was rewriting the EFI folder via the newer Clover.

The build is done. Mac OS seems to be performing nicely as do some of the more creative apps.

The machine has all put together and all the cables are cable managed.

Now it's time to take it back home and put it back into the studio.

The question everyone asks is "how is the performance?"

First we have black and white analytics. Raw horsepower.

A common tool to measure this is Geekbench. Download the Geekbench app, let it run and whammo, you get performance metrics.

I decided to compare my build against a top of the line Late 2017 iMac Pro, retailing for $13,199

as well as against a Late 2013 Mac Pro canister, with a retail cost of about $7,000 today.

My build came in at just over $2500. I've outlined the specs of each machine here.

You can see that my build beats the Mac Pro hands down...

but is handily beat by the multicore performance of a iMac Pro, albeit at a price tag that's 5x as expensive.

As each of these computers were built with much different parts, a straight horsepower comparison isn't enough.

So, I also benchmarked all 3 systems with Adobe, Apple, and Avid software.

First, I did timeline render tests with Adobe Premiere Pro 2018.

I also used Adobe Media Encoder and exported to an h.264.

The results are pretty much inline with the Geekbench results.

The iMac Pro was the fastest performer, followed by the Hackintosh, and then the aging Mac Pro. Remember, the shorter the time, the better.

Now on to FCP X, v10.4.2, where I expected my system to fall down

due to the graphics card being nVidia card as opposed to the AMD cards found inside other Apple computers.

I did a timeline render benchmark, plus a Compressor encode time trial.

For renders, all 3 systems were very, very fast, in fact FCP X rendered faster than any of the other NLEs.

My Hackintosh did indeed end up rendering the slowest – however all systems rendered within a few seconds of one another.

That being said, my build exported the fastest, barely beating out the iMac Pro.

Lastly, Avid Media Composer, where I tested with the 2018.5 Ultimate version.

The iMac Pro came in first again, with the MacPro actually slightly beating my Hackintosh...

however all 3 systems were within seconds of one another.

Export times are largely irrelevant out of Media Composer.

Each system exported at exactly the same time - given Media Composers reliance on 32 bit Quicktime 7 for exports.

So, "how long did it take you to build it?"

The initial build took 9 hours. This includes research, the hardware build, the software build and initial software troubleshooting.

However, in the month since I've build the machine, I've had to spend an additional 3 hours troubleshooting

thermal issues, and buying 2 additional fans and installing them.

Do I have any regerts? A few.

The motherboard I chose didn't have Thunderbolt on board.

Not that I have any Thunderbolt devices, but it would have been nice to have an option for the future.

I also haven't seen much performance gains between OpenCL and CUDA playback inside Adobe apps.

I purposely went with a GeForce GTX 1070 SC as I expected performance gains with CUDA enabled.

As other apps – namely Final Cut X, are optimized for AMD cards, I would have rather gone with a Vega card,

use OpenCL inside Adobe, and still maximize the performance from other AMD enhanced apps.

So, was it worth it?

As a full time tech nerd and part time creative – yes.

First time I've built a computer from scratch in over a decade,

and I learned more about the underpinnings of the Mac OS than I otherwise would have.

But does this cost savings outweigh the piece of mind of a fully supported, warrantied and sexy looking piece of Apple Gear?

For someone who is a full time creative professional- I'm gonna say no.

You need a system that works, one that you can apply updates when needed,

and easily add additional hardware and software.

Time is money, and the less time you can spend troubleshooting the better.

Have more Hackintosh questions other than just these 5? Ask me in the Comments section.

Also, don't forget that I'll post all of the parts, pieces, and guides I used for my build at 5thingsseries.com.

Also, please subscribe and share this tech goodness with the rest of your techie friends. The more the merrier!

And I'll be your bestest tech friend.

Until the next episode: learn more, do more – thanks for watching.

For more infomation >> 5 THINGS: Building a Hackintosh (ep302) Build & speed vs Mac Pro & iMac Pro w/ Avid, Premiere & FCPX - Duration: 23:27.

-------------------------------------------

Build a fantastic rental return property called Class 1B - Duration: 1:42.

Hi, my name is Frank Days from Modo Builders

And hi, my name is Elaine Yeo

I'm a finance specialist.. Many of my clients ask me, "Elaine, is it possible to buy a

positively geared property, especially in Melbourne, and you may be shocked to know that the answer is absolutely yes

and it's called class 1B. So what is class 1B? Class 1B is an apartment like building where you can actually build

completely separately

self-contained

studio apartments where you can have up to nine different tenants and that presents a phenomenal rental return and we're talking

15% and that's normal.

Not many people know about this type of property is like Melbourne's best kept secret until I actually met Frank.

Frank is actually the leading industry expert when it comes to class 1B.

In fact, we'll be running a seminar where Frank will be sharing with you how easy it is to actually

build one of these positively geared

properties and I'll be sharing with you how you can actually get finance with this type of property.

Thanks. That's right Elaine. So as Elaine mentioned

very unknown

area here in the 1b zone. Great financial opportunity for you and your family.

We will be hosting an event on Tuesday the 26th of July just

hit the button down here to secure your tickets and we'll see you at 7 o'clock at Hawthorn East Tuesday the 26th of July

That's right, and places are limited so do register and look forward to meeting you. Thanks. Thanks

For more infomation >> Build a fantastic rental return property called Class 1B - Duration: 1:42.

-------------------------------------------

✅ Why Ford and VW are in talks to build a strategic partnership in summer 2018: CAR magazine UK expl - Duration: 3:02.

 Advanced talks, no equity swapLikely to build vans together   Ford and Volkswagen have confirmed they are in advanced talks to build a strategic alliance which could see them co-produce vehicles together

A memorandum of understanding has been signed.  Few concrete details have been announced, but the two brands said they were 'investigating several joint projects,' including co-developed commercial vehicles

No: don't expect another VW Sharan/Ford Galaxy any time soon, although we wouldn't rule out cars being jointly built in future

 At this stage, it is not about corporate cross-ownership or sharing equity in each other

Why are Ford and VW looking to strike a partnership?  The move reflects the expense of developing new models - especially in an age when many manufacturers are having to stump up additional costs to develop costly new digital platforms, extra ownership services and autonomous driving capabilities

   Ford also announced plans to renovate the famous Michigan Central Station in downtown Detroit - a stunning 1914 landmark (above) that has run into disrepair in the Blue Oval's hometown

It will turn the Beaux-Arts Classical building into offices for 5000 software and tech specialists

 'Ford is committed to improving our fitness as a business and leveraging adaptive business models – which include working with partners to improve our effectiveness and efficiency,' said Jim Farley, Ford's president of global markets

'This potential alliance with the Volkswagen Group is another example of how we can become more fit as a business, while creating a winning global product portfolio and extending our capabilities

We look forward to exploring with the Volkswagen team in the days ahead how we might work together to better serve the evolving needs of commercial vehicle customers – and much more

'  Meanwhile, the head of VW Group strategy, Thomas Sedran, said: 'Markets and customer demand are changing at an incredible speed

Both companies have strong and complementary positions in different commercial vehicle segments already

To adapt to the challenging environment, it is of utmost importance to gain flexibility through alliances

'  

Không có nhận xét nào:

Đăng nhận xét