Media encoder cc pauses  while I edit in premiere cc!

If I try editing in premiere cc while encoding in media encoder cc, the encode pauses. what gives?

If you'll notice your encoding in AME, it normally maxes out all your CPU cores.  It does mine.  This is awesome!
But, if you want to edit, you need those cores, especially with Long-GOP footage that relies on CPU for real-time decompression.  So, in effect, you're telling your computer to let Pr take over the CPU when you start editing in Pr.
It's a pretty smart way that Adobe enabled this behavior, if you ask me.

Similar Messages

  • Media Encoder CC crashes while working on queued H264 files.

    While I am editing my videos I send them to Adobe Media Encoder CC as H264 for youtube.  Even with only encoder running windows 7 crashes with the blue screen.  This is the only program that causes this.  I was looking to uninstall this program and it is not an option in control panel.  Do I have to uninstall Premiere CC to have this removed?  I was going to try an uninstall/reinstall to test if this fixes it.  The machine is a current machine with 64GB ram running on SSD.
    Thanks all

    A BSOD on Windows 7 is most often a sign of a serious problem, much more frequently caused by faulty hardware or driver than the actual software running when the crash occurred.
    As exports often push a system to it's limits, I'd probably start by looking at the cooling of your system.

  • Adobe Media Encoder CS6 hangs while encoding Quicktime movies

    Every day I am enoding 2-3 videos 15-40 min long with AME CS6 and every second day it freezes or slows down to almost zero. The source material is mostly Quicktime ProRes 422 LT 1080 25p or Quicktime XDCAM EX 1080 25p. Target files are H264 videos in different sizes. The workstation is a MacPro 5.1 Xeon 8core, 12GB Ram and Nvidia Quadro 4000 with OSX 10.8.2. Only restart of the computer helps but just for a while then it slows down or freezes again. I am also using Davinci Resolve 9 lite which is sometimes not able to adress the QTencoder when AME is open ... ?
    Any Ideas for a solution?
    Thank you!

    I think it is a problem of Adobe QT32 Server. Adobe Media Encoder is encoding all Quicktime Movies through this Adobe QT32 Server, which is somehow the link between Adobe and Quicktime. But since Adobe QT32 Server is a 32bit application and Adobe Media Encoder a 64bit application it somehow blocks the Media Encoder. And if you have other applications running which somehow try to use Quicktime codec when Media Encoder is using the Adobe QT32 Server than everything slows down or collapses. These are my observations so far. I avoid any other video application as long as AME is open. For example: I close Davinci Resolve when I want to launch AME and close AME when I want to launch Davinci Resolve. This helps so far.

  • Adobe Media Encoder will not lauch for export in Premiere Pro CS4

    Firstly, I can launch Adobe Media Encoder from Windows Explorer.
    So, stand-alone it works
    The problem is that is will not lauch if I click on a sequence
    and select Export Media.  No AME splash ever lauches,
    after  a few minutes I wait but have to click escape to get
    back to the sequence.
    Adode Link to Encore works fine.
    Thanks

    Deactivate
    Uninstall
    Run Cleaner Tool
    Re-install.
    http://www.adobe.com/support/contact/cscleanertool.html

  • Adobe Media Encoder Dynamic Link Server NOT CONNECTING to Premiere Pro

    I have Media Encoder CS5, as part of the Creative Suite 5. My programs say that I have no updates to install, so everything is up to date.
    I am having an issue with the dynamic link server.
    Here's what has happened thus far.
    Recently when I have tried to encode a project sequence from Adobe Premiere Pro it DOES NOT work. This is the first time that has happened.
    I repeated the process and again, it still happened, unable to connect to the Dynamic Link.
    The Error messages that I was getting was "could not read from source. Check if it has been moved or been deleted"
    Once, I received this, I went to check to see if all files were linked properly, and they were. Everything was rendered and all was good in the timeline and the project itself.
    Yet, again, the error message appeared.
    Then I tested a previous project that I knew had been exported and worked through Adobe to Media Encoder. And all the files were linked properly and yet again received the error message I wrote above.
    Then I thought the Dynamic Link itself wasn't working properly, so I tested importing an Adobe After Effects Comp into a Premiere Timeline and it DID WORK.
    Then I went and tested if a video file of an already exported project would be able to sync to Media Encoder. And this WORKED.
    I then went to add the file directly from Media Encoder and when I went to add a sequence from a saved Premeire File, it would take about 5 minutes "Connecting to Dynamic Link Server", to then state, "Connecting to Dynamic Link Server Failed"
    My question is, how do I fix the dynamic link between Media Encoder and Premiere? Because, additionally, importing and After Effects Sequence works with Media Encoder.

    I've been searching/troubleshooting for days, none of the firewall, new shortcuts in folder, antivirus, you name it I tried it even wiped my system which seemed to work at first..
    What did it for me in the end was I had Dxtory (a software recorder, for recording gameplay) running on startup, and somehow it interfered with only Premiere projects in Media Encoder, I could still import AE projects go figure.
    Check all the programs you have running or use sometimes, if they have some sort of hook into other programs/deal with video/codecs this could be your problem too!
    Thanks to everyone trying to solve this problem!
    -JonOfAllGames

  • Media encoder exports seem overexposed - compared to within premiere pro

    i'm having constant issues with basic grading in premiere cc14 and then exporting with media encoder (h264) and things looking much brighter / overexposed on the SAME monitor.  its not a calibrated monitor (web vids only - although i know i need to remedy this) but this is happening on same monitor so problem must be in the encode, right?  others experiencing same issue have a good work around?  currently - i'm having to watch the h264 export and then go back and re-grade for that.  Pain.

    Why don't you just export from Premiere?

  • Can't Edit While Encoding With Media Encoder

    Does anyone else get this happening to them:
    When I begin the encoding process with Media Encoder, then go back to editing in Premiere Pro CC, EVERY time I hit the space bar to play a clip, Media Encoder Pauses its Encoding. Then when I stop playing the clip in Premiere Pro, Encoder begins encoding again. I'm fairly positive that Adobe touts that you can be encoding and editing at the same  time, but I can't believe that this is happening. Anyone else?
    Also, Encoder refuses to use my destination folder preference, instead targeting a folder I had used long ago and I have to manually target for every encode, every day.
    THANKS!!!

    Encoding is a real CPU/disc hog ... heh, it's an intensive process. Trying to both encode and playback in real-time ... um ... if you've got a rig with say four CPU's with 128GB RAM, two really hot v-cards that the Adobe program actually love to play with, and all programs/cache/footage/outputs on RAIDed SSD internal drives, you can maybe do both at the same time.
    Think about what playback is doing ... it's not just playing the video off the disc ... not hardly. It's taking bits of video from this spot on the disk, skipping to this section of another video file there, to that one here ... and while doing that it's also immediately "reading" whatever changes you've made in editing, whether sound, size changes, color/grading, masks, EVERYTHING ... and applying that to the video it's grabbing of a disc somewhere AS it is playing it. Using a ton of CPU, disc read/write throughput, and probably a chunk of the v-card's GPU & vRAM. What's left for AME to use?
    I've seen a lot of complaints around here as to why editing playback isn't smooth ... hey, in VLC, play that file, it plays back easy, what the * is PrPro doing?
    Um ... VLC is playing the "straight" file, PrPro is playing back the file with all the other stuff added to it ... which isn't yet added to the file in reality, it's only instructions as to what to do to the file. So ... PrPro is essentially doing much the same work as when AME renders to an output simply to play the file in the program monitor.

  • Using Premiere CC and Media Encoder CC at the same time

    Is this possible?  Doesn't seem to be.  Media Encoder bails on every job as soon as you try to render anything in Premiere.  I guess they don't play nice together, which is surprising.  I was hoping that Media Encoder would pause and wait for Premiere to finish a render.  Instead it dies on every render job, creating 0 size video files... while making a sheep bleating sound.
    Is this a GPU issue?  I have 2 nVidia cards, a 770GTX and 560GTX. (Windows 8.1, 16gb RAM, 3770k CPU)

    As soon as I initiate a render in Premiere, Media Encoder bleats, and all subsequent render jobs bleat and produce 0 size video output files... even if I quit the Premiere render before Media Encoder reaches some of those render jobs.
    I suspect this is a GPU sharing issue.... but can't be certain.
    What do you mean by new install?  Did I install it (AME or Premiere) recently? No.  I've had Creative Cloud on my machine for almost a year, and both Premiere and Media Encoder have been updated periodically.
    To my knowledge they have never worked together, but I only started using the queue feature within Premiere recently, so I haven't used AME until recently.

  • Premiere Pro CC not queuing exports into Media Encoder CC

    I try to make this simple...
    standard export from PP CC to ME CC
    File -> export -> media, then hit queue.
    Media encoder opens and just sits there. Left it for hours to see if anything would ever happen, and nothing ever did.
    I've restarted the programs and machine dozens of times and that does nothing.
    I can still export from PP CC.
    I have no CS6 products left on my box.
    I also tried to open the project from Media Encoder and load the sequence that way with no luck.
    Thanks for the help!
    On a Mac Pro
    Premiere version 7.0.1
    Media Encoder version 7.0.1.58
    Adobe Creative Cloud for Teams Member (so it's licenced and updated to the fullest)

    rforgaard wrote:
    I had this exact same problem, and I figured out the solution in my case.  I know the original problem report is ancient, but there are recent replies, so I am adding my solution here.  I spent untold hours figuring this out, so hopefully this will save someone else some time.
    There can be other causes to this problem, I'm sure.  I'm just telling you about what fixed this problem for me.
    Just to clarify, here is the symptom: Running Windows 8.1.  Standard export from Premiere Pro CC 2014.2 to Media Encoder CC 2014.2, using File -> Export -> click Queue.  Media Encoder opens and just sits there.  Premiere Pro is hung and has to be forcibly terminated.
    I spent countless hours on this.  I thought I had messed up my computer's configuration somehow, so (believe it or not) I re-installed Windows on a freshly formatted hard disk, re-installed Creative Suite, same problem.  (I can't believe I wasted all that time; I feel like a dummy.)
    I finally narrowed it down to a very simple test case with a very tiny one-clip sequence that is less than one second long.  Same problem.
    It turned out to be a problem in the Premiere Pro project file itself.  I suspect that a small file corruption somehow snuck into the project file, that was completely invisible.  In that clip in my project, if I removed the "Vocal Enhancer" effect, the problem with exporting to Media Encoder went away.  If I then re-added the very same "Vocal Enhancer" effect, the problem was still gone.  It must be some small corruption in the ".prproj" file that went away when I removed the "Vocal Enhancer" effect and re-added it again.
    NOTE: I DON'T think that there is some kind of bug with the "Vocal Enhancer" effect.  I don't think this problem has anything to do with "Vocal Enhancer" per se.  It is just some kind of small generic corruption in the project file.  When Premiere Pro tries to export that sequence to Media Encoder, the problem occurs.  It was just a coincidence in my case that removing and re-adding the "Vocal Enhancer" effect made the problem go away.
    BOTTOM LINE: If you find that you have this bug where Premiere Pro hangs when exporting to the Media Encoder queue, try the following: Create a brand new project with a single clip in it, and export it to the Media Encoder queue.  If that works, you know that it is not a problem with Premiere Pro in general; it's a problem in your specific project file.  Once you've made this determination, make a copy of your original project file, and remove clips from the project until the problem goes away.  Keep narrowing it down until you find the clip(s) that are the issue.  Then, try removing and re-adding any effects on those clips, or even removing and re-adding the clips themselves, to fix the problem.  Eventually, by removing and re-adding a specific effect or clip to your project, the problem will vanish (hopefully).  It's just a matter of narrowing down which half of your project the problem occurs in, then which half of that half, etc., until you have it narrowed down to one clip or group of clips that need to be removed and re-added.
    Having said all this, it is a bug that ideally should be fixed so someone else doesn't spend untold hours trying to figure out the problem.  To that end, I create a tiny ZIP file that just has project file and the single media clip needed to reproduce the problem, along with a small description "READ ME.txt" file that explains the very simple steps to reproduce the problem.  I have submitted this as a bug report to Adobe using their official online bug report form at www.adobe.com/cfusion/mmform/index.cfm?name=wishform along with a link to the ZIP file so they can download and reproduce the problem.
    If anyone else is curious about reproducing this same bug, you can also download the small ZIP file if you want to.  I guarantee it doesn't have any viruses or anything - it's just two small files to reproduce the problem.  To download the ZIP file containing that project file, media file, and "READ ME.txt" file, you can get it at www.forgaard.com/files/PremiereProBug.zip.
    I hope this saves someone some time.  This one sucked up a zillion hours of me chasing apparitions.
    I was having a problem with exporting a sequence to AME.  PPro would freeze and I would have to force the program to close.  This was on a project where I was just running out a bunch of interview clips for the director to look at.  One of them had a audio effect (DeHummer) on it, and it was the one that was giving me troubles.  I selected the audio and right clicked then "Render and Replace" then it would export to AME with no issue.  Thank you for your well written response to this thread.  While it may not have fixed the OP's issue, it did help with mine....
    Thanks,
    Phil

  • Is adobe media encoder in cloud or CS6?

    is adobe media encoder in cloud or CS6? ... maybe as part of flash, flash builder or premiere?

    Yes - Media Encoder will be installed when you download Premiere Pro, After Effects, or Prelude.
    EDIT: Also Flash Pro

  • Adobe Media Encoder CS5 APPCRASH

    Hi,
    I work for a television station, and we use Adobe Creative Suite 5 Production Premium.  Just recently for some reason or other our Adobe Media Encoder (AME) stopped working.  We primarily export files from Adobe Premiere as .mpg files.
    When we check to make sure we have the lastest version, Adobe says that everything is up to date.  I would rather not have to uninstall the whole suite and reinstall it if I don't have to.  I will include the Problem Signature below.
    Problem signature:
      Problem Event Name:                        APPCRASH
      Application Name:                             Adobe MediaEncoder.exe
      Application Version:                           5.0.1.0
      Application Timestamp:                     4c5bf70b
      Fault Module Name:                          WatchFolder.dll
      Fault Module Version:                        0.0.0.0
      Fault Module Timestamp:                  4c5be8ec
      Exception Code:                                  c0000005
      Exception Offset:                                00000000000121c5
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  cb30
      Additional Information 2:                  cb301b219f00a7389521aa91a1040f24
      Additional Information 3:                  d870
      Additional Information 4:                  d8706e5301f2031a9794be034fc115b2
    Any help would be greatly appreciated.  Thanks.

    I am still unable to get Adobe Media Encoder to work on our edit computer at the telvision station I work for.  I just did a clean install of Adobe CS5 using the Adobe Cleaner Tool before reinstalling.
    I tried to open Media Encoder to see if it would work and I have the same issues I have been having.  The error is below.  All I am doing at this point is trying to open the program.  It does the same thing when I try and queue a video file in premiere.
    Problem Event Name:    APPCRASH
      Application Name:    Adobe Media Encoder.exe
      Application Version:    5.0.1.0
      Application Timestamp:    4c5bf70b
      Fault Module Name:    WatchFolder.dll
      Fault Module Version:    0.0.0.0
      Fault Module Timestamp:    4c5be8ec
      Exception Code:    c0000005
      Exception Offset:    00000000000121c5
      OS Version:    6.1.7601.2.1.0.256.48
      Locale ID:    1033
      Additional Information 1:    cb30
      Additional Information 2:    cb301b219f00a7389521aa91a1040f24
      Additional Information 3:    d870
      Additional Information 4:    d8706e5301f2031a9794be034fc115b2
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    I would greatly appreciate some help on this matter.
    Ryan

  • Media Encoder 2014 - Dynamic link Premiere/AE - refresh problem

    Hello,
    I'm working on a edit with AE compositions into Premiere linked by the dynamic link. When i change something in AE it's updated in my Premiere timeline as expected.
    Now i want to export my edit to Media Encoder. But sometimes the export doesn't show the last change in AE !
    The only way i found to get this AE change in the Media Encoder is to quit Media Encoder and send again my edit.
    Is there a easier solution ?

    Kevin, the link work different whether you send from AE or load the comp into AME.  ie you can see the full path to the original comp when you load direct to AE.
    Ideally for the items loaded direct into AME there needs to be a right click "reload updates from last saved AE file".  Now that would be expected behavior

  • CS4 Media encoder - Crop+Resize problem

    I`m attempting to both crop and resize a video at the same time.
    I have an AVCHD 1920X1080 premiere CS4 project. I export it to media encoder.
    I`m attempting to encode it to flv or f4v.
    After having cropped the video in Media encoder I would like to resize it but then I encounter a problem:
    I have 3 options in the output settings:
    Scale to fit/Black borders/Change output size.
    `Black borders` is not what I want. I need my frame to contain nothing outside of the image.
    If I choose `Scale to fit` the video immidiately becomes terribly blurred. It can`t be not a resolution issue as the size is 429X622 after the crop and the original is HD (and if I encode it the result is accordingly strangely blurred) I can resize the video but it will be `blurred`.
    If instead, in the output settings I choose `Change output size` I get a normal video image (no blur, that is)  but the the `resize video` interface under the `video` tab is disabled - it is greyed out ( even though the checkbox next to it is still marked) and the width and height boxs are greyed out too. I can`t resize.
    I`ve attached to this message a JPEG capturing a part of the frame to show the strange blurring problem as well as the greyed out `Resize` interface.
    What am I doing wrong ?

    Jim Simon asked:
    But isn't that the size you want?  If not, how did it get set that way?
    Thanks for your interest, Jim Simon. Well, no, it`s not the size I want. I want to be able to resize at will, after I had cropped. How did it get set that way ? I got that 429WX622H frame merely by cropping the original 1920X1080 frame by using the `Media encoder` crop function, while the output is set to`Change output size` . If I would go now and rechange the size of the cropping frame I would get different dimension numbers. But as to how it got `set` this way, and now I refer to the word `set` as in `not being able to change anymore, being greyed out and disabled` - I have no idea at all, and this actually stands at the core of my bewilderment. If i choose to go about it differently and change the order of actions by resizing first and then cropping, for example, if I would choose first to change the size of the video from 1920X1080 to let`s arbitrarly say: 720X440 and then I would go and crop it in order to exclude from the frame certain imagery that I don`t need, then, Oddly enough, my previous resizing action will be strangely ignored and the cropping is re-calculated from the original 1920X1080 frame. I may even end up with a  `crop` which is larger than my `resize`.
    In other words: I need to be able to change both what I include in my frame and the final video resolution, and media encoder would not allow it in `Change output settings`  and it would allow it in `Scale to fit`  but then it insists on adding a strange and impossible bluriness effect even in the result encoded video.

  • Hilights Clipping Problem with Premiere CS3 Media Encoder

    I've just discovered a pretty serious problem with the way Premiere CS3 processes video to the Media Encoder.
    Many of you are familiar with the term "super whites", the ability of modern cameras to capture and record levels above 100 IRE. With HDV and newer technology, recording to 109 IRE is quite common.
    I was aware for some time that importing this footage into Premiere results in a hard truncation of whites above 100 IRE. However, I discovered last month that the Fast Color Corrector has a Output Levels adjustment that can rescale all the levels to fit down in the 0-100 IRE range. I verified this using the scopes in Premiere and by observing recovered details in my footage. I was even able to export frames to TIFF files and show the recovered highlights in the exported TIFFs. The difference is substantial and not subtle--it's the difference between a sky completely blown to white and one where you can see the sky is blue with clouds in it.
    Last night, I discovered that the Unsharp Mask filter doesn't handle footage above 100 IRE, either. Even if I use Levels to set 0-235 RGB range, somehow, Unsharp Mask is processing the un-level-adjusted signal, regardless of stacking order of the filters.
    I rendered two Blu-ray discs, one with Unsharp and the other without. To my astonishment, BOTH discs lacked any detail in the highlights--the whites were clipped at 100 IRE!
    Now I turned attention to the Media Encoder. Pausing on a frame where I can see the difference between 100 IRE and 109 IRE and shades in between, I fire up the Media Encoder and note that even in ME's previews screens, the whites are already clipped. There is more highlight detail in the program monitor, whereas it's all gone in the Media Encoder's display.
    It is obvious that highlight information, even scaled back to 0-235, is being treated as if it were 0-255 and clipped at 235 before passing to the encoder. This is a real disappointment, because there is another half f-stop of detail up there that I was trying to pull into the useable range of 100 IRE for the Blu-ray disc. Since it is very difficult to shoot footage and limit the peak whites in-camera to no more than 100 IRE, nearly all of us are losing valuable picture information.
    Even if you can recover the highlights on the timeline through a Levels filter, it gets thrown away again on the way to the Media Encoder. Short of exporting a few hundred thousand frames as .TGA files and then loading those back in and rendering out to whatever motion CODEC, I am at a loss as to how to get Premiere to leave the whites intact.
    I haven't seen this issue discussed in any detail here. Has anyone found a way around it, besides reshooting all your footage of one-time events to sub 100 IRE levels?

    I'd rather the camera added that extra lattitide within the appropriate 0 to 100 IRE range.
    That's a lot like saying you want 10 gallons of water in an 9-gallon jug.
    As it is, it looks like such adjustments will need to be done on a clip by clip basis.
    Or, you can do it the "Dan" way in AviSynth. I wrote a script function called SoftLimiter: It applies photoshop-style curves on the Y + U + V channels to bring the maximums within legal range… using a sort-of "soft-knee" approach to reducing extreme highlights and/or oversaturated areas.
    It causes a tiny bit of posterization in the highlights, just like all 8-bit per channel color adjustments do… but it is hardly noticeable on a computer screen and even less on TVs.
    SoftLimiter for AviSynth 2.5
    Create a folder C:\SoftLimiterCurves\ and place the .amp curves files in that folder.
    Place the other files in your AviSynth 2.5 / plugins folder.
    The example below assumes DV avi files and requires a DV codec (such as Cecocida DV, MainConcept, Canopus) that can read / write in YUV formats.
    Create a script like this:
    AviSource("dv.avi", pixel_type="YUY2")
    SoftLimiter()
    Open the script in VirtualDub, use Video / Fast Recompress, Select Cedocida DV codec. File / Save as .avi
    Before:
    After:
    And, Jim… you can place your dv2film() command at the end of this script if that's what you're trying to accomplish.

  • CS4 Media Encoder Crash after rendering - two files, help?

    I'm not a professional so I would appreciate any advice you can offer.  I was encoding a WMV HD video (edited in Premiere Pro from CS4) that was just under 2 hours long.  On an i7-920 with 9GB of RAM, it took just over 16 hours.  At the end of the encoding, the Media Encoder bar displayed 0:00:00 time left.  But it then froze at that point for about 30 minutes.  Then the program crashed.  I planned to take these WMV files and put them, via Encore, onto a dual-layer DVD with a few other special feature-related videos. 
    I now have two versions of the file in the destination folder, one that has the title I gave it and another that has a "._00_" before the title.  Both files are .wmv files and the one with the normal name is 6.64 GB whereas the one with the ._00_ before the name is 6.60 GB.  Both have problems if I try to play them beyond the 60% or so point.
    Is there a way to salvage these files without another 16 hour render? 
    How long should I expect, on a normal/successful render, for Media Encoder to continue to process the file after the countdown reaches 0:00:00?
    Thanks.  Any advice for this very untrained editor would be appreciated.

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

Maybe you are looking for