A low-level exception occurred in: HAP Video (Exporter:9) #41
Labels
help wanted
Extra attention is needed
Milestone
Comments
|
Sorry, should have added...This is in Adobe Premiere CC 2020. Thank you. |
|
Thanks for the report Sam, will have a look into it over the weekend. This plugin hasn't been tested in CC 2020 yet - are you getting the error for all exports? |
|
Thank you for the reply. Yes all the Exports I attempted with a couple different project files resulted with the same type of error. I also tried the different encoder settings just to see if it made any difference and I could not get a positive result. I understand that this version of premiere is a recent release and don't hold that against you. If you need me to do any other testing whether it be on the current version of the encoder or a new test release that you build let me know.
Sent from my Verizon, Samsung Galaxy smartphone
…-------- Original message --------
From: Greg Bakker <[email protected]>
Date: 1/17/20 12:47 PM (GMT-05:00)
To: disguise-one/hap-encoder-adobe-cc <[email protected]>
Cc: Patrick Sanphy <[email protected]>, Author <[email protected]>
Subject: Re: [disguise-one/hap-encoder-adobe-cc] A low-level exception occurred in: HAP Video (Exporter:9) (#41)
Thanks for the report Sam, will have a look into it over the weekend. This plugin hasn't been tested in CC 2020 yet - are you getting the error for all exports?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://link.zixcentral.com/u/4e0cd01a/ivodfVE56hGO-rH_hnsoMg?u=https%3A%2F%2Fgithub.com%2Fdisguise-one%2Fhap-encoder-adobe-cc%2Fissues%2F41%3Femail_source%3Dnotifications%26email_token%3DAGBC5Z5JDPUCMFRDBGGOHZLQ6HVMLA5CNFSM4KC5VDUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJIONEA%23issuecomment-575727248>, or unsubscribe<https://link.zixcentral.com/u/d423060b/dFYefVE56hGO-rH_hnsoMg?u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGBC5Z7SA23RNVRL5IF4UTTQ6HVMLANCNFSM4KC5VDUA>.
Links contained in this email have been replaced by ZixProtect Link Protection. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.
|
|
Thanks Sam, I've uploaded an alpha build of the new release at Along the way, whatever was causing the problem with CC 2020 seems to have been eliminated - I've just checked basic roundtripping in AME 2020 and AEX 2020. Please let me know if it's still causing issues for you. |
|
Haha, cheers Patrick! |
|
Hi Patrick, have made some fixes to framerate snapping (AfterFX plugin was incorrectly transcribing 5, 10, 15 and 23.98fps, Premiere plugin wasn't simplifying premiere-provided framerates; an issue for some media servers). Please find them in 1.2.0-alpha2 on the releases page. |
|
Ok, I will test it out and get back to you.
Sent from my Verizon, Samsung Galaxy smartphone
…-------- Original message --------
From: Greg Bakker <[email protected]>
Date: 1/21/20 7:57 AM (GMT-05:00)
To: disguise-one/hap-encoder-adobe-cc <[email protected]>
Cc: Patrick Sanphy <[email protected]>, Author <[email protected]>
Subject: Re: [disguise-one/hap-encoder-adobe-cc] A low-level exception occurred in: HAP Video (Exporter:9) (#41)
Hi Patrick, have made some fixes to framerate snapping (AfterFX plugin was incorrectly transcribing 5, 10, 15 and 23.98fps, Premiere plugin wasn't simplifying premiere-provided framerates; an issue for some media servers). Please find them in 1.2.0-alpha2 on the releases page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://link.zixcentral.com/u/11d95427/bCwEiU086hG5bKsBC2wmKA?u=https%3A%2F%2Fgithub.com%2Fdisguise-one%2Fhap-encoder-adobe-cc%2Fissues%2F41%3Femail_source%3Dnotifications%26email_token%3DAGBC5Z6G4V37DXQC6YYOFMDQ63WJ7A5CNFSM4KC5VDUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJPUK2Y%23issuecomment-576669035>, or unsubscribe<https://link.zixcentral.com/u/eba1695c/dnIEiU086hG5bKsBC2wmKA?u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGBC5Z2EAHSXPZUHCZ3FZWTQ63WJ7ANCNFSM4KC5VDUA>.
Links contained in this email have been replaced by ZixProtect Link Protection. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.
|
|
Hello again...Here are the latest testing results I have to offer (see below). I am going to continue to test using different frame sizes/ratios to see if that is a factor. The same error as indicated in original post is coming up for Premiere CC2020. The following error report was generated in AE CC2020: |
|
Let's focus on the Premiere testing to start off with. Please note that I've been using Media Encoder, but that uses the same engine as Premiere. I'm just going to check in Premiere. |
|
Understood...Yeah, I had tried ME previously; but not yet with this release. |
|
It's working in my copy of Premiere, so it's not that. Would you mind temporarily enabling a debug trace please. Do this by placing a file called with YourUserName replaced appropriately. When you re-run the export, you should end up with a file called HAP-log.txt on your desktop. Then please send that to me. |
|
OK, working on that now. |
|
The output file is attached. |
|
That's not the one from the HAP plugin, is there another file?
…On Tue, 21 Jan 2020 at 14:28, SAMincDEV ***@***.***> wrote:
The output file is attached.
HAP_AE_CC2020_Crash_Report_20200121.txt
<https://github.com/disguise-one/hap-encoder-adobe-cc/files/4091490/HAP_AE_CC2020_Crash_Report_20200121.txt>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=ABVIOE55HHGR24ZYQSS5TTDQ64BBVA5CNFSM4KC5VDUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJP5OWA#issuecomment-576706392>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVIOEYDTHA3MLITH4FWORTQ64BBVANCNFSM4KC5VDUA>
.
|
|
[you'll need to restart Premiere I should add] |
|
Sorry, I see that is that is the AE one...My apologies. One moment and I will get back to you. |
|
Another thing - what is the full path to the output file you're writing, and its name? |
|
There does not appear to be a new file generating to the desktop. The included images show where I have placed the config file, and, the output from Premiere. Your comment posted as I was working on this so I will reply on that here: I had not specified an output file name...just modified the path to include my Windows user name. c:\Users\TheMixNation\Desktop
|
|
That's correct, so in your case it should look like this: |
|
Note the double-\ characters are important. |
|
Roger that...I had left the double and then changed it to single after my last post just to test it and have since put it back. |
|
Windows does this thing where it appends ".txt" to files, is it possible that it's saved as "config.json.txt" |
|
Shouldn't be...I have view options set up to show suffix. Also, while saving the file with the json extension I was sure to change the Type to All Files rather than txt. |
|
Not sure whether this helps but I just found this log file timestamped for my latest render attempt (see attached) in the respective AppData folder for Premiere. |
|
re: filename Ah ok, good. re: destination - I've just validated that I can write to the 'Videos' directory in my Premiere, so it's not that either. Thanks for that file; it's not the one I'm trying to write, but it's helpful nonetheless. I'm looking into why config.json isn't enabling debugging; can confirm that's not working in Premiere for me - not sure what's happened there yet. |
|
Ok, I've uploaded an alpha3 to the same spot - could you please give it a try. |
|
OK - will do. |
|
After trying alpha3, I had encountered the same issues as previously discussed. I then looked at the CC manager app and saw that there was an update for Premiere; and clicked to accept that. With the latest version of Premiere, then, I am presently attempting to render with the HAP encoder. So far, there has not been any debug file output to the desktop and the progress window for the encode process appears to be hung . Though I don't know this for certain yet, it has been on 0% for more than 5 minutes. I am not getting the error as initially reported.
|
|
Reinstalled HAP alpha3 after force-closing Premiere. Re-ran test render and obtained output log! |
|
This is definitely progress. The point at which it has died is just after asking the HAP plugin for the file extension to use (.mov in this case), and then no further information. I suggest trying again first encoding to H264 instead of HAP to make sure the new Premiere is still getting the source sequence correctly. The next thing is to disable audio output and encoding temporarily. I'm going to verify those locally; also with Hap Q [I've been using Hap to now]. |
|
On it...will update shortly. |
|
With this particular video project which I had previously rendered out in full via H.264, I am now getting hung on 0% as well. However, with a much simpler "test" project with one video and one overlay I am able to render in H.264 and get the originally posted error using HAP. |
|
I am now going to try a different computer. |
|
Regarding HAP - are you outputting in Hap, Hap+Alpha or HapQ? One thing I've seen in the past btw - if the Media browser in AME is pointed at a folder containing a bad movie in it, AME used to have problems. If you're simplifying your test case, maybe take the video source from a single .mov in an otherwise empty directory, and write to an empty directory. [this is purely for debugging purposes] Also - if you're getting the originally posted error with a short test project, it's possible the HAP-log.txt has different information to the one posted; maybe check and send it if that's the case? |
|
Yes, I will take your guidance and verify accordingly. Also, I will post an updated log file for the shorter sequence if it is generating. I have a meeting for the next half-hour or so; and will get back to this in a short while. |
|
I'd also like to check that the HAP presets are in the correct locations. When you have a moment please open a command prompt (type cmd in the start bar) and do the following: You should be able to drag select the output and hit 'enter' to copy it, or right-click the window title bar, and choose Edit->mark to do the same. Please paste the result here. |
|
[you probably should be using one of the Hap, Hap Q or Hap Alpha when you export - selectable from top right of the export window in Premiere. In 2020 'Hap Alpha Only' seems to come up as the default choice; it's practically useless and I haven't found a way to change it - likely going to remove it] |
|
Thanks. Yeah, I was using all of the presets for multiple attempts to try and rule out one or the other. Moving forward, I'll avoid the Alpha Only option. I will have more time later today to take a look into this and will report back on the preset locations you requested. |
|
C:\WINDOWS\system32>dir /s /b c:\hap*.epr /s |
|
That looks a little odd - specifically I'm not clear why there are presets under 6.0.0, nor when that version of AME was current. Looking online it appears that was around 2012? Wasn't aware these plugins would even notice a version prior to 2018. I'm assuming that versions been uninstalled and can't conflict with existing versions though. Also I was expecting to see some in a different location [next to the plugin .prm / .aex] - is your copy of AME installed to another drive? [These shouldn't really be issues, but I'm trying to isolate the difference between your machine and mine] |
|
I did have CS6 on here at one point; perhaps that folder is something left over from previous uninstall activity(?) Everything is installed to the C drive. |
|
Is there a presets folder under and if there is, what is its contents? Finally, if there are any HAP[..].epr files in please remove them. [any of these should have been picked up by the earlier 'dir' command you did; I was expecting some under the HAP folder at least] |
|
Just the config file I manually created, HAPPlugin.aex and HAPPlugin.prm in MediaCore-->HAP folder. No plugins in the MediaCore folder itself (only subfolders) and a dummy.txt file.
|
|
That's really odd; there's supposed to be a folder called 'presets' alongside those - and in fact it's copied to those other locations. So either it's somewhere else entirely [and I don't know how that would have happened], it's been removed OR the installed presets are from an earlier installation. Just to check - is this machine managed some sort of IT domain policy installed by your IT team? Let me think on this; will send further suggestions. |
|
We haven't been able to reproduce this yet, but the plugins will be tested on CC 2020 for upcoming 1.2.0 |
|
OK, thanks. I am available to help with testing during these summer months if needed. |
|
Will ping you when 1.2.0-rc1 is up :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having the latest (Alpha) release, and trying with a couple projects with different resolutions and track complexities - able to reproduce error such as indicated below. Unable to output using HAP Encoder:
01/05/2020 06:13:10 PM : Encoding Failed
A low-level exception occurred in: HAP Video (Exporter:9)
Export Error
Error compiling movie.
Export Error
A low-level exception occurred.
Writing with exporter: HAP Video
Writing to file: C:\Users\TheMixNation\Videos\Sequence 01_2.mov
Around timecode: 00:00:00:00
Component: HAP Video of type Exporter
Selector: 9
Error code: 3
The text was updated successfully, but these errors were encountered: