hi, man, take it easy,
While I feel it may be a waste of time, I will make one last attempt to answer some of your questions.
1) theoretically reversible? I was not talking about the triming operation, I am talking about save operation. Take a test by youself.
I used the term "theoretically" because, while the process is reversible, it requires certain values which the average user is not likely to have at their disposal or want to try and calculate.
The title of your topic implies that you have used QT 7 Pro to select a portion of your clip's progress bar by manually setting "in" and "out" points, then selected the Edit menu "Trim to Selection" option, and finally saved the file with these changes. Further, since you now appear to be complaining that there was no "confirmation" request before the save, I must also assume that your source data was already stored in an MOV file container as content like H.264/AAC in an M4V file container would normally call the "Save As..." routine at this point and ask you to provide a filename for a new MOV file container. Add to this the fact that you say the file was saved with the playback display limited to the segement of the progress bar which you previously selected means that you must have used the "Trim to Selection" Edit option as otherwise the the "Save" operation would have saved just the selection points in the progress bar and would have been an operation which is completely reversible from within QT 7 Pro.
In short, only the active steps of setting. trimming, and saving the file seems to create the situation of which you seemingly complain and then, only if the source file is an MOV file type. As an experienced QT 7 user I am well aware of how the application works and do not have to be reminded or forced to continuously confirm my actions. On the other hand, I suggest you run addition tests to become more familiar with the application and its operation so you can make suggestions as to how the application can be enhanced to better suit your specific needs.
2) I am just a normal user, ok? how can I reverse it now? tell me, or.... tell me you do not know.
As am I. (I.e., I am neither a professional videographer nor a professional programmer.) Since I already covered the "how" of the recovery operation, I will only add that I use the Dumpster utility to access, enter, and save the various values that actually reverse what you have done.
3) yes, a subset of data is currently valid, while, while, while, a huge section of other data is in the file, but I can never do anything about it with QT. Isn't it a piece of junk? Or, you are still rely on other programs to restore it. Stop it, I am talking about QT's context. I guess you are not a software engineer.
Not "a huge section of other data" but rather the entire original file of data together with modified pointer values.
No, QT 7 is an editing utility—not an unediting utility (another enhancement you are welcome to request) nor is it a resource editor.
If you think it a piece of junk, don't use it. It serves my needs as a quick workflow for edits that do not require the use of a full video editing software suite.
To "fix" the changes you have made you now have to overwrite the values your changes overwrote in the first place with the values that were originally overwritten but no longer available within the file for QT 7 to use in your desired "unediting" process. So, yes, I do have to rely on other applications here, as well as, values which I either know or have to calculate and then test by trial and error.
Not familiar with the phrase "QT's context" or what you think you mean when using the term.
Lastly, as already indicated I am not a software engineer. On the other hand I am a problem solver and can often reverse engineer a solution as in this particular case. Consider this process as something akin to the generation of a longhand algorythm to calculate cube roots based on your knowledge of how to calculate square roots in longhand.
I told you your original suggestion is not working so far for me in my first reply. I do not have much knowledge about the MOV files, that is why I feel in trouble and ask for help here, ok? But I feel there might be a way, that is what I am ask for.
I only re-addressed the original suggestion as a possible solution which might be easily applied by an average QT user since the alternative would likely require lengthy one-on-one time to demonstrate. (I.e., something not lightly undertaken except possibly with other members of our local Video SIG and likely requiring more than one session of instruction, demonstration, and discussion to cover not only the basic workflow but also the background on which it is based and use of the utility involved.)
Since you indicated the file was not of any major loss and I assumed your were looking for a possibly quick and simple solution rather than one that requires a software development level of interest, I did not mention a work flow which I did not expect you use requiring software which is no longer be available from the Apple Deveoper's area to access and modify values which you are unlikely to have available.
As to there being a way to do this, earlier today I managed to recover a test file (MOV Apple Tutorial) which I "trimmed" and "saved" in the manner I assumed you had processed your file. Of course, I had the required values available and only had to "plug" them into the proper file locations to regain playback of all the clip's data.
While, I still think you are trying to help. Just do not understand, why it feels like you are protecting apple. What makes it so perfect?
I do not consider my attitude one of protecting Apple or its products. I neither work for Apple nor (unfortunately) own stock in their company. Based on my experience using the QT Pro appplication, I simply have a different concept regarding what it can or should be able to do and have adapted my workflows to avoid your so-called "bugs."
