Topic: how to set tempo for imported audio

Viewing 13 posts - 1 through 13 (of 13 total)
  • #1332
    anim8err
    Participant

    I am giving Podium CM a try but when I drag a .wav file onto a track and hit play it plays at the wrong tempo, and changing the tempo or bpm does not have any effect. I have also tried chaning the sample rate in the sound properties. The wave file was created in Audacity. What am I doing wrong?

    anim8err

    #10205
    Zynewave
    Keymaster

    Hi,

    You’re not doing anything wrong. Time-stretching is not yet supported in Podium. I started to work on this a couple of months ago, but other features got in the way. I hope to resume work on time-stretching later this summer.

    Frits

    #10206
    anim8err
    Participant

    So are you saying that I need to make sure that the .wav file is of a certain frequency in order to play at the correct speed. How do I use sound file or clips?

    anim8err

    #10207
    Zynewave
    Keymaster

    The tempo of the sound files you import need to match the tempo set in the arrangement. When I add support for time-stretching, the sound files will automatically be stretched to match the arrangement tempo.

    #10208
    Conquistador
    Participant

    When I add support for time-stretching, the sound files will automatically be stretched to match the arrangement tempo.

    Looking forward to that!

    Dragging and dropping any wave file into Podium and having it tempo match would really open up some more creative possibilities in Podium. šŸ˜‰

    #10216
    rinxai
    Participant

    I am not sure at all about this, I had a similar problem which is resolved by changing the bit depth of the sample/loop you want to import. For example if I audition a 16bit sample it plays about twice as fast, however if I first export/save that sample/loop at 32bit, the tempo is corrected. I have not used Audacity, but I guess that it is capable of saving out audio at 32bit. I also set sample rate to 96khz, so both Podium and samples have equal bit depth and sample rate – (Podium is always set to 32bit float)

    #10218
    kingtubby
    Participant

    As I understand it, bit depth – 16, 24 or whatever, shouldn’t make any difference to playback speed?

    Mart.

    #10221
    rinxai
    Participant

    Yep, Kingtubby, I also thought bit depth should not make a difference, however I just checked this again, and its true. I’m wondering if this is particular to my setup, or whether anyone else experiences the same. For example, when I audition any 16 bit sample in Podium, it always plays fast, about twice the speed and pitch. Yet when I convert the same sample (in Wavosaur) to 32bit, and then audition it again in Podium it plays fine. Weird huh!

    Next, when I import a 16 bit sample into a project, and then right click the sample to open in the audio editor the sample plays fine, yet when I drag the same imported 16 bit sample over to a track, it plays twice as fast and is pitched up. The sound output does not match the play cursor as it moves over the waveform display.

    However by converting the sample to 32 bit before bringing it into Podium this strange behavior ceases. I don’t know whats really happening, but at least its a workaround that allows me to use 16 bit samples.

    #10222
    kingtubby
    Participant

    rinxai – I did quick test and think the solution is to match the sample-rate of the audio files you’re using to the sample rate of the arrangement. Set the correct sample rate in ‘arrangement properties’ dialog, under the view menu in the arrangement itself. It worked for me anyway šŸ™‚

    Mart.

    #10223
    rinxai
    Participant

    šŸ™‚ Thanks kingtubby, setting the correct sample rate in ‘arrangement properties’ dialog is indeed the solution. IIRC I had a look at this previously but left it set at 96khz since I would like to keep my project at best audio quality as possible on me PC. Do you think there is much of a difference in audio quality between the various sample rates?

    #10224
    kingtubby
    Participant

    Well, I always stick to good ol’ 44.1k – it’s good enough for my ageing ears. But then I’m only a hobbyist making, ermm..’music’ for my own pleasure šŸ˜›
    Undoubtedly though, there is a significant improvement in quality using 96k over 44.1k, particularly at the higher audio frequency range.

    Mart.

    #10225
    Podianer
    Participant

    Undoubtedly though, there is a significant improvement in quality using 96k over 44.1k, particularly at the higher audio frequency range.

    One should consider here, that resampling from 96KHz down to 44 KHz can degrade the quality. Therefore a samplerate of 88 KHz during recording gives the highest possible qualit (downsampling process is easier to calculate). But imho recording at 44 KHz is pretty good. Using 24 Bit also ensures that you have enough headroom in your recordings which preserves dynamics and quality. My suggestions is to record at 24 Bit and 44 KHz…

    Max

    #10227
    Zynewave
    Keymaster

    when I audition any 16 bit sample in Podium, it always plays fast, about twice the speed and pitch. Yet when I convert the same sample (in Wavosaur) to 32bit, and then audition it again in Podium it plays fine. Weird huh!

    Then I would guess that wavosaur in addition to the bit depth change is also resampling from 44.1 to 96. This must be something you can configure in Wavosaur.

    Until time-stretching is supported in Podium, the arrangement samplerate must match the samplerate of your imported sound files, or else you will experience this speed variance during playback.

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.
Ā© 2021 Zynewave