WEBVTT

00:00:00.160 --> 00:00:05.440
whether you're a casual part-time wedding photographer or you're working

00:00:03.200 --> 00:00:10.880
on the next big budget hollywood movie every media production professional has

00:00:08.240 --> 00:00:18.000
run into this problem at some point they don't have enough space for all their

00:00:13.360 --> 00:00:19.920
photos graphics assets or video clips

00:00:18.000 --> 00:00:23.439
what's the solution well a lot of the time people will run out and buy things

00:00:21.760 --> 00:00:28.400
like these and whether they've got a hard drive inside them or an SSD

00:00:26.160 --> 00:00:32.320
external drives like these ones always run into some of the same

00:00:30.080 --> 00:00:37.680
limitations they connect your system using buses like usb or Thunderbolt that

00:00:35.440 --> 00:00:43.120
are not easily shared with other users so today as a spiritual follow-up to our

00:00:40.879 --> 00:00:48.160
recent budget 4k video editing workstation i'm going to be showing you

00:00:44.800 --> 00:00:50.559
guys what i consider to be the budget 4k

00:00:48.160 --> 00:00:54.719
video editing nas instantly see your current and past network activity detect

00:00:52.640 --> 00:00:58.960
malware and block badly behaving apps on your pc or Android device with glassware

00:00:56.719 --> 00:01:05.899
use offer code Linus to get 25 off at the link below

00:01:08.880 --> 00:01:15.760
i'm going to put aside the internals for now because really where the story

00:01:12.080 --> 00:01:17.439
starts is the case so this ticked all

00:01:15.760 --> 00:01:23.439
the boxes quiet reasonably professional looking and it

00:01:21.360 --> 00:01:28.159
can accommodate with the optional hard drive sleds up to 18

00:01:26.880 --> 00:01:34.079
hard drives fractal sent along the case for this video along with

00:01:31.680 --> 00:01:38.159
all the expansions but um i haven't looked at the reviewer's guide

00:01:35.759 --> 00:01:41.759
so i don't really know how any of this works

00:01:40.000 --> 00:01:46.399
there well there seems to be a slight problem my original email said the

00:01:43.680 --> 00:01:51.040
define 7xl holds up to 18 three and a half inch hard drives the reviewer's

00:01:48.720 --> 00:01:55.200
guide says 14 max

00:01:52.799 --> 00:02:00.880
and it's bolded i don't know how this works

00:01:57.520 --> 00:02:00.880
oh here we go

00:02:01.200 --> 00:02:06.880
so now what i want to do is reconfigure my fans before i start stacking hard

00:02:05.200 --> 00:02:10.720
drives in this thing now we're about ready to install drives but i found yet

00:02:08.879 --> 00:02:15.520
more conflicting information in the user's guide three and a half two and a

00:02:12.720 --> 00:02:21.760
half universal drive positions 18. which one is it fractal so for this project

00:02:18.239 --> 00:02:22.800
we're going to be using the ideal drives

00:02:21.760 --> 00:02:28.080
these are seagate's iron wolf pro nas drives

00:02:25.680 --> 00:02:31.280
so these are the 16 terabyte variant but they are available in a variety of

00:02:29.360 --> 00:02:37.680
capacities they come with a five year warranty including seagate's rescue data

00:02:34.480 --> 00:02:40.720
recovery service that's freaking awesome

00:02:37.680 --> 00:02:43.280
and as they're pro iron wolf drives

00:02:40.720 --> 00:02:47.920
they're rated for up to 24 drives in an enclosure because with drives that are

00:02:45.280 --> 00:02:52.319
not designed for nas use and for operation in close proximity to each

00:02:49.680 --> 00:02:57.040
other the vibrations of the next drive over can actually affect the operation

00:02:54.560 --> 00:02:59.840
of another drive so these are good for up to 24 and since we're going to be

00:02:58.400 --> 00:03:04.640
putting 18 or 14. in this chassis these were a

00:03:02.800 --> 00:03:08.080
perfect fit we got to put the anti-vibration rubber grommet then we

00:03:06.480 --> 00:03:12.239
lined that puppy up on the bottom of our drive now with an SSD

00:03:10.319 --> 00:03:14.800
you guys have probably seen me use as few as

00:03:13.440 --> 00:03:20.640
two screws or one or none and some double-sided tape

00:03:18.640 --> 00:03:24.480
but i would never recommend that with a hard drive when it comes to hard drives

00:03:22.560 --> 00:03:28.159
you mount them with as many screws as you can because even if your drives are

00:03:26.480 --> 00:03:32.000
designed to withstand the vibrations of nearby drives they are not designed to

00:03:30.400 --> 00:03:37.640
withstand the vibrations of nearby drives that are not mounted correctly

00:03:35.120 --> 00:03:40.730
so all four of our screws go in

00:03:42.959 --> 00:03:51.200
that's 16. okay none of the documentation said

00:03:46.560 --> 00:03:51.200
anything about 16. what the crap

00:03:51.440 --> 00:03:59.040
well that happened we're up to 19 drives which sort of leads me to wonder how

00:03:55.920 --> 00:04:00.799
much farther we can go like

00:03:59.040 --> 00:04:05.080
yeah you know what you can call it good at 20 right

00:04:02.959 --> 00:04:09.920
i mean 320 terabytes of raw capacity in a 200

00:04:08.239 --> 00:04:13.439
case let's start talking about some of our other components

00:04:11.680 --> 00:04:18.320
yes this is a strix gaming

00:04:15.920 --> 00:04:22.800
motherboard or whatever but what it also is is a good value board with lots of

00:04:21.199 --> 00:04:27.199
memory expansion which could be important if we want to run vms or other

00:04:25.120 --> 00:04:31.440
server functions on our nas it's got support for third gen ryzen processors

00:04:29.520 --> 00:04:36.080
with a BIOS update of course it's got lots of pci express expansion it's got

00:04:33.840 --> 00:04:41.840
two m.2 slots and we'll get to why we need those later and finally it manages

00:04:39.120 --> 00:04:45.600
to boot in headless mode without a graphics card installed and without an

00:04:43.600 --> 00:04:49.360
apu installed where you would be able to use the onboard graphics so that saves

00:04:47.840 --> 00:04:54.160
us some money because even though we're going to need a graphics card in order to configure our system we don't

00:04:52.560 --> 00:04:58.400
actually necessarily want to leave one in there unless we have some purpose for

00:04:56.240 --> 00:05:02.240
it like we want to use GPU hardware acceleration for media encoding for a

00:05:00.479 --> 00:05:08.560
plex server or something like that so we're going with a second gen ryzen 2600

00:05:06.000 --> 00:05:14.080
non-x because it's using the original zen architecture instead of zen 2 those

00:05:10.960 --> 00:05:16.400
individual cores are not as fast

00:05:14.080 --> 00:05:20.639
now we could go with something heavier if we intend to use this thing you know

00:05:18.639 --> 00:05:23.360
again as a you know a media server that's going to have to do you know

00:05:21.680 --> 00:05:29.759
heavy video encoding or whatever the case may be but our intent for the build today is to

00:05:27.600 --> 00:05:34.400
just have it be a file server and this is going to be plenty plenty of

00:05:32.080 --> 00:05:37.919
horsepower for that now i did consider going Intel for this build but even

00:05:36.000 --> 00:05:42.320
though we're using regular unbuffered memory one of the things that pushed me

00:05:39.759 --> 00:05:47.120
to AMD was their unofficial support for ecc or error checking memory on their

00:05:44.880 --> 00:05:50.720
consumer processors now it does require support from the motherboard and

00:05:48.800 --> 00:05:54.639
conveniently this one happens to support it as well as costing a little bit more

00:05:52.800 --> 00:05:58.720
but if you were gonna run something like zfs for your software raid it is a

00:05:57.120 --> 00:06:03.280
recommended feature to have and you should spend a little bit of extra for

00:06:00.560 --> 00:06:06.800
some unbuffered ecc RAM cooling is another item that i waffled about a

00:06:04.720 --> 00:06:11.520
little bit on this build so i ultimately decided to give it a shot with the AMD

00:06:09.199 --> 00:06:16.080
box cooler and then as long as my thermals and acoustics were fine stick

00:06:13.680 --> 00:06:19.280
with that and then if they're not then i can always upgrade down the line one

00:06:17.759 --> 00:06:23.360
thing i spent extra on that would normally be considered a splurge item

00:06:21.360 --> 00:06:28.560
but in this case actually makes a ton of sense is a modular power supply why don't we

00:06:26.720 --> 00:06:34.240
just say this the recommended way to do this would be to get your hands on

00:06:30.880 --> 00:06:37.360
some custom cables for the power supply

00:06:34.240 --> 00:06:40.000
all right that's 16 and we've got both

00:06:37.360 --> 00:06:44.800
one more harness as well as one more plug on our modular power supply to

00:06:41.919 --> 00:06:48.720
handle our other four drives i just really doubt that this is gonna work

00:06:47.360 --> 00:06:52.639
turns out this power supply does only come with one four connector molex cable

00:06:50.800 --> 00:06:56.800
but i was able to find one just kind of lying around in the warehouse so we've

00:06:54.240 --> 00:06:59.919
got enough even if you as an end user would end up having to order an

00:06:58.080 --> 00:07:05.120
additional one now comes the part of the build that's pretty much just down to

00:07:02.000 --> 00:07:07.759
however you want to do things connecting

00:07:05.120 --> 00:07:10.960
the drives to data as you can see the motherboard can only accommodate six

00:07:09.520 --> 00:07:15.280
drives with these connectors on the right hand edge fortunately as long as

00:07:13.120 --> 00:07:20.160
we've got pci express slots to spare we can add pretty much as many SATA ports

00:07:17.680 --> 00:07:24.960
as we want with boards like this now the most important thing to watch out for if

00:07:22.319 --> 00:07:31.360
you are expanding your storage is not to get a raid card you want an hba or host

00:07:28.880 --> 00:07:35.440
bus adapter because most software raid whether you're running it through free

00:07:32.560 --> 00:07:40.000
nas or unraid can behave erratically or at the very least not give you proper

00:07:37.199 --> 00:07:43.039
drive reporting if you are using a raid card another thing to watch out for when

00:07:41.840 --> 00:07:47.599
you're shopping for these is the types of connectors some of them just have the

00:07:45.360 --> 00:07:50.319
regular SATA connectors that you would recognize and you plug into them and

00:07:49.039 --> 00:07:53.680
then you've got an octopus of cables coming out plug into your drives but

00:07:52.560 --> 00:07:59.199
others use connectors that are more designed

00:07:55.759 --> 00:08:01.759
for SATA or sas backplanes so mini sas

00:07:59.199 --> 00:08:06.400
hd or sff 8087 are some pretty common ones the way that you connect these is

00:08:04.080 --> 00:08:09.919
with slightly fancier cables so here's a mini sas hd one this is an eight port

00:08:08.400 --> 00:08:15.919
card so you've got just these two connectors that go into the back of the drive and then

00:08:13.680 --> 00:08:19.680
way at the other end you've got the octopus

00:08:17.360 --> 00:08:23.680
oh yeah it's actually eight octopus okay so it's four per connector picking up

00:08:22.000 --> 00:08:29.440
cards like these second hand on ebay can be a great way to add a ton of connectivity to your system

00:08:26.400 --> 00:08:33.279
just one thing to watch out for guys is

00:08:29.440 --> 00:08:35.039
sas cards will work with SATA drives but

00:08:33.279 --> 00:08:40.800
not the other way around for whatever reason you have sas drives you can't buy

00:08:37.680 --> 00:08:42.800
SATA hbas so to be clear guys i am not

00:08:40.800 --> 00:08:47.279
necessarily recommending exactly the cards i'm using i'm just using whatever

00:08:45.279 --> 00:08:50.399
hba cards i had lying around a couple little housekeeping items still

00:08:48.800 --> 00:08:54.480
be taken care of i want to cable manage these kind of like this these ones for

00:08:52.480 --> 00:08:58.720
the bottom can go over here a couple of cable ties and then i've run myself an

00:08:56.720 --> 00:09:02.000
extra SATA cable for the future in case i want to plug in a second SSD down the

00:09:00.880 --> 00:09:05.200
line and still got to plug in these ones at the

00:09:04.320 --> 00:09:11.360
top overall actually this is not bad for having 20 hard drives in it i could use

00:09:09.440 --> 00:09:15.920
the built-in fan controller that's in the case but actually that would require

00:09:13.519 --> 00:09:21.920
another SATA connector and i don't have any right now all i need to do now is

00:09:18.080 --> 00:09:23.600
put in my temporary graphics card this

00:09:21.920 --> 00:09:28.480
is the fractal case yeah this thing is obnoxious what

00:09:26.560 --> 00:09:32.640
what do you mean obnoxious well okay i mean like in a good way this is awesome

00:09:30.640 --> 00:09:36.080
so i'm not that familiar with proxmox and i wanted to show people how you

00:09:34.240 --> 00:09:39.600
might configure a system like this in proxmox i wonder if you ceramic coated

00:09:38.399 --> 00:09:44.000
this if it would help with the fingerprints what is it with you in ceramic coating things i don't know

00:09:42.640 --> 00:09:49.440
that's cool by the way make sure you're subscribed so you don't miss our ceramic coating a phone video which was also his

00:09:47.279 --> 00:09:53.920
idea oh this is heavy man so i mean like straight into proxmox the only thing you

00:09:51.440 --> 00:09:58.640
can really create is a a single v dev pool so we could have one that's like

00:09:56.480 --> 00:10:03.200
raid z3 although if you're going to add more drives that would mean you would

00:09:59.839 --> 00:10:05.040
need to add 20 whole more drives i mean

00:10:03.200 --> 00:10:10.240
in an ideal world what i would probably want to do is like maybe

00:10:07.519 --> 00:10:14.640
three raid z ones so that would be three raid z1 v devs

00:10:12.640 --> 00:10:19.600
that would be three drives of capacity lost to redundancy and then i'd have two

00:10:16.959 --> 00:10:23.279
hot spares or something like that i mean if you're running stuff at your

00:10:20.720 --> 00:10:27.600
house like for me i have my ubiquity controller that runs on a vm on my nas i

00:10:25.279 --> 00:10:30.880
have a plex server i have lots of different vms just for doing all these

00:10:28.959 --> 00:10:34.959
little things home automation and like in proxmox you can do it really easy you

00:10:32.640 --> 00:10:39.680
can actually create containers which are still running in the host os so there's

00:10:36.880 --> 00:10:44.399
very little um overhead and it's super easy to maintain so why

00:10:41.760 --> 00:10:47.200
don't you just use freeness well aside from my bad experiences with it in

00:10:46.079 --> 00:10:51.600
the past it's sort of a question of

00:10:49.600 --> 00:10:56.000
what's more cost effective right right so unraid costs money yeah which is sort

00:10:54.079 --> 00:11:00.399
of a drag not a whole lot but but if i want to use zfs optimally in a way that

00:10:58.399 --> 00:11:05.200
is recommended by the experts who know a lot about zfs i'm actually spending more

00:11:02.800 --> 00:11:08.640
on memory upgrades if i don't care about the virtualization which is not how i've

00:11:06.800 --> 00:11:12.079
configured this in the first place than it would cost me to just buy an unrated

00:11:10.320 --> 00:11:17.120
license in the first place right and unraid does have some performance

00:11:14.720 --> 00:11:20.320
gotchas like if you allow your drives that you're not accessing currently to

00:11:18.480 --> 00:11:25.760
go to sleep so you disable turbo right that's bad

00:11:23.200 --> 00:11:29.760
and also if you configure it to fill up one drive then the next one then what

00:11:28.160 --> 00:11:33.920
that means is every project can potentially be i o bottlenecked by the

00:11:32.000 --> 00:11:38.240
individual drive that it's being pulled off of i just wanted to highlight a few

00:11:36.079 --> 00:11:43.360
different types of software that you can use for a config like this okay so we

00:11:40.640 --> 00:11:47.680
if we do df we can actually see it's 214 terabytes of capacity oh no i mean we

00:11:46.160 --> 00:11:52.959
lost what was it four drives good heavens three drives yeah oh man you can

00:11:50.399 --> 00:11:57.440
feel it wow the vibration is real you know what

00:11:55.839 --> 00:12:01.360
actually this would be a good way to check our drive thermals

00:11:59.440 --> 00:12:04.959
i'm going to put the covers on and then just like run 100 gig one and let it

00:12:03.200 --> 00:12:08.240
flash i'm going to install net data so we can

00:12:06.480 --> 00:12:13.519
actually look at the array it's nice that there's so much room for cable management on the back but in the event

00:12:11.200 --> 00:12:17.920
that you do have kind of a you know thick boy cable back here i would prefer

00:12:16.399 --> 00:12:20.560
if there was some way to screw on the side panel

00:12:21.040 --> 00:12:26.800
that's not that great mean it's holding but

00:12:27.440 --> 00:12:33.519
see that is what i'm talking about cable manager stuff better no wait watch

00:12:31.920 --> 00:12:36.959
out that's power for the drive there's a whole bunch what is it why is it like

00:12:35.279 --> 00:12:41.120
them like that don't worry about it now i did misspeak before i said that this

00:12:38.880 --> 00:12:44.160
was 200 it's 200 without the tempered glass side panel which we obviously

00:12:43.040 --> 00:12:51.120
wouldn't need for a build like this that's just the one they sent so we're using net data to monitor the disk usage

00:12:48.959 --> 00:12:54.399
it's always so funny because zfs messes around with it so it's like

00:12:52.720 --> 00:12:59.600
20 megabytes but that doesn't make any sense now that we're updated the first thing

00:12:56.639 --> 00:13:04.079
we need to do is create our unraid array so the parity disks right here are the

00:13:01.760 --> 00:13:08.480
capacity that we're going to give up in order to avoid losing data in the event

00:13:06.399 --> 00:13:12.320
of a physical drive failure so one parity disk means we give up one drive

00:13:10.560 --> 00:13:16.560
worth of capacity but it also means we can only lose one drive before we start

00:13:14.800 --> 00:13:21.519
to lose data after that while two means that we give up a total

00:13:18.720 --> 00:13:26.480
of 32 terabytes of space but we can lose two drives before we

00:13:24.240 --> 00:13:30.880
start to lose any data now it should be noted unread has a cache feature that

00:13:28.320 --> 00:13:36.000
allows you to have high speed ssds as like a faster storage tier but i use the

00:13:34.000 --> 00:13:40.240
word tier very loosely because it doesn't work the way you might expect it

00:13:37.519 --> 00:13:44.480
to you can use it to accelerate writes onto the unrate array but from my

00:13:42.399 --> 00:13:48.240
experience especially when working with very large amounts of data like you

00:13:46.240 --> 00:13:52.079
might when you're ingesting footage it can be a little bit on the finicky side

00:13:50.160 --> 00:13:56.079
and i wouldn't really use it for that what i would use it for is if i wanted

00:13:54.079 --> 00:14:02.079
to run virtual machines on this i would run all of my vms off of a raid1 set of

00:13:58.480 --> 00:14:04.959
ssds that i plug into my m.2 slots

00:14:02.079 --> 00:14:09.199
oh oh cool they built a new feature based on my feedback

00:14:07.120 --> 00:14:13.120
when it's formatting it automatically pauses parity sync because otherwise it

00:14:11.199 --> 00:14:16.000
takes like a day while we wait for the format we can adjust some of the

00:14:14.240 --> 00:14:20.000
settings that we talked about before so turbo write is technically called

00:14:17.920 --> 00:14:23.360
reconstruct write so we're going to go ahead and turn that on

00:14:21.760 --> 00:14:26.480
this is the second tweak i talked about we're going to use most free so as we

00:14:25.040 --> 00:14:30.639
write data to the share it'll go to whichever drive has the most free space

00:14:28.639 --> 00:14:35.600
on it which means that if we were to write 18 separate video clips it would go this

00:14:34.480 --> 00:14:39.199
one this one this one this one this one this one this one like that minimum free

00:14:37.519 --> 00:14:42.560
space is a really important parameter to tune so if we think our clips could be

00:14:40.880 --> 00:14:48.320
no bigger than uh 100 gigs then we need to make sure that

00:14:45.920 --> 00:14:52.000
we key that in now nicholas assured me that this is going to work but nicholas

00:14:50.320 --> 00:14:56.720
also brought me the wrong motherboard twice when we were doing that CPU repair

00:14:54.160 --> 00:15:02.800
thing here's our problem our chassis fans are running at 700 RPM which is

00:14:59.440 --> 00:15:04.560
nice and quiet but is just not enough to

00:15:02.800 --> 00:15:10.000
push enough air through all those friggin drives i'm gonna move our cable

00:15:07.360 --> 00:15:14.480
from our onboard gigabit network to our add-in 10 gig a quantcha card are we 10

00:15:12.639 --> 00:15:19.920
gig we're 10 gig share time who's not that busy right now

00:15:17.279 --> 00:15:22.880
there's my water bottle you bastard why would i

00:15:20.720 --> 00:15:28.320
take that i don't know but it has my name on it and also my stickers so right

00:15:25.440 --> 00:15:33.040
now mark is pulling in excess of gigabit speeds when he's playing back this is

00:15:30.000 --> 00:15:35.440
ten to one 8k red footage so really not

00:15:33.040 --> 00:15:40.480
what i had designed this system for and dennis how's it going okay so dennis 2

00:15:38.160 --> 00:15:44.240
is in excess of one gigabit but we're also getting some chop now so

00:15:42.560 --> 00:15:48.959
we're actually pulling three and a half gigabit per second off

00:15:46.560 --> 00:15:53.360
of that machine now the write speeds are not fast but the assumption that i made

00:15:51.519 --> 00:15:58.240
is that you guys are not working with 10 to 1 red footage and instead you're

00:15:55.440 --> 00:16:02.160
ingesting from sd cards in which case 60 to 80 megabytes a second should be as

00:16:00.720 --> 00:16:06.160
fast as you need as long as only one person's ingesting at a time the benefit

00:16:04.320 --> 00:16:09.440
of unraid that i think outweighs its slow rights in this case is that if

00:16:08.240 --> 00:16:14.639
you're the kind of person who's just starting out it allows you to just get

00:16:11.680 --> 00:16:19.199
one parity drive and as few as one additional storage drive and then just

00:16:16.720 --> 00:16:23.759
expand as you go as long as every drive that you add is smaller than the parity

00:16:21.600 --> 00:16:26.639
drive you can add as many different kinds of drives as you want and you can

00:16:25.199 --> 00:16:31.600
just add them one at a time that's something that you can't do with a zfs

00:16:28.959 --> 00:16:35.120
based solution like freenas or like proxmox

00:16:32.959 --> 00:16:37.440
i'm really surprised that this worked as well as it did

00:16:36.639 --> 00:16:43.279
i i mean that's like between the two of you that's around 350 megabytes a second

00:16:41.600 --> 00:16:46.880
that we're pulling off of that thing and drive temps have held steady even while

00:16:45.440 --> 00:16:51.839
we're pushing it so all the ones on the front are around 39 41 degrees and you

00:16:49.920 --> 00:16:55.759
can really tell which ones are the four that are in the top and at the back 47

00:16:53.839 --> 00:17:00.240
48 46 and i don't know maybe this one 43 could be

00:16:58.959 --> 00:17:04.160
worse though so it works great but of course the

00:17:02.000 --> 00:17:09.520
million dollar question is how much does it cost and when i say a thousand

00:17:06.160 --> 00:17:12.079
dollars with no drives so no ssds not

00:17:09.520 --> 00:17:16.880
even the usb to boot on radoff of that sounds like a lot of money but when

00:17:14.240 --> 00:17:20.319
you compare it to an off-the-shelf nas you would be paying more than a thousand

00:17:18.480 --> 00:17:25.679
dollars for one with just eight bays and it might have specs that

00:17:22.959 --> 00:17:31.039
are much worse than this one whereas we've got a six core processor 16 gigs

00:17:28.480 --> 00:17:36.799
of RAM 10 gigabit networking 20 hard drives two m.2s and two more SATA drives

00:17:34.720 --> 00:17:41.840
just comes down to what software works best for us so whether you choose unread

00:17:39.120 --> 00:17:45.200
freenas proxmox or whatever else floats your boat

00:17:42.799 --> 00:17:49.120
this is a great starting point if you're a starting out editor and you want to

00:17:46.960 --> 00:17:54.960
work with 4k footage or apparently even 8k even if you have a small team

00:17:52.720 --> 00:17:58.720
speaking of having a small team guys this video is brought to you by

00:17:56.400 --> 00:18:03.200
freshbooks freshbooks is the accounting solution for you and your small team

00:18:01.200 --> 00:18:07.039
freshbooks makes it easier to focus on your business instead of on complicated

00:18:05.280 --> 00:18:11.200
accounting software it's designed to be simple and intuitive and you can

00:18:08.559 --> 00:18:14.799
automate tasks like invoicing organizing expenses tracking your time and

00:18:13.039 --> 00:18:18.320
following up and the best part is everything is stored in the cloud so you

00:18:16.240 --> 00:18:22.640
can easily switch between your pc and your mobile device whether it's Android

00:18:20.160 --> 00:18:27.200
or iOS start your 30 day free trial right now at freshbooks.com

00:18:24.640 --> 00:18:31.679
tech tips pricing starts at just 15 a month with the 25 a month tier handling

00:18:29.440 --> 00:18:35.200
up to 50 billable clients so thanks for watching guys if you liked

00:18:33.200 --> 00:18:39.520
this video maybe check out our budget 4k video editing workstation it is a

00:18:36.720 --> 00:18:43.120
perfect companion for our budget 4k editing nas

00:18:41.280 --> 00:18:46.720
i mean that's what it's all about right getting work done keeping all your files

00:18:44.960 --> 00:18:49.360
organized in one place getting everybody access