setCallback/addSyncPoint do not appear to be working in 4.04.08.
I can call them and they return FMOD_OK but I no longer get the callback function called.
This was working in previous versions (not sure on the last version I used) as I count on it for my gapless playback and have only just recently noticed that I have no gapless playback anymore. (right before i’m ready to release!! )
In my code, I addSyncPoint on the sound and after that I setCallback on the channel.
Is this correct or has this now changed? Is this an FMOD bug or an oversight on my behalf?
I’m a little discontent with the lack of response to my above posts.
I’ve recently paid my shareware license fee and I’ve always been very happy with the response from the team. Now that I find a problem whereby it is blocking me from a release, I can’t seem to get any replies from the Firelight team, yet other posts are being replied to.
I realise that a Shareware license doesn’t bring in as much income as a full license, but I would have thought it would have at least warranted some sort of a response.
I remember a statement saying 24 hour turn around, yet it has been 4 days so far with no response.
I’m a little worried as my software is ready to go, other than the fact that the advertised gapless playback doesn’t actually work as the functions I require no longer appear to be working.
It wouldn’t be so bad if there was at least some sort of acknowledgment of the problem and perhaps an estimation of when I could expect the next build.
At the moment I feel totally in the dark and almost like the entire thread is invisible to everyone.
Could someone from Firelight team give some sort of acknowledgement/status/something so that I can guage when my release can go forward?
You’re posting on the messageboard. I have never said you get 24 hour turnaround on that. You are supposed to write to firstname.lastname@example.org for fast support. You never did this so if it is urgent, use email@example.com. This forum is checked regularly, but messages are not ‘pushed’ to us, we have to check it, so it is not going to be as fast.
The reason it wasnt replied to straight away is because I only reply when I have investigated the issue, and not promise a fix that might not even need to be made. I am not going to say it will be fixed in the next release because it might not even need to be fixed. I’ve just tested it now (I always had it on my list of things to look at but we have been extremely busy in the last week) and there is no problem that I can see, both addSyncPoint and wave files with embedded markers. Sync points are working as far as I can see and I cant think of any code that has changed that has anything to do with sync points.
If you had a reproducable case or more details, it would be easier to test, because now it can take a lot longer of me trying to make different combinations of code to make it happen (which i’ve just done, and it doesn’t, so i need more details than just that it doesnt work).
Ok, thank you for your replay and explanation
I will make note that I should be using the support email address instead of the forum for anything like this in the future.
I will have a look at making a reproducible case for you using the latest development build.
Since you mention that you use sync points for gapless playback are you using sync points to signal the end of a sound? If so, I’m pretty sure this is not reliable due to the way sync points seem to be implemented in fmod – I was unable to ever get sync points at the end of a track to fire reliably, due to the fact that they seem to be processed in system::update by checking how many ms have elapsed since the last update. If you perform an update before the sync point and then perform your next update after the sound has stopped, you won’t get the end sync point. My solution was to set a sync point about 500-1000ms before the end of the track and use that event to begin actively polling for the end of the track so I could switch in the next one.
- Janus answered 12 years ago
Please login first to submit.