Floh Peters
Forum Replies Created
-
Floh Peters
January 19, 2010 at 9:46 pm in reply to: Weird audio goings on in M100 suite 1.1.2 – help pleaseI think you should give Suite 1.1.3 a try. Not sure if this is a bug that is fixed in the latest version, but worth trying.
-
There is no free upgrade after 11.5.1; and I really don´t know if this is a bug or not. The error message appears on your deck, right? Do you have a chance to try another deck or camera to make sure that this is not something special with this deck?
[Henry Blood] “Any clues on what would make a DV audio signal invalid besides 48khz rate and 2 ch 16bit mode? “
Many things in the FireWire communication protocol…
-
Try to set your system to FireWire out (without the “mastering only”). This probably makes it easier to see where the issue is, since you don´t have to go into Master to Tape all the time to get an output from your system.
Next, in your Media settings (Command M), look what codec is selected there on the left side. The acquire codec setting also decides what you are sending out over FireWire. You could have your timeline in DV codec (or ProRes or whatever) and still send out DV or DVCPro if you set this setting to the codec you need. Maybe it is set to something your deck does not support.
Another thing you could try is to give the 11.6.4 version of Producer a try. Unfortunately as far as I know this was a paid update from 11.5.x, but the download should work as a trial version, which would make it possible at least to test it to see if it fixes your problem. If possible, i would create a copy of the startup drive (e.g. via CarbonCopyCloner), install 11.6.4 on the copied drive and give it a try from there. This way you can revert to 11.5 easily by starting from your old startup drive (make sure to create a copy from your timeline and project files, since I am not sure if you can open files once opened in 11.6.x back in 11.5.x; I think it was possible but I am not really sure). -
[David Crews] “If I select any media clip in any bin, it should show up (at least) in the Batch Reacquire windows, shouldn’t it?
I’m working with voice tracks I accidentally Acquired using the lower data rate. “Usually a good test is to enable the “error display” in the batch reacquire window. In the middle row of the batch reacquire window there is a yellow triangle (next to the “19” in the image).

Click it to see if your clips show up with Std. Mismatch. If yes, this means that some settings are not right and you are therefore not able to reacquire them. This should be fixed by entering the reacquire window while pressing CMD-Option or CTRL-Shift (or all of them), depending on if this is an audio or video mismatch.
Other reasons for clips not showing up could be that they were not acquired from tape, or without a deck control, for example. -
[Paul Crowe] “A) If I do this will this machine run snow leopard? “
Definitely. For web and email this still should be pretty fast (except mabye Flash, which is known to perform badly on Macs). Get as much RAM as you can put into the system, though.[Paul Crowe] “B) What are the other reasons this machine might be running slow and how do I determine this and put them right? “
I would bet that it is the RAM. 512MB is simply not enough these days. Other than that, I don´t see a reason why this machine should be slow. I have a MacMini with 1.83GHz CPUs, and it is extremely quick.
[Paul Crowe] “c) If I can successfully upgrade the RAM and load snow leopard (or not) could I reasonably expect the machine run Adobe CS3 or 4 design premium programs such as Photoshop, Illustrator, in design etc without going insane? “
Definitely. It is not a “pro” machine, but for Photoshop or Illustrator work you should have no problems. Even AE should be fine (although of course much slower than on a MacPro).
-
[Gregg Michaels] “When I hit “ready” the video indicator goes yellow and I lose signal to my hd monitor. “
Just tried it; connected to SDI 1 in is a DigiBeta, and to SDI 2 in is a HD-SDI out from a HDCam deck. Reacquired clips on a timeline using the HD-SDI 2 in on a Kona3 without problems, while the SDI 1 in got a signal from the DigiBeta. It also worked when having no signal attached to SDI 1 in.
How was your audio set up? I see that you don´t try to reacquire audio, but since this works for me I am wondering if there is something going on with an invalid audio sync…
-
[Wickham Strub] “Anyone else out there with a Kona3 having trouble with HD-SDI 2 input on Batch Acquire? “
I can give it a try tomorrow. Haven´t seen that (although we use the Kona3 SDI2 in only occasionally).
-
[John Twigt] “I exported from a program with three buses, but just one audiotrack in the QT player “
Hmmm, that is strange. It works for me. Maybe you should upgrade to Suite 1.1.2?
-
[John Twigt] “Sorry, i just saw that your message was from 03.43 instead of 13.43 (that’s why i made the remark of my late response) , just in case you thought I was sarcastic here 🙂 “
No problem. I already wondered why it took you so long to answer 😉
-
Try opening the exported file in QuickTime Player and look at the clip info (Command J). There you should 2 audio tracks if you have 2 buses, or one (stereo) track if you only have a single bus. Do you see them there?