No problem here either.
I'm willing to ask if you changed something in the template th\at you "forgot" to tell us about . . .

Hi Phoo,

What is a 'native' mov? Is it 29.97 progressive or interlaced?

"Click the Render button and absolutely nothing happens." This doesn't happen on my SMS13P, it renders as usual.

"Even though the project was created with this format MainConcept MPG-2 defaults to the Blu-Ray 1920*1080-24p output." What exactly is 'defaulting' to 24p?

@ musicvid10, "I'm willing to ask if you changed something in the template th\at you "forgot" to tell us about . . ." I tend to agree, if there is something in your source media, project properties, and/or render template from what you have told us, it may be the cause why we cannot duplicate your issue.


Best Regards.......George

No, no change in the template.

However, I had tried to use the Stabilize effect IN the track effects chain. There's a good likelihood that was related to the problem. I had removed it since it won't work there. I have jus upgraded to MS13 from MS12 and this was a learning moment. (grin)

-- Having the Stabilize effect in the video track, instead of applying it to the media clip will prevent rendering. Movie Studio really should block inserting effects that can't work in real-time from being inserted in the track effects chain, but it doesn't.

Even though I had removed the effect seems as the damage was done, setting up the failure scenario.

After this I needed to reboot to get any rendering to succeed. Even the project that had worked before wouldn't render anymore. After a reboot - AND PROPER USE OF STABILIZE - everything worked as expected.

Music Studio 13 is lacking in good error checking in these scenarios.

(Meant to post this update last night, but it was getting late.)

George,

'native' mov is the video straight out of an iPhone

Streams
Video: 00:10:08.562, 29.982 fps, 1920x1080x24, H.264
Audio: 00:10:08.618, 44,100 Hz, 32 Bit (IEEE Float), Mono, AAC

" What exactly is 'defaulting' to 24p?
The defaults of the project when using the MainConcept Blu-ray 1920*1080-24p template. Since that is THE PROJECT DEFAULTS it seemed unusual to me that the project wouldn't render that format, but would render a different format.

>>> After a reboot - AND PROPER USE OF STABILIZE - everything worked as expected.<<<

Are you sure you did not see this?
https://dl.dropboxusercontent.com/u/50473571/SonyStabilize13.JPG

vmast....yes I DID see that, didn't at first.

As a new-ish user, Music Studio should not allow me to insert plug-ins that will not work there EVER. Yes, I was wrong to try that.

Yes, user beware. Knowledge is wonderful and so are docs, yet I had removed the effect when I found out it wouldn't work. Even after that I needed to reboot, not just restart the application. (hardware acceleration had gotten horked)

>>>I needed to reboot, not just restart the application<<<

You probably will also need to reset and delete cached data on occasion.
You have been warned.

Hi Phoo,

"As a new-ish user, Music Studio should not allow me to insert plug-ins that will not work there EVER."

I have ver 13 build 955. It will not allow me to manually adjust, or 'Apply' a preset to an Event Stabilize FX. So, your issue I cannot duplicate.


Best Regards.......George

George,
My MSP 13 build 955 adds it to the plug-in chain, but does give the warning linked above.
Easy of course to remove with one click in the Video Event/Track/Output FX windows.

Of course....easy to remove, and there is a warning.

If it's smart enough to give the warning it's smart enough to not allow insertion. This is IU and user friendly 101. If it causes issues, is known to be not supported, then don't let them do that.

Yes, easy to remove, which is what I did.

My issue ultimately was that rendering was horked, even after removing the plug-in. Horked so much I had to reboot the machine to get rendering back.

Regardless, I'm good. I learned a lot and know what caused the problem. Will not do it again.

Thanks for the thoughts and questions.

Hi vk,

I think we are saying the same thing, it allows you to put it at the event level, warns you it will not work, prevents you from using it on the event, and advises you to apply it on a media level.

I thought Phoo was implying it worked on the event level, therefore corrupted the ability to render, then when it was removed, the same corruption continued until the system was rebooted.

I was trying to duplicate the issue that Phoo had and cannot. I'm probably missing something. I was also puzzled at the comment about upgrading from ver 12 to ver 13, as I had no problems doing that, but understand sometimes it's a matter of different folks, different strokes (results)!


Best Regards......George

George, you're probably right. I did not try to duplicate, I've always done in this what Chaka suggested way back when ("heed the warning and everything will be alright ").

I've come to a rather compelling conclusion over the years that some people just don't like instructions!
For those individuals, either magical thinking works or it doesn't . . .

Having recently retired after 20 years in the software industry I'm not surprised at the attitudes about READ THE FUCKING MANUAL. I have spent 20 years trying to make things better for early installers - new users - of applications. It's no wonder folks hate some software companies. Even new users read the manual and try to do things that are easy for experienced users. New users make mistakes and they don't know the product well enough YET to know what the real problem is.....EVEN WHEN THEY TRIED TO DO EXACTLY WHAT THE DOCS SAID.

I tired of running into issues that could be not only easily avoided but impossible to do with almost no effort from the dev team

I do have a question that is relevant.

How can I tell which effects will not work in real time before I accidentally try to use them in the track and hork my machine again? Seems like the only way is to try them, see which ones pop a warning - if they will - just wait until the app won't work

Your experience will likely facilitate the learning curve somewhat, but not replace it.
Attitudes change as a direct result of gaining that experience, as one discovers that there are many incompatibilities and physical constraints to self-expression using a nonlinear editor. The presumption that the software is always to blame is simply incorrect.

While you're waiting for that experience to accrue, kindly take it easy on your peers, and take their advice graciously, even if it doesn't quite match up with your unbridled expectations.

In the case of Stabilize, it must be applied at the Media level and rendered BEFORE proceeding up the effects-processing hierarchy. It is a simple, unavoidable physical constraint. A second, entirely unncessary render would have to take place if were applied higher up the effects chain; the logic of that being inescapable. If you don't like that constraint, I'm sure the developers will welcome your code patch with open arms, which you sound eminently qualified to write. Doing stabilizing and effects processing in parallel is an entirely new concept to me, but I won't rule out the notion that you may be on to something.

Really, we're only trying to help, but peer user assistance has been known to drop off precipitously when sniper-fire from a novice user is detected.

Sony has provided technical support and feature request pages for those who need to escalate their concerns, but those resources won't be reached through this forum, sorry to say.

That said, welcome to Vegas.
"

Suppose I am driving on a familiar road and choose to or accidentally ignore a sign warning about a hole. Am I likely to hork my vehicle in that hole, if I don't take a detour?

Hi Phoo,

I appreciate your question, "How can I tell which effects will not work in real time before I accidentally try to use them in the track and hork my machine again? Seems like the only way is to try them, see which ones pop a warning - if they will - just wait until the app won't work"

Part of the answer may be in your answer, that I have asked before, how can I duplicate your original issue? You are the only person that can answer this.

Please correct me if I am wrong......you used the stabilize FX on the event level despite the warning and that 'horked' your system. I cannot get that to 'hork' my system. Sony Stabilize FX on the event level simply does not work. Trying it results in a warning and nothing else. It doesn't corrupt my system preventing a render. Is there something else you did which I can duplicate, that may have lead to this situation? If you are correct that the cause is by the development team, I and others should be able to duplicate the issue.


Best Regards.......George

You are correct.

I put the Stabilizer in the track, on the event level, by mistake.

Then when I tried to render, nothing happened It would not render. That's more than the effect simply not working.

At that point I switched render from 24p to 60i and it succeeded. This is when I caught the mistake with the Stabilizer. I removed it. Tried to render again and clicking the render button did nothing for either 24p or 60i.

Exited Movie Studio and restarted it. Opened the project and was not able to render, any format.

Rebooted the machine and was able to render again.

I just now tried to open that project. to see if I can repro the problem again. Unfortunately, it will no longer open. Movie Studio pops an error that it is an invalid project.

"How can I tell which effects will not work in real time?"

This seems like a legit question.

"...the first thing one must do to get out of a hole is to stop digging."

A wise teacher said that.

Would it be feasible for you to reset (not reboot) as per SCS KB item 2744 and create the same project from the start (avoiding the mistake you made) in case the original project got corrupted? See if that'd get you out of the hole.
Be sure to see the window mentioned in the KB item.
Just asking what I think is a legit question as well.

Seems moot since I can't repro this any more, or many other issues.

I'd rather find steps that will cause it to happen 100% of the time.

"Don't do that" is not a bug fix.

Just because it doesn't repro 100% of the time doesn't mean there is no bug.

Intermittent bugs such as the ones I have been hitting are the hardest to track down.

I will try to be more aware of my steps in the future.

Sorry I asked. I try to be more aware of your philosophy in the future.