Any chance the -itsofffset option will be implemented one day?
I'm aware about another thread related to the issue and that you've already made it much better in version 0.7.1.
However, I'm forced to disable so4compoundplug in VP15-17 as it has issues with my 5.1 sources so I still have 1 frame audio shift 
Thanks.
5.1 audio works in my tests now. MediaInfo 20.03 reported 6 channels as for source.
I've tested it in VP18 (Free Trial) as well and everything as it should be: 5.1 audio in rendered file.
Waiting build for earlier VP versions.
Thanks a lot and take care.
Could you advice, was the issue fixed in recent versions of connector?
Thanks.
UPDATE: NVM, I checked Vegas Connector version 1.0.0 and the issue is still there. Only Mono and Stereo available.
I wanted the feature to render without audio. I was using this for testing only.
If I need to choose what to have at the end -- 5.1 or ability to render video only, I'd choose 5.1 for sure.
I do not really understand what fix you are talking about.
I've experimented a bit and tried to fix the offset in mp4 rendered with connector 0.5.1 using itsoffset ffmpeg option:
ffmpeg.exe -i voukoder.mp4 -itsoffset 0.044 -i voukoder.mp4 -map 0:0 -map 1:1 -acodec copy -vcodec copy synced.mp4ffprobe synced.mp4:
start_pts=1056
start_time=0.022000However, the synced.mp4 file behaves in VP exactly like file rendered using connector 0.7.1: if so4 disabled (default in up to VP14) -- the audio stream shifted one frame behind comparing to when so4 is enabled (default in VP15+).
So looks like the VP's decoders decode audio streams differently depend on the start_time stream information.
I suspect that Happy Otter Scripts is also affected.
As a result, you cannot actually fix this using the offset and the only way to fix it properly for VP is to add silence at the beginning or trim audio.
In any case, current implementation looks better as audio shift is smaller.
I'm having the same issue with connectors 0.7.0, 0.7.1.
In my view the audio rendered in voukoder is 1 frame AFTER the original audio, just see that the peak of the audio signal is on the right, when compared to the original audio. This happens in mine and in your screenshot.
Sure. But previously you said 'ahead', not 'after'. I said 'behind' == 'after'.
Yes, I also have the new so4 decoder disabled in internal preferences as it does not work correctly with my AC3 5.1 audio streams.
I'm confirming that when the so4 option is in default value (TRUE), the audio in mp4 file rendered with voukoder connector 0.7.1 is in sync with original audio.
When the option is in non-default value (FALSE), the audio in rendered mp4 file is 1 frame behind.
You do not need to re-render, just change the option, restart VP, put original an rendered on timeline & compare.
I've found my footage with Stereo (1080-59.940p, AC3 Stereo) and only see 1 frame offset after rendering (audio 1 frame behind original audio. I do not know why other member says it is ahead, based on his screen shot I'd say it is 1 frame behind).
Then I was able to correct it further using atrim filter (Start = 0.033, start in frames did nothing):
I do have the same issue with 5.1 audio: only 1 and 2 channels shown in audio config.
Rolled back to version 0.5.1: no audio config, but it rendered as per project settings.
With FFmpeg AAC only STEREO mode seems to be affected.
In the topic I started (link above), I rendered to AAC 5.1 and it was also affected (source -- m2ts from camcorder with AC3 5.1).
While comparing, I removed all audio tracks from project but front channel only for simplicity (otherwise it would be 16 audio tracks in comparison project: source, wav, Sony AVC, Voukoder -- a bit too messy) . However, other channels are also affected.
I can upload project + source again if needed.
Hm, I thought it is already on the list as I reported the issue:
I wish it would be possible to specify params that are passed directly to ffmpeg.
I'd use the -itsofffset then.
As in the AMD table there are "Yes", "No" and blank values provided in "xyz Encoder" column, I believe blank value means "no information available".
That is sad.
The audio shift I currently have with my footage from Panasonic X920 does not allow me to do final renders using Voukoder.
Should I post the same in Feature Request forum or you can move this thread there?
The same CQ value have different meanings for different encoders.
So you should not expect that visual image quality with the same CQ value would be the same for different encoders.
Yup, the opposite.
I tried to explain it from very beginning.
Could you please have a look at this:
https://www.dropbox.com/s/9vp35vgfle35…Shift2.zip?dl=1
In archive:
- Source m2ts file
- Simple project where I just dropped single file on timeline and delete all audio tracks but front one
- Wav file that I rendered from the project
- Two mp4 files rendered with Voukoder. One without atrim and one with atrim 0.044
- Comparison project in which I dropped all these files
=>
atrim 0.044 audio shifted more ahead. This is predictable as if I understand correctly, atrim stand for Audio TRIM and so it is trimming a bit of audio at start and the rest of audio shifting ahead.
For the project I need option to shift audio behind.
Thanks.
Any suggestion?
