Please add support for MXF files created by Blackmagic Hyperdeck Studio

We have a Hyperdeck Studio that records DNxHD220 files in a MXF wrapper. Right now it is not possible to import them into Premiere CS5.5.
It would be great if Adobe would add support for those files.
Regards
NFact

It's mostly users here in the forums. Here's how to get Adobe to listen.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Similar Messages

HT201071 Please add support for Hasselblad CFV-50

I just replaced my Hasselblad CFV-16 with the CFV-50, and now I have bad redish view only of my files both in Preview and Aperture.
Please add support for the file format from CFV-50, it's not a all new Digital Back (it's out since severals years now).
We can still convert files into DNG using Hasseblad tools and made the DNG file reconized by Preview and Aperture, but would like to be able to manage my original RAW files from Hasselblad in Aperture like I was used to do

This is a user-to-user forum and is not monitored by Apple for feedback purposes. You can give feedback to Apple here: Apple - Mac OS X - Feedback

How to add support for new file type.

Using the ESDK, I would like to add support for new file type ( a new extension). this new extension will function like any other non visual code editor but will have specific syntax highlighting, code folding and explorer.
I am trying ot figure out if I need to create a new editor or use existing JDeveloper code editor and add support for new file type. Does anyone have a high level outline on how to do this using the ESDK that is specifically targeted at adding new file type support for a text based code editor?
I have looked at the Samples and keep going in multipe directions. It would be cool if there was an example that was how add syntax higlighting for new file type.
Thank you

Brian, thank you. I looked at this extension and it answered a lot of questions for me. I was going in the right direction but needed a little help and bost of confidence, this is just what I needed. I created the LanguageSupport, LanguageModel, Addin, Node and TextDocument that are specific to the new file type. I was getting hung up on how to hook this into the JDevelpoer editor. I keep thinking I have to create a custom editor but it looks like I don't have to and it looks like I can associate this file support with the editor framwork, for version 10.1.3.2, with the following in the Addin Initilize() method.
Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
I have done this but still not able to recognize the new file type.
At this point, I just want to be able to recognize the new file and display it's associated icon or display a messare to the message log. I put a System.out.println("test") in the Initilize() method of my addin. then I registered MyAddin in the extension.xml. JDeveloper sees this new extension and it is loaded but I have not been able to show the test message or display the new icon when I open the new file type.
extension.xml
<?xml version="1.0" encoding="windows-1252" ?>
<extension xmlns="http://jcp.org/jsr/198/extension-manifest"
           id="teisaacs.jdev.myext.MyAddin" version="1.0.0" esdk-version="1.0"
           rsbundle-class="teisaacs.jdev.myext.resources.MyResBundle">
    <name rskey="EXTENSION_NAME">My Code Editor</name>
    <owner rskey="EXTENSION_OWNER">Me</owner>
    <dependencies>
        <import version="10.1.3">oracle.jdeveloper</import>
    </dependencies>
    <hooks>
        <jdeveloper-hook>
            <addins>
                <addin>teisaacs.jdev.myext.MyEditorAddin</addin>
            </addins>
        </jdeveloper-hook>
        <feature-hook>
            <description>My Code Editor</description>
            <optional>true</optional>
        </feature-hook>
        <document-hook>
            <documents>
                <by-suffix document-class="teisaacs.jdev.myext.model.MySourceDocument">
                    <suffix>my</suffix>
                    <suffix>MY</suffix>
                </by-suffix>
            </documents>
        </document-hook>
        <editor-hook>
            <editors>
                <editor editor-class="teisaacs.jdev.myext.editor.MyEditor">
                    <name rskey="EXTENSION_NAME">My Editor</name>
                </editor>
                <mappings>
                    <mapping document-class='teisaacs.jdev.myext.model.MySourceDocument">
                        <open-with editor-class="teisaacs.jdev.myrext.editor.MyEditor"
                                   preferred="true"/>
                        <open-with editor-class="javax.ide.editor.CodeEditor"/>
                    </mapping>
                </mappings>
            </editors>
        </editor-hook>
    </hooks>
</extension>
public class MyAddin implements Addin {
    public static final String MY_EXTENSION = "my";
    public void initialize() {
        System.out.println("MyEditor Constructor");
        new MyLanguageModule();
        Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
        CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
        LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
}I have added and removed the editor hook along with many other modificaitons to the extension.xml but still not recognizing the new file extension.
Todd

IOS Newsstand app, add support for .folio files

Hello!
We have an iOS Newsstand app to provide our issues to our clients, and we use a PDF reader.
We would like to add support for .folio files in the app, by using a folio reader in our app.
Searching around, I've only found the specifications for the .folio files and the Adobe Content Viewer app.
Is it possible to have some more specific information on how we can make something like the Adobe Content Viewer app that we can integrate in our app?
For example how we would parse the xml files, what views/controls to use (eg. UIWebview?) etc.
Thank you very much!

Neil let clear something:
- After the .folio specification became public (with license off course) the "This really isn't possible to do" is not truth.
I believe that what people need to know is that: "Are we allowed to build a viewer?" / "Does Adobe allow programmers to give it a go?"
Before March this wasn't allowed but since the spec became public we all hope (and I believe Adobe too) that this format will have an industry standard acceptance - like the PDF. In this case many people will try to create viewers, software, builders etc.
The DPS is a great platform but VERY EXPENSIVE. Companies around the world have developed and are in a position to develop great experiences and great apps. Sharing the .folio is big and this is what we need to clear - and not the number of staff working on the DPS Viewer.
Thank you in advanced.

HT201071 Please add support for Camera RAW Canon PowerShot G2

Please add support for Camera RAW Canon PowerShot G2,
it may be ancient, but there are still a lot of G2s out there, and it's annoying to have a different workflow for pictures from them...
best,
case

You are not writing to Apple here. This is a user to user help forum.
Instead, send your comments or suggestions directly to Apple via Mac OS X Feedback.
You are unlikely to get a direct response from your "Fedback", but you can be certain that the responsible Apple people will see your input for consideration in future product development.

Can you please add support for Gmail's archive feature?

Can you please add support for Gmail's archive feature? I would like to be able to "archive" emails using the menu when I'm accessing my gmail account, reading and browsing emails. I would also like "archived" emails to be removed from the email listing once I tap the refresh option on the menu. Could you tell Blackberry to implement these features on the next update?

hello, you can do this in current versions already :))
for detail please see [[How to clear the Firefox cache]]

Please add support for Lumix DMC-LX1

I've had this excellent camera for a few months and am frustrated I can't use its RAW files with Aperture.
At least I can use it with Lightroom and Photoshop CS2, but I want to use Aperture. I sincerely hope cameras are added to Aperture at least as quickly as Adobe can add them.

I doubt you will have much luck here. I wish support for my Konica Minolta A200 would be added but there is little hope now Konica Minolta have left the market.
One of Apple's main shortcomings in this area is their lack of RAW support. This will probally lead Adobe to have the upper hand with RAW processing as they support 100s more cameras than Apple do!

Please add support for Tiles

I have been looking on other lists and sites and this seems to be a big missing piece of both JSC and JSF -> the ability to template the layout of pages.
As a Struts developer, I find creating page templates in Tiles, them being able to reuse, inhertit from and tweak with only a few lines of XML in the tiles-def.xml and incredibly powerful and time saving tool. Yet apart form some clever us of prelude and coda in a few demo apps (Bookstore6 from the J2EE14 Tutorial), ther seems to be little support for this in either the IDE or the spec.
I realize that JSF is about components, but layout is just as important.
Any kind of page layout templating support would be appreciated - it doesn't have to be Tiles but it would be nice.
In the mean time, has anyone come up with workarounds for this?
M

JSF does support the use of Struts-Tiles, but Sun Java Studio Creator does not. I've tried using Tiles within Creator, but it will not allow me to modify the included JSP pages properly. For example, when I remove the html, body, and f:view tags from the page to be included, Creator automatically re-adds them, resulting in broken functionality.
The lack of templating support is rather distressing and is one reason I am holding off on using Creator to create production code. For now, it's more of a play thing.
Templating support is a must!

Please add support for JPEG Exchangeable Image File Format (EXIF)

It seems that now Adobe® Illustrator® can export only to the JPEG File Interchange Format (JFIF). We should have an option to produce the JPEG Exchangeable image file format (EXIF) as well (just like Photoshop does!). Why this is so important to me? I generally work under Illustrator and I often post my work on Behence. I work with 'sRGB IEC61966-2.1' color profile. When publishing I use *.jpg with embedded ICC Color Profile. But it looks like Behence doesn’t fully support the JPEG JFIF – for example it cannot read its icc data correctly. The effect is that my work looses its quality! The only option to produce the JPEG EXIF I have now is to: Export *.ai file to JPEG (under Adobe Illustrator) > go to Photoshop > Create new project > Paste the *.jpg > and Sava As JPEG with icc embedded. This guarantees my files are being processed correctly.
(JPEG) Formally, the EXIF and JFIF standards are incompatible. This is because both specify that their particular application segment (APP0 for JFIF, APP1 for Exif) must be the first in the image file. In practice, many programs and digital cameras produce files with both application segments included. This will not affect the image decoding for most decoders, but poorly designed JFIF or Exif parsers may not recognize the file properly. ( http://en.wikipedia.org/wiki/JPEG_File_Interchange_Format#Exif_comparison )
I’ve analyzed my files using JPEGsnoop 1.6.1 (an app by Calvin Hass, http://www.impulseadventure.com/photo/) and here is the result:
A) an *.jpg file produced with Adobe Illustrator > File > Export > JPEG > ICC profile embedded:
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP0 (xFFE0) ***
OFFSET: 0x00000002
length     = 16
identifier = [JFIF]
version    = [1.2]
density    = 72 x 72 DPI (dots per inch)
thumbnail = 0 x 0
B) an *.jpg file produced with Adobe Illustrator > File > Save For Web > JPEG > ICC profile embedded:
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP0 (xFFE0) ***
OFFSET: 0x00000002
length     = 16
identifier = [JFIF]
version    = [1.2]
density    = 100 x 100 (aspect ratio)
thumbnail = 0 x 0
C) an *.jpg file produced with Adobe Photoshop > File > Save As > JPEG > ICC Profile embedded
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP1 (xFFE1) ***
OFFSET: 0x00000002
length          = 1320
Identifier      = [Exif]
Identifier TIFF = 0x[4D4D002A 00000008]
Endian          = Motorola (big)
TAG Mark x002A = 0x002A
EXIF IFD0 @ Absolute 0x00000014
Dir Length = 0x0007
[Orientation ] = Row 0: top, Col 0: left
[XResolution ] = 720000/10000
[YResolution ] = 720000/10000
[ResolutionUnit ] = Inch
[Software ] = "Adobe Photoshop CC 2014 (Windows)"
[DateTime ] = "2014:08:02 17:21:15"
[ExifOffset ] = @ 0x00A8
Offset to Next IFD = 0x000000D4
EXIF IFD1 @ Absolute 0x000000E0
Dir Length = 0x0006
[Compression ] = JPEG
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[JpegIFOffset ] = @ +0x0132 = @ 0x013E
[JpegIFByteCount ] = 1006
Offset to Next IFD = 0x00000000
EXIF SubIFD @ Absolute 0x000000B4
Dir Length = 0x0003
[ColorSpace ] = sRGB
[ExifImageWidth ] = 200
[ExifImageHeight ] = 200
Regards,
Pawel Kuc

This is a user-to-user forum and is not monitored by Apple for feedback purposes. You can give feedback to Apple here: Apple - Mac OS X - Feedback

Cover.jpg - *PLEASE* add support for it!

I know importation of album art has been covered many times so please accept my apologies for starting yet another thread however there seems to be little discussion of the "cover.jpg" method for associating album tracks with the associated cover art imagery.
Placing a file called "cover.jpg" in each album directory is fairly common practice with many (most?) media servers and works perfectly well, consequently I have no intention of adding embedded cover art jpg's to every track in my library (10,000+ tracks) just so that my N85 can show me an album cover.
It would be so much easier for us users (you know, Nokia customers) if the S60 media player could identify the cover.jpg file that sits in every album directory I have so far synced over to my N85, and then import those cover.jpg files as the album art for each album. Also, the cover.jpg files should then NOT appear in my photo gallery.
Is this really so difficult to make happen??? Not supporting this feature seems to be the cause of so much aggravation for Nokia customers when transferring files to Nokia devices.
BTW, I'm not suggesting that embedded cover art should be ignored - if it's there then use it but when it's not present then also look for the cover.jpg file as an alternative source...

05-Jan-2009 11:47 AM
shayesta wrote:
nokia are not going to bother with cover.jpg that can be loaded from each folder depending on what track you play. only SE do support that. i think embedded album art is waybetter than seperate jpgs in each folder.
The trouble is some people already have music collections with thousands of songs, and don't want to add a 30KB image to each song just because Nokia are too stupid/too lazy/too arrogant to implement a simple solution to what is very obviously a common problem. SE implemented the solution because it's not difficult and it's what their users want - why can't Nokia give users what they want for goodness sake?
I can put over 1500 tracks or ~150 albums on my N85, and if I add a 30-35KB jpg image to each and every track that's 52MB wasted rather than the 5MB it would take to store one album cover image with every album directory. It's not rocket science.
I don't disagree that supporting embedded album art is a handy feature, but it's embedded album art is certainly not common with those who have music collections dating back more than a few years, nor is it desirable for many people. Adding album art retrospectively to an entire music collection in order to view a picture on a Nokia ain't going to happen either - I'd rather buy a consumer-friendly SE phone next time.

Please add support for using Slim Server with ITunes

I just purchased a SqueezeBox and it awesome! However, it uses Slim Server to stream music to it, and all the cool songs I purchased on Itunes are not available due to the DRM (I hate DRM!). I purchased these songs, they live on the Mac, and all I want to do is stream them to this slim device and listen to them. This should be allowed.
Thank you.
Mac OS X (10.4.6)

Apple has not to date licensed their DRM to anyone other than Morotola (for inclusion in a couple of phones), so it's not likely to happen anytime soon, if ever.
BTW, we're just your fellow users here. Feedback to Apple is best submitted through the feedback pages. For feedback on iTunes itself, use the Mac OS X feedback; the iTunes feedback is just at this point for suggesting new content to the iTunes Music Store.

Add support for custom xmp panels

Please add support for custom xmp panels.
Thanks

I would strongly support that too!!!
Here is why: We have been working at an XMP implementation of the Darwin Core to support standardized metadata on biodiversity information. Have a look here. I would love to have an Panel in Lightroom to support the metadata that I am embedding with IDImager:
http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27
Cheers,
Frank

Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?

We are using Premiere CC Pro on the Mac-plattform against a shared storage soulution. We need to be able to open growing files from an EVS system to edit soccer-highlights while the matches are still playing. The problem is that the codec is DNxHD 120 and the wrapper is MXF op1a. This works fine with a QT-wrapper, but not with a MXF-wrapper. It is not possible for us the change the wrapper on the EVS system, so we need to do something on the editing side. We have tested it, and confirmed that this works fine in Final Cut Pro and Avid, but we want to use Premiere Pro. Can you provide us with a solution? Please do not say that the solution is to use FCP... ;-) Thanks in advance for all help!

Hi Peter!
Latest version. Cc 2014 with all updates.
Mac OSX 10.10.2 Yosemite.
Error during opening. As soon as the file is closed, it opens fine.
Mvh
Marius Borge
Sendt fra min iPhone
Den 10. feb. 2015 kl. 18.40 skrev petergaraway <[email protected]<mailto:[email protected]>>:
Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?
created by petergaraway<https://forums.adobe.com/people/petergaraway> in Premiere Pro - View the full discussion<https://forums.adobe.com/message/7181513#7181513>

Bridge support for MXF video files?

I use the Canon XF305 and have been using Bridge with other cameras (like the 7D) to log metadata and preview files before importing into Pr 5.5. However, I find that I can't view the MXF format files in the Mac version (I've not tried the Windows version). Is MXF not supported by Bridge? If not, it should be.
The ability to use Bridge to add metadata to MXF files would be a real boon. I typically shoot three camera shoots and need to go back and log the data.

There is a utility for logging metadata from Canon that comes with the camera, so I'm going to see if there is any transfer of their metadata to what Bridge uses.
In doing more reading,and watching more Adobe videos, it appears that Adobe wants video producers to use On Location, both before, during and after shooting to log metadata. It's a bit confusing why some of the trainers are recommending Bridge, which doesn't support all the various codecs, while others are recommending OL. But it appears that OL will do what I am after.
It would be good to see an Adobe document that highlights the pros and cons of using both and where they fit in the Adobe landscape.
I'm off for a morning of video and testing of OL.
More info from Adobe staff from Bridge would be useful (both for me and future newbies).

Please add options for file names on camera or PlayMemories import (ie: 00001 DateTaken DSC)

Please add options for file names on camera or PlayMemories import (ie: 00001 DateTaken DSC= 00001 2014_10_21 DSC )

if(!getNewContactsName())
               createNew();
               return;
          if(!getNewContactsSurname())
               createNew();
               return;
          String checkName = newName;
          String checkSurname = newSurname;
          if(!checkIfDuplicate(checkName,checkSurname))
               createNew();
               return;
          if(!getNewContactsHomeNum())
               createNew();
               return;
          if(!getNewContactsWorkNum())
               createNew();
               return;
          if(!getNewContactsCellNum())
               createNew();
               return;
          if(!checkAtLeastOneNumEntered(newHome, newWork, newCell))
               createNew();
               return;
          }This can all be done in 1 if statement just use the or operator (||) will save some room
private void deleteFromList(String nameOfContact, String surnameOfContact)
     {//Start of deleteFromList()
          int confirm = JOptionPane.showConfirmDialog(null,"Are you sure you wish to delete the contact from the phonebook?","Please confirm",JOptionPane.YES_NO_OPTION);
          if(confirm == JOptionPane.NO_OPTION)
               return;
          elseWhy do you have a return statement in a void method? there's no need for this you can cut out the no part and just keep the yes

Please add support for MXF files created by Blackmagic Hyperdeck Studio

Similar Messages

Maybe you are looking for