
In my humble opinion, I would avoid any sync problem and make a video with the new soundtrak.
The free Shutter Encoder have a fonction to replace the soundtrack without recompressing image.
You can even have a movie with the two selectable tracks.
Jacques

@gpeddino said:
Is there any "audio player" actor that can also be operated with timecode, so that I can do both simultaneously
To the best of my memory, if you change the position input of a Sound Player or Movie Player actor to "scrub" it (which is what you'd be doing continuously if using a Movie Player in timecode mode to lock a movie to external timecode) it won't cause the actor to output audio because the file isn't actually playing, it's just being told to move the playhead to a different position in the media file.
You could use a Timecode Comparator to trigger the 'play' input of a Sound Player actor at a specific time, but as far as I'm aware we don't yet have a way to lock audio playback to external timecode.

@gpeddino maybe just a video with the audio in it -> play with the movie player and just use the audio
I want to project a movie file but I have a different audio file (with the exact same duration) that I want to use as its soundtrack instead. I'm receiving external timecode and using it to control the movie player actor.
Is there any "audio player" actor that can also be operated with timecode, so that I can do both simultaneously? I'd rather not have to edit the movie file with the new audio.

@ril said:
- Have you noticed (or at least in my case) that if you draw quickly and furiously, certain glitches appear, like sharp lines that break or interrupt the stroke?
Yes, we're aware of that

@woland Thanks a lot...your work around solve it !!
I'd like to take this opportunity to mention two more situations:
- Have you noticed (or at least in my case) that if you draw quickly and furiously, certain glitches appear, like sharp lines that break or interrupt the stroke?
- And the other thing: sometimes, with the same super-fast stroke intent, the pointer enlarges as if zoomed in (maybe it's a Mac system issue?)
Thanks, Lucas.

Thanks for this report. I've been hunting this bug for a while but couldn't get a solid repro until I got some clues from your post. I've just logged five different ways to cause this issue so that we'll be able to fix it when we have time.
In the meantime, my testing showed that, once you've hit Output > Show Stages, a reliable way to get the cursor to disappear and never reappear is to left-click and then move the cursor. In all five cases, once I did that, the cursor would not re-appear unless I did Output > Hide Stages then Output > Show Stages again.

Hi everyone!
I was wondering if anyone has experienced the following strange behavior related to the mouse pointer: when you go to "Full Screen" the pointer always appears until you move the mouse.
The other situation is similar, using the User Actor Live Drawing from the add-ons page. In full screen, every time I release the shift key or press to generate a new stroke, the pointer appears. Does the same thing happen to you? Thanks a lot!
ps: @woland, have you experienced this with User Actor Live Drawing?

Has anyone had any luck getting VOR to hear MSC commands from Isadora?
It seems to stay "...waiting"

@maria said:
The sensor lights red (connected to power source and via hub, because this Mac model doesn't have an internal standard USB port) Status output unit in OpenNI BETA actor says resolving uri. I tried to download the Kinect-test-macOS folder, found in the forum, but cannot run it because of security. I'll be very happy to hear a suggestion from you.
Sometimes the order and configuration of things matters for finicky hardware like the Kinect, for example you can try:
- Launching Isadora then plugging in the Kinect
- Quitting Isadora, plugging in the Kinect, then launching Isadora
- Plugging in the Kinect, restarting the computer, then launching Isadora
- Not having the OpenNI Tracker actor in the very first Scene of your file so Isadora finishes all startup processes before you move into a Scene with the OpenNI Tracker actor.
- Trying with an unpowered hub (avoid putting anything else on the hub)
- Trying with a powered hub (avoid putting anything else on the hub)
- Trying with a USC-C converter instead of a hub (this is what I would personally recommend because it removes all the variables that come with using a hub)
You get the general idea, trying things in a different order or a different configuration sometimes has different results when it comes to hardware-specific issues.