Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Telestream weird playback speed

  • Craig Seeman

    September 22, 2009 at 4:42 pm

    Thanks for that. I sent this info to Telestream so I’d suspect they’ll have a fix in the not too distant future.

    BTW what version of Quicktime are you using?

  • Paul Collins

    September 22, 2009 at 5:36 pm

    This is with QuickTime 7.6.4 both on broadcasting Mac and receiving Mac. Seems like this might be a QuickTime rather than a WireStream issue – I’ve been seeing audio problems using QuickTime Broadcaster as well. I I’ll try to post a bug report when I can.

    Web/cablecasting: https://ashlandtv20.com
    Software Development: https://www.gracion.com

  • Paul Rogati

    September 29, 2009 at 4:22 pm

    I apologize for my slow responses. Once the school year started I have little time to test. Here is an interesting round of data. Yesterday I made a recording with the same settings I had used a week ago with no problems, but this time the audio was slooow. My starting settings were H.264, 15fps, AAC audio at 128kbps, 44.1kHz with Better compression.

    Excuse the jump because I discovered something today. I was able to correct the audio with Amadeus Pro and when I went to recombine the fixed audio track with the normal speed video track in QTPro I discovered the following Durations in the file properties:
    File – 1:36:48.51
    Video Track – 0:48:24.30
    Sound Track – 0:48:24.30
    Hinted Video – 0:48:24.30
    Hinted Sound – 1:36:48.51

    I have another post in this forum about Hint tracks getting messed up, usually the audio hint track is missing, so I’m suspecting there might be a correlation.

    Back to compression settings. Once I noticed the aberrant audio, I made a series of test recordings, and the setting that made a difference was stereo/mono: mono recorded normally, stereo recorded slow. But what I didn’t test (based on today’s discovery) was recording and NOT having Wirecast hint the file in real time.

  • Paul Rogati

    September 29, 2009 at 6:57 pm

    Addendum: system details

    Mac mini 2.26 GHz, 4GB RAM, OS 10.5.8
    Wirescast 3.5.4 with HDV option
    Canon VIXIA HV40

  • Paul Collins

    October 2, 2009 at 4:37 am

    I try to keep hinting off, as my recordings are not directly published without some sort of conversion. The problem recordings I got with “chipmonk” fast sound speed were probably not hinted, and certainly the good recordings I’ve gotten lately with stereo AAC recording are not hinted.

    Web/cablecasting: https://ashlandtv20.com
    Software Development: https://www.gracion.com

  • Robert Broad

    January 12, 2010 at 11:30 pm

    Hi there, we just ran into this bug and after a few hours of troubleshooting SDP files etc, and only THEN finding this thread, we can confirm that the stereo/mono thing is the culprit.

    One thing we did notice along the way, however, is that Wirecast does not seem to write as much information to it’s SDP files as Quicktime Broadcaster, in particular the lines that specify the audio bit rate etc. Not sure if this has anything to do with it…

    Anyways, thanks for the thread!

    Robert.

    Intel 2.4 GHz MBP
    Mac OS 10.5.7
    Wirecast 3.5.2
    AV in: Built-in Firewire

  • Craig Seeman

    January 13, 2010 at 12:27 am

    Always stay current with updates. They are bug fixes. Wirecast should be on 3.5.6 and you should update your OS to 10.5.8.

  • Robert Broad

    January 13, 2010 at 10:16 am

    True enough. Just updated everything and now there are a bunch of new issues. sigh… 😉

    Intel 2.4 GHz MBP
    Mac OS 10.5.8
    Wirecast 3.5.6
    AV in: Built-in Firewire & Epiphan VGA2USB LR

  • Paul Rogati

    January 13, 2010 at 6:50 pm

    An update, focused on the one system I have that uses the Kona LH card (Mac Pro G5, 2 GHz DP, 4 GB RAM, OS 10.5.8). Over semester break I did what updates I could – Wirecast to 3.5.6, Kona drivers to 7.1, Mac OS updates. As I geared up for the new semester, I did a recording and playback behavior was wacky (it played faster than real time and sometimes there was audio but sometimes not), and I could hear the audio cut in and out while monitoring. After several tests Wirecast crashed and I could not get it to launch without crashing (I tried deleting prefs, re-installing, downgrading to 3.5.4 and even Kona 6.0.3). Getting desperate I emailed Telestream support and they said “Wirecast does not support video capture cards”. This got me to thinking (plus I was anxious to get things working for classes today). So I just uninstalled the Kona drivers – which meant I had to use a different camera that gave me Firewire, but I had one – and Wirecast came back to life and appears to be working well again. I will update with observations, but I now feel I was recording all Fall on the edge of incompatibility between Kona and Wirecast. I think I will abandon the LH card. – Paul

  • Paul Rogati

    January 27, 2010 at 4:11 pm

    Another system: Mac mini 2.26 GHz Core 2 Duo, 4 GB RAM, OS 10.5.8, Wirecast 3.5.6.

    Record settings: H.264 (Main), 512×288 pixels, best quality (no bit rate constraint), 30 fps, key frame every 90, audio 64 kbps 44.1 kHz “best” 16 bit mono
    Stream setting: LAN – H.264 default

    Last week I started both the record and stream and tried to watch the stream remotely. The stream started with chipmunk audio and then the audio ceased, so I gave up watching. The lecture recorded fine.

    This week I decided to leave things as is and just record. The audio in the recording was exactly double speed – I was able to change the timing to 50% in Amadeus Pro and now have a good file. So with no change in setting, one week recorded fine and the next didn’t.

    I noticed the RTP Payload in the Packetizer settings was H.264 Video (which seems to be the default). I have had success in the past changing that to QuickTime, so I have changed that and nothing else. I will keep you posted. – Paul

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy