Resolume shrinking audio files?

[balaclava_man]

Hi Guys
Here's a funny one. From the screenshot you can see that I have an audio file of 23 seconds in length. When I place it in the composition Resolume gives it 16.54 seconds! I can make it last 23 seconds by changing global bpm from 120 to 90 but this is not exact and I need exactly 23 seconds NOT 16.54. Why is Resolume doing this? I checked and it routinely shortens all my audio files! I've been using live audio until now and file length is crucial to what I am working on now. All my DAWS; Logic, Ableton etc see the file as 23 seconds and give it that length, regardless of projects bpm setting. Anyone else having this? Oh, I forgot to mention the fact that aswell as shortening the length it changes the pitch - so it is actually shrinking the file and not just displaying the wrong numbers. This is very bad. Help, please?
The B_man

[balaclava_man]

Hey guys
just checked this on my mates set-up. I thought by lack of response it must only be me - but nope! He gets it too. He's on windows xp 64, Resolume 3.1.1. I'm on MacBook pro 10.5.8, Resolume 3.1.3. A 23 second file on both machines plays and displays as 16.54 secs. A 20 second file ays and displays as 14.41, a 10 second file should therefore display and play at exactly half that if this is a well behaved bug! And sure enough it does. 7.20 seconds. Now eithier we are the only two people in the entire world that get this or the entire Resolume community are playing their audio files too fast Could someone please confirm or deny this behaviour? Just a simple 'me too' or 'not here' would ease my pain. Thanks
B_man

[VJair]

what frequency are your samples?

[VJair]

just made a sample in audacity and tested it. i made a 23 second test tone at a sample rate of 44100. i played it in avenue with the master clock set to 120bpm. it played for 23 seconds.

in audio apps if you play a sample with is a lower frequency in a 44100 project, it will play back quicker than intended.

are you using a 32000 hz sample? ( that sounds about right to get that result ) if you look in avenues preferences, the lowest frequency it likes is 44100, whch ( i would guess ) is why it shows at 44100 in the inspector.

[VJair]

here is the 23 second test tone i made - i culdnt attach it in this forum ( it wont allow WAV extentions ) so i have put it on yousendit

http://download.yousendit.com/VGljUGhYTmFENlJMWEE9PQ

does this play quicker than 23 seconds for you?

[balaclava_man]

Hi VJair
thanks for looking into this. I did what u did. Made a 16bit 44.1khz test tone in audacity - same result. 16.54 seconds. It does this with ALL samples including the demo samples that ship with Resolume. And as I said it also does it oN my mates windows machine. 2 machines different samples wav/aiff - what goes on? I'm pleased to hear that it can work properly, just need to know why it is not here. Are u in the UK? Perhaps our electricity is different!
thx 4 ur time. B_man

[balaclava_man]

Postscript!
Things are getting worse! I noticed the test tone sounded right i.e. not fast. So I timed it - it played in 23 seconds. But Resolume still displayed it as 16.54. (bangs head on table).

[Tim Walther]

Hi, this might be a (tad) too late..

Are you still having troubles with this issue? I might be responsible for it.. but I might be able to help you as well A stupid question perhaps, but did you try upgrading to a never version? If so, could you please send me the audio file you were talking about? please send it to tim{(dot)}walther{(at)}hotmail{(dot)}com.

The posts mentioning a incorrect samplerate are not true, I've tested files to as low as 8k sampleRate.. no troubles there. I know for sure that the current-development Avenue plays files lenghwise 100% accurate, but it might have something to do with you using AIF/ (maybe some wierd encoding?)

Cheers,

Tim

[VJair]

thats good to know you can go lower than the stated rates in avenue. i havnt used much audio with it so was drawing on my knowledge of audio aps.just for reference, the version i was using without getting that same problem was th newest version.

[balaclava_man]

Hi Tim
Thanks for taking a look at this. The speed issue might be my stoopidity so lets put that aside for now - the problem that I can consistently reproduce [ in fact I can't avoid it ] is that Resolume displays the wrong time in the Transport pane. In the Audio pane I have [right now] a 16.0040 seconds audio file and in the Transport pane Resolume displays it as having an 11.47.363. It has nothing to do with my file encoding as it happens on a PC with windows files too, and with the installed demo content. It is not a HUGE problem but it does mean you cannot tell where you are in an audio file by watching the transport bar.
The speed thing is from Resolume trying to beat match samples, I bring my 16sec audio file into a project with a120bpm global setting and Resolume gives the clip a bpm of 59.768 which obviously plays twice as fast - can you turn beat matching off?
cheers
B_man