What is Reddit's opinion of Screenlight?

From 3.5 billion Reddit comments

read this: https://screenlight.tv/blog/five-mistakes-video-editors-make-when-freelancing

Essentially - make a contract, define project expectations, and ask to be paid a deposit BEFORE working.

you are talking about intermediate codec and not proxy.using them will help you depending on your pc/work flow /what do you do with the footage here is a good article explaining that.

I found this article about bitrates https://screenlight.tv/blog/bits-and-bytes-the-simple-math-of-premiere-pros-exports so what I did was I tried to match the bitrate of the original file from Premiere's export options and I was able to make the export file as small as the original. I got 34 mb using this way.

At the end of the day, each editor needs to have a copy of the footage they can access: either local machine storage, or shared network storage (a NAS or SAN for example).

I think you can use CC storage to facilitate the transfer of this but I don't believe it allows you to edit off of it directly (I'd just imagine due to latency).

But hey perhaps I could be wrong. Team Projects have a Media Management page where editors can view what media is offline and online, and what specific assets are need.

This goes over it fairly well: https://screenlight.tv/blog/collaborating-with-team-projects-in-adobe-premiere-pro

i actually use frame.io for the studio I work at and it's great but I agree with others here, it's actually pretty advanced and most clients don't actually utilize the full potential. It works really well for teams though. When I freelance on my own I use screenlight.tv, it's basic and a lot cheaper and still offers timecoded notes.

Nice!

To save you a step, there are a couple of plugins for Premiere that will take a CSV and import it as markers to a timeline. Screenlight has one that is designed for their video review system, but will work with any correctly formatted CSV. You could modify your stopwatch to output the correct CSV, and skip manually adding markers all together!

I found this guide helpful:

https://screenlight.tv/blog/the-definitive-guide-to-adobe-premiere-pros-media-cache

Not sure how much has changed since it was last updated.

Preview files are effectively Quicktime movies created using the framerate/resolution/codec that you've specified in your sequence settings. As such, they can be stored on any device that meets the bandwidth specs for your sequence. For instance if your sequence settings are 23.98 fps, 1920 x 1080, Prores LT, then a regular USB drive would work fine (of course an SSD would be great, but you'd have to budget for it.)

The small mcdb files in your cache require lots of fast, tiny, I/O operations, so an SSD is better suited to the job. The default location for the cache is the boot drive on the computer which nowadays is likely to be an SSD anyway.

The .cfa files found in the cache are just uncompressed audio files created when compressed audio/video formats are used in a project. They're not high-bandwidth, but they can take up lots of room, especially if you don't clean out your cache periodically. They also get created automatically if you move the project to another machine, which takes time... We've started writing the files next to the source media on the project drive instead, so they travel with the project.

Likewise the .pek ("peak") files, which store the audio waveform drawings that you see in your timeline. Recreating these for a large project takes a while, so we've found it's better to keep them next to the audio so they're not recreated every time the project is opened elsewhere.

Someday everything will be on NVMe/flash storage, and most of these issues will be moot. But for the time being, bulk storage on spinning discs is still a necessity.

Hope this helps.

Im actually ramping up again after taking some time off from writing. Ill be writing more for Wipster soon hopefully. I have a couple older articles I wrote for Screenlight.tv which can be found here: https://screenlight.tv/blog?author=5761b4d5d51cd4cfb9620b49

​

But a couple of them are out of date now, like creating text templates in Premiere and some parts of Export one for Premiere (because settings and presets have changed).

I wrote an article on this a while back. Some stuff is slightly out of date (the presets have changed), but the math still works!

​

https://screenlight.tv/blog/bits-and-bytes-the-simple-math-of-premiere-pros-exports

I think you need to understand the principle of ram preview. Long story short after effects can not play in real time. Take a read : https://screenlight.tv/blog/the-definitive-guide-to-ram-previews-and-disk-caches-in-after-effects-ie-those-blue-and-green-lines

Your problem seams to be linked to ram preview and not your headset. I'm guessing you are still new to after effects, so here's an explaination :)

After effects can not play your footage in real time, it needs to calculate every bite of what you created before playing the footage. If you take a look, above the timeline, where you have your different layer, there's a green line. This is what you "pre-rendered". Everything under this green line is playable in real time. After effects make these calculation while you play the video, and often while watching your creation you will reach the part currently in calculation. At this point the sound is disorted and slowed down, your footage seams often chopy/slowed down too. Just continue to play your video with that creepy sound, and watch that green line grow. When the part you want to watch will be under the green line, try to watch again the video. You will see the sound will be normal.

So, to summaries, after effect make is calculation while you watch the project. If the sound become distorted, let after effects make is calculation. Continue to preview your project with the sound distorted, since after needs you to play your video to make is calculation. A green line above your timeline tell what part is watchable in real time. One the part you need to watch is calculated, play it and eveything will sound fine.

Edit : here is a clearer and more in depth explaination of what I tried to explain. I highly suggest you to read at least the 3 first paragraphe https://screenlight.tv/blog/the-definitive-guide-to-ram-previews-and-disk-caches-in-after-effects-ie-those-blue-and-green-lines