[EDITING] One of those days

[Required]

Hi, guys.

I just had one of those days, and I needed to share it with the community. Also I created this thread for all the editors having a bad day while editing a Cock Hero video. This is a hard, long and lonely process, and I think this can be a way to share our feelings when things go wrong.

So, I was having a great day, didn't have to go to work today and thought of spending the day editing a round. I still have a few round pending for Island 5, and today I wanted to edit a round with Tessa Fowler. She's my #1, and I'm in love with her, so I thought "this is gonna be easy man. I love Tessa, this is gonna be so much fun to edit".

Open Premiere Pro, import the clips and... BAM! The previsualization screen is not working at all. The bar moves in the timeline, and the music sounds, but the screen is fucking frozen. After a few minutes checking the settings, I decide to uninstall, and install again. It doesn't work. I install 2017 version. Doesn't work. Install 2019 version. Even worse. Finally install the 2018 again (the one I usually work with) and all of a sudden, the fucking program works perfectly.

AARGGGGGHHH!!!! I've lost the whole afternoon with this shit! I could have that round completed already!

Have you guys had any recent bad day at editing Cock Hero vids?

[doremi]

Vegas has its share of crashing too when pushed too much. I keep an old version (v14) and refuse to upgrade it because my actual workload is pretty much fine tuned.

And if you talk about other kind of compilers... I just upgraded my C++ Builder compiler to the latest and greatest and $####.## too. And holly fucking fuck, they changed the string format from a series of 8 bit ASCII codes to a series of 16 bit UNICODE codes. And when trying to use it, I noticed that they kept the name of some functions the same with the new format, and created whole new function sets with hybrid formats as well. What a giant ass mess! I wasted a day as well trying to figure out how to plug my legacy code somewhere in there.

Programmers and Software Architects do not use the software that they create, and it's the source of all these problems.

EDIT :
I went from the BORLAND release, the original product founder, version 1.0 in 1997 to version 10.3.2 from the new owners Embarcadero. 22 years is a huge step.

[high_octane]

I hear you, Required.

I use Kdenlive, and I must say that I've been pretty disappointed with it. There was this one really nasty bug where, if you apply a speed effect to a clip, and later change the location of the clip and reopen your project, it will say that it cannot find the clip. Okay, so then you tell it where the clip has been relocated and then everything loads up. However, all of the speed adjustments and positions subsequently become screwed up (and I didn't notice until too late), and now you have to redo all of your work from scratch.

Also, Kdenlive's interface is just not intuitively designed, and causes me headaches on a regular basis. I'm about ready to drop it for something else. Maybe it's time to go back to using Blender for video editing! Ironically, some aspects of Blender's video editor are more intuitive, or at least more flexible (like keyframe extrapolation), and video editing is not even the project's main focus!

And if you talk about other kind of compilers... I just upgraded my C++ Builder compiler to the latest and greatest and $####.## too. And holly fucking fuck, they changed the string format from a series of 8 bit ASCII codes to a series of 16 bit UNICODE codes. And when trying to use it, I noticed that they kept the name of some functions the same with the new format, and created whole new function sets with hybrid formats as well. What a giant ass mess! I wasted a day as well trying to figure out how to plug my legacy code somewhere in there.

Ouch! What compiler or program are you referring to?

Programmers and Software Architects do not use the software that they create, and it's the source of all these problems.

In most cases, I'd agree with that. I'll also add that sometimes, when developers are pressed for time, and they need to meet a deadline, their code cannot be fully tested and debugged before it's shipped out, which is unfortunate, but it happens relatively frequently.

[PrimeSwitch]

Rewind to three years ago, I was working on Cock Hero Prime University.

Everything was being worked on with my 2012 MacBook Pro. It was 4 years old at that point, but still chugging along alright. Then, out of nowhere, the hard drive died. It started with me editing a round, the computer freezing, and when I restarted I got the dreaded folder with the question mark icon. Unreadable disk.

I was able to recover some of the contents and transfer them to a brand new solid-state drive! A few rounds were missing, but I re-did them (for the better, I think) and Prime University was released! Then a couple months later, while working on Cock Hero Prime World, the cable connecting the SSD to the motherboard died (a common design flaw in the 2012 MacBook Pro). That's when I upgraded to an entirely new MacBook Pro. I reuploaded my Final Cut Pro files and everything was... different. Because this version of FCP X was updated and some of my plug-ins didn't transfer over correctly. It was, suffice it to say, a pain in the ass. But eventually, Prime World was released and that was all fine and good.

I haven't done a "large-scale" Cock Hero since, partially out of superstition that it would break my current laptop haha. But I am in the planning stage for my final large-scale Cock Hero, and it will come out... eventually. Even with the bad days factored in. Hang in there, buddy!

[doremi]

PrimeSwitch, use a PC to keep your Mac safe.

[Biggie]

Damn Required, I thought you we're going to say you lost edited material with weeks of lost work! THAT would be scary!