The Worst Case Bug - The Sudden Loss of Personal Data

[tzurby]

Below you find a draft of an article which describes, to a broader audience, what I experienced and what I call the Worst Case Bug (for Personal Computers - large technical applications can have bugs way more severe, of course, cf. Wikipedia: Software bug).

 

Any comments are welcome. I wonder if anyone else experienced this bug.

 

Excuse me for the faults. My mother tongue is German.

 

The Worst Case Bug - Apple, "Logic" and the Sudden Loss of Personal Data

 

There are many bugs around, most of them are very annoying, but hardly ever they destroy personal data. And if so, the bug might affect the document one is currently working on. That's bad. But it is much worse when hundreds of hours of work is gone just by one click, and the program lets the user pull the trigger, so to speak, without him knowing that he does. Here is the story.

 

In 2002, Apple bought an Digital Audio Workstation called "Logic". The program, initially programmed for Atari computers somewhere in the 80s, does not feature that much "logic", however. In this program, as in all audio software, there are song files with all the details of a song's composition, and there are audio files, usually many large files, with vocals, guitar, drums etc. The preferences [i.e., the recording path] usually are set so that these audio files, when recoreded, are automatically stored in the same folder as the song file. When a song folder, containing the song file and all audio files, is moved to a new hard disk in order to have the software and the personal audio files on separate hard disks, which is recommended due to the large amount of audio files used in a song, [i was told so] the newly recorded audio files will not be stored in the song folder, though the path is still set to it. These files then are stored elsewhere, and there is no failure message. Guess where. They are store in the trash! OSX obviously does not have a true trash with files put there being out of function. These files are still working, but the user does not know that they actually are on the verge of erasure. [i experienced this data loss. But I did not know why. Fully by chance, a friend of mine, who has a little studio, did exactly what I had done, i.e. move the song folder to another disk. And, alarmed by my experience, checked the path for new audio files recorded, and it was the trash!]

 

So, users still work on their songs, adding many new audio files, acting out their creativity. When, maybe after many months of work, the trash is emptied in order to make more disc space available, for example because more space is needed to give space for backup copies of all the song and audio files, the user does not suspect that he is pulling some kind of trigger. All the audio files, and all the intellectual property created, will be deleted. And is very hard, if not impossible, to recover these files on an Apple (as opposed to other types of personal computers with a different systems software, like Windows). [The file structure is deleted on a Mac, not on an IBM.]

 

How does Apple respond? Of course the company refers to the small print, knowing that for a single private user it is very hard, and extremely time consuming, and risky, to challenge a software giant like Apple legally. When confronted with the demand to accept at least some moral responsibility (as opposed to some liability in the legal sense, which might or might not be given here), in the sense of fair dealing, Apple explicitly refuses to answer the question if it does or does not accept some kind of moral responsibility. Which is quite strange. Why should a company not being able to answer a simple question? Also, Apple does not understand the difference between moral and causal responsibility (causation). It is not the user who deleted the files. It is the program, or the concurrence (or team play?) of "Logic" (storing newly recorded audio files in the trash without warning) and OSX (allowing files moved to the trash still to work - as long as the trash is not emptied), which brought this about. There is not question that Apple, not the user, caused the data loss.

 

Instead of accepting some causal, and thus some moral, responsibility, Apple says to be happy to help the user - which amounts to nothing but to recommend some professional data recovery service. This kind of, and amount of, commitment to the users must be regarded as quite cynical by the user. (The cost for such of recovery will be some thousands of Dollars, and still then it is uncertain if the audio files will be actually recovered. Even if so, it will take many, many hours to reconstruct the songs, as the hundreds of sought-after audio files will be plunged in the sea of thousands of deliberately deleted audio files.) The first task, which is quite delicate, should be accomplished by the best experts available. The second task is quite cumbersome. There might be some software or programming facilitating this task.) Also, Apple declares that the software it sells has to be regarded "as-is" products. So, the company admits that it sells software which operates erratically. One wonders how long such a company will be able to stay in the market with such a commitment to its products. Also, one wonders if Apple will or will not warn the users of "Logic" against this fatal bug. And one wonders what is going on in the background in order to fix this disastrous bug. It seems, however, current victims of this bug will not benefit from this error correction, which surely will be accomplished in order for Apple to sustain its reputation as a professional, as opposed to an erroneous, software supplier.

 

Thanks for your reading.

 

Ulrich

[David Nahmani]

It doesn't sound right to consider a software (or hardware) manufacturer responsible for your loss of data. Software has bugs, hardware fails. That's a reality of modern times, and it is the computer user's responsibility to backup, backup, and backup some more. If your hard drive dies, is the hard drive manufacturer responsible for your loss of the data on the drive? Can you imagine the sheer amount of lawsuit?

 

In Logic, whenever you move any file, you should be careful and make several checks in the Finder.

 

So you can curse at Apple, you can scream at them, you can criticize them for the way file management works in their products, for bugs in their applications.. but surely you can't have them be responsible for your data. Otherwise song corruption alone would be a ground for pretty much every single Logic user to sue Apple.

 

Now back to Logic. To move a project folder, quit Logic, move the project folder on the new drive, open the new song file in the new project folder and choose File > Project > Consolidate. ALWAYS check the location of your audio files in the Audio Window. ALWAYS make a backup on an external drive (you don't need to consolidate your backup, just drag the whole project folder on your backup drive).

[vpunk]

Excellent rebutal David!

 

I've inadvertanly lost an entire session once (!), but of course it was my fault.

 

C'est la vie.

Tyler.

[KJ]

I don't know what your problem is but this not even a bug, at least not on the way you described it. I move data from one disk to another all the the time and i have never had all my new files written to the trash. Even from a default save menu on ANY osx application it is very easy to see that you are writing files to the trash. Unless you have not been paying attention to what you are doing this all sounds really weird to me.

 

btw. your story has some things in it that don't match. It is just as easy to recover files on a mac then it is on a windows machine. HFS+ and NTFS/FAT(32) handle deleted files basically the same way. I totally don't understand your remark about IBM

[Fred B]

Out of curiousity I've tried to reproduce the problem. I just copied a Logic project to another disc and trashed the original. Now, when using the project for additional recording, the files are in fact recorded into the trash, ie. the original project folder. Apparently the recording path is not updated automatically when moving a project to another disc.

 

Nevertheless, I completely agree with David's statements.

[David Nahmani]

Yup.

 

If you wanted to properly copy a project and have it update the record path you'd have to open it in Logic and do a "Save As Project". Not move it in the Finder and trash the original.

 

Every time you move Logic files around in the Finder, Logic won't be able to automatically update file paths, so you'll have to do some manual checks.

[Ashermusic]

It doesn't sound right to consider a software (or hardware) manufacturer responsible for your loss of data. Software has bugs, hardware fails. That's a reality of modern times, and it is the computer user's responsibility to backup, backup, and backup some more. If your hard drive dies, is the hard drive manufacturer responsible for your loss of the data on the drive? Can you imagine the sheer amount of lawsuit?

 

In Logic, whenever you move any file, you should be careful and make several checks in the Finder.

 

So you can curse at Apple, you can scream at them, you can criticize them for the way file management works in their products, for bugs in their applications.. but surely you can't have them be responsible for your data. Otherwise song corruption alone would be a ground for pretty much every single Logic user to sue Apple.

 

Now back to Logic. To move a project folder, quit Logic, move the project folder on the new drive, open the new song file in the new project folder and choose File > Project > Consolidate. ALWAYS check the location of your audio files in the Audio Window. ALWAYS make a backup on an external drive (you don't need to consolidate your backup, just drag the whole project folder on your backup drive).

 

Standing ovation!

 

In real estate they say only 3 things matter:location, location, and location.

 

In computing it is: backup, backup, and backup.

[toysun]

Hi,

You are both right! Of course, David's advice is great and I hope I remember it, but at the same time, if this is so well known to y'all, then why can't Logic be smart enough to check the record filepath upon opening a song give us an dialog box: "Please update your record filepath"? How hard would that be from a programming standpoint? I'm no programmer, but wouldn't it be:

Upon open

Check record filepath

If = trash or "unknown"

then display message "update record filepath"

 

Check my syntax, boys! Seriously, this is the kind of thing that the program should do, doncha think?

 

People, there is nothing wrong with asking our software companies to do better. Isn't that what these forums are for? I don't advocate (excuse the pun, David) getting lawyers involved, but at the same time, Logic costs $1000.00 That's a lot of money for a musician. A lot of software EULAs are just so consumer-unfreindly, it's ridiculous. How does a company get to sell a "tool" for more than $1k and yet offer no guarantee that it will work, and you can't return it (or sell it to someone else) I call BS.

 

John

[David Nahmani]

I'm no programmer, but wouldn't it be:

Upon open

Check record filepath

If = trash or "unknown"

then display message "update record filepath"

 

I studied programming and my wife has been a programmer for more than 10 years. This is the most common misconception about programming: that things are simple.

 

Believe me, it's far from being like that. Programmers are probably laughing a nervous laughter reading your message. In programming, everything is interconnected, and with a deep program such as logic, adding a function could mean breaking 10 other things. Fixing ONE of those other things could mean breaking 12 more.

 

I have a little experience, even if it's just programming javascript, php scripts, mysql database for this website. Change the design of the menus and the background color, and all of a sudden people can't stay logged in anymore. Seems to be utterly unrelated, right? Well in some twisted way, it ended up making some kind of sense.

 

Anyway if you've ever done any kind of beta-testing for a big software (I have), then you'll know that when you want a totally innocent and simple feature added, it usually comes at a price, and that price is days of testing....

 

OK to cut the BS as you would call it (even though it definitely isn't), Logic offers the function: it's called Save As Project. It's not equipped to detect that you haven't used the function it provides you with, but used another application instead (the Finder) to save a copy of your project.

 

The rule of thumb is: if you move files using anything OTHER than Logic, don't expect Logic to automatically guess what you've done with the files. And the solution? Just manage your file locations with Logic!

 

Now I'm certainly not saying not to suggest to the developers to add that as a feature in a future version. I'm just saying that you can't hold them accountable for your loss of data because you didn't use their product the way it was intended to be used (which is to properly save a project, use the function "Save As Project", don't use the Finder).

[Fred B]

I wonder if the user could avoid any problems with moving/copying projects just by using the Project Manager. Here is a quote from manual page 430:

 

"Set Song’s audio recording path: If you’re not yet finished with all recording sessions for a song, it’s a good idea to allow the Consolidate function to set the song’s audio record path for you. Future recordings will automatically be placed in the right folder structure, if you keep this option checked."

 

So it sounds like the user could move projects around in the Finder, and PM takes care of updating the record path. Is this true?

[editbrain]

it is also just a push of the "A" button to see your recording path.

 

but keep in mind the very first thing you should do before you record a thing is have a proper work flow, and to me that is "name and save my song as a project"

 

this eliminates all possibilities of the takes being recorded outside the project folder unless you change them manually.

 

every time you open the project it will set the path automatically to the "Audio" folder in the project.

[Ashermusic]

I'm no programmer, but wouldn't it be:

Upon open

Check record filepath

If = trash or "unknown"

then display message "update record filepath"

 

I studied programming and my wife has been a programmer for more than 10 years. This is the most common misconception about programming: that things are simple.

 

Believe me, it's far from being like that. Programmers are probably laughing a nervous laughter reading your message. In programming, everything is interconnected, and with a deep program such as logic, adding a function could mean breaking 10 other things. Fixing ONE of those other things could mean breaking 12 more..

 

Great post David and if I have your permission I am going to use it on several forums I participate in.

 

People act as if Apple doesn't implement or fix certain things they want in Logic out of laziness or stubbornness. Your post expains exactly what it is that they do not get.

 

Why is it everyone always thinks everyone else's job is easy?

[michkhol]

I'm no programmer, but wouldn't it be:

 

I studied programming and my wife has been a programmer for more than 10 years. This is the most common misconception about programming: that things are simple.

 

Believe me, it's far from being like that. Programmers are probably laughing a nervous laughter reading your message. In programming, everything is interconnected, and with a deep program such as logic, adding a function could mean breaking 10 other things. Fixing ONE of those other things could mean breaking 12 more..

 

Great post David and if I have your permission I am going to use it on several forums I participate in.

 

People act as if Apple doesn't implement or fix certain things they want in Logic out of laziness or stubbornness. Your post expains exactly what it is that they do not get.

 

Why is it everyone always thinks everyone else's job is easy?

You guys really made me laugh. Please share it with other programmers so they could also have a good time. If a single change breaks a program in 10 other places in means only one thing: BAD DESIGN. If it is really a case with Logic, I have no more words..

 

Programmer

[David Nahmani]

You guys really made me laugh. (...)

 

Programmer

 

I told you this thread would make programmers laugh.

[Ashermusic]

I'm no programmer, but wouldn't it be:

 

I studied programming and my wife has been a programmer for more than 10 years. This is the most common misconception about programming: that things are simple.

 

Believe me, it's far from being like that. Programmers are probably laughing a nervous laughter reading your message. In programming, everything is interconnected, and with a deep program such as logic, adding a function could mean breaking 10 other things. Fixing ONE of those other things could mean breaking 12 more..

 

Great post David and if I have your permission I am going to use it on several forums I participate in.

 

People act as if Apple doesn't implement or fix certain things they want in Logic out of laziness or stubbornness. Your post expains exactly what it is that they do not get.

 

Why is it everyone always thinks everyone else's job is easy?

You guys really made me laugh. Please share it with other programmers so they could also have a good time. If a single change breaks a program in 10 other places in means only one thing: BAD DESIGN. If it is really a case with Logic, I have no more words..

 

Programmer

 

Really?

 

Thousands, maybe hundreds of thousands, of lines of code dating back to the early 90's and you make this judgement?

 

I wonder if your work could be held to that standard. But maybe it can so please can I forward your resume to Apple so you can straighten them out?

[michkhol]

 

Really?

 

Thousands, maybe hundreds of thousands, of lines of code dating back to the early 90's and you make this judgement?

 

I wonder if your work could be held to that standard. But maybe it can so please can I forward your resume to Apple so you can straighten them out?

Lines of code are not bricks and concrete (and even buildings get fully reconstructed). Maybe it was worth spending some time on software design than writing "hundreds of thousands" lines of code since 90's.

And thank you for your offer, your help won't be necessary.

[Colinc]

The rule of thumb is: if you move files using anything OTHER than Logic, don't expect Logic to automatically guess what you've done with the files. And the solution? Just manage your file locations with Logic!

 

agreed. if theres one thing I've learned over the years of dealing with computers (from PC to mac) it is you NEVER assume or expect the computer to know what you want to achieve. If you understand that, and realize that ALL software to some degree has faults, your computing will be much less frustrating.

[marcel72]

The rule of thumb is: if you move files using anything OTHER than Logic, don't expect Logic to automatically guess what you've done with the files. And the solution? Just manage your file locations with Logic!

 

So when I want to do backups, I should do Save As Project initially onto the backup drive, and then let my auto-backup program go from there? Like, can I assume these backups are workable sessions after the initial Logic Save As, even if changes are updated regularly?

 

(I use Dejavu for backups).

[David Nahmani]

I don't go through the trouble when backing up. I just drag and drop the whole folder on an external drive. If I ever need to recover a backup (which I rarely do), I drag and drop the folder from the external back on the regular drive, open the project and consolidate.

[marcel72]

Thanks...

 

Now that you put it that way, this doesn't sound like something I'd ever encounter... Both my work drive and backup drive(s) are external (ATA for work and FW for backups), so I habitually check the record path whenever I move something anyways. Not that I do very often, either, although I have occasionally launched the wrong session for whatever reason and had to 'copy back'...

[ski]

In the past, on a few occasions, not understanding the cause at the time, I've seen Logic record to the trash also.

 

BTW, I've also seen it happen on Digital Performer.

 

Logic. I love this program. The capture record feature is absolutely essential in my being able to retain spur-of-the-moment compositions/improvisations that would have otherwise never gotten recorded. And the things I've been able to do with beat mappings and manipulation of tempi lately have made me grateful to be working on this platform.

 

But it all comes with a price, and that price is bugginess. Logic is absolutely riddled with bugs. The bug report database on this website reflects this in part. I say "in part" because, had I the time, I'd add at least 2 dozen additional fat, juicy bugs to the database.

 

Now, the middle ground... all software has bugs. This is a given. The severity of bugs are usually rated on a scale of A, B, C, D, or similar. There are plenty of what I'd consider "D" bugs in Logic --- things that make it an utter pain in the ass to run, but don't crash the program or end up altering data. One such bug is when you edit an EXS instrument and, after closing the editor, clicking on "Save As". BUG: you cannot type in a new name. WORKAROUND: hit "cancel", then do a new "Save As" operation. Clearly and unquestionably a bug. And there are many such interface & dialog bugs like this that sometimes make Logic less than a joy to work with.

 

When bugs prevent you from actually accomplishing the task at hand, or operate in a way that's highly unintuitive, such bugs are referred to as a "show stoppers" by software engineers and beta testers. And as far as moral obligations are concerned, I think a software company has such an obligation to communicate about show stoppers (as a first obligation) and then to fix the problem. Unfortunately, this is not the way Apple works. They are tight-lipped to a fault when it comes to admitting to the existence of highly problematic behavior. Hell, wouldn't we all be so much better off if there was some kind of official acknowledgement about issues at hand? For example...

 

How many dozens of posts have there been both here and at the Apple/Logic forum about songs where parts are suddenly transposed? Or the fact that on MacPros, scores display "off the page", or that tempo events in the tempo editor are essentially uneditable. Or that beat mapping operations can destructively interfere with previously defined tempo maps made in the tempo editor? Or that the Project Manager interferes with the loading of EXS instruments... I could go on...

 

Where's the official acknowledgement about these well-known bugs? Very little such acknowledgement exists on Apple's website. In this respect, compared to Emagic's long-lamented accessibility, they're being "icky-corporate", the kind of "corporate" that doesn't translate well, if at all, to people on the outside.

 

Anyway, it's all been said before... Logic's in need of an overhaul. But in the meantime, we can't stop working, right? So we continue to use whatever version of Logic we've settled on and hope that the future will present some big improvements -- both in code-writing integrity and, perhaps even more importantly, communication from Apple on these kinds of issues.

 

Forewarned is forearmed. Make a point of visiting the bug database and familiarizing yourself with Logic's flaws. Learning how to run Logic means also learning about Logic's bugs.

 

-=sKi=-

[tzurby]

There is quite an extensive discussion going on here on bugs. Sorry, I could not answer to the posts to my initial contribution earlier.

 

Of course, if one backups all the time, no software manufacturer can be made responsible for anything. But I still think we discharge Apple all too early then. This is a severe bug, and I still don’t know of any more sever bug (in PC software). If anybody has heard of any more severe bug, with regard to consequences, let me know. This especially applies to those who think that my objections are ridiculous. (Thanks, Fred, for having checked for the bug. Yes, it is there, though it is still hard to believe.)

 

By the way, David, I am not talking about a hardware failure, but a program failure stemming from the fatal interplay of two programs, i.e. “Logic” not giving a failure notice, and Apple not having a real trash. If the data loss would result from a bad disk, bad luck for me. But this is a total different story. Also, the bug here i not like any of the thousands of bugs out there (in “Logic” or other programs), as David seems to suggest. The failure not to give a failure notice, or that it is possible to have data stored in the trash, with them still working, at all, is a severe error by the software manufacture, and he should concede this error and he should take corrective action, to the program in the long run (you will see, Apple will surely do), and to the sufferer.

 

David, I am a (part time) user, and not a programmer, or computer expert, as most of the people posting here seem to be. Programmers, it seems to me, regard programs not as finished products, but as ongoing projects in a constant infant state. In contrast, I, as a normal user, expect programs simply to work, at least being tested thoroughly enough to rule out failures like the one I fell prey to. I demand software manufacturers having done their homework. This failure simply is too severe to having Apple get away with it.

 

KJ, I was told that with Windows, the data path is still there when a file it deleted and restored, not so with OSX. I got Data Rescue II, and I recovered about 30 gigabyte of aiff files. I got them in 7 random folders. The only way to look for a lost file is its size (the size of the lost files is still displayed in Logic). I checked for some files, but all the files I found with the same size did not fit. Maybe in this sea of restored files the one or the other of my lost audio files still can be found (I assume it’s about 300-500 files). Most obviously, it is wiser to re-record the files.

 

That’s what I call the Worst Case Bug.

[David Nahmani]

I'm not sure why you insist on calling it a bug: you're not using the software properly, or at least not the way it was intended to. Open your project in Logic and choose File > Save As Project.

 

If you save an XML file in Final Cut Pro, and then use the Finder to move the XML on another drive, but don't move the audio files, then the XML file won't find the audio files again. Is that a bug in Final Cut Pro?

 

Once again, if you move files around using an application other than Logic, don't expect Logic to magically guess what you've been doing with the files.

[Ashermusic]

I'm not sure why you insist on calling it a bug: you're not using the software properly, or at least not the way it was intended to. Open your project in Logic and choose File > Save As Project.

 

If you save an XML file in Final Cut Pro, and then use the Finder to move the XML on another drive, but don't move the audio files, then the XML file won't find the audio files again. Is that a bug in Final Cut Pro?

 

Once again, if you move files around using an application other than Logic, don't expect Logic to magically guess what you've been doing with the files.

 

Exactly. If I had a dime for every time someone calls it a bug when an app does not behave thec way he/she wants it too I would be a wealthy man.

[tzurby]

Sorry folks, your answers are cynical. Please keep down to earth. Your trick to simply call this "my faul" instead of a "bug" does not work. You are trying to evade my question. This is not reasonable. Call it what you like. This is what I call a program failure. It must not happen that I record files and these are stored in the trash without notice. It does not matter what I have done before. I surely did not tell the program to store the files in the trash.

Your answers are partisan, full of prejudice in favour of programmers. (Or of Apple?...) Instead of sophistry, you rather should answer the question whether there is or is not any more severe bug - or "unintended program behavior (UPB)", if you prefer this expression. You are the experts, you should know. But I very much doubt that you find more severe cases of UPB (as always, in the realm of personal computers).

[nickweston]

I've been using Macs since their inception in 1984 (Apple II, 128, 512, SE, SE-30, IIci, Performa 6400, Powerbook 1600, Powerbook 520c, Beige G3, Blue & White G3, G4, Powerbook G4, iBook G3, G5, MacBook, MacBook Pro).

It only took a couple of times early on losing date to formulate a system to insure that this would never happen again.

Having started in Vision, then to StudioVision, then Performer, and finally Logic, I have seen many ways of backing up data. One thing I've never done though is blame a software developer for my lack of planning or knowledge.

 

That being said, I use .mac backup every night, rotating three drives (one at the studio, one at home, and one in the trunk of my car) religiously.

 

Also, at the end of ANY project, I save AGAIN as project, but this time to 2 DVDs, as xxxFINAL PROJECT. This doesn't really take up that much time, but it does deny me the pleasure of blaming a programmer for lost data.

 

ALWAYS start a new song by saving as project and you'll save yourself a ton of problems.

 

NEVER expect a programmer to make up for your lack of planning or understanding of the format you're working in!

 

Interesting that after a huge long rant against the "Logic" of Logic, and the benefit of numerous intelligent replies, TZURBY never posted again.

 

I don't do this much, but maybe, just maybe, tzurby should use an analog recorder. Just don't blame the tape manufacturer if you happen to erase the tape!

 

Either that of Cakewalk and an E-machine. Then backup to your Zune.

 

(sorry, I couldn't resist)

 

great forum

[Ashermusic]

Sorry folks, your answers are cynical. Please keep down to earth. Your trick to simply call this "my faul" instead of a "bug" does not work. You are trying to evade my question. This is not reasonable. Call it what you like. This is what I call a program failure. It must not happen that I record files and these are stored in the trash without notice. It does not matter what I have done before. I surely did not tell the program to store the files in the trash.

Your answers are partisan, full of prejudice in favour of programmers. (Or of Apple?...) Instead of sophistry, you rather should answer the question whether there is or is not any more severe bug - or "unintended program behavior (UPB)", if you prefer this expression. You are the experts, you should know. But I very much doubt that you find more severe cases of UPB (as always, in the realm of personal computers).

 

You can look at a horse and call it a donkey all you want, it will not make it a donkey but if it makes you happy to think it is a bug then I am happy for you. Enloy!

[Fred B]

It must not happen that I record files and these are stored in the trash without notice.

Agreed. But on my test I've noticed that Logic's recording progress window clearly indicated "...Trash" as recording path. So from the system's view, ignoring this information may be called "unexpected user behavior".

[marcel72]

It must not happen that I record files and these are stored in the trash without notice.

Agreed. But on my test I've noticed that Logic's recording progress window clearly indicated "...Trash" as recording path. So from the system's view, ignoring this information may be called "unexpected user behavior".

 

Good point... How many hours have I spent watching those numbers count down...

 

I knew that was there for more than just to give me some sort of distraction during the otherwise repetitive process of tracking.

 

LOL