esq2man
When I first start VDJ and play a 30 minute long mp3, the song will load up and the length of the song will appear in the proper window. I could try to load that same song again 2 or 3 songs later and the song length indicator will be blank, and the song won't play until I restart VDJ. I have 1.04. This happens whether I set the options to preview the song or not.
Posté Wed 13 Aug 03 @ 4:55 am
DJ Coco
you need to much ram to play a big file with VirtualDJ !
How much you have?
How much you have?
Posté Wed 13 Aug 03 @ 5:12 pm
DJ PHIL IT
I have the same problem too why in atomix I put in any big song it loads in sec I don"t think this has any thing to do with ram this is a bug so just fix it please, I got fx & bpm pro and they all load any big song fine, I got hundreds of my cd mixs and when I rip them as one song and they all 80 min cds. so I don"t think it's a memory issue when I buy BPM years ago I had only 128 of ram and I put in any long song in there,
Posté Fri 15 Aug 03 @ 3:31 pm
DJ Coco
VirtualDJ and Atomix works different.
VirtualDJ loads the entire song in RAM, that`s why you can see the whole structure of the song..
VirtualDJ loads the entire song in RAM, that`s why you can see the whole structure of the song..
Posté Fri 15 Aug 03 @ 4:05 pm
apopsisdj
Maybe VDJ needs better memory managemant.
Take a look at how latest software samplers work,
like Halion and Kontakt.
They have the option of loading only a part of the samples
in memory and not the whole samples. This trick really works
on big samples.
I made some test last night loading songs in VDJ watching
the memory/swap file usage.
Mem. usage - no programs running ~ 80 MB
Mem. usage - VDJ running ~ 120 MB
Mem. usage - 1 song loaded ~ 180 MB
Mem. usage - 2 song loaded ~ 240 MB
Even with 2, 3min+ songs loaded, the memory usage can
easy reach the 256 MB of most todays laptops,
(mine has 256, that is 240 MB for windows +16 MB for graphcs).
So thats why there are skipping problems with 256 MB
machines, VDJ works always at his limits (for the memory)
and using swap file is not a good idea.
Its easy to say upgrade your memory, (and it is for desktops)
but for laptops it is not so easy and not so cheep.
So a better memory managemant with options of loading
in memory only the first seconds of a song + and also the first
seconds from each cue point, will lesult at a much quicker
loading time, and will allow for loading big files.
Many of us have some 60-80+ min mp3's ripped from mixed
cd's and these are really pain to play with VDJ
Take a look at how latest software samplers work,
like Halion and Kontakt.
They have the option of loading only a part of the samples
in memory and not the whole samples. This trick really works
on big samples.
I made some test last night loading songs in VDJ watching
the memory/swap file usage.
Mem. usage - no programs running ~ 80 MB
Mem. usage - VDJ running ~ 120 MB
Mem. usage - 1 song loaded ~ 180 MB
Mem. usage - 2 song loaded ~ 240 MB
Even with 2, 3min+ songs loaded, the memory usage can
easy reach the 256 MB of most todays laptops,
(mine has 256, that is 240 MB for windows +16 MB for graphcs).
So thats why there are skipping problems with 256 MB
machines, VDJ works always at his limits (for the memory)
and using swap file is not a good idea.
Its easy to say upgrade your memory, (and it is for desktops)
but for laptops it is not so easy and not so cheep.
So a better memory managemant with options of loading
in memory only the first seconds of a song + and also the first
seconds from each cue point, will lesult at a much quicker
loading time, and will allow for loading big files.
Many of us have some 60-80+ min mp3's ripped from mixed
cd's and these are really pain to play with VDJ
Posté Fri 15 Aug 03 @ 6:34 pm
Yan-X
This option has been added in v1.03 with the max load option.
Simply set the max load to NONE to never load a full song in memory on light systems.
Simply set the max load to NONE to never load a full song in memory on light systems.
Posté Fri 15 Aug 03 @ 7:11 pm
apopsisdj
Yeah !, you're right.
I knew about this option, but had 1.02 demo
I made some tests again with 1.04 and -yes- its working
as expected. Maybe one more option to let the user
choose the limit will be usefull.
(a value between ''none'' and ''5min'', lets say 4min is more
safe for 256 MB machines)
Anyway, thanks for your great support.
I knew about this option, but had 1.02 demo
I made some tests again with 1.04 and -yes- its working
as expected. Maybe one more option to let the user
choose the limit will be usefull.
(a value between ''none'' and ''5min'', lets say 4min is more
safe for 256 MB machines)
Anyway, thanks for your great support.
Posté Sat 16 Aug 03 @ 5:00 am
esq2man
I have 512mb ram and get this problem.
Posté Thu 21 Aug 03 @ 1:31 am