Resolume Forum

Thanks for taking the time to look at this...

1.One MacBook Pro has 10.6.8 the other has 10.7.2
2. By firmware update I mean apples' latest Firmware update for MacBook Pro [ I got it through software update, I can't find it as a download on their site :( ] which addresses amongst other things the ...

Really wouldn't object if someone were to address this. It is after all a repeatable problem and not just some random anomaly.

Ok.
Since no-one seems interested in this I have followed it up myself. I got hold of another 2011 MacBook Pro ran Resolume without the Firmware update and all was fine. I can send the output to Display 1, either windowed or fullscreen. I then ran the latest firmware update from apple and I get the ...

Hi all
This is probably a Mac problem rather than a Resolume problem and I'm curious to see if anyone else has come across it. I recently upgraded the firmware on my [2011] MacBook Pro and it no longer allows me to send the display to either the windowed or fullscreen display 1 option, the options ...

Thanks so much for that Tim. I was beginning to feel quite isolated on this one. Good to know it will be fixed. U guys are the bomb!

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 ...

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).

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. :cry: 2 machines different ...

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 ...

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 ...