Red-rob Rothkopf
Forum Replies Created
-
Vegas 14 — still has the same issue. I haven’t test in Vegas 15 but I’m guessing still a problem.
-
I haven’t had this happen in a long time, and then tonight when I tried playing with BCC Particle Emitter 3D, I had it start happening.
It worked for a while and then WHAM-O.. enter key goes to start of project or does nothing at all. Play button on both the preview window and Vegas do nothing either… and then after a while, it starts working again (closing/opening also gets it to work for a bit).
Maybe a memory issue?
-
Oh yes.. forgot to mention that source footage is shot with a mix of Sony NX3 (avchd), Canon G30 (avchd or mp4), a JVC, XHA1S (HDV) and GoPro.
-
Ah.. I forgot to mention..
Currently all projects are shot 1080 either 30p, 60p or 60i. My finishing workstation edits master track footage where I apply FX, titles and master the audio. My editing station typically edits 4-7 source videos (multicam) to create that master track video for finishing.
It would be nice not to have to prerender before editing.
It would he nice if prerendering was at leat 1-to-1 speed.
It would be nice if final rendering to DVD (MPEG2) or H.264 for Web would be at least 1-1 in speed, instead of 2 or 2.5x media length.
-
Ah.. sure.. I totally get it. ☺
For the record, we are in Buffalo
-
Where are ya based.. maybe it’d be cheaper to hire a camera op who already owns one?
😉
-
Whenever a lighting designer for stage productions asks me, I always give them this same answer:
- Do NOT mix LED and Tungsten lights for front lighting on performers. We’ve seen countless times where conventional cans are used for front lighting, but then they’ll use LED up-lights on the downstage lip of the stage (blue/black, reds) — whenever a performer gets on top of them the cameras ONLY see that color on them, which is extremely intense — all other colors get washed out and it makes exposing for the performance extremely challenging.
- LEDs are *great* for accent, hair-lights, cyc lighting, side-lighting, etc. When there’s a choice, use tungsten-style lighting for frontal lighting, not LEDs
- If you must use LEDs for all your lighting, then use them for all of your lighting ☺ We do shoot one venue which recently put in all LED lights, but still has non-LED spots. We white balance our cameras for Tungsten but set them closer to 3400 than 3200 if we want things to look a bit more natural.
Regarding the blue as purple — my gear is a mix of Canon, Sony, JVC and GoPro — we can white-balance all to the identical temperature, but they’ll see blues/purples differently.. same thing goes for red/pink. I think we finally got them to match most of the time now by mucking with the different color-space profiles in-camera.. very VERY glad we took the time to do that.
-
Theoretically it should work perfectly, but as with any wireless gear there is risk of interference to foil your plan ????
I’ve used it successfully to:
- Send a wireless feed to my switch 100′ away across the Richmond Aud
- Send wireless feed from the stage wings to my switch
- Test hand-held walking around my house (worked fine until out of range)
- Send signal from from FOH to a backstage monitor
That all said, I’ve been let down a few times where I kept getting sporadic (unexplained) signal drops leading to us not using that camera in the switch.
Regarding latency, it hasn’t been an issue at all with this device. When it works (which is the majority of the time) it is a joy to have. Although I’ve gone direct into my switch with it, I do convert other HDMI signals to SDI for 100-150′ runs and haven’t had issue. I delay my audio 66ms to compensate for switch output delays, but I don’t believe that has to do with HDMI->SDI conversions, and definitely not because of the Aries Wireless Pro.
-
OOPS.. I totally forgot about that one.
THANK YOU.
Since there are multiple forums, and multiple support and download areas now, it’s not really clear where I (we?) need to look for updates and such.
-
> We follow Agile development methodologies and therefore do not have a
> set schedule for releasing updates.For 16 years (leading up to my decision to be a full time life journalist) I worked as software engineer, and lead technologist for a software firm. We switched to Agile methodologies the past many years I was there, so I’m familiar that while still within that paradigm, teams are able to meet production goals. We had lists of critical fixes, and prioritized enhancements and implementation of new designs (and products). Being Agile allowed our team to create deliverable releases if needed, and whole blocks of work could be done and tested without having to wait for the full release to come together.
To say that Agile development disallows scheduled releases I believe may be selling Agile short a bit ????
> Rather, we release an update when we feel that the work we’ve done is significant
> enough and benefits enough users to prompt one.That makes sense.
AND — it seems reasonable (to me) to share your prioritized bug-fix list and enhancements list with customers so they can look forward to the release when it happens, ya? Nothing to gain (IMO) by keeping this info. private.
> We’ve already had three updates since the initial release which have fixed bugs as
> well as added new or improved functionality, and a fourth is due within days.Woo hoo! I haven’t seen a published release history anywhere, so this isn’t something I was aware of.
> We use several methods to let users know that a new update is available including
> forum announcements,Where? Here on Creative Cow? On a Magix forum somewhere?
> but you can always visit your user page at https://www.magix.com to
> check and see if you have the latest build.Every time I’ve done that, even when new builds were available, it says that there are no new updates.
For example, I just checked.
- Vegas’s ABOUT box shows I’m using Version 14.0 (Build 178) 64-bit.
- Going to the MAGIX Tech. Support “Personal Service Area”, in the upper-left is reads “Patches for your products: There are no patches for your registered products available.”
This is the same thing it said before I installed Build 178 when it was available.
> To download the update, log onto your MAGIX.com account. Then, click MyProduct and click
> the Installation program link.
> After the installation is complete, you will have the latest update.Yup. That’s how I got the last one installed. The thing is — I can’t find anywhere that it actually tells me *which* version will be downloaded and installed, or the ability to see corresponding release notes (bug fixes and enhancements) so I can tell whether or not I want/need to go through the install process.
> We’re committed to VEGAS Pro and that means not only working on
> future functionality, but also improving the current version so that we
> can provide the most stable software possible.I appreciate that commitment 100%.
Thank you!
????Rob