Lesspain Software Support

How can we help you today?

Strange Audio Dropouts - Wrong Workflow?

A

Axel Schreiter

started a topic
5 months ago

So I directly browsed the SDXC card with Kyno, made sublips, named them, duplicated and edited the preset so that the new subclip name is followed by the original name, exported all subclips as ProRes and, well, quitted Kyno.

Then I imported the new folder in FCP X, leaving files in place. On first playback, all clips had audio dropouts. I was worried first but found they eventually vanished. But how is that? Aren't that ordinary ProRes files that should play back well in FCP?

Next time I used the send to FCP X command, and that *seemed* to have be the solution.

Can you explain this? Is there a better way to do this?

What about using an FCPX archive (backup of original card) and browsing this with Kyno. Can I do any harm by renaming the clips, for instance?

Axel Schreiter

said
5 months ago

And by the way: awesome software, recommended Kyno to friends and on fcp.co forum. Keep up the good work. I wished though, that FCP X had this functionality (I mean media browsing and organizing prior to import) ...

J

Jay Ryde

said
5 months ago

I have this one everytine I play back!!

T

Thomas Meyer

said
5 months ago

You mean you have audio dropouts in Prores material transcoded using Kyno? If possible, could you send us a short sample where we ca reproduce this to samples<at>lesspain.software using wetransfer.com or something similar? We would definitely like to take a closer look.

J

Jay Ryde

said
5 months ago

Wow .. I’d sent you this issue weeks ago and you’ve only just replied - Not impressed! Unfortunately (for this issue) this film has now been completed and the project now taken off-line so I don’t have easy access to the material any more. The issue was reported on your forum by other users and there’s even a thread about it on FCP.co forum. For me, the issue was a nightmare in completing our last film as every timeline preview had to be rendered out as a file before we could reliably preview it. Since we’ve ditched Kyno and now considering other media management software.
Issue: The camera rushes were exported/transcoded in Kyno into ProRes 422 and then put into a folder. These folders were used for media import into the final cut pro X libraries - then the editing would start. Occasionally, when playing back the material inside final cut the audio would randomly drop out. Odd considering if it were a data-throughout Problem one would have thought the video would have been affected, but it wasn’t!

T

Thomas Meyer

said
5 months ago

Sorry for the delay, sometimes things get busy here and complex problems like the one you're describing need time to evaluate. I totally agree that we should've replied sooner.

Do you remember from which camera you converted the material from? We want to get to the bottom of this, the ProRes encoder is an important part in Kyno.

If you want to get another trial let me know and I'll reset your status once the problem is fixed

T

Thomas Meyer

said
5 months ago

@Axel could you also tell us what camera the original material was from? We have a suspicion and want to verify this. If we are right it does indeed not have anything to do with bandwidth/throughput.

Axel Schreiter

If possible, could you send us a short sample where we ca reproduce this to samples<at>lesspain.software using wetransfer.com or something similar? We would definitely like to take a closer look.

Hello Thomas,

I consider the issue as solved. Didn't reappear after (as I wrote) I started sending the media to FCP via XML.

Neither QTX-Player nor VLC had these (playback-) dropouts, just FCPX. Feel no need to try and reproduce it. The files in question were XAVC UHD from Sony A6500 and Sony ARii, browsed directly from the cards (iMac SDHC card slot) with Kyno, subclipped and transcoded to ProRes.

Thanks for answering.

Thanks for answering anyway.

J

Jay Ryde

said
4 months ago

So.. again, no comment by Lesspain.. well this issue is STILL a PAIN! When is it going to be solved?

T

Thomas Meyer

said
4 months ago

Sorry about the silence. We are investigating and we are pretty confident that we have a good lead regarding what might be causing this. We are trying hard to get a fix for the behaviour some people observed (it doesn't happen for everybody) into release 1.4 which is planned for about the end of the month.