logo Sign In

Hal 9000

User Group
Members
Join date
14-Oct-2003
Last activity
12-Dec-2025
Posts
11,382

Post History

Post
#1381226
Topic
The Rise of Skywalker: Ascendant (Released)
Time

dgraham414 said:

Was checking out the KoR voices in the new workprint and noticed that you used the exact same “Traitor” audio clip for when Ben first sees the KoR and when Ben is surrounded after being beaten. I know the set of voices that axlanian provided had another take for the “Traitor” line that you can use. Right now it sticks out that they are the exact same audio clip.

Huh. I’ll take care of that. Thank you!

And I’ll address the other audio related changes, too. I appreciate the feedback.

You may need to try to download the file rather than play it inside your browser. If it says it’s been accessed too many times, try copying it to your own Google Drive and then copying it again within your Drive. That should be enough to fool it into letting you download it.

Post
#1381008
Topic
The Rise of Skywalker: Ascendant (Released)
Time

I do, too. I PM’d him about a week ago and haven’t gotten anything. I do hope to see a return from him, but obviously it’ll depend on that.

I think I found the problem with the video encode, and I hope it’s just a weird glitch rater than the video file being corrupted. Worst case I have to redo the color grade after re-exporting from FCP7.

Post
#1380998
Topic
The Rise of Skywalker: Ascendant (Released)
Time

I hope to put out one more workprint in the near future, now that I’ve got everything finally situated. It won’t include kewlfish’s crackly saber video or audio. So, if for any reason he isn’t able to finish that work, this will be pretty close to the end product.

Right now I am troubleshooting some issue that is preventing me from exporting video from FCPX or Compressor. I can export audio-only stuff fine, so I’m not sure what the deal is.

Post
#1380163
Topic
The Rise of Skywalker: Ascendant (Released)
Time

I tried to, but it gave my a cryptic complaint (about the drive lacking a “firmware partition”) that I believe wouldn’t be there if the internal drive had 10.13 or later installed.

Didn’t anticipate this as a problem, but should be solvable. Plan A is to move the original internal drive to an enclosure and boot from it in order to format and work with the new one.
Otherwise I’ll have to get creative about removing the screw I stripped and temporarily putting the original internal drive back in so I can format the new one.

And I’ll say this: even though the screen is busted, it’s nice to have a MacBook that isn’t dented and dinged to hell like my 2011 machine was when I got it. (That’s how I got it as cheaply as I did.)

Post
#1380052
Topic
The Rise of Skywalker: Ascendant (Released)
Time

I got a 2014 13” machine. I popped a new NVMe drive into it. I can boot into recovery or 10.12 Sierra via external USB, but neither option lets me detect the new internal SSD via disk utility or terminal.

I don’t know how the new drive came formatted, and it wasn’t listed as specifically for Mac so I’d be surprised if it was APFS.

So, I’m hoping that an enclosure will let me address the drive so I can format and install macOS. Apparently it may matter that it’s internal.

Does that sound like a good plan or do you have any insight?