Import bug

When I import from the new Sanyo VPC-FH1 with the iFrame format, iMovie 09 only imports half of the clip. Anyone else having problems with importing clips from a memory based camcorder?

I have a similar problem with my Canon HG10 AVCHD camcorder. My suspicion is that the camera causes an error occasionally when recording, and iMovie doesn't know what to do when it hits this error so it hangs. In my case, it doesn't matter how long the clip is; some short clips are affected and some long clips. Chances are, however, that really long clips have an error in them somewhere.
I have already suggested to the iMovie team at Apple that they enhance iMovie so that it skips the error if and when encountered and start a new clip beginning at the next frame.

Similar Messages

Nwrfc 0.0.5 with important bug fix!

I have just pushed version 0.0.5 of the new gem to rubygems.org (you can also access the latest repo at GitHub).
0.0.5 introduces an important bug fix in Table#each. Previously only the first row would continuously be returned. Now you can actually treat a Table like an Enumerable!

To quote Metalink Note 161818.1 (Oracle Server (RDBMS) Releases Support Status Summary)
"Terminology Used in this Article
Patch Set
*Patch sets are cumulative. For example, 10.1.0.4 includes all the fixes in 10.1.0.3 as well as new fixes for 10.1.0.4.* "

I believe I found an import bug in LR 5.4

I believe I've uncovered an import bug in Lightroom 5.4 under Mavericks. I noticed a folder with 19 photos and videos, but LR was only showing 18. So I tried synchronizing the folder, and still only 18 were found. So, in the import screen I unchecked "Don't import suspected duplicates", and it still would not import. So, I removed the folder containing the photos from LR, then re-imported them, and still only 18 photos!
So, the .jpg file listed here will NOT import into LR regardless of my efforts. The mp4 imports just fine. It seems like a bug pertaining to files with the same name but different extensions, or something similar. Here are the file names:
bernie3_blue_baby_shopping_walmart-09-2.mp4 - IMPORTS OK
bernie3_blue_baby_shopping_walmart-09-2.jpg - WILL NOT IMPORT

I’m not sure it’s a bug but rather by design. For example if you do external editing from Lightroom in Photoshop the word Edit is automatically added to the tiff or PSD file with the same name. Simply change the file name for the jpeg and it will import. LR does permit jpeg and raw files with the same name but it requires enabling in the prefs. I assume there is no similar pref setting for videos, as they would always be numbered separately when importing directly from a camera card; so the situation would never usually arise.

IDML Import Bug?

Hi All,
Just wondering if anyone can reproduce what appears to be a CS4/CS5 IDML import bug.
I typed
11
22
33
44
55
(first 3 digits in bold) then tagged "22" as an XML element before exporting an IDML file.
When the IDML file is imported, I get
11
22
33
44
55
(all digits in boldface except for the trailing 2.)
The problem seems to be on the import side of CS4/CS5 since the exported IDML looks okay to me:
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>11</Content>
 
 </CharacterStyleRange>
 <XMLElement Self="di2i7i6" MarkupTag="XMLTag/Story">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>2</Content>
 </CharacterStyleRange>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 <Content>2</Content>
 </CharacterStyleRange>
 </XMLElement>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 
 <Content>33</Content>
 
 <Content>44</Content>
 
 <Content>55</Content>
 
 </CharacterStyleRange>
</ParagraphStyleRange>
Comments anyone?

Hello Larry,
i am the developer of the IDMLlib http://idmllib.com/ a Java library which is able to read/modify/create IDML.
I have also noticed some strange behavior regarding the importing of IDML, where the order of elements affect the parsing of the IDML in CS4/CS5.
My first thought was, i have created an invalid IDML, but the IDML Relax NG compact schema is very explicit, order doesn´t matter.
The best example i have at hand, which is very easy to reproduce is the TabList. A valid tablist attached to ParagraphStyleRange for example looks like this:
<TabList type="list">
 <ListItem type="record">
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 <Position type="unit">144</Position>
 </ListItem>
</TabList>
If you change this by moving the Position to the top, which is no problem regarding the schema which doesn´t enforce a strict order of the elements:
element Alignment { enum_type, TabStopAlignment_EnumValue }&
element AlignmentCharacter { string_type, xsd:string }&
element Leader { string_type, xsd:string }&
element Position { unit_type, xsd:double })
So if you change this example to this, and reimport the IDML into CS4/CS5 INDD the <Position/> will not be parsed and you wont see a TabList
<TabList type="list">
 <ListItem type="record">
 <Position type="unit">144</Position>
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 </ListItem>
</TabList>
If you export this again as IDML the <Position/> if set to 0
I circumvented this problem by forcing the creation of TabList Items with a constructor that will only allow to create TabListItems with all values present and therefore i can force the order of the created childs. But i think this will not be the only problem where parsing doesn´t do what it is supposed to do.
There has been a posting from a guy complaining about different import results regarding the attribute order of IDML element:
http://forums.adobe.com/thread/637711
I will try to reproduce the behavior you decribed.
Cheers, Andreas

FB3 Beta 3 - another organize imports bug

I'm getting lucky :-) Here is another organize imports bug in
FB3 Beta3...
If you have some simple hierarchy where base class defines
public (or protected) method, and sub class tries to override this
method you will encounter this bug. Let say that base class looks
like this:
package test {
import flash.display.Shape;
public class BaseClass extends Shape {
public function BaseClass() {
public function myMethod():void {
trace("In BaseClass.myMethod()");
and that sub class looks like this
package test {
public class SubClass extends BaseClass {
public function SubClass() {
super();
Now, if you try to override myMethod() from BaseClass and
start typing in subclass something like
override public function m
and use Ctrl+Space, FB will insert appropriate method but it
will also insert errorneous import statement like this:
import test.BaseClass.myMethod;
So you will end up with sub class which looks like following:
package test {
import test.BaseClass.myMethod;
public class SubClass extends BaseClass {
public function SubClass() {
super();
override public function myMethod():void {
Wrong import is correctly marked as error but issuing
"organize import" does not remove it so it must be removed
manually.
Regards,
Damir Murat
PS: Sorry for bad code formatting but there is no option for
inserting in-line code and attach code is a little bit
awkward.

Damir Murat,
Did you already file a bug for this? If not, would you mind
adding it to the public bug base so we can track the issue.
Thanks,
Peter

Address Book contact importing bug

Bug reproducing sequence:
1) Create any smart-group in the Address Book
2) Double-click that group's name to rename it
3) Command-Tab from Address Book leaving it in status waiting to enter new smart-group's name
4) Double click on any .vcf file to import a new contact into Address Book
5) You'd be forwarded back to Address Book with a window offering to confirm contact's import
Bug itself:
Pressing the Add button actually imports a new contact to the Address Book, but does not close this pop-up window. As a result you can create many copies of the same contact before you notice the problem and close this window pressing Cancel button.
Testing the same sequence on MacMini and iMac caused creation of many Unnamed contacts and did not import a new contact at all.

I found the solution in a different post in the community.
You need to go into yr address book on yr MAC. Edit each contact 1 by 1... Cut (Cmd X) and copy (Cmd V) each pix back in... When you synch yr MAC and iPhone again, pix miraculously appear in Contacts and when you get a call from one of them.
Not a fancy solution but works!...

ICal import bug when creating calendars in iPhoto 2011

Hi,
I just created a calendar in the new iPhoto 2011 and imported an iCal calendar to the project.
What I discovered is that it only imports one event per day to the calendar in iPhoto, although the calendar in iCal has sometimes more than one event per day.
Fx. in my calendar in iCal I have two events on a certain date, f.x my mothers birthday and my son's birthday on January 18th. However when importing this calendar to the calendar project in iPhoto only my mothers name gets imported. This was not an issue in iPhoto 2010.
Am I doing something wrong or is this a bug?

Definitely a bug and unforgivable given the time of year - I usually order a couple of calendars as Christmas presents - If I can't order them in time for Christmas then Apple have lost the business.
It seems to me that iLife 11 was rushed out for Christmas. First the appalling upgrade problems and then the realisation that Calendars were not included. Two patches later and we still have an un-useable Calendar.
The worst part about it is, it's not obvious - I wonder how many people have ordered calendars and not noticed the missing Birthdays. I can see a lot of disappointed friends and relatives next year whose birthdays will be missed.
My only hope is an old backup of my Macbook - pre upgrade. If I can boot from that disk, import my recent photos, import the latest version of the iCal Calendar events, I can recreate the Calendar with iPhoto '09. Not sure I can be bothered,

Java SDO API import bug

There is a bug in the Oracle Java SDO API. It cannot import compound geometries which consist of either 3 or 4 sub-elements. e.g., the following geometry cannot be imported:
SDO_GEOMETRY(2002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 4, 4, 1, 2, 1, 9, 2, 2, 13
, 2, 2, 17, 2, 1), SDO_ORDINATE_ARRAY(278222.37, 179102.519, 278222.37, 179111.223,
278222.37, 179176.31, 278223.164, 179194.567, 278224.751, 179206.473, 278238.913,
179237.143, 278262.587, 179261.242, 278288.15, 179273.083, 278316.033, 179277.117,
278336.935, 179274.471, 278357.997, 179271.272))
Apparently the API does not validate the SDO_ETYPE when checking the SDO_INTERPRETATION value in the geometry.
SDO_INTERPRETATION values of 3 and 4 are assumed to be a rectangle and circle, respectively, independent of the SDO_ETYPE value. In fact, these SDO_INTERPRETATION should be handled such only for SDO_ETYPE value of 3.
For an SDO_ETYPE value of 4 (as in the example above), the SDO_INTERPRETATION value indicates the number of sub-elements in the compound geometry element.
Any ideas for a workaround or fix for this bug?

Hi Sunil,
This is a bug. There doesn't seem to be a workaround.
Can you contact me via email or post your email?
Thanks.

Import Bugs

Nice work, guys! This is exactly what I've been waiting for, and I'm very excited to put the new app through its paces.
For starters, I encountered a few bugs with document importing.
1) I was unable to import a script written in Word 2007 (DOCX file format). After converting the doc into Word 97 - 2003 format (DOC), the document was successfully imported.
2) There seems to be a problem with conversion of special characters (curly quotes, m-dashes, n-dashes, etc) during a Word document import. This is especially prominent in scene headings (see the screenshot below for details).
3) Most of the time, the different script elements (scene heading, action, character, dialog) are successfully recognized, but sometimes character names get incorrectly identified as "shot" elements. In fact, as I look through the imported script, it looks like scene headings, parentheticals, transitions, and dialog seem to be 100% correct. But about 90% of the character headings are imported as "shot" elements. The strange thing is that my doc has very good formatting consistency (since I use a Word template to create the doc, and all of my script elements have their own word "styles")
FYI, in addition to the screenshot attached below, I'm adding a link to the Word 2007 template that I use for auto-formatting my Word docs into screenplay format. (It's a heavily-modified version of the template originally found here; it's a pretty popular template, so I think it'd make a lot of sense for Story to support it, and others like it.) This should give you an idea for how my scripts are formatted before import.
If you have any questions, let me know.
(Also, do you plan on opening a public bug database for alpha/beta testers? I'd be happy to log bugs directly if such a database existed.)

Really looking forward to putting this through a solid working test drive.
I had one major issue with importing my Final Draft 7 file. All of my apostrophies and quotes were turned into Õ and another O but with a carrot on top (a symbol not readily at my disposal at the moment).
After an attempt at a simple FIND and REPLACE, it promted me to use my BROWSERS find function, which did me no good when working with my scirpt. Hence I had to manually find and replace all the apostrophes, and quotes in my script. Luckily, it's only a short. Had it been a 120 feature, that would've been an instant dealbreaker.
Hope this helps.
Zach G.

Wsdl import bug?

Dear All,
I have found the following piece of code in the "Import Web Service" Function
This piece of code strips of the https:// as it does not equal http://
This then said that my URL was bad (Which it isnt) and stopped me from importing my webservice.
See NI arent I kind to you! I have never reported a bug and I dont even know if this is one (Although I am pretty sure it is) so I havent posted anything related to bugs etc.
I did manage to get my web service imported by short cutting the above piece of code (Hence the TRUE Constant)
Thanks
Craig
LabVIEW 2012

Hi Craig,
Where exactly is this code located? I wasn't able to find the VI this is inside. As a workaround for the issue in LabVIEW 2009, you can do a quick check to see what the protocol is, rather than just accepting it's always correct with a true constant. You can use the following method to implement that:
If you let me know where this located, I can check whether this has been fixed for the latest build of LabVIEW already.
Regards,
Imtiaz Chowdhury
Head of Digital Technologies
Brand786
Attachments:
url_protocol.vi ‏8 KB

Custom aac importing bug

I use itunes on my pc and when I try to import songs in AAC custom form the program returns 2 the AAC default (128KBPS\64KBPS). the custom option does work in MP3 importing and stuff and it used to work in AAC as well but now I cant shake this bug:'(
plz help me!!!
I use win XP pro and itunes 4.9.0.17
10X 4 Ur help hope U can solve my prob :-?

Thanks for the lead Buegie, but that was not the problem for me. Neither of those files were read only, and both show having been modified today.
That feels like a good direction though. It's wierd that no error messages are generated, and it lets you go through all the steps to make the change, nothing grayed out, you click OK, then... no changes are recorded in the "Details" box, although "Custom" is displayed in the drop down menu. It thinks it's doing something, but some part of the process fails further down the line.
I've only had this computer running for a few months, but I know that I have recorded at a custom AAC setting with it within the past few months. The songs are on the hard drive. I don't know when the problem started happening, and I've made too many changes to the system to pin the cause down.
btw, path for second file should have been
....<username>\Local Settings\Application Data....

Static import bug?

Hey just discovered something new...does this sound like a bug to you guys?
I have a class with a static method called, say, omgMethod()
and I have another class with a method (not static) with the same name (omgMethod) but different signature.
now when I try to use import static classA.omgMethod in the second class, it generates a compiler error:
cannot find symbol method omgMethod( etc...)
any thoughts? i'm thinking about adding it to the bug report.
-Cuppo

I'm not so sure about that. I have never used static import so I checked out Sun's tutorial which is here:
http://java.sun.com/j2se/1.5.0/docs/guide/language/static-import.html
It talks about importing "members" and says you can import "members" individually. And (I had to look this up too in the JLS), "members" means classes, interfaces, fields, and methods.
So that says to me that you can indeed import a static method from another class, and then use it without qualification. Yeah, I'm surprised too. But you're just importing the method's name, not its signature. So if that name conflicts with a name of a method in your class, then I don't know what is supposed to happen. I looked through the JLS a bit and section 6.5.7.1 says
"The Identifier must name at least one visible (�6.3.1) method that is in scope at the point where the Identifier appear or a method imported by a single-static-import declaration (�7.5.3) or static-import-on-demand declaration (�7.5.4) within the compilation unit within which the Identifier appears.
See �15.12 for further discussion of the interpretation of simple method names in method invocation expressions."
Possibly section 15.12 discusses conflict resolution in this case. But I will let you carry on from there.

Import Bug in Bridge

Hi. I've just spent all day trying to work out why I couldn't import from bridge for various files. I finally worked out that Bridge fails to import to premiere properly when the file is on my external drive. The same file imports fine from my C drive fine. The extrenal drive isn't locked in any way so I guess this is a bug?

Not an auspicious way to start the year, is it?
First, you're posting to the Bridge Macintosh forum but refer to your "C drive", which means you're on Windoze.
Second, you give absolutely no information about your setup.
When you do find your way to the Bridge Windows forum, make sure to give them exact details about your OS, your exact version of Bridge, etc. There are some clever folks over there, but no mind readers or clairvoyants.
Happy New Year to you and good luck.
Wo Tai Lao Le
我太老了

Cannot import Bug Tracker demo app

Hi. complete newbie
Have installed Enterprise Edition on a test box at work (we have a license so don't panic).
Installed Apex 3.1.1 over the top, using PL/SQL gateway.
All works sweet, and insrtalled partial Production data and created a few simple reports.
Tried to install Bug Tracker and it fails with a msg "invalid Import file".
Checked the zip and instructions; we're doing it right.
Any ideas?
John

John,
Tried to install Bug Tracker and it fails with a msg "invalid Import file".
What are the steps you followed? And what is the actual error message you got? I can't find the message in our product files that you showed, and if there is such a message we clearly need to fix the punctuation and spelling.
Scott

L3 Import Bug

I am re-importing my whole collection of about 50,000 photos one or a few folders at a time. I am converting to DNG on import to a separate Hard Drive on a folder with the same name as the original (ex: 2010-05-08 - Scotland).
Some of the folders contain only RAW images (CR2) and some other contain RAW and JPG. Occasionally (about one time out of five) when the file is created, Lightroom has copied not just one JPG image but also created an identical 2nd, a 3rd and sometimes even a 4th. If I close Lightroom and restart it usually things go back to normal (but not always).
To sum it up:
Original folder 2010-05-08 - Scotland contains:
_MG9293.CR2
_MG9293.JPG
New folder will contain:
_MG9293.DNG
_MG9293.JPG
But sometimes it will contain
_MG9293.DNG
_MG9293.JPG
_MG9293-2.JPG
or:
_MG9293.DNG
_MG9293.JPG
_MG9293-2.JPG
_MG9293-3.JPG
or even:
_MG9293.DNG
_MG9293.JPG
_MG9293-2.JPG
_MG9293-3.JPG
_MG9293-4.JPG
I have no changed the settings at all, so this can only be a bug IMO.
Anyone else?

OldFrank wrote:
Becky,
You may be on to somethng with the "Don't Import Suspected Duplicates" check box. I, like many other newcomers to LR, have followed Nat Coalson's advice on page 51 of "Lightroom 3". He says "Also, on the File Handling panel, make sure Don't Import Duplicates is unchecked. We don't want Lightroom deciding for us what's a duplicate and what's not".
He goes on to say "There may be the odd scenario where this option could come in handy, but I haven't found it yet"
Any finally finshes by saying that if there are duplicate files LR won't import them anyway, whether or not this is enabled.
Again on page 48 he states in bold print "A Lightroom catalog can only contain one instance of each photo:if the photo is already listed in the catalog, you can't import it again.
Is it possible that LR's handling of exact duplicate photo files has been changed since the version he used in writing the book.
It actually makes more sense if this function works the way you indicate, Becky.
I've used Lr since v1, and I do not believe it has ever behaved in this manner. This option is enabled by default, and it is very useful. Under the right circumstances you might want to disable it, but for most people it should be enabled. Little in this quote is actually how Lr has ever worked, to the best of my knowledge.
In fact, I would argue the complete opposite of what this person says. I'd argue that letting the computer make good decisions and doing the repetitive grunt work is exactly what computers are for, letting the person running it make the real decisions.
At any rate, if you try to import the same file into the same directory, Lr will silently and correctly add it to the catalogue with a slightly modified name. Even if you have a naming template in most cases this will happen with duplicates because the metadata you can use in the templates will also be the same (it is, after all, the exact same file.) A catalogue entry has to have a unique filespec.
My advice is to leave "don't import duplicates" enabled, and make sure you format your media in-camera once you know it has been transferred successfully to Lr and a backup and you will not run into this problem.
Don't sweat the actual folder arrangement in most cases. If you need a specific on-disk folder arrangement you might be better off managing that yourself, and then just import via "Add" (i.e., not Move) in-place (or sync the folders if they are already in Lr.) 95% of the time you just want a bog-standard set of nested folders based on the date of the image, and use Collections and other metadata driven techniques to slice through your ever growing dataset. I actually untick the Folder panel from my Library view because it serves no daily purpose. I re-enable it when I absolutely have to access things via the filesystem through Lr (which is rare.)
Life is to short to not let computers take care of the boring stuff.

Nice import bug

Hi,
Using (prod) 10.2.0.3.0, I exported a user:
exp userid=borabiec file=mydump.dmp
The using 11g xe I tried to import file:
imp userid=superuser file=mydump.dmp ignore=y full=y
I expected borabiec user to be created, but instead I had a message:
importing boraciec's object into superuser schema.
And after import, borabiec's objects are in superuser schema.
The user borabiec was NOT created.
I thought a full import would keep exported file's owner (and create it!) ???? Am I wrong or is this a bug?
Regards,
Alain
Edited by: Alain on 21-juin-2011 5:04

Hi Alain,
it seems you didn't do a full export, but just a dump of the objects belongig to the exporting user, so I think if you are expecting the import of that dump to be "full" you are wrong.
-Udo
Edited by: Udo on 21.06.2011 14:25

Import bug

Similar Messages

Maybe you are looking for