14 videos 📅 2024-05-06 08:00:00 America/Creston
39:11
2024-05-06 08:57:50
3:11:28
2024-05-06 10:30:19
24:39
2024-05-07 07:20:20
19:49
2024-05-07 08:03:25
1:14:35
2024-05-07 08:35:13
15:41
2024-05-07 10:06:25
38:33
2024-05-07 10:37:03
2:48
2024-05-07 11:19:01
59:37
2024-05-07 11:33:56
6:10
2024-05-07 14:55:25
39:40
2024-05-07 15:02:44
9:45
2024-05-08 06:44:21
29:27
2024-05-08 08:09:24
2:51:40
2024-05-08 12:09:24

Visit the Apache Nifi - GROUP 1 course recordings page

                WEBVTT

00:00:00.000 --> 00:00:03.240
Alright, we'll just go around the room. Sean, how are you doing?

00:00:04.080 --> 00:00:10.440
Mostly okay. I was kind of doing some catch-up from this morning still too, but I got it.

00:00:11.060 --> 00:00:18.020
Converting all the CSDs into JSON and putting them into a separate directory.

00:00:19.120 --> 00:00:22.620
And I was just trying to figure out how to merge them right now.

00:00:23.100 --> 00:00:26.300
Oh, very nice. You can pick them back up.

00:00:30.180 --> 00:00:34.120
Instead of writing the JSON, you might want to just send it to the next processor.

00:00:34.300 --> 00:00:37.660
But if you want to write it to disk and then turn around and pick those back up

00:00:38.580 --> 00:00:44.420
and then look at what Pedro and I were just going over, the EvaluateJSON processor,

00:00:44.420 --> 00:00:54.180
you can then... Okay, okay. So I think you're very close. You've got the CSVs and the JSON all

00:00:54.180 --> 00:01:02.520
aligned. It's now just the final calculations. So you're very close. Okay, good deal. Any

00:01:02.520 --> 00:01:04.760
questions I can answer? No, I don't think so.

00:01:06.400 --> 00:01:09.820
Okay. Alright. How about Aaron? Aaron, how are you doing?

00:01:11.320 --> 00:01:18.580
I'm going. Are you in the room with everyone else?

00:01:19.320 --> 00:01:26.040
Yeah. I am very surprised that the room is not complete. I figured you guys would be just

00:01:26.040 --> 00:01:30.380
sharing information constantly. So we are.

00:01:30.380 --> 00:01:35.700
Okay, good. But as far as we can get is making sure they're all in JSON format.

00:01:35.700 --> 00:01:40.120
As far as we've got, well, some of us are best with merging right now.

00:01:40.680 --> 00:01:48.260
Okay, okay. So again, you may want to look at the EvaluateJSON processor. Now that you have

00:01:48.260 --> 00:01:57.140
everything in JSON, you can write it to disk. If that's easier, pick it back up and look at

00:01:57.140 --> 00:02:03.940
that and look at taking those JSON values and pushing them up as an attribute. But it's

00:02:03.940 --> 00:02:07.600
funny as I was thinking, I was like, you know, there's three, four, five people in

00:02:07.600 --> 00:02:12.640
the same room. Like it would be so easy just to copy off of each other and be done.

00:02:13.560 --> 00:02:17.300
Yeah, we're trying. No, there's no, you know,

00:02:17.300 --> 00:02:20.460
nobody's gonna get dinged for helping your buddy, right?

00:02:22.460 --> 00:02:27.900
Okay, so who else is in the room? We have Brett in the room, I think.

00:02:27.900 --> 00:02:34.520
No, Alyssa. Okay, let's go to Alyssa. Alyssa, how are things with you?

00:02:36.780 --> 00:02:43.760
I got to the merge JSON. Okay.

00:02:44.860 --> 00:02:52.680
I haven't looked into the EvaluateJSON processor yet, but I basically merged all the files

00:02:52.680 --> 00:02:57.700
together. It doesn't look good, but they're merged.

00:02:58.300 --> 00:03:06.080
Don't worry. If you want to beautify the JSON, do remember we have, you know,

00:03:06.080 --> 00:03:13.580
if you bring down processor and you start typing JSON, there is numerous JSON processors.

00:03:14.000 --> 00:03:21.280
Some of those are used to beautify JSON. So, you know, I think it's, go down just

00:03:21.280 --> 00:03:30.220
a little bit. There's the flatten JSON that helps. EvaluateJSON is one that you will probably use.

00:03:30.440 --> 00:03:40.740
Scroll on down. Keep going. There's a jolt transform JSON. So, I'm surprised no one's

00:03:40.740 --> 00:03:46.660
kind of looked at that processor yet because you can actually write a jolt transformation

00:03:46.660 --> 00:03:55.880
and probably accomplish this task in four or five processors. So, you know, definitely take a look

00:03:55.880 --> 00:04:03.100
at the jolt transform JSON. Take a look at the EvaluateJSON path. I think you're getting close,

00:04:03.100 --> 00:04:12.200
right? So, yeah. I was thinking, you know, somebody in that room is going to write a jolt

00:04:12.200 --> 00:04:18.260
transformer and just have all this working within two or three processors. But no,

00:04:19.040 --> 00:04:24.680
I think you're getting close. Any questions I can answer right now? I think you're on a good

00:04:24.680 --> 00:04:32.640
path, but I just want to check in and see. Yeah, I think we all just need to play around

00:04:32.640 --> 00:04:43.600
with it a bit more. Like, we didn't find all the processors. There's over 300 processors. And so,

00:04:44.980 --> 00:04:50.880
make sure when you go into your processors, look for JSON processors. Look for CSV processors.

00:04:51.440 --> 00:04:56.760
Look for the items that you're trying to do. And you'll start narrowing down your list.

00:04:56.760 --> 00:05:02.840
Even as someone like myself that is extremely experienced at building data flows and

00:05:04.060 --> 00:05:09.340
9.5 processors and those, I will, you know, when I go look at, you know, when I have a

00:05:09.340 --> 00:05:15.320
problem, I'll go to my processors. I'll do a keyword like JSON. Let me see what's out there.

00:05:15.340 --> 00:05:21.240
Let me see what's available. You know, what are some of the capabilities? I keep the

00:05:21.880 --> 00:05:31.560
9.5 documentation up. And that way it has the documentation as well. One tidbit of information

00:05:31.560 --> 00:05:39.320
on the evaluate JSON path. You're only able to extract one field if you're trying to do a

00:05:39.320 --> 00:05:49.960
flow file content. So make sure you have flow file attribute so you can extract all the

00:05:49.960 --> 00:05:57.720
processor. But I think you're getting close. I would definitely look at the evaluate JSON path

00:05:57.720 --> 00:06:03.960
and they don't transform depending on your skill level and your skill set. You know,

00:06:03.960 --> 00:06:09.020
you might be able to solve some of this pretty quickly. Any questions that I can answer for

00:06:10.880 --> 00:06:20.000
Lisa? No, I would just need more time with her. Okay. Like I said, you know, take all the

00:06:20.000 --> 00:06:27.360
time. Like training stops at five, but I don't stop. I mean, I keep going, whatever it is to

00:06:27.360 --> 00:06:33.680
help support you all. So, you know, just keep going. What we'll do is we'll start in the

00:06:34.460 --> 00:06:43.100
flows. And even if you do not complete your flow, you know, if you at least have, you know,

00:06:43.260 --> 00:06:49.840
here's how I want to design this and here's how I think this might work. I'll take that as a

00:06:49.840 --> 00:06:55.680
answer as well. I would like to see this completed. But also, you know, we have

00:06:55.680 --> 00:07:01.480
different mix of technologies and things like that in the room. So, you know, it's

00:07:01.480 --> 00:07:08.800
if we just take it complete. So, okay, good. Who else do we have in the room with you all?

00:07:08.980 --> 00:07:17.060
Just me, Amanda. I didn't really get far. I just need to play around a little more with it.

00:07:17.420 --> 00:07:23.440
Okay. Is there anything really like you're hung up on or stumping you?

00:07:24.900 --> 00:07:28.340
I just don't know how a lot of these processes work, honestly.

00:07:28.840 --> 00:07:32.100
Okay. Because at first, like one of them, I was like trying to

00:07:32.640 --> 00:07:37.780
change the data and then trying to split it by like commons with these on attribute

00:07:37.780 --> 00:07:40.980
that I try to split the text, but that didn't work. I did. I tried.

00:07:44.680 --> 00:07:53.320
No worries. No worries. So for you, you want to get the weather data. If you, again,

00:07:53.320 --> 00:08:01.960
if you want to solve this very pretty quickly, reuse the CSV processors that we did for the

00:08:01.960 --> 00:08:08.260
previous exercise. And then you can actually write that JSON back to disk if you want

00:08:08.260 --> 00:08:13.600
and then have a new processor that grabs all your JSON. So it would include that station,

00:08:13.680 --> 00:08:18.540
that third station ID. And then you can bring all your JSON in together.

00:08:19.260 --> 00:08:25.500
You can evaluate the JSON path, extract the data, and then you can manipulate it using

00:08:26.020 --> 00:08:33.900
attributes. So just play around with it. If you don't get complete, no big deal,

00:08:35.420 --> 00:08:45.180
we can work on it. If you need to reference the previous exercise, you can upload that.

00:08:46.090 --> 00:08:51.850
It's in that zip file. I just didn't advertise it at first because I wanted to walk us through the

00:08:52.650 --> 00:08:59.970
flow itself. But you're able to bring down a process group, import that flow, and it

00:08:59.970 --> 00:09:04.590
should work for you. So if you need to reference the previous flow and even if you

00:09:04.590 --> 00:09:09.450
didn't get it finished, you can import it and it's complete. And that should give you some

00:09:10.370 --> 00:09:17.530
helpful tips on processing that CSV that you get. Any questions Amanda I can answer right now?

00:09:18.590 --> 00:09:24.810
Oh, no. I'm good. Okay. Well, try your best. And like I said, any questions, just

00:09:24.810 --> 00:09:28.950
feel free to reach out. And is there anybody else in the room with you?

00:09:28.950 --> 00:09:39.830
Hi, I'm Ben. I hope you like to scroll. Who was that, Cody? Ben. Oh, yeah. I was going to say

00:09:39.830 --> 00:09:47.670
Ben should be in there. Do I like to scroll? Oh, Lord. What's spider web? Oh, my God.

00:09:48.650 --> 00:09:58.010
Did you read Charlotte's Web before this? Well, what's the next thing I have to do?

00:09:59.390 --> 00:10:02.470
I have no clue where to start. Is this like a maze?

00:10:06.190 --> 00:10:11.370
Top left. So you're getting the source file. Oh, you identified the mom type.

00:10:17.450 --> 00:10:25.070
All right. So if it is a JSON document, you're sending it to write JSON to work. If it is a

00:10:25.070 --> 00:10:31.770
CSV, you're converting the record, and you're putting the file to JSON, just like we were

00:10:31.770 --> 00:10:37.790
doing on the first, you know, the previous exercise. And then you're pushing everything

00:10:37.790 --> 00:10:48.670
to a funnel and logging. Okay, so what's on the right? So I see your work folder.

00:10:50.450 --> 00:11:01.250
Okay, so it gets work files. Oh, okay. And then you merge JSON data, rename the file,

00:11:01.810 --> 00:11:10.910
you put the file again. Okay, perfect. Well, the nice thing is, I think you're very close

00:11:10.910 --> 00:11:19.390
on normalizing all of your data. Okay, perfect. So look at picking that back up.

00:11:20.010 --> 00:11:28.110
Might as well put a few more files on there. You don't have enough. Go ahead and get the file

00:11:28.830 --> 00:11:39.810
and take a look at the evaluate JSON or the flatten JSON processor, the evaluate JSON processor,

00:11:39.810 --> 00:11:46.790
the jolt transformation processor. I bet if you were to Google, I want to jolt transform

00:11:46.790 --> 00:11:55.030
a JSON document, you will see tons of great examples. Okay. So I think you're very,

00:11:55.050 --> 00:12:00.490
very close. Do you have any questions I can answer right now? And if not,

00:12:00.490 --> 00:12:10.230
we will go over this in the morning. Okay. Thanks, Ben. That is a spider web. Tyler,

00:12:12.130 --> 00:12:18.150
how are things going with you? Oh, wow. Wow.

00:12:19.870 --> 00:12:26.410
Just in just the files, I check the MIME type, my update to the schema attribute,

00:12:27.090 --> 00:12:36.250
route on attributes. Otherwise, it will convert to JSON. Wow. That's nice. Nice and clean.

00:12:38.070 --> 00:12:43.230
Then it queries the records to do the aggregations and pushes out the aggregations here,

00:12:43.350 --> 00:12:50.570
but I haven't branched that part out yet. And then this query record does the warning for

00:12:50.860 --> 00:12:58.700
speed. I haven't added any other warnings yet. And then I have it splitting the records and then

00:12:59.840 --> 00:13:07.380
extracting out the date as an attribute and then I'll merge it all from the same date

00:13:07.380 --> 00:13:13.740
to aggregate them for the reporting. And then I haven't fleshed that out yet.

00:13:14.700 --> 00:13:24.700
Oh, good Lord. You're almost done. You nailed it. And I was very surprised to see query record,

00:13:25.140 --> 00:13:31.820
split record. I really like that approach because that approach is a data engineering

00:13:32.420 --> 00:13:38.680
thought process where you can then take this and build some of the reusable components

00:13:38.680 --> 00:13:47.240
and process data like this in the future. I think you're very, very close to being complete.

00:13:47.900 --> 00:13:52.720
Any questions that you may have that I can answer? Any major roadblocks in your way

00:13:52.720 --> 00:13:57.100
that I can answer? But overall, great job. I don't think so.

00:13:57.620 --> 00:14:04.740
I think you're very, very, very close. So great job. If you need anything, let me know,

00:14:04.740 --> 00:14:09.300
but wow. Nicely done. Thank you.

00:14:10.440 --> 00:14:18.240
All right. Brett. I think Brett's done.

00:14:20.940 --> 00:14:22.980
No. Can you hear me? I can.

00:14:24.060 --> 00:14:28.820
So I started one way and then I switched and I started using the evaluate JSON.

00:14:28.820 --> 00:14:36.660
Okay. So I have for the native JSON file in there, I'm able to grab the

00:14:39.280 --> 00:14:45.860
file and get all the attributes for all the elements in there. So then now I'm just,

00:14:47.000 --> 00:14:58.800
because I split, I had two different paths for CSV JSON. The CSV path was the old one that we

00:14:59.360 --> 00:15:04.640
tried to go to the success to do the same thing. I haven't tried that yet.

00:15:05.120 --> 00:15:12.560
Okay. It may require a different evaluate JSON processor just to, you know, depending on

00:15:12.560 --> 00:15:20.080
if the JSON is exactly the same or not. But you're extremely close and good job using

00:15:20.080 --> 00:15:28.780
the evaluate JSON processor and pulling all of that data out as an attribute. You have it all

00:15:28.780 --> 00:15:35.540
of the capabilities you have, you know, now with that data. Any questions I can answer?

00:15:35.620 --> 00:15:40.840
This is, you know, you and Tyler are just really rocking it. Any questions I can answer?

00:15:42.720 --> 00:15:46.160
No, I think it's making sense. Okay. Perfect. I think you're very,

00:15:46.160 --> 00:15:50.720
very close. So I've been struggling with the canvas and the latency that we have though.

00:15:50.720 --> 00:16:01.400
You and me both. If it was my way, we would have a different environment. But I am as well. I just

00:16:01.400 --> 00:16:07.100
got a warning that I'm 300 milliseconds. And, you know, I'm like, come on now.

00:16:08.560 --> 00:16:13.760
But no, I get it. I get it. Okay. Well, if you have any questions, let me know. Great job.

00:16:14.280 --> 00:16:18.380
We'll go over this in the morning, but I think you're extremely close.

00:16:22.600 --> 00:16:24.880
All right. I think we went over

00:16:28.620 --> 00:16:31.740
Alissa and Amanda. Randy. How are things going, Randy?

00:16:36.280 --> 00:16:41.800
Well, that doesn't sound good. Well, it sounds like Randy's allergies are really getting to him.

00:16:41.820 --> 00:16:46.400
It is that time of season. So we'll come back. Randy, if you have any questions or anything,

00:16:46.400 --> 00:16:53.640
let me know. But I'll check in on your flow when I can see it and see how far you've gotten.

00:16:55.680 --> 00:17:02.160
Okay. Let's see. Who did I miss? Erin, I think I got you, but did I miss you?

00:17:03.340 --> 00:17:07.780
No, you looked at Erin's earlier. That's what I thought. It's confusing

00:17:07.780 --> 00:17:14.440
me with somebody in the room. And then, so did I miss anyone? And if I did,

00:17:14.440 --> 00:17:23.900
let me know. If not, does anyone have any questions I can answer right now? Okay. So

00:17:25.540 --> 00:17:32.860
it's about 30 minutes after, 22 minutes after I am going to call it. It's almost 5.30 my time.

00:17:33.500 --> 00:17:41.320
We will start off tomorrow morning going through these flows. We have enough time in the morning

00:17:41.320 --> 00:17:48.440
to spend 30 minutes to an hour going through these or updating them or finishing them up.

00:17:49.240 --> 00:17:55.680
So do your best you can. Again, if you do not get complete, what I'm looking for is just

00:17:55.680 --> 00:18:02.420
an explanation, a story on how you're planning to design your data flow and some of the things

00:18:02.420 --> 00:18:08.380
there. Little tips. I would try to get it organized and get some of the labels and the

00:18:08.380 --> 00:18:16.100
stuff that we went over. You know, on the canvas as well. You know, beautify the flow.

00:18:17.520 --> 00:18:23.660
Try not to read Charlotte's Web tonight, Ben. And, you know, have a great evening.

00:18:23.700 --> 00:18:28.900
If you have any additional questions, you know, speak now. If not, I'm going to go

00:18:28.900 --> 00:18:35.820
ahead and leave the meeting. But I will also check in on everyone's desktop later tonight

00:18:35.820 --> 00:18:43.440
because I have Minify and Notify processor development to go over tomorrow. And I need

00:18:43.440 --> 00:18:51.480
to make sure you all have the files for that. Awesome. Well, thank you all very, very much.

00:18:51.900 --> 00:18:58.060
Continue working as you as you want and we will pick up tomorrow morning. I will see you all

00:18:58.060 --> 00:18:59.340
then. Have a good evening.

00:21:29.160 --> 00:21:35.180
I'm saying that I am not an expert, but I am the mother of a trans child.

00:21:35.520 --> 00:21:41.320
And the other thing is that I love the sensations of medication for the trans community,

00:21:41.680 --> 00:21:45.820
specifically mine or someone else's. So rolling that in brief, all I had ready

00:21:45.820 --> 00:21:52.520
as for me, started developing super light in fourth grade. And you could tell that she

00:21:52.520 --> 00:21:59.020
was sitting on her skin and it was warm over her. But here's the thing. By seventh grade,

00:21:59.300 --> 00:22:05.660
we all caught up and learned and enjoyed the best for childhood. My school told me so.

00:22:06.100 --> 00:22:12.420
So the next thing to learn and trans kid is that we don't have the same luxury of

00:22:12.420 --> 00:22:18.860
everyone else catching up. But everyone else is doing the same as us. So the anxiety

00:22:18.860 --> 00:22:27.300
level that is created by not allowing children to take these medications and take care of

00:22:27.300 --> 00:22:34.820
and grow into themselves is so strong that we actually may be hurting certain children.

00:22:49.000 --> 00:22:57.740
Existing governments say to theirs, the sexism of an eternal and pressing death

00:22:57.740 --> 00:23:03.360
chain tradition for the rest of their life. And if you try to hand-ize people into

00:23:03.360 --> 00:23:08.120
making them believe that they are happy in this death, you think they're successful?

00:23:10.220 --> 00:23:15.080
I describe to you just there exactly what is going on in the world today.

00:23:18.120 --> 00:23:21.700
Yes, there's the scene. There's the scene.

00:24:15.080 --> 00:24:18.760
I'm between myself, my closest friends.

00:24:19.080 --> 00:24:20.400
And then I can't draw a straight line.

00:24:20.720 --> 00:24:21.880
It seems kind of cool.

00:24:22.820 --> 00:24:24.100
No, of course I am.

00:24:24.180 --> 00:24:25.920
So I'm going to need you for a script.

00:24:26.140 --> 00:24:28.540
I've got 24 hours and I'm going to tell you something.

00:24:28.700 --> 00:24:30.640
It was a dangerous job every day.

00:24:31.020 --> 00:24:32.040
So yesterday's...

00:24:32.040 --> 00:24:33.000
I think you got it.

00:24:33.940 --> 00:24:34.760
...liberal woman.

00:24:36.120 --> 00:24:38.240
Look, nobody's coming for your support.

00:24:38.840 --> 00:24:42.920
Okay, what we really want is common sense of what's in control.

00:24:43.540 --> 00:24:44.300
That's this.

00:24:45.680 --> 00:24:46.560
It's hard.

00:24:47.460 --> 00:24:49.180
To make a motion for no reason at all.

00:24:49.360 --> 00:24:53.960
And doing it on this place where it's cold out, mostly green, roughly, is not a good idea.

00:24:54.120 --> 00:24:56.360
There's also a problem doing it when it's too hot outside.

00:24:56.660 --> 00:25:00.140
Every time that's happening, you're rising pretty above 100 degrees, for sure.

00:25:00.580 --> 00:25:02.880
For all the work that you're doing at Society of Iowa, it is a good idea.

00:25:03.240 --> 00:25:04.160
Yeah, of course.

00:25:07.560 --> 00:25:08.440
That's it.

00:25:08.440 --> 00:25:09.160
Okay.

00:25:12.360 --> 00:25:16.520
And the father of you would do the same.

00:25:29.820 --> 00:25:34.340
That sailor from Stormy Daniels has been on the witness stand for a couple hours.

00:25:35.100 --> 00:25:42.040
Ladies and gentlemen, as you're all about to snap on water, I just wanted to share a new sock set I just bought for you guys.

00:25:42.420 --> 00:25:46.780
It's a pretty good size, and I'm pretty happy to upload it.

00:25:47.160 --> 00:25:57.900
It goes all the way, it starts at 26 inches, and then it goes 26 by 20s, and then 20 by 10 degrees, and 26 by 10.

00:25:57.900 --> 00:25:59.880
It's also better to be able to move stuff.

00:26:00.020 --> 00:26:02.640
I would say it's like 300 to 500 meters.

00:26:02.760 --> 00:26:04.720
All you have to do is take it on in 500 meters.

00:26:05.080 --> 00:26:06.060
It's a pretty good size.

00:26:07.420 --> 00:26:14.500
So, I mean, you could probably set it up to like an adapter, if you wanted to use this for any traction or something.

00:26:15.020 --> 00:26:16.140
But pretty good stuff.

00:26:16.740 --> 00:26:21.380
Here are the top ten largest churches in the United States based on attendance, per week.

00:26:21.540 --> 00:26:27.240
According to AppReach 100 data, at number 10 is Fellowship Church in Great Valley, Texas.

00:26:27.240 --> 00:26:32.540
When I popped the hood of this 2011 Honda Odyssey, a lot of y'all said that it was fake.

00:26:32.980 --> 00:26:35.880
Those of you that knew it was real just wanted to hear it out.

00:26:36.200 --> 00:26:38.500
We're going to cover both topics right now.

00:26:38.620 --> 00:26:45.220
We're going to listen to this thing out, and we're going to take a better look at the hood and back story for those of y'all that missed it.

00:26:45.380 --> 00:26:48.880
We've only got a little bit of time left, and I did, because I think it was my game.

00:26:49.200 --> 00:26:50.160
I'll do it at number three.

00:26:50.340 --> 00:26:51.140
First, I'm going to turn it on.

00:26:51.720 --> 00:26:52.100
I'm going to turn it on.

00:27:22.100 --> 00:27:24.100
We're going to turn on number three and number four.

00:27:24.960 --> 00:27:26.060
I'm going to turn it on.

00:27:26.420 --> 00:27:28.100
I'm going to turn it on.

00:27:30.180 --> 00:27:30.740
We're going to turn it on.

00:27:30.740 --> 00:27:31.700
Oh, jeez.

00:27:32.540 --> 00:27:34.200
Oh, jeez.

00:27:34.200 --> 00:27:36.200
We're going to turn it on.

00:27:36.220 --> 00:27:37.460
Our head is in lock.

00:27:47.980 --> 00:27:56.960
I can't even do that for all of you, you have the freedom to do whatever you want.

00:28:01.820 --> 00:28:05.320
Give me all the sound into that song on my head.

00:28:05.320 --> 00:28:13.040
Give me all the sound into that song on my head.

00:28:13.300 --> 00:28:16.680
Give me all the sound into that song on my head.

00:28:16.680 --> 00:28:23.140
Give me all the sound into that song on my head.

00:28:23.140 --> 00:28:24.880
Give me all the sound into that song on my head.

00:28:24.880 --> 00:28:35.980
Give me all the sound into that song on my head.

00:28:36.880 --> 00:28:38.060
Give me all the sound into that song on my head.

00:29:05.240 --> 00:29:08.040
Give me all the sound into that song on my head.

00:29:16.140 --> 00:29:30.080
Give me all the sound into that song on my head.

00:29:34.440 --> 00:29:37.180
Give me all the sound into that song on my head.

00:29:37.180 --> 00:29:40.740
Give me all the sound into that song on my head.

00:29:41.960 --> 00:29:45.760
Give me all the sound into that song on my head.

00:29:45.760 --> 00:30:15.740
Give me all the sound into that song on my head.

00:30:17.620 --> 00:30:28.300
Give me all the sound into that song on my head.

00:30:30.980 --> 00:30:38.740
Give me all the sound into that song on my head.

00:31:07.580 --> 00:31:08.520
Give me all the sound into that song on my head.

00:31:11.820 --> 00:31:38.360
Give me all the sound into that song on my head.

00:31:40.840 --> 00:31:58.360
Give me all the sound into that song on my head.

00:31:58.360 --> 00:32:26.980
Give me all the sound into that song on my head.

00:32:26.980 --> 00:32:56.740
Give me all the sound into that song on my head.

00:32:56.740 --> 00:33:03.080
Give me all the sound into that song on my head.

00:33:03.080 --> 00:33:32.880
Give me all the sound into that song on my head.

00:33:32.880 --> 00:33:38.660
Give me all the sound into that song on my head.

00:33:38.660 --> 00:33:50.780
Give me all the sound into that song on my head.

00:33:50.780 --> 00:33:59.760
Give me all the sound into that song on my head.

00:34:06.640 --> 00:34:13.680
Give me all the sound into that song on my head.

00:34:13.680 --> 00:34:43.660
Give me all the sound into that song on my head.

00:34:46.340 --> 00:35:11.320
Give me all the sound into that song on my head.

00:35:21.820 --> 00:35:41.300
Give me all the sound into that song on my head.

00:35:41.300 --> 00:35:48.340
Give me all the sound into that song on my head.

00:36:08.740 --> 00:36:18.320
Give me all the sound into that song on my head.

00:36:18.320 --> 00:36:46.220
Give me all the sound into that song on my head.

00:36:46.220 --> 00:36:48.420
Give me all the sound into that song on my head.

00:36:48.420 --> 00:37:09.800
Give me all the sound into that song on my head.

00:37:09.800 --> 00:37:27.940
Give me all the sound into that song on my head.

00:37:27.940 --> 00:37:57.700
Give me all the sound into that song on my head.

00:37:57.700 --> 00:38:03.560
Give me all the sound into that song on my head.

00:38:03.560 --> 00:38:28.040
Give me all the sound into that song on my head.

00:38:28.040 --> 00:38:37.620
Give me all the sound into that song on my head.

00:39:04.800 --> 00:39:07.600
Give me all the sound into that song on my head.

00:39:36.480 --> 00:39:37.340
Give me all the sound into that song on my head.

00:39:37.340 --> 00:39:40.260
Give me all the sound into that song on my head.