View Issue Details

IDProjectCategoryView StatusLast Update
0009797New issuesScriptingpublic2018-09-30 13:40
Reporterrbxf234Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionunable to reproduce 
Summary0009797: BASS Error 4 in middle of playing a song
Description

I've been scripting on my project, and whilst song was playing it stopped for no reason. I've found the issue unexpected and strange and restarted the resource.
Then I got an error "Attempt to index a field 'sound' (a boolean value)"

Everytime I've restarted the resource it said that error. That error is supposed to be created only when the path to song is invalid so playSound returns false,
but the song is fine in my cache, plus i can play it fine as well and there's nothing wrong with it except one thing.

I've stopped my resource which plays the file and it didn't let me delete the song file from cache afterwards.
The error message says that it's open in gta_sa.exe and that i need to close the file in order to delete it first.

F8 Console gave a BASS Error 4 everytime I've started the resource up.
BASS ERROR 4 in CreateTempo path:C:\Program Files (x86)\MTA San Andreas 1.5\mods\deathmatch\resources\myresourcename\files\sounds\music.mp3 3d:0 loop:0

All code associated with sound:
local bt = getSoundFFTData ( self.sound, 16384, 1921 )
CLogin.main.visualizer.sound = playSound(songs[randomIndex])
CLogin.register.visualizer.sound = playSound(songs[randomIndex])
CLogin.register.visualizer.sound:setVolume(0)

Please note that song path is valid, and both of playSound functions create the same song, except the 2nd instance of it is muted. The debugscript 3 error which says that .sound is a boolean value comes from :setVolume line.

Steps To Reproduce

No idea.

Additional Information

Client:
Multi Theft Auto v1.5.5-release-11815.2

Server:
MTA:SA Server v1.5.5-release-11705

TagsNo tags attached.

Activities

arranTuna

2018-01-06 14:26

manager   ~~0026389

I guess errors like this could occur based on a problem on your PC. If that is not the case and you get the same problem on another PC well then you would need to upload a resource that will specifically reproduce this bug.

Issue History

Date Modified Username Field Change