harley davis

My feedback

  1. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    More info... Check your playback controls. There may be several software clashes going on.
    First, I found that Adobe DV and the immersive environment both have a few issues when there are external enhancers in front of audio or video. Overlay enhancers, fps enhancers, anything and everything that sits between adobe and the main driver will initially cause problems. That's because the enhancer does a pull data pass, and adobe does a push.
    Without going any further I can give you several possible solutions.
    For me, turning off a dolby enhancer allowed me to pass Adobe DV through. Turn it off before starting the app, turn it on afterward. The "Enhancer" on my system isn't really an enhancer, it just allows me access to all of my speakers, not just left\right. I have a subwoofer and the speaker power level can be much higher than the standard system provides, requiring me to turn on the enhancer to fully activate my speaker system. When I turned this off, Adobe DV was capable of playback again. I suspect it always was, but it didn't get sync info from the enhancer the way it would from the audio system driver.
    If you have any Video enhancers in your drivers, turn them off, start the program and begin playback, during playback turn the enhancer back on and determine if the video stops. If not, leave it be. Stop playback and start again to be sure. If it quits, then keep your enhancer turned off while working.
    I think it's inteligent that adobe passes graphic data to a driver in such a fashion that you can actually have it sent out to external devices in a similar mode, and be synchronized. The downside is that it doesn't give you the ability to choose which hardware device id it uses to do so. It lets you choose a compatible synch driver, like adobe DV or immersive, but it doesn't let you select what path they use to get out. IF you send data to an enhancer, it only acts on the data and passes it out to a hardware driver, not necessarily back to the place the data came from (sometimes the hardware driver passes the data through the enhancer on its own, but if you have to activate the enhancer, chances are it interrupts the data transmission path and looks like a driver enough to be mistaken by some software).

    An error occurred while saving the comment
    harley davis commented  · 

    So... ...I've now made another discovery... ...If I turn off adobe DV, everything is fine. I'm wondering if it wasn't part of the DV library structure that was just removed from windows that might be causing this.
    No it wasn't "Physically" removed, it just cannot be run any longer. It's kind of sad really, that windows is locking out all the library files that older software uses to actually function fully. That means that most software that uses it for playback will start getting errors.
    This is only backed by the fact that some versions of these files are included with some utilities I've downloaded, and are placed in their respective folders to allow access. When these files (same name but older version) are taken out of the folder and replaced with the newer, they function fine. Remove the files completely, and they fail at first. That means that any projection passthrough like adobe dv will fail to function.
    This could also be due to some missing dlls, I've recently removed a lot of vc+ libraries that came with software I no longer need and this really started fouling up. How about an installer that puts it all in Adobe? Not just the "Neccessary" files in the main folder, but actually check for dependencies in the updates, and overwrite once in a while. Even with my beat up SSD I'd take that over missing functions.

    An error occurred while saving the comment
    harley davis commented  · 

    And by rendering, I mean preview cache.

    An error occurred while saving the comment
    harley davis commented  · 

    So it's definitely a mercury graphics problem. I got the same behavior in after effects after rendering a few times.

    An error occurred while saving the comment
    harley davis commented  · 

    Turn off mercury transmit in premiere, turn on in after effects... ...weird.

    An error occurred while saving the comment
    harley davis commented  · 

    I turned off Mercury transmit and it all came back up in premiere. The problem is, now after effects has a larger issue as well.
    I have a feeling this has to do with DV support and the linkage to dvcam devices being dropped in Windows. It's not a big deal, as most can be captured with new shuttle and transfer devices, but most consumer grade are a heaping, stinking pile. So far, premiere is the only one i've been able to use to passthrough a VCR through DV ilink without having a tape in the dvcam, and since most DV footage can be played back natively in AVI, using an intermediary like Adobe DV might just put more strain on the whole system. It's mercury transmit that's causing the problems in playback. Try it without that.

  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Media Encoder » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    harley davis shared this idea  · 
  3. 35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    37 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    Kendra, if you have a cuda card, MERCURY will use it, check the end of the title of the renderer. Mercury playback now seeks out your installed card, checks for renderers, and special renderers are loaded into your apps. If you have cuda, the mercury coding language now uses ubiquitous calls to it, and will pass data to it on your card. It will also utilize the main cpu. It will not forceably only use one or the other. This is due to the latest windows upgrades. Unless you are a super hacker\coder and can write a driver for this, you're stuck with using both. Major effects will out to cuda, but most frames will pass through main-concept to the primary cpu graphics. It does speed some things up, others it drastically slows. It's also better quality.

    An error occurred while saving the comment
    harley davis commented  · 

    Hey guys. Sorry if this is a bit late in the game.
    Yes the paired streams have a problem, no adobe didn't break it, and you can get past it easily.

    First, We just want the audio to come out right, correct? So all we want is audio. I want you to render out all of your subclips using AME and the WAVEFORM preset. Drop them in and drop it on, set and render the audio out. Now create a bin for subclip containment, create another for subclip sequences. select all subclips, and use the menu to create sequence from clip. In each sequence you will replace the audio with the file you just rendered out. Replace the subclips in your main sequence with your new sequences you just created and built. The audio will line up.

    The drift is caused by a problem with frame drop that occurs when your stabilization is on, so the number of frames doesn't actually match the timecode. Manufacturers mistakenly thought that doing this would enhance quality when the video was played back (it either creates a blended smudge or a single still frame), and allow the compression algorithm to function better, saving space on small memory cards. This didn't work. For a while, most software had a problem with this, and after some redesign, most use multiple stream clocks, one for video, one for audio, and both are played simultaneously and kept in sync by a third clock that shows where they should be. If a frame is missing or dropped, it gets blended or still-repeated, leaving the audio at each frame in sync. This also has drawbacks. When the two clocks are so far apart that they don't sync at the second mark, they can drift, so many software manufacturers employ methods of dropping audio samples (smaller than a frame) to make up for the drift, or they speed ramp the audio to correct it. Much of the time it isn't noticeable, but it takes accuracy out of your work, and can be troublesome if music and other tonal qualities are important. For me they are, so I just use the method above as a "Pre-edit", rendering out my entire set of files first to a video file, and audio file separate, then sequence together, then output to a set of clean dailies. Prelude used to be able to do this with the FRAME BLENDING mode, but recently this has been broken. I'll try the other modes later, but it used to work in AME as well.
    CORRUPTED AVCHD folder? AVCHD is a corrupted version of MP4 compression! Of course the folder's corrupted! Whatever numbskull told you the folder was corrupted was probably not a video engineer in any way, just giving you a run around so you'd leave them alone. The formatting the camera employs is the problem. Get a new camera, turn off stabilizer, use tripod. When you cannot control those three, use my method. Works every time.

  4. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Audition  ·  Flag idea as inappropriate…  ·  Admin →
  5. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Audition » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    For all wondering, this is an Optimus problem with nvidia and amd gfx cards. There’s a fix for nvidia, not sure about amd Radeon etc.
    For nvidia check the forums for white screen in adobe dimension

    An error occurred while saving the comment
    harley davis commented  · 

    Durin, yes. I used an earlier version that worked. 11.0 worked. I found the problem and it is fixed now. I would love to elaborate on it, as it affects NVIDIA primarily, but it can happen with other setups. My setup has an intel builtin graphics CPU based controller and a GPU by Nvidia, in a laptop. The culprit is OPTIMUS. I had to download the nvidia profile inspector (not the graphics driver or control panel), then find the optimus setting in the global profile, set it to enabled, then apply changes, click on create new profile, name it for Adobe Audition CC (I also did this with Dimension CC), click the "add application to profile", and point it to the EXE of audition (and dimension), and then click apply changes for each profile. After this, they all worked. The microsoft DLLS for optimus do not cut it for these apps. Something is amiss. The Nvidia DLLs are used when I force it to Enabled in the profile inspector. Some apps have this done already, some don't but still work, due to support in the windows provided DLLs. Either way, they are working now.

    An error occurred while saving the comment
    harley davis commented  · 

    I've tried everything from permissions on the cache files to reinstalling. No help. Please get on this as soon as you can. It's not my primary recording interface, but it is my primary audio for video interface. I have a lot of work pending. I'll have to go to something else until you fix this.

    harley davis shared this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Audition » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    This sounds like the optimus bug. You need to activate it for your graphics card. for nvidia you need the profile inspector. google it. It's not the control panel. The profile editor will allow you to force it to be enabled on the card. Open the profile inspector, in the main area (biggest section) scroll down to find the Optimus setting under the OTHER heading. Set it to ENABLED. click apply changes. Restart and try audition again. If this doesn't work, there's another step. But message me if you need that one.
    Other cards will have GL and optimus in their control panel, so you can set it to use your discreet card.

    If you don't have a discreet graphics card, update your graphics drivers from the intel site, download the drivers on your own, and install them. Don't use "Wizards" on the site. You may have some broken files in your current drivers and they will not get scanned, only the version. You can repair optimus and any other damaged settings with an over the top install. Restart, and try again.

  7. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Audition » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    It's Windows Optimus. At least it was for me. Do you have a discreet graphics card? Radeon or nvidia?
    If so, you need to force optimus into enabled mode. On nvidia, you need to google Nvidia Profile Inspector, and get the version 2.9.x. Get a Zip folder, then unpack to a folder, and put it in
    Program files/Nvidia Corporation/ folder, then open the nvidia profile inspector program, and set the global values. Find Optimus under "Other" in the big part of the window. Change it to reflect an ENABLED value. Apply changes. restart and try the app again.

  8. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Audition » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    Do you have an nvidia or similar discreet graphics card? If so, you have fallen prey to optimus bugs. Optimus is a software controller that sends rendering from the program to the discreet card, and then to the intel layer for the screen.
    For nvidia, you need to download the Nvidia Inspector, latest version, with the Nvidia Profile inspector. Don't open your Nvidia graphics control panel. Just put the profile editor and inspector into your C:/Program files/Nvidia Corporation/ folder. Open the profile inspector. It will have a global setting to start. This is the best way to go. Start by going down the list to OpenGL renderer, and switch it from auto to the first odd-name value in the list. This will let gl processing go to your discreet card. The name of the value is on the left, the actual data in the value on the right, and the data is a dropdown list, so click it. It may look greyed out, but it works just fine. Go down to Optimus... ...The name has optimus in it, but is different on some cards. Set it to the first Enabled value in it's dropdown. This will allow it in most apps. Now apply the changes. Then restart and try the apps. IF they are still bunked, you can go back to the profile inspector, and click the "New Profile icon", copying the global to a new profile for your apps. Name it for the app you are targetting. Apply changes. THen find the icon with a + at the top, it will add apps to your profile, and select the EXE of your bunked app in your program files. Apply changes. Restart and try the app again. You should see them working. If not, you have some other graphics problem.

    Other cards have a control panel, they might have an optimus enable feature. Update your drivers and try to find it. Turn on opengl and make sure it's set to use your discreet card, not set to automatic.

    These fixes have worked for me, they should work for you. I had the same problem, audition and dimension both had it. After enabling optimus for them in the profile editor, they were fine.

    alternatively, install 2-3 versions lower of audition. Older versions tend to work. 11.0 and lower.

  9. 58 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    harley davis commented  · 

    What about adding a queuing function to the menu that will queue the renders to Adobe Media Encoder for background renders. You could then initiate the render at your leisure. Of course, if the render were started immediately, it would still allow for queuing multiple renders, all while you continue to work. However, you would also need access to each of the sequences being rendered, which would require XML access to the sequence and direct access to the video sources. To keep this from being interfered with, I wouldn't mind offlining the clips affected until the render is complete. It would allow me to move on to another section, keep me from getting a kind of tunnel vision on any one section and promote best artistic practice.

    harley davis supported this idea  · 

Feedback and Knowledge Base