Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
vanlazarus2013
Engaged
vanlazarus2013
Engaged
Activity
‎Dec 16, 2018
07:55 PM
Ok, I'm doing that. Also reset my preferences. Hasn't happened in a few hours of work. If it does again, I'll turn off gpu rendering and see if it solves it.
... View more
‎Dec 14, 2018
10:41 PM
This has been happening for months now.... During an edit, the program monitor suddenly goes blank. Nothing is shown as you scrub through any sequence timeline and the only way to restore it is to save my project and restart Premiere. And because Premiere is so slow, that is a huge productivity killer. It takes 2 minutes+ to save, close Premiere, restart it, load the project, and wait for Premiere to load all of the media. I have noticed no patterns as to why and when this happens. Sometimes after only a few minutes, and sometimes after an hour.... But in the last 2 days it's happened often. I do suspect it's related to some interface bug with the CUDA graphics drivers, but I'm editing 5k footage so I can't afford to disable acceleration. I have the latest Nvidia drivers installed. My system is Windows 10 64 bit, i7 5960X CPU, 32gb RAM, Nvidia GTX1070, with a project on a 11tb RAID 0 drive, and 2 monitors (1 4k and 1 2.7k). I called Adobe support (taking about 45 minutes) and the guy was convinced that a reset of my preferences would solve this problem (holding down ALT while restarting Premiere). I saw no discernible change. A restart does revive the program monitor, but then it dies at some random time later, regardless of a preference reset. An alternate version of this problem is to have all effects control keyframes or motion bounding box graphics disappear. This is equally frustrating when one is trying to use those tools and I'm forced to restart Premiere and reload the project to continue. Any assistance in how to cure this problem would be greatly appreciated.
... View more
‎Dec 14, 2018
05:41 PM
I'll try it. Just concerned that it'll result in the same scaling degradation of the 2k VFX shots. I'll do some tests. Thanks.
... View more
‎Dec 14, 2018
04:01 PM
Thanks for the info Warren. I'll look into some of those other options for scaling. But in regards to my main problem... preserving framing when moving to a different sequence resolution... I think I'll just have to redo hundreds of unique framing changes in the 2k sequence.
... View more
‎Dec 14, 2018
08:53 AM
You're both misunderstanding my expectations and the problem this post is about. Of course 720p footage is not going to look as good as 5k footage. But scaling of footage is not rocket science and software does this with every image displayed. My issue is with Premiere's apparent bug in scaling something up and then down. Take a photo in Photoshop, scale it up 10x, and then scale it down 10x. It should look nearly identical. I just did this in Photoshop with excellent results, so Adobe has the ''technology'. When Premiere does this, there is some kind of major inaccuracy that reduces the quality vastly. And I fully understand that doing this scaling up and down is not desirable regardless. The point if my post is not to lament this poor scaling implementation, rather Premiere's inability to adjust scaling and position keyframes when moving clips from one sequence resolution to another. It should be able to do this effortlessly and provide visually identical frames, provided the aspect ratio of both sequences is the same. If a 5k footage scale setting shows 75% of the image in a 5k sequence, then Premiere should be able to set that scale to show 75% of the 5k frame in a 2k sequence. It's simple math and a computer's forte. Yet this simple feature is unavailable in Premiere. Clip scale implementation is very clunky and confusing in Premiere. Why not have the scale setting be a function of the clip's relation the the frame size? Then a setting of 80% scale would result in the same look regardless of sequence resolution.
... View more
‎Dec 13, 2018
09:54 PM
2k source looks worse when scaled up in a 5k sequence that is rendered to 2k. My work around is to render the 2k source to a 5k intermediate. Then, when that 5k intermediate is placed in a 5k sequence and rendered to 2k, it still looks good. To get an extreme example of the problem, take a 720p clip and place it in a 5k sequence and render to 720p. Instead of looking like the 720p source material, it looks awful.
... View more
‎Dec 12, 2018
10:50 PM
That's unfortunate. I just want the clips to look exactly the same as they did in the larger resolution sequence. I am familiar with copy and pasting attributes but that doesn't help me in this situation. Many of the clips have unique framing tweaks that are completely destroyed when moving to the 2k sequence. Sometimes with keyframes that change throughout the clip. It's truly a mess and moving clips to a new resolution sequence undoes all framing work done on the previous sequence. Thanks, I will try the maximum render quality setting you refer to..... but admitedly, I'm very skeptical that this will preserve the quality of 2k media in a 5k sequence rendered to 2k.
... View more
‎Dec 12, 2018
09:46 PM
Is there any way, when copying clips from a 5k sequence into a 2k sequence to keep the scale and position of clips identical in relation to the frame size? For example, if a clip is zoomed in 15% on the 5k, is there a way to copy it and have it zoomed in 15% on the 2k? I've played with the project settings and have Default Media Scaling set to 'Set to Frame Size', but this just ensures that my 5k footage is massive in the 2k sequence, and not looking the same as it was in the 5k sequence. If I've done any framing adjustments, they are all screwed up when copying to the smaller sized sequence and I have to set them from scratch. I'm editing a large project and it's a huge pain to move all of my sequences to the smaller size, but I'm forced to because Premiere has a rendering inefficiency/problem where 2k media in a 5k sequence that is rendered at 2k looks far worse than if I place that 2k media in a 2k sequence and render to 2k. I'm forced to make this move now because all of our visual effects are being finished in 2k. I thought it would be great to keep all of our 5k footage in a 5k sequence in case we wanted to render it in 5k, but now it's biting me.
... View more
‎Nov 11, 2018
03:02 PM
1 Upvote
I think the 'load into a new project' solution may work for some (one?) of the 'low level exceptions' but there are so many in Premiere now that you'll mostly likely encounter them again in a new project. I get them at random times, doing a variety of tasks, and have yet to notice any consistent pattern. There are just too many of them. Usually, I'm forced to close Premiere and reload my project, or Premiere will eventually crash. Actually, the latest version of Premiere seems to have more 'low level exceptions' and crashes than the previous version. It's almost unusable right now. I'm having issues queuing and rendering our project now. Takes forever to queue the project with no visual feedback (one thinks it's crashed) and the last render attempt crashed at the 50% mark after going for 90 minutes. I believe my attempt to work on another project while AME was rendering did some GPU interruption of some kind. Nice to see that Premiere use is interfering with AME. Can this suite's stability get any worse? Probably.
... View more
‎Oct 11, 2018
09:35 PM
Ah, Kevin, you poor man. Still fighting the good fight I see. Thanks for your calm mediation in what must be a maddening place for Adobe employees to enter.... the Premiere Forums! I did click on that link and it seems like a really cool interface/process. I just a read a few of the first entries and already found mention of a few of my issues. Do these user requests actually get addressed by the engineering team in a timely fashion? Is there any chance that you could convince the big wigs to stop adding features for 6 months (or a year!) and instead focus on killing off some of the big bugs or rewriting whole code sections for efficiency? It's not like Premiere is going to lose many users by stopping the mad push for features. Where else can we go? It's maddening that the user hardware processing power has dramatically increased and yet Premiere is getting slower and slower and clunkier and clunkier.
... View more
‎Oct 11, 2018
01:29 AM
3 Upvotes
Just need to vent a bit..... I know that this is not going into a bug report that can be left at the very bottom of a large list of bugs, but I just want to share my experience with Premiere while editing a feature film. To Adobe's credit, I can now have a full 2.5 hour edit in one sequence timeline without bringing Premiere to it's knees immediately (unlike 3 years ago when I last tackled such a large project with Premiere), but Premiere gets down on it's knees and then falls off the cliff pretty quickly even still. I'm really curious how someone like Fincher and his team edited Gone Girl in Premiere CC. Truly. Premiere just doesn't seem like an application where stability is paramount. Sure, when editing single stock clips and short 10 minute projects, Premiere is relatively good.... aside from the 'unknown error' that often crops up at mysterious times and prevents an export, usually at 3am when trying to meet a deadline. But for large projects, Premiere is a gluttonous pig. I'm running a fairly powerful Windows 10 system i7 5960X with 32gb of RAM.... nVidia GTX1070.... My film footage... 16tb of 5 and 6k Red Dragon clips resides on a local 27tb Raid 0 drive. Yes, the project media is large in size and resolution.... but playback is not the problem here. It's Premiere's terrible parsing (loading/saving) of the media, extremely slow display of the timeline, and most troublesome.... bugs.... bugs.... everywhere. Let's go through a few of the current issues I face: 1) Who was the genius that thought that loading multiple projects at the same time should be implemented with no other changes to the interface? Loading up 2 large projects into Premiere creates a cesspool of tabs, sequences, and windows in which it is difficult to tell which sequence belongs to which project. Yes, it's great that I can copy and paste from one project to the other.... a great feature. But why was no other thought put into making it clear which sequence belongs to which project. It's not even clear how one changes from saving one project to saving the other? Merely selecting the project's tab? Projects that are loaded into Premiere (when others have already been loaded) seem to inherit all the tabs and workspace settings of the previous project.... It gets very messy very quickly. Also, copying sequences from one project to another WITH IDENTICAL MEDIA causes Premiere to randomly add new identical copies of the media in your project list. This bug has existed in various forms for over 5 years. Premiere's management of media seems chaotic at best. It can't identify identical media. 2) Workspaces. I swear a new workspace that I've saved only seems to survive for a few sessions before loading of it opens nothing..... just a blank window. I'm forced to resort to one of the default workspaces that Premiere has built in. And Premiere can never remember which monitor to place things on. It keeps on moving the main Premiere window to a new monitor every time I load a workspace. I get so confused and frustrated with workspaces that I've stopped creating them.... I can't create a consistent layout that stays FOREVER.... so I've given up. This makes using Premiere a constant search for where one put the Media Browser, or Effects, or Effects Controls.... Not consistent and certainly not professional-grade. 3) Large project timeline manipulation.... Our film currently stands at 1 hour and 48 minutes..... just over 2000 cuts, with 1 to 8 layers of video (usually 1) and 5 to 24 layers of audio tracks. Premiere can't handle it. If I try to use the A tool to shift some of the footage, the screen freezes for a random number of seconds and eventually comes out of a coma with your media moved to a random location..... but you couldn't tell where exactly it's going to move it because the refresh rate is so slow. I'm not running this on a Pentium 4 with 1gb of RAM and an integrated graphics card. Computers can move 4000 little boxes of pixels at very fast rates.... It's just that the engineering of this software is so bloated and inefficient now that my fast computer has to go through a trillion hoops before it can decide what it has to move.... My work station over the years has multiplied in performance in leaps and bounds and Premiere is getting slower and slower with each Creative Cloud release! It's awful and Adobe needs to clean it's code house. I don't even see how they can keep this mountain of code from completely exploding with their extremely risky concurrent version development for the Creative Cloud. The age and inefficiency of the Premiere code base is showing. I don't think the Adobe engineers even have a chance of tracking down all the inefficiencies and bugs. Is it a million lines of C++ code now? Ludicrous. I pity the engineers that must deal with this behemoth. 4) A low level exception has occurred..... AERedFilter? This happens all the time when editing our project. It's just a matter of time. In order to avoid a fatal crash you need to save the project right away, shutdown, restart Premiere, and reload the project.... If you wait too long, you sometimes can't even save the project.... the project bar just hangs.... and even when it hangs, sometimes the project still does get saved.... it's all so random and unreliable. 5) Even shutting down Premiere and Media Encoder can be a challenge. Sometimes I need to load the task manager in Windows and 'End Task' for Premiere. It can't even shut down without crashing! Also, Premiere seems to spawn a thousands processing threads and if any of them remain alive in some zombie state, you can't restart Premiere. Clicking on the icon will do nothing. And there is rarely useful feedback when something goes wrong. Premiere just starts acting strange. Try running Premiere when your cache drive is full and you'll be sent on a wild goose chase. Premiere's code is not robust nor it's error 'reporting' informative. 6) Edit Clip in Adobe Audition..... Trying to do this on an audio clip from a multi-camera clip creates a zombie wav file that is not properly linked to the project. Quality assurance? What is that? 7) Markers.... I've recently had hundreds of markers for a sequence just suddenly disappear.... Magic. Too bad if you spent an hour placing them and edited for another hour before noticing that all the markers are gone. All in all, I feel that the CC type of release schedule has been bad for Premiere's stability. I suspect the code base is so large and so fragile that perfectly functioning features get broken all the time in Adobe's mad rush to add new features. The most important feature for any professional editor is reliability.... next is efficiency. Premiere is losing both. I moved from Sony Vegas to Premiere 5 years ago because Vegas was getting too buggy. Will I be forced to move to Avid soon? Can any software developer choose reliability as it's most important feature or are we now permanently in a era where beta software is released to the public with an endless patching strategy to address the ever increasing bug list? Does Adobe really feel this is a long-term winning strategy? They do want Premiere around in 20 years, don't they? Maybe not.
... View more
‎Feb 12, 2018
03:32 PM
1 Upvote
UPDATE: I had to abandon using Premiere to edit VOB files. Even after pre-processing multiple VOB files into 1 uniquely named VOB file with MpegSteamClip before injesting into Premiere, I was encountering a seemingly random sync issue where Premiere places video 12-14 frames too early in relation to the audio in exported MP4 files. I haven't noticed any pattern other than it's either in sync or 12-14 frames pre-mature in relation to the audio. This made using Premiere in a professional workflow unusable. I've since gone back to an old but reliable tool, Handbrake. Handbrake interprets the VOB files correctly, does a better job of deinterlacing than Premiere, and outputs video files that are always in sync with the audio. The only drawback is I can't (easily) trim or zoom the video in Handbrake. But audio sync is more important to clients than these other cosmetic tweaks.
... View more
‎Jan 31, 2018
12:06 AM
1 Upvote
Deleting the slstore and pcd directories did the trick for my friend. Thanks kglad!
... View more
‎Jan 28, 2018
10:07 PM
1 Upvote
Hi Kevin, I haven't yet had a chance to try out the new version and am not currently working on a large narrative project at the moment. Looks like the news is positive from others though, so I hold high hopes based on their reports that this import issue is finally resolved. Yet, still, delivery of these updates happens in a vacuum. When I click on the 'more info' about the latest Premiere patch, all that is said is 'this version contains additional format support and minor bug fixes'. Is there another location that lists a more detailed report where we could read something from the engineers saying that they found and fixed a bug related to importing? Is Adobe just hoping that something they changed fixed the import problem? It wouldn't take much to make customers feel like Adobe cared about this horrible problem.... like, for example, at least listing it as something that was fixed in a new version. But if Adobe considers this import bug to be 'minor' or doesn't know if they fixed it, it adds to the feeling that they don't really care.
... View more
‎Jan 11, 2018
03:57 PM
Yes, Ian.... It doesn't matter where the file is located or what format it is. This problem seems to be related to project size. Projects with nothing yet imported into them take a short amount of time to import new media, but import a few files and the wait times grow exponentially very quickly. There is some huge inefficiency/bug in the Premiere import code. It goes into a coma, or over analyzes the current pool of media when adding even a 2 second WAV file. I had a project of about 3tb of Red media, and importing a simple short WAV file would take almost a minute. Yet in versions of Premiere from 2 years ago, imports were normal (instantaneous!) with the same size of project. This currently makes Premiere unusable for professional projects.
... View more
‎Jan 04, 2018
03:18 PM
2 Upvotes
Thanks ReelArts for performing this test. Nice to see what the normal import of 479gb of media should look like. It is unbelievable how a bug like this is not a 5 alarm blaze at Adobe QA. It's been this way for months and not a peep from Adobe. Business as usual.
... View more
‎Dec 14, 2017
05:59 PM
Is it true that if Premiere hasn't finished conforming audio of media in the timeline, and you initiate a render of that timeline in Media Encoder, that the audio will be blank in the rendered file?
... View more
‎Dec 14, 2017
04:40 PM
Hi Warren, I have to disagree that there is a huge advantage in quality by converting to DV from mpeg2(VOB). Video can only be as good as it's source. Sure, DV enables Premiere to parse through the video in both directions quicker, allowing for a smoother editing experience (at a cost of 500% the storage space!), but the visual quality of DV generated from mpeg2 is identical to the source file. Premiere cannot add detail nor quality. Any chroma sampling information added in the DV version is based on the original limited source. Saying that converting mpeg2 to DV creates a huge improvement in quality is like saying that converting a 320x240 pixel camera video to a 4k ProRes444 file will make a huge improvement in quality. And saying Premiere is editing the DVD data structure is not quite accurate. I refuse to give Premiere so much credit with being able to read VOB files. It can interpret a VOB file, which is a very strict version of an mpeg file. It's just another file format Premiere understands. There is no special structure related to multiple files that Premiere is 'editing'. I'm dragging the VOB files onto a timeline. Premiere does not understand the DVD structure and will actually place the VOB files out of order on the timeline if I don't select them in a very specific way. Michael
... View more
‎Dec 14, 2017
02:30 PM
Sorry Warren, but I'm not editing the DVD video structure from the DVDs directly. I'm loading the DVD VOB files from the DVD into a unique folder on a local hard drive. Premiere would lose it's mind if I tried to edit directly off of the DVDs (access times and such). Also, I don't want to upconvert the mpeg2 VOB files into DV files. That would increase the file size from approximately 4.6gb for the DVD to 26gb with no advantage in quality. Premiere has no problem with editing the mpeg2 VOB files. It's having problems with media files that have the same name. I'm sure I'd get the same behaviour with identically named DV files.
... View more
‎Dec 14, 2017
01:42 PM
Thanks for the clarity on the Correct Answer button. I should have realized when every subsequent post was labeled Correct Answer. Whenever I do anything different in Premiere than I did before, I invariably encounter an issue. Sometimes small, sometimes an issue that labels me as incompetent with my clients. I rant on here, the forums, because I have NEVER ONCE received any feedback on a reported bug. At least it allows me to vent my frustrations until the next roadblock I encounter. I once had an in with one Adobe engineer in Utah, who helped me through another horrible Premiere bug that was causing incredible grief while I was editing a feature film.... maybe I should reach out to him again with this latest bug.... just don't have the time to do QA work for Adobe.... just a few minutes to vent.
... View more
‎Dec 14, 2017
01:28 PM
3 Upvotes
Thanks Jeff. No worries. I understand that Premiere stores old metadata based on filename, which is also incredibly stupid. Why would it ever assume that a file with the same name as a previous import is the actual same file. A filename is just that... a name. It doesn't indicate that a file is identical. I'll try clearing the cache as Ann suggests. This is also another of those black magic voodoo solutions that is suggested with every bug I encounter. Caches should help the user, not hinder them.
... View more
‎Dec 14, 2017
01:09 PM
2 Upvotes
Sorry Jeff, but your suggestion is not relevant to my problem because I am using Media Browser to import these files. And this is also a new project not created with an earlier version of Premiere. I appreciate your suggestions but am tired of the black magic voodoo methods that many bring up to solve problems with Premiere. How is it that different methods of import in Premiere DO NOT USE THE EXACT SAME CODE TO IMPORT? And why is the mantra of avoiding project files created with earlier versions of Premiere so prevalent? If Premiere is not backward compatible with old project files, then don't allow it to load them. Period. Some form of half backward compatibility is completely misleading and a complete garbage policy by Adobe, which their marketing department seems oblivious to. Either the CC suite is backward compatible or it is not. Apparently, it is not. Has someone flagged your response as the correct answer to make it appear that the problem I report is user error?.... as if using the 'incorrect' method of import is considered user error?
... View more
‎Dec 14, 2017
12:02 PM
I'm editing many VOB files from different DVDs in the same project. Files from one DVD have the same files name as files from other DVDs, but placed in separate directories. Not only does Premiere get completely confused when previewing the videos (playing video from a completely different sequence than the one selected with the play head), but it replaces the incorrect audio from wrong files when rendering... or drops the audio for certain VOB files entirely. The only way to get Premiere to correctly reference the correct file placed on any sequence timeline is to pre-process all of my VOB files with Mpeg Streamclip, saving one large uniquely named VOB file per DVD, and importing that file into Premiere. How is it possible that Premiere cannot handle files that have the same name? This is beyond amateur.... Professional grade? Really? I'm having a hard time showing people at work that Premiere can be used in a professional environment. I'm having to resort to using a decade old video converter (Mpeg StreamClip) to read and correct issues that Premiere completely chokes on. Combined with the horrible extremely slow import bug that plagues large projects, and the decade old 'Unknown Error' encountered by many during export, Adobe is showing that their software is not professional grade and cannot be counted on in work environments. But what choice do I have? Sony Vegas became horribly buggy 5 years ago, pushing me to Adobe Premiere. Avid Media Composer? Software standards, with the advent of never-ending patches, have turned all customers into beta testers. This is not acceptable yet seems to be the industry norm now. In 4 years of my CC membership, paying an average of $75 CAD/month, I've spent over $3500 to use Premiere. Adobe is repaying loyal customers with terribly buggy software that is only getting more and more buggy.
... View more
‎Nov 25, 2017
12:47 PM
1 Upvote
Actually, I've found the Adobe Bug Report Form to be even a bigger waste of time than venting to these forums. Venting to these forums enables me to share my pain with others that are suffering and hear their tales of foe.... it's therapeutic. Whereas filling out that bloody bug report form feels like the biggest waste of time.... like flushing 10 minutes of my time down the toilet. I've NEVER received any feedback and or engagement from these bug reports. It's like they go into a black hole far in space and are never seen by anyone, ever again... let alone Adobe engineers that are working on fixing them. Surely filing a bug should elicit some response from Adobe... at some point over the subsequent 3 or 4 years.... like reaching out for further clarification of how to recreate the bug, or confirmation that my reported bug was fixed in a future release. Alas, that has never happened. With out any confirmation that someone actually is working on those bug reports, why should anyone spend time reporting bugs?... and do it in a thorough manner, which can take considerably more than 10 minutes? Engagement with those reporting the bugs is like Quality Assurance 101 and Adobe seems to be clueless. And if they have too many reported bugs for their engineers to handle.... and they can't even spare a few minutes to engage those reporting the bugs, then Adobe has some bigger problems.... like too many bugs.... and too few personnel fixing them.
... View more
‎Nov 10, 2017
08:11 PM
It is shocking how inefficient Premiere has become. Most of us, here on the forums, are running high end computers, and yet Premiere gets slower and slower with every release. I'm still suffering with import times in the MINUTES for a dozen clips or WAV files. Adobe, please take the pedal off of the gazillion features pipeline, and, instead, bug fix and optimize. Your code base must be a mess. It's getting worse and worse. There is something very wrong with a program that takes MINUTES to import a bunch of files into a project. It's not useable. My standard procedure with my current workflow is to start an import and come here, to the forums, to vent. Oh, and I demanded my subscription to be free for 2 months. And I'll demand it again in two months if the import bug still exists. Everyone using this beta software should DEMAND the same. EVERYONE! Seriously, if you're here, suffering one of these project crippling bugs, you shouldn't be paying for the Creative Cloud. I'm tired of marketing that sells new updated software when I'm terrified to upgrade knowing there's a good chance my productivity will be destroyed. Demand your refund or free months of subscription today. Please. For the benefit of everyone here. Adobe will only change if they start to feel it in the bottom line.
... View more
‎Nov 04, 2017
11:06 AM
Sorry to hear that you had to do this in order to get a functioning program. Most projects don't turn out well when exported to XML.... as that just keeps basic info about the edit.
... View more
‎Oct 31, 2017
10:49 AM
This problem still persists! I upgraded to the latest version (2018) and the problem is unchanged. It takes over a minute to import one WAV file into my timeline. This is completely unacceptable. I have a very fast computer setup with lots of RAM. I've installed the latest Premiere, latest graphics drivers, and cleared my bloody media cache (which seems to me their default bug workaround methodology for everything).
... View more
‎Jun 18, 2017
02:23 AM
Thanks Matt. It would appear then that all my Adobe sales are through Fotolia's website. Is there any way to prevent Fotolia from selling my videos at resolutions below 720p? Getting $3.60 for a sale is just depressing and I'd rather not sell my videos at that price.
... View more
‎Jun 01, 2017
09:37 PM
3 Upvotes
There is absolutely no excuse for a file import taking 60 seconds. Maybe this would make sense if this version of Premiere was running on a computer from 1995, but with a high end computer from any time in the last 5 years, it should be instantaneous. This is a brutal bug. The latest updates do not fix it. Adobe needs to focus on solid software, not adding as many features as they can cram into every update. Ultimately, editing software needs to be reliable. I'm demanding a refund of my Creative Cloud license fee for every month this bug remains.... And all of you should do the same. Fix your software Adobe! We're not your beta-testers!
... View more
‎May 31, 2017
01:46 PM
I've been contributing 4k video to Adobe Stock for 7 months. In this time I've made 8 sales on roughly 500 clips. The average earnings per clip has been $12.48. Two of the sales generated only $3.60 each. This is very poor. It seems I'm only selling 720p or 480p versions of my clips. Are most Adobe Stock buyers only buying low resolution content? It seems I've only made 1 HD sale and absolutely no 4k sales. At this rate it is certainly not worth my time to upload and tag content at Adobe Stock. What are other contributor's experiences?
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices