Gearshift Overdrive? M2t render work around

epirb wrote on 7/5/2005, 10:02 AM
In light of the issue, of too many m2ts on the timeline causing a render crash (see other post). Is it possible to adapt the script to do the same thing with the Cineform intermeadiate files ?
For instance if we were to create CFDI's from the m2t originals.
then the Gearshift option of creating proxy files -instead of converting the m2t file we convert the CFDI file to a dv proxy, do our editing, then "Shift gears back to the CFDI for rendering.
I know its a few more steps but not nearly as many as I have had trying to "work around" this issue.
I'm not knocking Gearshift, its a great tool,I love how "it" works and I like working with the proxies, it 's more the issue of Vegas NOT being able to handle many M2t files on the timeline.
My work flow for this recent project requires many small clips, and the time required to rerender , subdivide the veg etc... is costing too much time..
So I'm turning the Batlight on for JohnnyRoy the Script master, is this a possiblity?

Comments

Wolfgang S. wrote on 7/5/2005, 12:04 PM
I do not know if such a "workaround" is feasible, Jonny and Douglas should be able to comment on that. But I think that Sony will come up with another update to fix that bug, hopefully in the near future.

In the meantime it is better to capture long files - and limit the number of m2t files in the timeline. However, I am aware that this is not a solution, but only another workaround.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

JohnnyRoy wrote on 7/5/2005, 12:10 PM
HOLY RENDERING BATMAN, COMMISIONER ERIC NEEDS OUR HELP! ;-)

Actually, Spot and I were discussing this just the other day. We agree that the CineForm files would be of more use as a final render format than a proxy and we should move them to the other list. I am planning an update to GearShift and I’ll include this.

It sounds like you can’t wait for an update so, in the mean time, here is a little trick to work around this. GearShift looks for any rendering template that begins with “HD “ (that’s H, D, <space>) and places it in the YUV dropdown. You can just save one of the HDV Cineform templates as “HD Cineform for GearShift” (or anything that begins with HD space) and you can render your project to Cineform and create DV proxies. GearShift will then shift between the DV proxy and Cineform like you want.

This works because GearShift looks for an AVI file first (in case you made a YUV copy) and then an M2T file. It will find the AVI from Cineform and treat it just like a YUV AVI. In the next update, I’ll place the CineForm templates in the YUV dropdown so you don’t have to do this little trick anymore.

~jr
epirb wrote on 7/5/2005, 4:23 PM
Riddle me this ..... what shines brightly that all can see, but is not light.
Your Brilliance JR !
I just got home and tried your idea with a test m2t file, Creating the "HD Cineform For GearShift" template,then,using GearShift to create a proxy and a Cineform For GearShift avi as per your instructions . did some quick editing and slammed it into 3rd gear(swapping out the proxy, it replaced it with the Cineform avi.)Worked perfect !! Now I can do all my next modules of this project this way.
I'd come up and Kiss you, but ....well my girlfriend might not approve, and I forgot to brush my teeth this morning, and I really dont kiss guys BUT ... you have made me VERY HAPPY! I can continue to use the GearShift method that I love so much.
Sony should be licking your boots or Kissing your feet!
Now Oh Mighty Script Keeper, one last question.
On my current project, being one that has m2t files(orig) and GS-DVproxies that I used for editing.
What would happen if I reGearshifted (double clutched : 0 ) ) the original M2ts, thus creating a new Cineform avi and not creating another dv proxy.
when I went back to shift gears to back to the orig or high quality clips,would it then see the cineform avi instead of the m2t?
All this is wishfull thinking to save the amount of time I have to recover this first project, if not no big deal.
I'm still Amazed that I had what I thought was a great idea, and low and behold you and Spot Allready got something in the works, plus its already really there!

Gotham is Saved AGAIN !
Spot|DSE wrote on 7/5/2005, 4:56 PM
Gee...JR just wrote it. It was my idea. :-) I don't want a kiss, I just want to spend an afternoon driving your super cool, airconditioned leather seats car around the slammin' streets of Miami!
epirb wrote on 7/5/2005, 5:15 PM
Shoot Spot ! I just tried my idea aboveand I think it'll work.
I'm so happy , Heck I'll come mow that ol shaggy lawn you got there.
what is it a mere 50-100 acres, push mower...no problem?
Just got done tweakin' the car the other day, improving its render times ;-).
You can drive it anytime, just kepp Mannie away from my headrests!
JohnnyRoy wrote on 7/5/2005, 6:02 PM
> What would happen if I reGearshifted (double clutched : 0 ) ) the original M2ts, thus creating a new Cineform avi and not creating another dv proxy.

As you already tested and found out, it would work fine. GearShift looks for AVI first, then M2T if it doesn’t find AVI’s. So you can make the AVI files later and it will then shift between the AVI and proxy. If you wanted to shift between the M2T and proxyn again, you could move the AVI's to another directory so only the M2T files and proxies are found.

AND GearShift was definitely Spot’s idea. I don’t even have an HD camera yet. AND kisses are definitely out of the question. BUT I will take a dark beer as payment. (Guinness... the 4th food group) ;-)

~jr
PeterWright wrote on 7/5/2005, 6:19 PM
Not directly related, but a client wanted some stills from an HDV project, and Gearshift was very helpful - used proxies to quickly select still frame, Gearshift back to m2t and make snapshot.

I got a buzz each time I saw the proxy still change to m2t and leap up in colour/quality.
Wolfgang S. wrote on 7/6/2005, 1:10 AM
Johnny,

but there should be the possiblity to have the choice

- if you wish to shift back to m2t files; or
- if you wish to shift back to Cineform Intermediates.

Some people do not like to render their final produkt from Cineform intermediates, and would prefer to use some few, but large m2t files.

Just my 5 Pennys...
;)

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

epirb wrote on 7/6/2005, 5:45 AM
Wolfgang,
I tried a few cenario's with this using the current version of GearShift.
You can do what you are talking about just by either moving the cineform avi's to a different folder temp then it will use the m2t.
or in the case like mine, where I created the cineforms after the fact, I choose not to create avis for a couple of the longer m2ts.
So when I shifted gears back to the HQ files I had many avi's but a few long m2t's on the timeline, as you suggested.
And it's rendering now as we speak with no crashing!
I highly recc. you let your friend with the many clips that you mentioned in the other post ,know about this now workab le solution. At least to help him finish his current project by his Aug deadline.
If he needs more details on how I did it he can email me directly @
epirb(at) epirbfilms(dot)com

Eric
Wolfgang S. wrote on 7/6/2005, 6:10 AM
Eric,

thank you, we follow and discuss also in the German forum the two threads here, describing this workaround and the Vegas-bug.

However, in addition I have forwarded your nice invitation for support to Mike too.

Kind regards,
Wolfgang

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Spot|DSE wrote on 7/6/2005, 8:24 AM
Eric,
If I'm understanding your post accurately, you're suggesting that you used GearShift to place more than one file type on the timeline? I can see how it would work, based on the way it seeks files, but never, ever considered that as a workflow.
Any chance of additional detail?
epirb wrote on 7/6/2005, 10:07 AM
Spot,
here's a brief rundown of this project:
intially had alot of small m2t files, these are component shots compiled into groups, ie a/c main panel tight, wides &medium shots.
(I need to have them separated this way because they will be used in different projects in the future.Plus this way they can be filed as such for quick reference.)
These obviously totaled up to quite a few fairly small files.10-15 20-30 second clips etc. about 54 clips.
Now when you factor in using them multiple times on th T/l for layers ie " cookie cutter hightlight" ,the number count on the T/L really grows.

Then I also had some other shots that were longer and only used once on the timeline(me talking to the audience ,about this specific boat)

So my original plan was , and what I first did was to use the traditional GearShift method, and as you know I ran into the m2t file limit crash on render.

Sooo..... after using yours and Johnny's help what I ended up doing was creating the Cineform avi's for all of my short clips, but NOT my longer Narrative shots. Then shifting gears it used the avi's for all the many and multiple small clips but using the m2t's for the larger longer Narr shots.
Basicly , I did it this way to save time rendering, plus it saved me space on the project hard drive, because as you know the avi's are much larger than the m2t's.
When the project is finished I will delete the avi's and keep all the m2t's for archive

The final output of the project will be DVD and .wmv, My thoughts are that there should be no noticable/visual difference in rendering the two type files on the T/L to the final output formats. But thats where your expertise might tell me different.

Is that what the info your looking for?
Spot|DSE wrote on 7/6/2005, 10:16 AM
That's exactly what I was looking for, and that's a pretty smart way to work around the m2t problem that we're seeing. Gotta try this myself!
epirb wrote on 7/6/2005, 12:43 PM
Plus as you probably already know that was creating the Cineform avi's using GearShift, and rendering to the same folder as the m2t's leaving the proxy set to none ,cuz I already made them earlier.

worked pretty smooth.

Now if I can find a way to chop my long captured m2t's into my little subclips with out rerendering to another m2t file I'll be sittin pretty.