WEBVTT

00:00:03.360 --> 00:00:07.440
So first question, what does
Bard Bivou(m)acs mean? Good question.

00:00:07.440 --> 00:00:10.800
In one version of my talk, I spent too
long explaining it,

00:00:10.800 --> 00:00:14.559
and decided to cut it out.

00:00:14.559 --> 00:00:20.960
It's basically a bad pun on band camp.

00:00:20.960 --> 00:00:22.480
A bivouac--I don't even know if I'm

00:00:22.480 --> 00:00:25.199
pronouncing that correctly--it's like

00:00:25.199 --> 00:00:29.199
a tent or a camp that you put up hastily,

00:00:29.199 --> 00:00:32.239
and a bard is a musician, of course.

00:00:32.239 --> 00:00:36.480
Yeah, I don't know. I like puns. I'm a dad.

00:00:36.480 --> 00:00:40.960
That's the best I could come up with.

00:00:40.960 --> 00:00:42.879
I'll probably find a different name for

00:00:42.879 --> 00:00:45.039
it but I liked that "bivoaucs,"

00:00:45.039 --> 00:00:48.719
if you stick an m in there, it becomes
Bivou(m)acs.

00:00:48.719 --> 00:01:00.160
It's kind of like editor macros for
generating some HTML.

00:01:00.160 --> 00:01:07.782
Yes, it is confusing, chatting on IRC at
the same time. Great question.

00:01:07.782 --> 00:01:11.398
(Amin: Grant, so right now, you're
sharing your screen.

00:01:11.398 --> 00:01:14.479
Are you planning on showing something
with it, or for example,

00:01:14.479 --> 00:01:16.036
should I maximize you?)

00:01:16.036 --> 00:01:20.400
I don't know. I can turn it off for now.
Okay.

00:01:20.400 --> 00:01:22.299
(Amin: You can turn on the webcam.)

00:01:22.299 --> 00:01:22.880
Yeah, okay.

00:01:22.880 --> 00:01:25.694
(Amin: I'll maximize your webcam.)

00:01:25.694 --> 00:01:28.240
Okay, thanks.

00:01:28.240 --> 00:01:30.000
I'll get to the answer for my color

00:01:30.000 --> 00:01:31.360
theme here in a bit in IRC.

00:01:31.360 --> 00:01:35.105
Next question on the Etherpad,

00:01:35.105 --> 00:01:38.479
does this metadata workflow also support

00:01:38.479 --> 00:01:41.360
unsynchronized lyrics within ID3 tags,

00:01:41.360 --> 00:01:42.720
multi-line metadata?

00:01:42.720 --> 00:01:45.920
I don't know, actually.

00:01:45.920 --> 00:01:47.920
It's funny because I was trying out

00:01:47.920 --> 00:01:49.280
different things with metadata,

00:01:49.280 --> 00:01:52.640
and really the biggest thing was to

00:01:52.640 --> 00:01:55.360
figure out how to do mass tag editing.

00:01:55.360 --> 00:01:56.399
And that was like...

00:01:56.399 --> 00:01:59.600
It wasn't very intuitive, like I said,
with EMMS.

00:01:59.600 --> 00:02:03.040
I think EMMS is really great, but its
interface is huge.

00:02:03.040 --> 00:02:07.040
like if you do M-x and type emms,
you get,

00:02:07.040 --> 00:02:10.160
I don't know, 270-some candidates.

00:02:10.160 --> 00:02:13.200
There's a lot of functions going on.

00:02:13.200 --> 00:02:18.879
I basically found the features that I
needed to get this workflow working.

00:02:18.879 --> 00:02:22.160
I would guess that you probably can do
it, and if you don't,

00:02:22.160 --> 00:02:24.026
if you can't do it out of the box,

00:02:24.026 --> 00:02:28.160
I think you could script EMMS
to do that.

00:02:28.160 --> 00:02:33.268
I'd like to know more, and I'm certainly
going to be investigating it.

00:02:33.268 --> 00:02:39.519
I will try and post my findings
somewhere online.

00:02:39.519 --> 00:02:42.080
Is it possible to import batch metadata?

00:02:42.080 --> 00:02:46.496
I'm not sure. I would guess yes is the
answer.

00:02:46.496 --> 00:02:50.712
EMMS can connect to metadata services.

00:02:50.712 --> 00:02:53.040
I haven't done that because I was just

00:02:53.040 --> 00:02:56.959
using audio files that I created myself.

00:02:56.959 --> 00:03:00.165
I know that on the back end, it calls out

00:03:00.165 --> 00:03:02.319
to shell programs for tagging things.

00:03:02.319 --> 00:03:06.165
There's a lot of different options that can
shell out too.

00:03:06.165 --> 00:03:12.239
I was using the vorbis tools to tag the
particular files I was working with.

00:03:12.239 --> 00:03:15.840
You can also use tiny tag, and there's
some other...

00:03:15.840 --> 00:03:17.498
That might be the python library.

00:03:17.498 --> 00:03:20.971
I can't remember. There's two other
libraries that I can shell out to

00:03:20.971 --> 00:03:24.400
for doing metadata.

00:03:24.400 --> 00:03:26.400
My current workflow for tagging music is

00:03:26.400 --> 00:03:29.040
to first apply replay gain in fubar 2000,

00:03:29.040 --> 00:03:31.119
fix egregious mistakes,

00:03:31.119 --> 00:03:35.118
use beats to apply metadata from music
brains or discogs,

00:03:35.118 --> 00:03:38.400
go over remaining albums with fubar 2000
again.

00:03:38.400 --> 00:03:43.280
Is there a chance textual tagging
could allow doing it all in one program?

00:03:43.280 --> 00:03:46.400
Have I experimented with mass tag
update queries?

00:03:46.400 --> 00:03:47.280
I have not.

00:03:47.280 --> 00:03:49.120
Again, I was just doing this workflow,

00:03:49.120 --> 00:03:54.799
taking raw files with no tags and doing that.

00:03:54.799 --> 00:03:58.159
I believe because it calls out to

00:03:58.159 --> 00:04:00.811
the programs in the back end,

00:04:00.811 --> 00:04:03.040
I'm sure you could work that out.

00:04:03.040 --> 00:04:06.159
I think EMMS would benefit from

00:04:06.159 --> 00:04:08.239
having something like that because

00:04:08.239 --> 00:04:11.280
we work with text, and being able

00:04:11.280 --> 00:04:14.000
to use Emacs as a front end for those

00:04:14.000 --> 00:04:16.647
updates would be really fantastic.

00:04:16.647 --> 00:04:18.560
So really, it's just a matter of

00:04:18.560 --> 00:04:22.720
writing the interface to the external tool.

00:04:22.720 --> 00:04:24.560
Is there a link to some info expanding

00:04:24.560 --> 00:04:28.479
philosophy of how to compensate
musicians?

00:04:28.479 --> 00:04:31.199
No, I don't really have a lot of

00:04:31.199 --> 00:04:32.052
philosophy around that.

00:04:32.052 --> 00:04:33.919
I guess the first thing
I could say would be

00:04:33.919 --> 00:04:36.378
something like a universal income.

00:04:36.378 --> 00:04:38.960
I feel like that would solve
a lot of problems,

00:04:38.960 --> 00:04:41.772
if musicians could just be musicians

00:04:41.772 --> 00:04:44.742
and not have to worry about their pay.

00:04:44.742 --> 00:04:46.240
I will think about it more.

00:04:46.240 --> 00:04:52.015
This is one of my first forays into
getting public with some of these ideas,

00:04:52.015 --> 00:04:53.360
so I will try to do more

00:04:53.360 --> 00:04:55.187
and let the community know.

00:04:55.187 --> 00:04:57.199
What Emacs theme am I using?

00:04:57.199 --> 00:05:02.240
Can't remember. It's one of the Kaolin themes.

00:05:02.240 --> 00:05:05.680
I think it was Aurora

00:05:05.680 --> 00:05:09.120
or Bubble Gum, maybe, but the

00:05:09.120 --> 00:05:12.880
Kaolin themes are nice. I recommend them.

00:05:12.880 --> 00:05:16.000
Not using Doom Emacs, Doom mode line though.

00:05:16.000 --> 00:05:17.296
It's very pretty.

00:05:17.296 --> 00:05:20.080
SVG support built into Emacs?

00:05:20.080 --> 00:05:25.520
I'm using Emacs 27.1, and yes, SVG
support is built in.

00:05:25.520 --> 00:05:30.639
I may have had to compile it with some
Cairo support.

00:05:30.639 --> 00:05:33.840
I don't remember for sure.

00:05:33.840 --> 00:05:41.199
But yes, you can even take screenshots
of your Emacs from within Emacs, in SVG.

00:05:41.199 --> 00:05:44.320
It's pretty great.

00:05:44.320 --> 00:05:46.160
I don't know how much more time we have

00:05:46.160 --> 00:05:48.000
left for questions.

00:05:48.000 --> 00:05:52.639
That's most of the things on the etherpad.

00:05:52.639 --> 00:05:54.320
(Amin: I think we have like 10 more minutes to

00:05:54.320 --> 00:05:56.479
catch up with the schedule.

00:05:56.479 --> 00:05:59.120
If there are more questions,

00:05:59.120 --> 00:06:01.919
feel free to answer them.)

00:06:01.919 --> 00:06:05.440
I'll start looking through IRC.

00:06:05.440 --> 00:06:09.680
(Amin: And keep an eye on the pad too.)

00:06:09.680 --> 00:06:12.688
Thank you all for listening

00:06:12.688 --> 00:06:19.440
and for enjoying the talk. I'm glad it
turned out well.

00:06:19.440 --> 00:06:36.000
Awesome. Yeah, it's been fun so far.

00:06:36.000 --> 00:06:40.015
How did I manage? I can post
a snippet of that,

00:06:40.015 --> 00:06:46.319
or actually I can share my screen,
can't I...

00:06:46.319 --> 00:06:49.599
Okay. I actually have it up right here.

00:06:49.599 --> 00:06:53.440
So I think I got this from alphapapa, to
be honest.

00:06:53.440 --> 00:07:00.960
I define screenshot-svg.

00:07:00.960 --> 00:07:04.960
It's an interactive command. Oh yeah,
there's alphapapa.

00:07:04.960 --> 00:07:08.560
Okay, there we go.

00:07:08.560 --> 00:07:13.249
I would like to change this so that I
can get it into the copy-paste buffer

00:07:13.249 --> 00:07:20.560
so I don't have to copy the file in, but
I haven't really hacked on it yet.

00:07:20.560 --> 00:07:24.400
Okay, org heading colors.

00:07:24.400 --> 00:07:26.319
That might be a good question.

00:07:26.319 --> 00:07:33.199
I know, the presentation...

00:07:33.199 --> 00:07:35.520
Sorry, it's hard to think and type at

00:07:35.520 --> 00:07:36.479
the same time.

00:07:36.479 --> 00:07:41.680
Think and talk and type.

00:07:41.680 --> 00:07:45.120
So the presentation is just a

00:07:45.120 --> 00:07:48.960
normal org file, right, so I have my headers,

00:07:48.960 --> 00:07:50.466
and the author--you can even stick

00:07:50.466 --> 00:07:52.560
your email and other headers in there.

00:07:52.560 --> 00:07:57.599
But there's a package called org-tree-slide.

00:07:57.599 --> 00:08:01.440
Whoops, why is it not...

00:08:01.440 --> 00:08:03.618
I must have not required it.

00:08:03.618 --> 00:08:04.594
Good question.

00:08:04.594 --> 00:08:09.599
(Amin: Grant, can you try sharing your
screen maybe?)

00:08:09.599 --> 00:08:13.199
Oh, is it not shared? I'm sorry.

00:08:13.199 --> 00:08:17.039
(Amin: Thank you.)

00:08:17.039 --> 00:08:22.000
There we go, should be coming up.

00:08:22.000 --> 00:08:26.720
(Amin: It's coming up. Yep, we see it.)

00:08:26.720 --> 00:08:38.800
Awesome. All right. Okay. I don't know
why this isn't working.

00:08:38.800 --> 00:08:56.080
It was working.

00:08:56.080 --> 00:09:01.839
Okay, you want to see the screenshot.

00:09:01.839 --> 00:09:06.839
Whoops. Okay, I just took a screenshot.

00:09:06.839 --> 00:09:09.760
So, org-tree-slide.

00:09:09.760 --> 00:09:12.800
I don't know why it's not launching.

00:09:12.800 --> 00:09:16.000
I thought that I had required it, but I
must not have.

00:09:16.000 --> 00:09:30.959
Maybe I'll try. Okay.

00:09:30.959 --> 00:09:34.560
So there we go. So org-tree-slide is a
way that basically uses

00:09:34.560 --> 00:09:38.880
narrowing and some kind of font tricks to...

00:09:38.880 --> 00:09:42.640
it changes your titles
or your metadata into

00:09:42.640 --> 00:09:44.560
this banner for the title here,

00:09:44.560 --> 00:09:46.560
and it automatically sets the
faces for you.

00:09:46.560 --> 00:09:53.938
You can customize that, of course. And
then, as you go through the Org file,

00:09:53.938 --> 00:09:59.600
you get these kind of nice animations
and--

00:09:59.600 --> 00:10:04.160
what's it called--breadcrumbs up at the top.

00:10:04.160 --> 00:10:06.399
So org-tree-slide. I highly recommend it.

00:10:06.399 --> 00:10:10.024
It's really nice because you can give
your presentation and practice it,

00:10:10.024 --> 00:10:12.560
and while you're practicing it, you can
edit things as well,

00:10:12.560 --> 00:10:16.160
because it's still just an Org document
using narrowing, you know.

00:10:16.160 --> 00:10:20.079
It doesn't actually change anything.

00:10:20.079 --> 00:10:24.079
Definitely recommend org-tree-slide mode.

00:10:24.079 --> 00:10:29.760
Okay, let's see, what else...

00:10:29.760 --> 00:10:32.880
Share my screen to demo. Oh, that's the SVG.

00:10:32.880 --> 00:10:39.519
Let's see.

00:10:39.519 --> 00:10:41.279
Okay, so I don't know if you can see this now,

00:10:41.279 --> 00:10:49.360
but I'm actually viewing the SVG
screenshot that I took with Emacs.

00:10:49.360 --> 00:10:52.720
See here's the source of it. So Emacs
made that.

00:10:52.720 --> 00:10:58.160
And here's the image.

00:10:58.160 --> 00:11:01.570
It's cool because you can even do it
again and again,

00:11:01.570 --> 00:11:05.360
and open more screenshots of
screenshots.

00:11:05.360 --> 00:11:14.880
Yeah, definitely Emacsception.
Fun stuff.

00:11:14.880 --> 00:11:18.079
Anything else in chat?

00:11:18.079 --> 00:11:20.160
Heading colors? Oh, yeah. I talked about the

00:11:20.160 --> 00:11:24.800
themes. This is another Kaolin theme.

00:11:24.800 --> 00:11:34.959
I think the one in the talk was
maybe this one, Aurora.

00:11:34.959 --> 00:11:36.560
Oh, here, there's something funny when

00:11:36.560 --> 00:11:37.785
you start org-tree-slide

00:11:37.785 --> 00:11:38.880
with a different theme.

00:11:38.880 --> 00:11:41.823
This top header bar gets the faces

00:11:41.823 --> 00:11:43.395
from that previous theme.

00:11:43.395 --> 00:11:47.760
I have not figured out how to
fix that yet.

00:11:47.760 --> 00:11:49.200
Did I have to compile to get the

00:11:49.200 --> 00:11:51.120
screenshot? I think maybe I did.

00:11:51.120 --> 00:11:54.480
Yes, if I'm remembering correctly.

00:11:54.480 --> 00:11:58.399
I got Emacs 27. I'm not on a Mac.

00:11:58.399 --> 00:12:01.424
I saw alphapapa's comment on reddit,

00:12:01.424 --> 00:12:08.839
and then I recompiled it with Cairo
support.

00:12:08.839 --> 00:12:18.000
Yes.

00:12:18.000 --> 00:12:21.920
Okay, lots of good conversation on here.

00:12:21.920 --> 00:12:25.839
Yep, I have like one or two more minutes.

00:12:25.839 --> 00:12:34.240
Okay. I guess while I'm here, I might as

00:12:34.240 --> 00:12:36.993
well say thank you to the organizers.

00:12:36.993 --> 00:12:40.320
I really appreciate everybody's
work on this.

00:12:40.320 --> 00:12:42.720
It's fun to be a part of this community.

00:12:42.720 --> 00:12:45.929
I'm enjoying the other talks I've seen
so far today,

00:12:45.929 --> 00:12:48.560
and I'm looking forward to
to the rest.

00:12:48.560 --> 00:12:53.570
It's really interesting, just from being
on Emacs in IRC for a few months,

00:12:53.570 --> 00:12:54.720
I've already connected

00:12:54.720 --> 00:12:56.959
with a lot of interesting people

00:12:56.959 --> 00:13:04.079
and have a lot of cool connections
already.

00:13:04.079 --> 00:13:07.519
(Amin: Thank you for being a part of the
community, Grant.)

00:13:07.519 --> 00:13:08.883
That's good to be here.

00:13:08.883 --> 00:13:16.560
I have another talk tomorrow as well.

00:13:16.560 --> 00:13:18.399
Oh, thanks for everyone in the Etherpad

00:13:18.399 --> 00:13:21.680
for putting more comments on these
questions here

00:13:21.680 --> 00:13:29.360
and taking the notes.

00:13:29.360 --> 00:13:31.680
(Amin: I think that's about all the time

00:13:31.680 --> 00:13:33.040
that we have for the Q&A.

00:13:33.040 --> 00:13:36.720
Okay. Thank you again so much, Grant,

00:13:36.720 --> 00:13:39.920
for your awesome talk and for popping in
for questions.)

00:13:39.920 --> 00:13:46.800
Yeah, thanks again for hosting. See you
later. Cheers!