Resolume Forum

Hi Bart & Edwin,

I love the new version of Resolume you guys are developing. It is a slight paradigm shift away from the 2.41 way of thinking but way more powerful! An incredible framework has been laid down and I am excited to see how Resolume Avenue will progress.

Here are the main bugs I have noticed so far, and are seriously impacting my ability to use this out live, listed below. I know you guys are busy, but if you could take care of these critical bugs I would appreciate it:

BUG #1) You cannot play an audio clip in reverse if it is a minute or longer. When you try to reverse a clip containing audio, it makes a terrible SCREECHING noise and freezes the software. Sometimes, it will crash it.

I wasn't even aware you could play a clip in reverse with audio in it until I read a thread and went back to test the stock footage that came with it. I tried loading up one of my own content which is around a minute long (both with the audio and video files contained within the same file, and a seperate .MOV (audioless) and .WAV file combined in the software, and nothing worked. I also loaded some .WAV files purchased from beatport and could not reverse/go in forward either.

I tried rendering shorter loops, from 5-10 seconds and these ended up working great! I can alter pitch/bpm and reverse, forward play, and trigger cue points all while affecting the audio. This was one of the ground breakers and I decided to commit to giving this application serious consideration after knowing that it IS possible to scratch audio & video, albeit buggy as hell right now.

Reading the description inside the software, it says that you can add video clips and audio clips of any length, but this is a bit deceptive because you cannot reverse play audio for clips longer than probably 10 seconds (i only tested 10 seconds and 1 minute so I don't know the cutoff)

BUG #2) When trying to MIDI map to transport controls <contextual or application> (for rewind and forward, to essentially scratch audio / video), it will make the software crash when trying to scratch/bounce/reverse audiovisual clips (same clips that work by using the mouse or keyboard).

The only way I have been able to get around this is mapping to the keyboard instead or using the mouse, which work GREAT! It is only when using MIDI transport controls to scratch audiovisual clips that will make my software crash.

For example, on my UC-33 I have buttons 7 8 and 9 mapped to layer 3's :backwards, pause/play, and forwards. When I have an audiovisual clip and hit reverse on the MIDI controller, it will cause the application to crash or screech in the audio. However, if instead of hitting the 7 button on my MIDI controller but map the 7 to the numpad on the keyboard, it will work fine.

I'll update if I have any more bugs to report. Hope you understood what I meant, if not please let me know and I will definitely give more info.

Thanks!

BUG #1, FIXED, this is a stupid mistake we made, so that won't be a problem anymore.

BUG #2, We will give this problem you described a go and see what we can find. So just mapping a MIDI-note to the backwards button already makes it crash? that's a serious one indeed.

Thanx for your feedback

bug #2 - just gave it a try.

the only audiovisual clips i had to hand to try this on were the ones in the demo deck. i used my uc33e and tried buttons sending both cc data and note data. i couldnt get it to crash or give me audio distortion or screeching, even when hitting them quickly.

The screeching only happens with files bigger then a given filesize , smaller files won't have the screeching problem.
We can't seem to reproduce the MIDI crash either.

Hi guys, thanks for the quick response.

------------------------------------------------------------------------------------------------------------------------------
BUG #2, We will give this problem you described a go and see what we can find. So just mapping a MIDI-note to the backwards button already makes it crash? that's a serious one indeed.:
------------------------------------------------------------------------------------------------------------------------------
It's not when I MIDI map it, but when I actually use the MIDI mapped note to affect the transport controls is when it crashes. It will recognize correctly the MIDI notes I am mapping, but it is only when I hit reverse that it will crash.

I have reproduced bug #2 on both Windows XP 32 bit and Windows Vista 64 bit, also with two seperate MIDI controllers. I used both a UC-33 and Bitstream 3x and tried different buttons on these. Also uninstalled, and reinstalled, and cleared the midi mapping and have tried multiple buttons.

When mapping transport in application mode with a global MIDI map, or compisition mode to the current layer it will make it crash when I try to reverse or forward a clip that is a .WAV, or a .WAV combined with a .MOV. This is for audiovisual clips that I can scratch by rewinding and pressing forward with my keyboard and mouse. It has worked once or twice in my history of working with resolume avenue but lately I cannot get it to work at all.

My comp specs are:

Intel Core 2 Duo 3.0 ghz wolfdale OCed @ 3.6 ghz
4 gb RAM
2 x 8800GTs running in SLI
Onboard sound card (I believe it's a Realtek)
10,000 RPM WD Raptor
Using video files encoded with DVX codec and .WAV files exported from sony vegas 8.0.

If you cannot reproduce this bug maybe I can record with a camera what it looks like on my computer, but I think you should get the idea by my description.

I believe I have uncovered a clue to the problem! I have tried mapping rewind and forward to a slider, not MIDI buttons. And it works, without crashing if used under certain conditions:

When the midi slider is all the way down, it is on the "reverse" setting - works fine
When the midi slider is 1/4th of the way up, it is on the "forward" setting - works fine
When the midi slider is 2/4th of the way up, it is on the "pause" setting - works fine
When the midi slider is 3/4th of the way up, it is on the "Random" setting - CRASHES if the clips don't have the ability to do random mode, like audio visual clips when they are currently running.

For some reason, I think the triggering of random mode is causing the crashing of scratching with MIDI?