Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
4th September 2018, 22:28 | #701 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,345
|
Quote:
Did you check at what stage of the process that it occurred ? e.g. is it in your source, in resolve after decoding , after export, or after decoding the export then encoding to your final format ? What about other export formats ? eg. uncompressed . If that has problem too then that suggests problem with your settings (maybe fps mismatch) or problem with source decoding in resolve Maybe a mod should move these last few posts , because they have nothing to do with magicyuv |
|
5th September 2018, 00:26 | #702 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
The 'test encode' is a 720x302, 23.976, AVC.mkv file - there's no way it came out of Resolve.
Quote:
@Preludium975. I see you registered on the Blackmagic Forum: https://forum.blackmagicdesign.com/v...it=HDR#p434386 Probably best to address all of your Resolve-related issues there. I'd suggest you give more contextual information though, if you want answers.
__________________
Nostalgia's not what it used to be Last edited by WorBry; 5th September 2018 at 04:41. |
|
5th September 2018, 06:24 | #704 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
Quite honestly if that is your target x264 format and you are only using Resolve for the HDR>SDR conversion, why jump through these hoops, generating large intermediate files in the process - you could do it all with AVISynth(+) or VapourSynth, like Kolak suggested?
__________________
Nostalgia's not what it used to be Last edited by WorBry; 5th September 2018 at 06:35. |
|
5th September 2018, 13:28 | #705 | Link | |
Registered User
Join Date: Aug 2018
Posts: 12
|
Quote:
I need the Resolve, because this is the best solution. The last thing, what need to be works, the DNxHR HQX. Because this is a visually lossless encoder. Cineform are great too, but this is also duplicating frames... |
|
5th September 2018, 15:44 | #706 | Link |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Well if there's a FPS mismatch going on it will appear in the Resolve export whatever the format. Like Poisondeathray said, to pin-point where that is occurring means going through your Resolve project set-up. Really this is not the place for that, but if it brings closure on this issue (and this segment of the thread gets moved anyway):
1. What is the format and FPS of your original HDR source, as declared (Clip Details or Clip Attributes) by Resolve on import ? 2. What is the declared project timeline frame-rate after you have loaded your clips on the timeline. Check in Project Settings > Master Settings > Timeline Format. Resolve defaults to 24FPS. If your source frame-rate is different, when you import the first clip you will be given the option to change the project frame-rate to match the source or leave at default 24FPS, in which case it will be 'locked' at 24FPS - can't be changed subsequently. Otherwise you should set-up the project Timeline Format beforehand. Your problem could be right there. 23.976p source in 24p project maybe ? 3. I'm assuming you didn't mess with Clip Speed/Duration/Retime on the timeline ? 4. What was the render (Delivery) frame-rate setting on export to Cineform, DNxHD ?. Default is the project frame-rate, but there may be other options. A 24 FPS project timeline for example will give the option of exporting at 24, 23.976 or 30 (3:2) FPS. Potential for FPS discontinuity there also. With that advice you should be able to figure out where FPS discontinuity occurred, if it did. Don't bring it back here though. If you still have issues, address it on the Blackmagic Forum. Based on what ? Again though, not a point for discussion in this thread. Edit: Incidentally where exactly (frame sequence position) are the duplicate frames occurring in your 'Test.mkv' file ? Started manually frame stepping through the file with VDub2 but got fed up about a third of the way .
__________________
Nostalgia's not what it used to be Last edited by WorBry; 5th September 2018 at 21:28. |
13th July 2019, 14:41 | #707 | Link |
Registered User
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
|
According to the e-mail I got earlier in the week v2.1 is out now.
2.1.0 Released: 2019.07.11. NEW: Added v308, v408 pixel format support (YUV 4:4:4). NEW: Added 10-bit YUV 4:4:4 compressed format. FIX: Core: Fixed a bug that prevented encoding of 16-bit planar RGB pixel formats. |
2nd January 2020, 21:07 | #708 | Link | |
Registered User
Join Date: Dec 2017
Posts: 90
|
Quote:
If the programmer is still reading this thread, I still have one plea: Please make a native After Effects plugin. I know I can use MediaCore plugins via Media Encoder and Media Encoder can encode After Effects projects, but you lose control over the more detailed render settings, most importantly the export color space, which Media Encoder incomprehensibly doesn't let you set. So it's impossible to, for example, export a floating point linear composition as in HDR PQ color space, which After Effects can do with native export plugins but not with Media Encoder. As such I still end up having to export an image sequence from AE in order to finally encode the video with MagicYUV. Anyway, great codec, thanks for making this! |
|
18th January 2020, 22:20 | #709 | Link |
Registered User
Join Date: Dec 2005
Posts: 250
|
@TomArrow
Yes, I occasionally read this thread. Glad you can make use of the plugins. The MediaCore plugins were a major pain in the rear to write in the first place for a number of reasons. But it adds the greatest coverage for Adobe tools, albeit as you say After Effects export through Media Encoder has it's limits. The problem is that After Effects uses a completely different API/SDK for its plugins, and I haven't yet looked into it that much. An important thing to note though is that the plugins don't really do anything with color spaces for higher bit depths. That means that through MediaCore I get 16-bit RGB values and encode them without any transformation (except bit depth reduction to 10/12/14). On import the project must be set up manually to properly interpret the footage (I presume). I'll look into the After Effects SDK and see how much effort would it take to make a dedicated plugin for it.
__________________
http://magicyuv.com - MagicYUV: a new fast lossless video codec for the 4K and multi-core era... |
23rd January 2020, 20:21 | #710 | Link | |
Registered User
Join Date: Dec 2017
Posts: 90
|
Quote:
I really don't know anything about how it works behind the scenes, but I would wager that After Effects already delivers the RGB values in the correct color space to the plugin that is exporting it, so you wouldn't have to deal with that yourself. Only with Media Encoder there is no way to set the output color space whereas with After Effects there is. I would then guess that the RGB values you get from Premiere/MediaCore are Rec709 or sRGB by default, but I really don't know to be honest. And I totally feel your pain there, I also once wanted to inform myself about how to write some Premiere/AE plugin and I gave up quickly after glancing over the SDK, being the complete C++ beginner that I am. |
|
27th April 2020, 10:29 | #712 | Link |
Registered User
Join Date: Mar 2004
Posts: 1,120
|
@Ignus2 PLEASE can you update the benchmarks on your website as it compares MagicYUV v2.0 with UTVideo v17.1.0 instead of the latest MagicYUV v2.2.0 and UTVideo v21.3.0.
Last edited by hajj_3; 27th April 2020 at 12:57. |
27th April 2020, 10:57 | #714 | Link | |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,542
|
Quote:
Picture we have a MKV. What is a good frame accurate VFW reader? What a pity they did not develope a AVS/VS plugin.
__________________
@turment on Telegram |
|
22nd September 2020, 12:32 | #715 | Link |
Registered User
Join Date: Mar 2004
Posts: 1,120
|
v2.3.0 Released: 2020.09.21.
NEW: MagicYUV plugin for Vegas Pro 17/18. NEW: New codec variant: 10-bit YUV 4:2:0. FIX: Fixed incorrect video length of certain AVI files when imported into Adobe software through the plugin (particularly files recorded by vMix). FIX: Minor Adobe plugin improvements: better error handling/reporting (like disk full, etc.). |
Thread Tools | Search this Thread |
Display Modes | |
|
|