QVPN / QuickVPN - Showstopper bugs identified

I've been struggling with Client VPN on WRVS4400Nv2 (fw. V1.00.09-ETSI) and the QuickVPN 1.2.11 software. These problms are still present with QVPN / Quick VPN client version 1.3.0.3.
The problem was, that I couldn't connect to the router with QuickVPN (the classic "Remote gateway not responding" error). I found a way to debug from the command line from experts-exchange.com (I think it was this link). So here goes...
This is what I found:
If I used the 123456789.dnsalias.net (number represent the lenght not the real hostname) the client didn't work, but once I changed to using the IP address it worked. The reason seem to be, that the server address in ipsec is LIMITED TO 16 CHARACTERS or it should be an IP address.
The command string with problems when running "c:\Program Files\Linksys\Linksys VPN Client>ipsec -debug":
NetshCommandStr = netsh advfirewall consec add rule name="IPsec_Tunnel"endpoint1=192.168.0.100 endpoint2=10.0.0.0/24
action=requireinrequireout description="IPsec Tunnel" mode=tunnel enable=yes profile=any type=static localtunnel=192.168.0.100
remotetunnel=123456789.dnsalirequireinrequireout auth1=computerpsk auth1psk=kNF7askq2ghhkFDbcp5h
qmsecmethods=esp:md5-3des+60min+50000kb,esp:sha1-3des+60min+50000kb,esp:md5-aes128+60min+50000kb,esp:sha1-aes128+60min+50000kb
qmpfs=mainmode
As you can see the server address is truncated to just "123456789.dnsali". The generated ipsec.conf-file has the whole address. The QuickVPN FRONTEND for the console program should do it's job correctly. Latest version also has the bug. Got my VPN working today by using IP-address instead of remote.verylongdomain.com.
THE BUGS - SUMMARY:
1. QVPN doesn't handle long hostnames - MUST USE IP address (sadly this is not a joke - ).
2. Client doesn't give ANY errors from that part of the execution, but only later when the ping doesn't work.
3. Client doesn't give spesific errors (example. It should say if the problem was the password, or the gateway, etc., not combine them all)
4. Client doest run on Windows 7 without compatibility mode (in the Vista SP2 compatibility mode it works as well as in native Vista)
4.b Error message is flawed "This only works in Windos 2000 / XP" - It does work on vista....
The Real problem IMHO:
If Cisco decides to create a quickly ductaped piece of software that is a combination of OpenSSL, GNU Wget and Marcus Muellers IPSEC-tool, you should give them credit, distribute the source code (Don't know really if open source principles apply here), or maybe hire them to do the job correctly
This is basically the same info as my old post here.
PS. Who got the great idea of minimum 9 character usernames and the n+1 step software download process

Similar Messages

CS3 bug identified. Will it be fixed?

I am excited to upgrade to CS3, but I am experiencing an issue that is not present in the previous version. The program crashes when trying to render the audio previews of a nested timeline. The error looks like this:
Premiere Pro Debug Event
"[..\..\Src\AudioRender\StackAudioBuffer.cpp-58]"
This is not a problem in version 2.0. I simply cannot upgrade to CS3 until this has been fixed......Will a patch be released? I found a user forum where someone else had the same problem. This is what he wrote:
"I can continually reproduce this audio bug. Whenever I use a "constant power" audio transition on a stereo clip with a "fill left" filter applied that is at the end of one of the adjoining clips, I get an error about a audio stack problem. I can reproduce this all day and night. Simply remove the audio transition and it works until I hit the next transition that does not have any overlap on one side"
The timeline I am trying to render has many occurrences of what he is explaining, so it could certainly point to the problem.

>There is no guarantee that anyone from Adobe is here
I have seen the teams of other apps here on the Forum but never for Premiere!
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=7
That is the bug report page.
>So its a godo idea to document it here and have others duplicate it to confirm it is indeed a >big and not an local environment problem.
That is a good point but keep in mind that the environmental issue might be one that many users will encounter and may be determined not by the condition of the environment but by the configuration. This might not be confirmed here on the forum if the users here have a different configuration. Unless it is clearly determine that is corruption, conflict or lack of resources.
To that regard the what is your configuration? And are all your plug ins up to date?
BTW it is also possible that both users have a corruption that is identical so it can still go either way!

Speakerphone bug identified in 1.1.2

While on a call using speakerphone, adjust volume while you talk. Your voice will completely drop out to the listener on the other end. Drop outs seem to last about 3-4 seconds, enough to drop 4-5 words or so each time you press the volume (in either direction).
I'm told this is a mic gain problem, software in nature, and was worsened by 1.1.2. Even though the speaker and mic are so close together, they apparently can be adjusted to work together - Motorola has done it for years.

(I assume with the recently added/edited articles link ;D)
i eventually realised that trying to conduct the conversation using edits in my previous post wasn't tremendously helpful. yep ... that one showed up buried underneath all the KB docs related to Mac OS 10.4.6. we may yet see a few more explicit reports of bug-fixes coming through over the next few days via that link:
Articles modified in last 7 days
... although i don't have as good a feel for that as i do for patterns of bug-fix reports after new itunes versions come out. (less practice.)
love, b

Showstopper bug in latest UEKR3 kernel - can't create LVM snapshot of ext4 fs

cross-posted to gain a wider audience, because this is urgent
When my backup system attempts to create an LVM snapshot of an ext4 fs, it fails, and the log is full of kernel warnings. Some of my servers actually reboot themselves. i've had to turn off backups for the moment.
It seems that this is a known problem, and a patch for it already exists. See: Re: warning in ext4_journal_start_sb on filesystem freeze (Linux Ext4)
I gave this info to a receptionist at Oracle on 12/30, and she seemed to understand that it needed to get to the Oracle Linux product group, but so far no one has contacted me for details, or to let me know that they're working on this.
It seems to me that this is a 100% critical bug, that *ought* to have gotten an immediate reaction. Does anyone here know how to get Oracle's attention?

Hi @cooldog ,
I hit this same LVM2 snapshot kernel oops on several Oracle Linux 6.5 servers running UEK R3 kernel version 3.8.13-16.3.1. I have Linux Premier Support so I opened a Service Request. Oracle Support got back to me with the following notes.
Hello Matt,
Bug 17487738 : EXT4: STRESS TESTING WITH SUSPEND/RESUME FS ACCESS CAUSES FS ERRORS This bug is fixed in kernel version: 3.8.13-18. This kernel will be available quite soon for download.
You may upgrade the kernel once its available. ~Siju
Update
Dear Matt, Latest available UEK3 kernel version 'kernel-uek-3.8.13-26.el6uek.x86_64' incorporates the required bugfix. [root@server1 tmp]# rpm -q --changelog -p kernel-uek-3.8.13-26.el6uek.x86_64.rpm | grep -i 17487738
warning: kernel-uek-3.8.13-26.el6uek.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID ec551f03
- fs: protect write with sb_start/end_write in generic_file_write_iter (Guangyu Sun) [Orabug: 17487738] <<<<<<======================================== You can download the UEK3 kernel from ULN or from public-yum repo.
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-firmware-3.8.13-26.el6uek.noarch.rpm
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-3.8.13-26.el6uek.x86_64.rpm Hope this helps! ~Siju
Subscribe to the Oracle Linux el-errata mailing list .
The latest kernel-uek-3.8.13-26.el6uek.x86_64 version fixed the problem.
- Matt

TO EVERYONE HAVING NETWORK ISSUES: Possible Bug Identified. Need Testers.

Please do the following and report back if it solves your issue.
sudo ifconfig en1 mtu 1400
... or if you're on Ethernet (en0), go to System Preferences / Network / Ethernet / Advanced / Ethernet and set the configuration on Manual. Set the MTU to 1400.
This isn't the most optimal value, but it's low enough to account for the issues I've tested.
What seems to be happening is that the MSS value being sent by OS X is not accounting for the additional bytes required for the TCP optimizations that were added (timestamps in particular). So servers are probably trying to send larger packets than they should back to the client (You most likely).
Message was edited by: mreckhof

It doesn't matter what you're using (Ethernet or Airport). They both default to an MTU of 1500 and therefore an MSS of 1460, which is too large for PPPoE users with timestamps enabled.
So reducing the MTU (temporarily - again, this is not a fix, it's a setting to prove that this is the issue) to 1400 now reduces the MSS to 1360 which is plenty small unless you've got a lot of tunnels in path which most people won't.
If we can confirm this is related to the problem that most people are having then we'll have a very solid case for what the bug is.

CS4 Rectangular Marqee & Guides Bugs Identified

One of the first things I noticed upoin upgrading was that any rectangular marquee selection appears 1 pixel to the right of the pixel snap point. Interestingly, guides brought in with snap-to-pixel appear just to the left (x-plane) or above (y-plane). See below for some screen captures I refer to in my analysis:
http://cstashuk.aristotle.net/cs4/
GUIDES:
When bringing in guides I was snapping-to-pixel and I even watched the Info dialog window showing I was snapped to the pixel location of 100, only to let go of the mouse button and see the guides "shifted slightly". The grey line that appears while you are moving/establishing the guide does however click to pixels as I am moving the mouse. See "ps_cs4_guides.gif" to make the point. These are guides brought in at 100 pixels on both the x and y axis. It shows the red guides shifted slightly which I suppose is not such a big deal, but why has this changed from ALL earlier versions. For someone who is trying to use guides to insure exact crpping, this is disappointing.
RECTANGULAR MARQUEE:
The other samples I posted show how snap-to-pixel rectangular marquee selections are off on the left side only (see samples 1-3). Note however that sample "ps_cs4_marquee_circular" which shows that the circular marquee successfully represents it left "x=0" location.
I would love to know if anyone has solved these issues. Thanks in advance!!
Christopher

Ann,
Check your Photoshop 11 Preferences > Performance > GPU Settings > Advanced Settings > GL Settings >
Advanced Drawing
This last box should be grayed out because you're running a PPC machine. It's certainly grayed out on my machine.
Folks with Mac-Intel boxes have full access to all Advanced Drawing options, including a box for
Use for Image Display.
If they have that enabled, I can see it making some pretty heavy demands on the graphics card. Those of us running G4 and G5 boxes don't have to worry about that. ;)

After Effects CS4 & Wacom Showstopper bug.

Hi! For more than one year I've being feeling that my machine was the slowest machine on Earth, so I spent a good deal of money on a new HP Z800 with a Quadro FX 5800 and 24GB of RAM with windows 7 64 and a set of SSD raid that gives me over 700MB per second, after install After Effects CS4 and try it, was awesome, such a good response and super fast, but.... after finish installing all the rest, AE was slow like on my previous 4 years old machine..... so something was wrong. To make the story short, was the Wacom driver, if I turn it off, all goes back to normal, turn it on and all goes slow, so far I was able to reproduce it on 7 machines, Win XP, Win XP 64, Vista 64, and Win 7 64, the all show the same problem, and all the machines are different. And the problem can be reproduced very easily. I've made a video showing how to reproduce it. This problem render the Wacom with AE as a non viable option for anyone. I've noticed this since about 12 months ago, but never thought is was a hardware / driver problem. Just thought AE was excruciatingly slow.
Here is the video
http://www.youtube.com/watch?v=6KwzASwrnC0
Hope Adobe and Wacon recognize this problem and fix it as fast as possible,

Hello,
I'm using the trial of CS6 Production Premium, and After Effects CS6 has a terrible problem with the Wacom. After a video preview with audio or even just an audio preview, the Wacom will become very slow, almost like the computer is under insane processor load, but my CPU monitors don't seem to be doing much. I have a 24-core Dual-Xeon PC with 48GB memory and I am trying to make use of the multi-processor capability (it would be criminal if I couldn't use it).
The Wacom becomes slow with AFX and occasionally unresponsive. It makes it impossbile to work with AFX. I refuse to use a mouse, so that's out of the question. Also, this software should work with a Wacom like everything else does. I don't have this issue in any other program.
I've set AFX to use either 20 or 16 processors with .75GB memory per core. Seems this should work ok but the Wacom is being pummeled into submission, and that's a really bad problem if I can't even move my cursor. Makes me want to close down AFX ASAP, so I hope to find a fix.
I am using the latest Wacom driver and the trial for this software is only days old, so this problems should have been fixed by now according to this thread. I'm not too motivated to spend $1800 for this suite if I can't even use AFX with a Wacom, which is the main reason I'm after the Production Suite.
If I can't get this working I will probably just buy Vegas, even though Vegas is a big old crash monkey. No Wacom problems at all though.
Any ideas?
Also, anyone notice funny cursor behavior when typing in this forum? It seems to jump around on its own and this doesn't happen to me anywhere else. Could be a residual effect of the Wacom weirdness. This fields don't seem to like 'Shift+Enter' either.
Thanks,
Dan

Keynote 6.0 - Functionality Questions & A few Bugs

I'm a presentation designer who works in Keynote extensively. The new version really turned everything sideways with some good changes and some bad. I've got a lot of questions (and obvoiusly the help file is only "eh" -- it's so not a manual for how to use the app and what's changed and where from Keynote '09. So I figured I'd turn to the community with a few questions to see if any of you have answers:
Customize Toolbar - Anyone know if this is possible in the new version? I HEAVILY relied on the customized buttons I put up there (Bring to Front, Send to Back, Bring Forward, Send Backward, Adjust Image, Instant Alpha, Copy Style/Paste Style etc.)... Would be a REAL shame to have to now have to flip through the context sensative pane at the right to access all this stuff.
Copy Style/Paste Style - There a button hidden anywhere? I know there's a set of hot keys... I just preferred the button up top
Mask with Selection through Context Sensative Right Click - now why on earth would you remove that option? COME ON!
Show Obsolete Transitions - Is there ANY way to re-enable these? I used Grid from time to time, as well as droplet. There's no good reason to remove these transitions so far as I'm concerned, as an advanced option, rendering previously created presentations degraded if opened.
Export to PowerPoint - This is a gripe, rather than a question... but seriously Apple? Still PPT and not PPTX after all these years? Don't you realize that presentations are still largely consumed by business people on PC's? I've done my fair share of encouraging my clients to switch -- but why not make it just a little easier for me when they won't or can't?
AAAND I hit a showstopper bug...
At some point during my drafting, accessing the master slides became IMPOSSIBLE. Hitting the "Edit Master Slide" button after tapping the canvas didn't work... nor would selecting "edit master slide" from the menu bar pulldown. Quitting and re-opening keynote wouldn't work either. The only way around it, I found was to save the file out to Keynote '09 and then re-open it in Keynote 6.0
I'm sure I'll discover more as I go.... but for now that's what I've got.
Lastly -- Does anyone else find it telling that Apple's product managers finally decided to change the numbering system from the year to a version number...? Make it not so blaringly obvious that they hadn't updated the software in YEARS. Ugh -- Apple truly is a hardware company. Been focusing on incrementing their silly ipads and iphones for too long. If you're going to create a closed system - how about focusing some more energy on the core apps that make them usable, instead of throwing it to the world to do it for you.
Thanks!
-s

FYI - I recieved the following from the iWork product team via email in response to the Master bug. I sent them all the information along with the buggy file... but didn't hear back beyond that. At least it's nice to know they're listening, even if not responding.
-Shane
Hello there,
We have heard about your issue from the discussion thread below:
https://discussions.apple.com/thread/5480664?tstart=30
We would like to know if you would be able to provide the following:
1. Can we get a copy of the file?
2. How did you create this file? (in Keynote 6.0, imported from Sage, or created on an iOS device)?
3. Is this a local file? Or is it stored on iCloud?
4. Can you reproduce this issue consistently? If so, what are the steps?
5. If you can’t reproduce the issue, do you recall what were the things you did before this problem occurred?
6. Were you working with other apps (copy/pasting, switching apps, etc) at the time?
7. Any other information that may help us reproduce the issue is appreciated.
8. Can you provide us with the Console logs as you are running into the bug.
Console logs:
1. Launch Console app from your Applications/Utilities folder
2. Click the Clear Display icon on the Tool Bar
3. Launch your app and your steps to reproduce your issue
4. Copy the log on the right pane
5. Email this back to us
Thank you,
The iWork Team
15320640

Is there a breakdown for Cisco bug ids?

I'm curious about what the values in the bug id represent. For example. All bug ids start with CSC followed by two letters and a series of numbers. Do the two letters represent anything beyond random unique values? I was hoping that by looking at the release notes for a new code release, that I could easily identify what type of bugs were fixed. More specifically in my case, I want to easily identify if security vulnerabilities were fixed in a particular code release without having to maintain a comprehensive list of all the security bugs.

Short answer: No special meaning, just a sequential counting identifier.
Longer answer:
DDTS (Distributed Defect Tracking System from Rational Software was the original bug tracking system that Cisco installed in the early 1990s for the software that would eventually come to be known as Cisco IOS. The bugid format enforced by the software at the time was XXXxxNNNNN. Remember, 1990 was pre-web - this was all 80x24 terminal screen and character based. Pre-Y2K bugs. A long time ago in a galaxy far, far away.
At the time the lettering was selected:
CSC was for "Cisco Systems Corporation"
di was for "Defect Identifier"
and then the number was just a sequential defect number.
So the earliest bugs were of the form CSCdi12345.
This went well until the 100,000th bug!
At that time, it was decided to increment the letter, to dj, dk, dl, etc etc. as it it were just a counting digit. CSCekXXXXX is the highest set I see in the 12.4 release notes.
Don't be alarmed that the number is so high - defect identifiers are assigned for ALL defects and also a lot of administrative testing events, including ones in internal testing and very early development. A small fraction of identifiers apply to released code.
At some point, the IOS "S" family of releases picked new two-letter baseline for some classes of bugs. "sa" formed the baseline defect identifier for a revised code base, and I see bug identifiers in the CSCtcXXXXXX range at this point. It seems that the 15.0 release now uses that "sa-and-higher" counting index, as does the ASA. I'm not sure what event moved people to start using the "sa" baseline.
I think some other Business Units may have picked other baselines, but it is most appropriate to think of the two-letters-and-five-numbers at the end of a bugid as just a 7 digit number with base-26 as the high order bits.
There is no specific signifigance to the lettering, just a lot of history.
Athough DDTS was replaced some time ago, so many tools orbiting the system expect the CSCxxXXXXX bugid form that its use persists to this day.

"Search Results Go To" tentative Bug Report

Start from the following simplified situation:
Then go tho the Numeric Control terminal and right-click>> Find>> Local Variables.
The Search Results window should show this:
If you double-click any of these two occurrences, LV will bring you to it.
Now change one of the Numeric Control local variables into a String local variable (simply left-click on it and select String from the drop-down list.
You'll get this:
Now check the Search Window again (don't do a search, just go back to it).
It hasn't been updated!
If you double-click on the second "Write" item in the list above (which does not exist anymore, since it is now a local variable associated with String), you will be brought to...the String local variable:
Brings you here:
I would have expected something similar to what happens in the Search Results window when you delete an object, that is, the occurence of this object in the Search Results window becomes grayed out, like this (check item 2):
which proves that the Search Results window CAN respond to user events happening in some other windows
Now, are you ready for the best part?
OK, so if I Undo the deletion of the local variable on the diagram (which I did to obtain the snapshot above), what do you think happens?
Well, obviously nothing, to be consistent with the previous lack of update of the Search Results window... or wait... it did actually react to a deletion, but it does not to an "undeletion"?
So now we have two "Numeric Control" write local variable on the diagram, but only one is accessible from the Search Results window (same snapshot as above).
I tried the usual black magic Ctrl-Run Arrow trick, but to no avail.
I'd say it is a bug.
Tested in LV 2013 SP1 W7-64

Jeff is saying to stop creating code in LabVIEW that has bugs. The steps you undertook to come across this bug within LabVIEW itself are very unusual. You created a local variable of the wrong data type. Then you needed to search through that code for all the instances of that local variable and need to replace it with a local variable of another data type. As a result, the search dialog box just didn't handle its updating as cleanly as you would've liked it to. If you didn't create a bug in your code where you used the wrong local variable, you never would have needed to do the search and replace that you did.
In order to stumble across the LabVIEW bug, you had to create a certain set of circumstances that no ordinary LV programmer has ever seemed to done. There is a reason why this particular LV bug has never been discovered before. Using the wrong local variable and needing to replace it with another this not that uncommon. But using the wrong local variable that is one datatype such as numeric and then needing to replace it with another of a different datatype such as a string, especially much later that you need to use the search function to find them all, normal people just don't do. Usually, you figure out you have the wrong variable when you see you have the wrong datatype and it doesn't wire up to the rest of the code the way you might expect without broken wires.
I'm sure NI appreciates you finding bugs and reporting them. You seem to have an uncanny ability to find bugs that nobody else seems to come across. More than your fair share. I don't know why that is. Somehow I think you have a different mentality than other programmers that leads you down paths that others just never think to do. Whether that is a good thing or bad thing, I don't know. NI takes notes issues CAR's and evaluates them and tries to fix them as they can based on priority, scheduling, resources, .... They aren't going to be able to fix things as quick as you might like them too. And if it is bug that is not significant, or not affecting a lot of people, or has a viable but perhaps inconvenient work around, then it is going to take them much longer to get to fixing it then a major, showstopper bug that affects everyone with no workaround. It might even take years. But you seem to have developed more of a negative attitude such as "I can't just believe NI allows this bug to exist in their code that obviously has existed for years" for bugs such as this that I don't think anyone before you has ever come across before.

Experts: How to deal with showstopping bugs?

I was working on a project where I had to emulate the GUI from a 3rd party app. I hit a snag regarding keybindings.
http://developer.java.sun.com/developer/bugParade/bugs/4632139.html
To make matters worse, most of the classes affected by the above bug have finalized the methods I'd like to fix :( .
So now I'll ask the experts. What have you done in the face of showstopper bugs? Any brilliant hacks or workarounds or methedologies you'd like to share?

Like so:
    class KeyBugMap extends HashMap {
        public Object put(Object key, Object value) {
            KeyEventWrapper wrapper = new KeyEventWrapper((KeyEvent) key);
            return super.put(wrapper, value);
        public Object get(Object key) {
            KeyEventWrapper wrapper = new KeyEventWrapper((KeyEvent) key);
            return super.get(wrapper);
        private class KeyEventWrapper
            private KeyEvent event;
            public KeyEventWrapper(KeyEvent event)
                this.event = event;
            public int hashCode()
                //... add mod to KeyEvent hashCode here
            public boolean equals(Object o)
                //... add mod to KeyEvent equals here
    }

FCPX, just the tip of the iceberg

I know that everybody on this forum felt, at some point, a kind of hesitation regarding the software "I don't want to call it upgrade because it's not". I felt the same, but for some reason, probably related to my blind trust in apple and in all what Apple does, I hit the buy button anyways.
My slow internet connection allowed me to take my time to watch and read plenty of reviews and demos while the software was downloading, most of them were exciting except for the one issued by Apple in which we get the shocking advise to not install FCPX on the same disk where FCP Studio is located! I panicked because I had a project still in the rough-cut stage and I just couldn't afford not to be able to continue working on it on my FCP studio applications.
But It was too late as FCPX was installed and all of my FCP Studio apps were moved to a new folder.
I followed Apple's advise in moving my FCPX to a new folder and then bring FCP Studio apps back to the application folder where they used to be.
Apple instruct to lunch Motion-4 first, so I hold my breath and did just that, it launched perfectly well, I tried the rest of my FCP Studio apps, everything was working well. ufff, that was a at least a good start.
Now to FCPX, the app launched in no time and that was my first good impression, sat back and contemplated the UI and for some reason I felt HOME.
I'd barely used iMovie before, except for it's built-in trailers that I find funny to use as a teaser to showcase among friends, I'd never used anything else for editing except FCP "since version 2"
Second impression was, again, speed, a 2 minutes cut took less than 5 minutes of editing, I was literally flying cutting those iPhone-4 clips taken last weekend while cycling.
Third impression, still in the positive side, is the export speed, THIS-IS-THE-FUTERE.
everything worked smooth and like magic, smooth cam did a huge job stabilizing my shaky cycling footage, color correction and effects gave the whole movie a totally different look and feel, the rendering speed was just phenomenal. I was hooked to the bones.
I'm not here to defend the software as an absolute must have, neither I am here to tell you that it can replace FCP studio right now,not a all. We still got to keep FCP studio for some time... we all know that.
The actual version of FCPX is not perfect with some glitches and missing feature we all know about, but still, I can confidently say that this piece of software is indeed A GAME CHANGER and it will SOON grow on us in every direction. Apple must be busy working on the next update as we speak so let's keep the moral high.
I highly recommend every FCP user to get the X version and start getting used to it. Personally I'm taking the X experience a step further, I'm enjoying it

"all the clip connections live in the editor's head" - You can't import in and out points based off of time code? ***? What? Even SMOKE can read FCP edits. Premiere can. Avid can. Randy's telling me that FCPX can't?
A "new paradigm in editing" indeed.
Nobody wants to answer the basic analogy here: If Photoshop CS5.5 didn't open up PSD files from any version of Photoshop (which it can, by the way), would people be upset? Yes, this is a huge dealbreaker and a showstopper. This should be classified as a major showstopper bug, in all actuality.
Mail form Randy Ubillos, the designer of FCP X
"FCP7 projects do not have enough information in them to properly translate to FCPX (in FCP7 all of the clip connections live in the editor's head, not in the timeline). We never expected anyone to switch editing software in the middle of a project, so project migration was not a priority.
Final Cut Pro X 1.0 is the beginning of a road, not the end."

I'm struggling to install Logic Pro 9 upgrade on Mountain Lion

Way back we bought one of the last pre-Intel G5 in order to do music processing. We also bought Logic Studio v6 or 7. Then we upgraded to Logic Studio 8 and later decided to use a macbook pro instead of the G5. So far so good. We then upgraded to Logic Pro 9 and can run this on Lion on the Macbook Pro.
My partner is now working away and takes his Macbook with him, so we want to set-up Logic 9 on my macbook pro which is running Mountain Lion 10.8.4. Once this is done we will take it off his machine, so not pirating in any way.
I have managed (at great length) to install Logic Studio 8 on my machine using Pacifist, and I can open it and create projects etc... I now want to install Logic Pro 9 on this machine but I get a message saying that a qualifying copy of Logic or MainStage was not found on the disk. To complicate matters, we can't find either the logic pro 9 disk or an image copy, so I downloaded from the following link:
http://dl.dropbox.com/u/2972851/logic-downloads-fixed.html
which I found in this thread: https://discussions.apple.com/thread/4948612
I have already spent many many hours fiddling with this, does anyone know how I can get around this problem?

Im using LPX and have found it to work well.... and no less stable than LP9 in terms of general stability. There are some bugs but given we are still in the early stages of development, that is not surprising and is no different to how it was with LP8 and 9 in their early days. I should add I haven't come across any "showstopper" bugs that affect my own personalo workflow and method of using Logic... just a few niggles and minor annoyances... that for the most part can be worked around if they haven't already been fixed in the 3 updates that have come out since initial release.
I have had no real issues with importing LP9 projects into LPX other than of course, the lack of 32bit Plugin support in LPX which means LP9 projects that contain 32bit plugins.. will not fully import into LPX. The midi/audio data imports ok.. the 32bit plugins will be missing however... if you don't have equivilant 64bit versions installed. For me, this issue has been very minimal simply because almsot all the plugins i use, have already been updated to 64bit versions over the last few years.
There has also been an issue with certain parameters in the track/region Inspector after import into LPX, containing weird values.. I have only had this issue once out of maybe 40+ LP9 Projects and in this one case i simply reset the values and all was well. Other users have reported different levels of how often this occurs.
Note: Once a project has been opened and then resaved in LPX the LPX version cannot be opened in LP9 as project compatibility is only backwards and not forwards.
If you cannot find your disk and serial..(which you will also need) Contact Apple as they may be able to provide you with replacements disks if they have any left. Bear in mind if, as it appears, your LP9 is an upgrade from LP8 you will also need your previous LP8 serial as well as your upgrade LP9 serial to properly install Logic on a new Mac. Once installed you can and in fact must... then update LP9 to 9.1.8 via software updates in LIon or Mountain LIon... for Logic to under those OS versions.

Spanning Columns, Messes TOC Order

Hello
I have earlier posted a thread with my problem. See: Re: TOC Problem, Wrong Order, Connected/Unconnected Text Frame
Now when the problem is tracked down (spanning of columns) I choose to create a new thread hoping that someone has encountered the same problem and has a possible solution. (Using CS 6)
The problem:
I have chapters (H1) with sub-chapters (H2). The text is flowing freely between the chapter text-frames, until a new chapter (H1) starts. The chapter title (H1) spans over all columns, defined in its paragraph style.
When creating a TOC I have found that if a sub-chapter (H2) is above a new chapter (H1) the spanning column function messes up the TOC order. See chapter 1:4 in my example.
The problem may be bypassed by doing one of the following things:
Disable the column span of H1. E.i the chapter heading in a single column messes up the original layout.
Connect all text frames. E.i, flow text thru all text-frames, may become a problem when rearing the chapter order.
Remove the text-frame connection of the text-frames….
None of these solutions are sufficient. I have never during my 13 years with Indesign encountered such showstopper/bug.

Thanks for your replay.
The numbers is written text to make it easier to comprehend the example. These are not auto-generated.
In the other thread I had got some response:
"When the textframe flows from an even page number to an uneven page number the problem (like from page 2 to page 3) the TOC is incorrect.
But when the textframe flows from an uneven page number to an even page number (like from page 3 to page 4) the TOC is correct."
Which does not make any sense at all.

IOS7 slows down iphone

I am the biggest fan for Apple. I love using Apple gadgets and my iPhone 4S. I am pretty knowledgable in technical aspects of OSX and iOS and its basic functionality. After i updated my 4S to iOS7, my device has bcome dead slow though d free space is 4GB+. Its pretty annoying and disappointing. There are several apps like "Google Places" crashes though i try to reinstall it. I personally feel iOS7 has attracted many disappointed clients like me.
It takes time to call back when i access a missed call on my locked screen.
It takes time to access any app when i access it on my locked screen
Camera doesn't let me click as easily as i was able to to do it on iOS6 and many more..
I tried reinstalling the OS and have done all possible troubleshooting by myself and also by taking help from my Pals who are apple certified technicians and the situation remains the same.
This article is for iOS developers to rework ASAP on the bugs identified to ensure they dont drop the value of their product.

This article is for iOS developers to rework ASAP on the bugs identified to ensure they dont drop the value of their product.
This is a user-to-user tech support forum and Apple and their developers do not routinely read posts. If you have something to say to Apple, post it here:
Apple - iPhone - Feedback

QVPN / QuickVPN - Showstopper bugs identified

Similar Messages

Maybe you are looking for