Page 3 of 4

Re: Adobe 2018 April kills DXV

Posted: Thu Apr 19, 2018 09:55
by jjames
Excellent really looking forward to it. The showing of the artwork is next Friday. So I am happy to beta test - or alpha test.

My current work around is to render to Jpeg 2000 MXF OP1a using RGB 4:4:4 10bit and include Alpha Channel. This is only an option in Adobe Media Encoder, and does not show up in the AE export options.

PNG Sequences didn't work for me. For some reason Premiere didn't want to import them as an image sequence, and would only let me import as 2 frames each.

Are there any other PC users that have a work around that is better? Or is everyone else just waiting for the plug in?

Re: Adobe 2018 April kills DXV

Posted: Tue Apr 24, 2018 09:36
by jjames
Any word on the plugin? I need to load this on to the show computer. The PNG sequences worked when there was no audio.

Fall back to H264?

Re: Adobe 2018 April kills DXV

Posted: Tue Apr 24, 2018 10:21
by Zoltán
jjames wrote:Any word on the plugin? I need to load this on to the show computer. The PNG sequences worked when there was no audio.
Fall back to H264?
The plugin is coming.

You could export the audio separately and then join the video and audio streams in Resolume in a single clip.

Re: Adobe 2018 April kills DXV

Posted: Mon Apr 30, 2018 03:30
by Kaizen
ChrisVids wrote:after effects went back to 15.0.1 as well and premiere to 12.0.1
Confirmed, Premiere Pro and Media Encoder BOTH need to be version 12.01 for you to get your DXV export option back. Use the "Other Versions" method shown in screenshot in this thread.

If you're still having problems, double-check your version numbers in About (the Adobe program)... I had to "downgrade" Media Encoder twice before it seemed to stick with 12.01, not sure what happened the first time.

Re: Adobe 2018 April kills DXV

Posted: Mon Apr 30, 2018 03:33
by Kaizen
Foggy_Lens wrote:Is the general consensus that mpeg streamclip is the best solution for batch transcoding to DXV?
Yes, it's the only game in town that I know of for doing batch DXV on PC.

Re: Adobe 2018 April kills DXV

Posted: Tue May 08, 2018 18:09
by samuelmancebo
Any news on the DXV codec?

Re: Adobe 2018 April kills DXV

Posted: Tue May 08, 2018 21:11
by Zoltán
samuelmancebo wrote:Any news on the DXV codec?
Not yet, we're working on it.

Re: Adobe 2018 April kills DXV

Posted: Wed May 23, 2018 07:45
by Cymascopic
How about now? I think a bunch of us are starting to get Antsy

Re: Adobe 2018 April kills DXV

Posted: Wed May 30, 2018 14:13
by nightjar84
Maybe its for the better.

Once the Quicktime security threat was revealed Adobe and Davinci came out with a solution for ProRes which worked much faster than when installing QT7.

Why does Arena / Resolume need a propietary codec? Doesn't make sense. Just work on agreat implementation of ProRes / DNX / Cineform ....no need to keep pushing the own codec.

Just my two cents

Re: Adobe 2018 April kills DXV

Posted: Thu May 31, 2018 12:44
by Zoltán
nightjar84 wrote: Wed May 30, 2018 14:13Why does Arena / Resolume need a propietary codec? Doesn't make sense. Just work on agreat implementation of ProRes / DNX / Cineform ....no need to keep pushing the own codec.
Prores is an Apple product that requires licensing if you want to play it without quicktime. Apple doesn't let anyone license their products.
viewtopic.php?f=12&t=15024&p=63243#p63099

Even if we can get licensed at one point, it will still have to be decoded on your CPU.
With one layer and clip that's no problem for most machines, but as you get up to 10 or more layers, all with prores clips, you bump into trouble.
That's not an issue with DXV and a modern GPU.