Red-rob Rothkopf
Forum Replies Created
-
> “open a support ticket”
easier said than done!!
went to their site, and they don’t have an option for a Vegas 14 support issues… they have older SCS software (through 13) and other products they sell.. but not Vegas 14!!
grrrrr
-
When loading my V14 project, it is taking *21 minutes* to load.
0-3%- instant
- @3% 11 minutes
- @ 11% 10
minutes –> Timeline populates then and project seems loaded.
@ 3% my CPU was at 16% (Vegas using 15%), memory @ 28% and Disk I/O at 52 MB/s
When loaded fully, CPU was at 36% (Vegas using 33%), memory @ 56%.I loaded a V10 version of this project into V10, and it loads instantly. (that version was from beginning of day — since then I’ve tweaked LOTS of edits, audio envelopes, and added media effects (mostly color correct).
To assure it wasn’t my changes, I then loaded that same V10 version of the project into V14 as a control. Similar results to my newer V14 version of that project.
- 0-6% 3 minutes
- 6%-11%->100% 11 minutes
- Sat at 100% for another 11 minutes then the timeline loaded.
Because of the theories here that it is the .M2T file format, I loaded that V10 project into V10, removed the .M2T and loaded in both V10 and V14. I ran this test while also rendering an AC3 file in another window.. so I expect these results to be a bit slower than otherwise due to that. That said — without the .M2T file, the load times were as follows:
- V10: 103 seconds
- V14: 130 seconds it jumped from 12 to 100%. Then took an additional 106 seconds sitting at 100% before the timeline
loaded.
MANY times faster than with the .M2T file in V14. So, clearly the .M2T file is causing the majority of the excessive load times (and me to stay up way later than I should! 😉 ) Then there’s some other process after it gets to 100% which is causing an additional delay, significantly quicker still without the .M2T file.
How best to report bugs to MAGIX team?
-
Red-rob Rothkopf
October 3, 2016 at 4:20 am in reply to: SLOW Project Load — Did V14 change File I/O routines? Crash on opening Render dialog. -
I’d imagine that it’s just a matter of finding the correct Mini cable for input into your phone, ya?
This slightly-dated article talks about some different cable/jack configurations, and suggests there is an Android standard now so if you get it working, it should work with all your Android devices.
This one looks close, but may not be wired with the right tips… B&H folks are usually pretty helpful (not always) and might be able to assist?
-
According to this link, you do *not* need a work Visa if part of a film or media crew that won’t be joining the local labor market:
https://www.cic.gc.ca/english/work/apply-who-nopermit-result.asp?q1_options=16
That said, I do believe that registering the equipment you are bringing in is a good idea so when you return they don’t think you’re sneaking gear back and forth across the border.
-
Red-rob Rothkopf
February 11, 2015 at 7:12 pm in reply to: Sony vegas pro 13, only imports audio from .MOV files (PRORES 422(PROXY) 1920X1080 millions)OOPS… installing QT 7 seems to have fixed my problem… sheesh.. so easy
-
Red-rob Rothkopf
February 11, 2015 at 6:58 pm in reply to: Sony vegas pro 13, only imports audio from .MOV files (PRORES 422(PROXY) 1920X1080 millions)FYI — I just received my first footage from a BMD Cinema Cam and am having the identical problem. Audio imports, no video.
It was recorded using ProRes LT. It plays fine in VLC and other players. Vegas only imports the audio. Besides dragging it in, I tried “import media”… says it can’t understand the video format 🙁
ID : 1
Format : apcs
Codec ID : apcs
Duration : 24s 57ms
Bit rate mode : Constant
Bit rate : 102 Mbps
Width : 1 888 pixels
Original width : 1 920 pixels
Height : 1 062 pixels
Original height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 fps
Bits/(Pixel*Frame) : 1.699
Stream size : 293 MiB (98%)
Language : English
Encoded date : UTC 2014-01-31 18:51:03
Tagged date : UTC 2014-01-31 18:51:03 -
I’m having a similar problem in 10e…
Clips are fine on their own, but when overlapping two events (standard crossfade) where one was an AVI loaded from a Sony MRU and the other is DV-AVI loaded from any other camera, this happens.
– Preview.. happens
– Rendering to MPEG2 or DV-AVI… happensChanging Dynamic RAM has no effect… HELP!
-
Hi! Did you ever find out what caused this? I’m having the identical problem when overlapping footage recorded on a Sony MRU and other footage… footage looks fine when not overlapping, but when it overlaps for standard crossfade it shows artifacts with frames jumping between the two clips.
This happens in the preview.
It also happens rendering out to MPEG2, or DV AVI.Changing Dynamic RAM setting did nothing but slow things down…
HELP!
-
Red-rob Rothkopf
June 15, 2011 at 2:58 pm in reply to: Regarding a December post about CD track namesDespite the specs. you sited, there must be some newer standards-based way to include track names in a CD. I say this because I’m re-editing a recital CD created by another professional in town, and when I import that CD into Vegas, every track has a name, and it’s definitely names he gave it, like “songABC_MarcyFinalVersion1”.
I’d love to name the tracks too and/or preserve the names he gave it after importing the songs and creating a new CD, but haven’t figured out how in Vegas to save track names. 🙁


