Working in the software QA industry FT and PT DJ every weekend
I’m absolutely loving the capabilities of VDJ trial version. I couldn't
figure why this awesome program would just abruptly freeze on a
2.4Gh 512MB system. I was able to get allot more out of the program
after increasing my virtual memory and page file settings. But still after
about 2 - 3 hours the program would freeze. I decided to use some
memory tools to debug the software. The results are staggering.
Virtual DJ 2.01
Launching the program at the Idle state:
memory usage = 37,436K
Virtual mem = 178, 232k
Side one loaded with 8:09m mp3 file:
memory usage = 94,752k !
Virtual mem = 184,537k
At the end of my 2:45 minute practice session the
memory usage had climbed to 270,316k!! The Virtual
memory had climbed to 424,012k ! .....I would say a
slight memory leak.
I ran the same test using Automixmp3
Launching the program at the Idle state:
memory usage = 4,436K
Virtual mem = 17,216k
Side one loaded with same 8:09m mp3 file:
memory usage = 3,789 !
Virtal mem = 17,216k
At the end of the session approx 2 hours
memory usage was at 3,128k with a peak
memory spike at 21,484k
Can somebody please tell me how functional
the trial version is in terms of memory usage.
I love the program and would love to buy it.
However, is this what I can expect for memory
usage. Please tell me that I'm only seeing this
because I'm using the trial version. Is there a
Virtual DJ lite in the works?
I’m absolutely loving the capabilities of VDJ trial version. I couldn't
figure why this awesome program would just abruptly freeze on a
2.4Gh 512MB system. I was able to get allot more out of the program
after increasing my virtual memory and page file settings. But still after
about 2 - 3 hours the program would freeze. I decided to use some
memory tools to debug the software. The results are staggering.
Virtual DJ 2.01
Launching the program at the Idle state:
memory usage = 37,436K
Virtual mem = 178, 232k
Side one loaded with 8:09m mp3 file:
memory usage = 94,752k !
Virtual mem = 184,537k
At the end of my 2:45 minute practice session the
memory usage had climbed to 270,316k!! The Virtual
memory had climbed to 424,012k ! .....I would say a
slight memory leak.
I ran the same test using Automixmp3
Launching the program at the Idle state:
memory usage = 4,436K
Virtual mem = 17,216k
Side one loaded with same 8:09m mp3 file:
memory usage = 3,789 !
Virtal mem = 17,216k
At the end of the session approx 2 hours
memory usage was at 3,128k with a peak
memory spike at 21,484k
Can somebody please tell me how functional
the trial version is in terms of memory usage.
I love the program and would love to buy it.
However, is this what I can expect for memory
usage. Please tell me that I'm only seeing this
because I'm using the trial version. Is there a
Virtual DJ lite in the works?
Posted Fri 13 Aug 04 @ 8:45 pm
keyon
yikes. i don't like the sound of your tests. I doubt they'd put out a lite version but I hope they speak to the memory usage if that's a common occurence.
Posted Fri 13 Aug 04 @ 11:35 pm
djzero
that is pretty standard when using large files (5 mins +), it is due to vdj decompressing the audio format to play it, this would also make it alot easier to add support for new formats i think as you would not have to rewrite the algorithm for each format.
decompressing the music into memory is i think an excellent idea as it does not require any extra processing, which means lower latency for the output.
a feature that i'd love to see built into the load time selection, is say a setting such as +-5, 10, 15, 20, 30min etc... so it will preload the first 5, 10 mins etc... either way of the start and then free memory for the space before when this feature is enabled.
as regard to pagefiles i run a dedecated page file on a seperate partition at the end of my harddrive which is alittle over 2gb (with 512mb ram) never had any problem such as this, i think a dedecated static pagefile is the way to go as it is all pre allocated and less stress on the system.
i've put this through 8 hour straight + tests and never had any problems
decompressing the music into memory is i think an excellent idea as it does not require any extra processing, which means lower latency for the output.
a feature that i'd love to see built into the load time selection, is say a setting such as +-5, 10, 15, 20, 30min etc... so it will preload the first 5, 10 mins etc... either way of the start and then free memory for the space before when this feature is enabled.
as regard to pagefiles i run a dedecated page file on a seperate partition at the end of my harddrive which is alittle over 2gb (with 512mb ram) never had any problem such as this, i think a dedecated static pagefile is the way to go as it is all pre allocated and less stress on the system.
i've put this through 8 hour straight + tests and never had any problems
Posted Sat 14 Aug 04 @ 11:52 am