I use fmod for quite a long time now, but when changing from 3.71 to 3.72 here’s what happened…
I use a positioning bar as the one in winamp… it worked fine with fmod 3.71 – user moves the bar, it sets the position of the streamand then the poitioning bar moves forward accordingly to the stream…
In 3.72, when the stream is moved, the timer still gets the time before moving for a split second, and updates shortly after that… Therefore the bar flickers – looks terible… – This is not a vb bug or whatever, because simply changing back to the last version (3.71) corrects the problem…
Was the get time api changed?
Was this a bug, and if so, is it fixed now?
- Oricron asked 13 years ago
It could be the thing that not so many people in vb (if this is vb related only) use fx and spectrum at the same time (without FSOUND_HW2D)… Or had flickerig before because of their code… I don’t know… However, thanks, really to listen to me… etc… I was not sure either since no one had this problem… Big thanks for the efford 😀 Keep up the GOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOD work 😆
Still no idea on how to fix the posbar flickering with 3.72? 😥
Then the VB users will be forced to use the older version:( Since using the new one looks unproffesional 😥
However good library 😉 othervise it works perfectly (small usage of memory, great quality of sound, etc…)
How about setting a saparete GetTime like an oldGetTime, that would work for us to? I know, notpossible, just dreaming 😳
Theres nothing wrong with the DLL. Flickering couldnt be caused by FSOUND_Stream_GetTime, all that does is return the current elapsed time. Flickering could only be caused by the code that you use to draw your progress bar. I use VB for my media player and I use BitBlt to do all of my graphics, including the progress bar, and there is no flickering.
- Paranoid_Android answered 13 years ago
- Maybe make a delay after seeking song, so the progress indicator will not be updated with the old time meanwhile…
- Use a simple picturebox that uses .line methode. When seeking, don’t redraw it manually, so it will not flicker until fmod returns the correct time.
- Don’t think its really a visual basic bug… maybe it depends on the buffer size?
Let me explain again – it worked perfectly with 3.71 (it still does) – only when the dll is replaced this problem occurs.
And yes , offcourse I use bitblt…
The only way to make this work, was to create a timer delay, that refreshes the bar (after position change) – it has to be set more than the buffersize – then it works 😕
Again – the code worked well with the 3.71 – no changes! – sice going back to 3.71 works fine…
I tryed… Like I said it works if there is a delay set after seting the position…
Here is the way that it works without the timer ohn 3.71:
[b:jwg84tdz]1.user kliks on the posbar
2.the timer that moves the posbar during playing stops
3.when the user releses the posbar button, the setpositon api is called
4.the timer is set to active again[b]
Since no one has similar problems, than it appears to be my fault…
I belive that this has something to do with this new accuracy…
Could the new gettime be slower, or the refresh rate slower?
- oh, about the luck on the timing routines
I played zilions of mp3’s before trough (the position rutine has not changed for months and i use my player as the default one) – i never noticed this problem, however i get this flickering problem each time – if not setting the delay – with 3.72 with the same playlists – if set back to 3.71 it works again (it flickers in this way – the user moves it to the new position and then after setting the position of a stream, the button jumps back to the position where it was before setting the new one, and then after a moment it goes on the real position)
I realy am sorry to bother you with this problems, since it appears that i’m the only one having it… So I’m starting to believe it’as my fault… – but I could not find any problem what so ever…Really…
Thanks for all the replies…Please if anyone knows what i’m doing wrong please send it here…Thanks[/b:jwg84tdz]
this is a possibility, i haven’t tested it
the old gettime was less accurate so the problem might be that you get something like this:
FMOD 3.71 time positions in timer:
but in FMOD 3.72:
the posbar has to redraw 2 times faster (because the value is changing faster) and then there could be some flicker.
- Chris answered 13 years ago
Nope, not it
Its like this the current time is 1:23 and then you move it to 2:30… the posbar is at the 2:30 – not flickering since the timer is not enabled… then i set the time trough fmod api… after that i enable the timer… TRhe result is that posbar jumps back to 1:23 for a short time (split second) and then to the new position and moves according to it… The same is with displaying time… Hoveever the order of timers and setting position is correct…
So in my opinion it appears (maybe even cpu or disk related) that when the position is set, fmod takes a wild to set the position so the get time api still gets the old time since the stream is not set yet…
Colud this be a problem? 😳
Please login first to submit.