Frage von strohy:
If I want to edit the sound of a clip with Soundtrack Pro (for example, remove noise) I do that, as usual, from 7 per finalcut "s.Soundtrack Send Pro Audio Project"
I store the file then go back s.and into Final Cut is the sound asynchronously suddenly (faster than the Picture)
I work with and ProRes422 HQ 1080 25p
in Soundtrack synonymous is nothing like pulldown, or set something like
Bit rate is both 16-bit
I'm just a little perplexed ...
Antwort von Schleichmichel:
Keep'st You always have the same sampling frequency? Sounds synonymous higher the sound file?
Antwort von strohy:
I imagine at least s.Sampling nothing. Higher sounds like nothing - the offset is synonymous only very minimal but just noticeable.
Antwort von Schleichmichel:
An "offset" is anything but "will [...] asynchronously (faster than the Picture)".
The offset one can fix relatively easily, despite the detection of the cause.
Antwort von strohy:
An "offset" is anything but "will [...] asynchronously (faster than the Picture)".
The offset one can fix relatively easily, despite the detection of the cause. Video Speed reduced to 99%?
Antwort von Schleichmichel:
Um ... izzit wot??
Without an accurate description of the problem is no help! Is it an "offset", or in fact, different "speeds".
Current fluctuations between Picture and Sound hang usually either of different frame rates was (yes auschgeschlossen) and / or of different sample rates from (synonymous if you have changed anything, maybe something IS bad for your set procedure). Since there was the original soundtrack of the video, which has only made a brief excursion into another program, the error must be somewhere there. So I unceremoniously a digital audio file will not suddenly slower or faster.
Now the video to get 99% speed, that's rubbish. First, you have not yet found the cause, second, the video suffers from such a treatment. Then adjust even more audio, since - depending on the method - with hardly any impairment may be associated ....
But first: What is the problem ...
Antwort von strohy:
The clip has a length of 00:02:54:10 with original sound
Data, according to Final Cut 7:
1080p, 25fps, 422 Apple ProRes HQ,
Audio 48.0 kHz, 16-bit integer
The edited Tonfile has:
a length of 00:02:54:06
Audio 48.0 kHz, 16-bit integer
So up to the fact that there are 4 frames is shorter, everything is identical.
When I open my file in Soundtrackpro is, however, turn on a bit Depth features of 32 bits.
In the Project Settings, I have indicated, however, export the 16 bit - I know now synonymous not know where I could change the bit rate in Soundtrack Pro.
Greeting
Antwort von srone:
I should clarify first time by direct comparison with the original file if the file processed with missing front or rear 4 frames or file a total of 4 frames to run faster, it is different that is the key.
I guess you have the original file in the window cut to shorten it, or the sequence set limits is not clean, so that rather above one possibility under consideration is to move to.
lg
SRone
Antwort von Schleichmichel:
Bit depth is almost care less, as the only resolution refers to the dynamics, and not to the sample size (and thus does not affect the running time). Within an audio editing program that works in 32bit kindly to minimize the rounding error in any destructive signal processing (less noise). That is exported in 16 bit relieved, the return import as rendering accounts. Therefore everything is correct.
It is based on your descriptions do not show whether a variation is present. One can easily find out by simultaneously in a multi-program the original and the edited file is happening.
Should diverge (I do not really believe), then somewhere a change of velocity have been made .... unlikely.
It is intended to run constantly. I can imagine that the InOut marker which marks the area to be exported, not exactly s.der beginning or the end of stand.
In the settings of soundtrack can be synonymous to set pre-and post-trigger times. I never work with Soundtrack, habs only just opened and rumgeguckt have no idea ... so, it is obs. Check again Try it and position of audio data (should be correct because "send" was used ... but who knows) and InOut markers.
