Great music player! I really like it. I like it so much, that I have left it playing twice for an entire evening. However, after about two hours it complains about running out of memory. When I look at the pagefile usage it runs sky high, but in small increments. I assume it must be the music library2 plugin, as that one was active. GBPVR wasn't recording etc. Is there a memory leak in your code?
Also, I'm using a touchscreen, so scroll-bars, or navigation arrows would be great!
MaBo Wrote:Great music player! I really like it. I like it so much, that I have left it playing twice for an entire evening. However, after about two hours it complains about running out of memory. When I look at the pagefile usage it runs sky high, but in small increments. I assume it must be the music library2 plugin, as that one was active. GBPVR wasn't recording etc. Is there a memory leak in your code?
MaBo Wrote:Great music player! I really like it. I like it so much, that I have left it playing twice for an entire evening. However, after about two hours it complains about running out of memory. When I look at the pagefile usage it runs sky high, but in small increments. I assume it must be the music library2 plugin, as that one was active. GBPVR wasn't recording etc. Is there a memory leak in your code?
Also, I'm using a touchscreen, so scroll-bars, or navigation arrows would be great!
Greetz, and thanks!
MaBo
Hmm, I'll have a look, not sure what is thinks it's doing while playing. But I'll check it out. I've been fairly conscious of the memory for navigating, and getting in an out of the plugin since I do have to hold quite a bit in memory.....but I didn't think I was doing anything while playing.
For the 2 hours of playing, was that just one playlist, or did you keep adding playlists (i.e. random button many times), or continually queuing tracks??
I just want to get a feel for what's going on. I've ran mine at home for a couple of hours, but I have some "tracks" that are at the 2 hour mark by themselves.
psycik, thanks that you will look into this. It was after initially seting up a playlist (tens of tracks, once 97), then letting it play by itself. Once or twice I skipped a track.
So, not much navigating and interaction with the plugin.
Yeah I think I've found it. I don't think I was doing things very well and was chewing up a fair hunk of memory.
One thing to try, don't leave the library viewing the playlist screen. See if that affects you memory. The memory leak I have identifed if when viewing a currently playing play list.
Ah ha, it was the play back position causing the problem!!!
I don't think I'll be able to get a fix out directory for that, since I've started working on a couple of other things.....but if nothing else I think I've started handling memory better.
Just wondering how long it would take to scan 70 Gig of MP3's. The files are networked and directory setup is set to point to //server/MP3 (where MP3 contains artist/album/songs). I don't see any scan progress and the MusicLibary2.mdb does not seem to be growing. This is after two hours. But I do see lots of network activity. Anything I should be looking for or am doing wrong?
Regards,
Hasso
[SIZE="2"]Server: NPVR 2.2.6, Asus E35M1-M PRO motherboard, 2 x 2GB DDR-1333 memory, 1 x 1.5TB SATA Samsung HD, 2 x 2TB SATA Seagate Green HD, 1 x Hauppauge HD4400, 2 x Hauppauge Nova T 500, Windows 7 Home. Clients: EGreat M34A with MVPMCX2; HDX1000 with MVPMCX2 and internal 2TB SATA Seagate Green HD.[/SIZE]
hmm, 70 gbs would be slow. The first thing it does is get a list of files that's why there's disk activity but no database stuff, and then you're probably paging a bit as well.
I don't think you're doing anything wrong....check the logs for errors though.
The other thing to make sure it is working is to go into the config and change it from you're whole collection to a subset to make sure that's all going.
I'm doing a fairly big update to it at the moment adding some features......I might look at the update component and streamline it a bit....obviously some people have much bigger collections than me, and i don't think the update bit was the most efficient.
psycik Wrote:hmm, 70 gbs would be slow. The first thing it does is get a list of files that's why there's disk activity but no database stuff, and then you're probably paging a bit as well.
I don't think you're doing anything wrong....check the logs for errors though.
The other thing to make sure it is working is to go into the config and change it from you're whole collection to a subset to make sure that's all going.
I'm doing a fairly big update to it at the moment adding some features......I might look at the update component and streamline it a bit....obviously some people have much bigger collections than me, and i don't think the update bit was the most efficient.
40gb takes about 20 mins on my athlon 64 3000 200 gb sata drive