Well....as usual if it can be crashed I will be the 1 that makes that happen.
I downloaded 4.16 and installed it. I copied last year's xlights_rgbeffects.xml file into the show folder along with an old .xml file from last year (from 3.15) and when I try to open the file I get an error for EVERY model in the old 3.15 setup that says...."Last channel (for model trying to load) is beyond the end of the configured number of output channels"
If I remover the xlights_rgbeffects.xml file and replace it with the 1 that v4.16 installed I get a message that says models don't exist.
Any thoughts on where to start looking for the problem?
You needed to also copy the xlights_networks.xml because it contained all your channel mappings from the Setup tab. Without that you have no channels defined and that's why the message is popping up.
CopperCreekLights wrote:You needed to also copy the xlights_networks.xml because it contained all your channel mappings from the Setup tab. Without that you have no channels defined and that's why the message is popping up.
Thanks Gil.....
There is a reward in the next life for folks like you who take care of the feeble minded! LOL.... :blush: :blush: :blush: :blush: :blush:
This is a perfect example of a little knowledge being dangerous..... When you don't play with the underlying files very much you either don't know what you don't know or forget because you so seldom have to access the knowledge.
It also goes to show you....when dealing with a literal person...how they follow directions to the letter..... It gets me in trouble often when I deal with this kind of stuff.....as what appears obvious to others often never occurs to me....due mostly to my not understanding the underlying theory well enough. That kind of stuff makes my head hurt but I keep sticking my head back in there for another dose! LOL.... :blink:
I am grateful for the patience you guys demonstrate on a regular basis with some of us on the user side of things..... It is a credit to a strong character.....
Deleted.....dual post.....
OK....next crash....
When trying to load media I get this message...... "ERROR reading data from mp3 too much data read"
Now what did I miss?
OK....next crash....
When trying to load media associated with the xml file I get this message...... "ERROR reading data from mp3 too much data read"
Now what did I miss?
UPDATE: OK....I tried a second sequence and it works fine.....the first 1 still won't work but plays fine in 3.15...... I'm so confused I don't know which way to point my elbow! :blink:
That means we aren't getting the correct size when we ask the mpg123 library how big that MP3 file is. I thought we had fixed that because I ran into that with another MP3. I bet if you ran the file through Audacity and exported it the file might work. It would help if we could run that mp3 through our code to figure out how to handle it. Of course we would promise to delete the mp3 afterwards and not listen to it for personal enjoyment....lol. Actually I think I know how to fix this but it seems crazy to have to parse the entire file twice.
CopperCreekLights wrote:That means we aren't getting the correct size when we ask the mpg123 library how big that MP3 file is. I thought we had fixed that because I ran into that with another MP3. I bet if you ran the file through Audacity and exported it the file might work. It would help if we could run that mp3 through our code to figure out how to handle it. Of course we would promise to delete the mp3 afterwards and not listen to it for personal enjoyment....lol. Actually I think I know how to fix this but it seems crazy to have to parse the entire file twice.
Gil....you are batting 1000...... Went to Audacity and exported it.....works fine now.....
Leave it to me to stumble into a bug that makes me think I'm dumb as a rock... :biggrin2:
Good thing you are on top of things or I might be burning a pile of pixels....LOLOL....
If you still want that file that didn't work let me know where to send it....it was an mp3 that I had converted to run on the FPP last year.
Now here's another question about that mp3.....Do I need to now go and change it out on my FPP to replace the original that plays with the fseq file?
Maybe...currently there are issues with certain bitrates. I think it works best to export as 192K constant bit rate. You can tell if you click somewhere other than the start in the waveform and see if it looks like the sound is matching the waveform. If it's not right the sound will be around 1 to 1.5 seconds too early. Something to do with the media player not decoding into the packet. It just starts playing at the beginning of a compressed packet instead of where we commanded it to go. LOR had the same problem a few years ago. When I started with them I had to convert all my mp3's. They've had more time to fix it. I believe they convert the audio to an internal format now to get around that type of problem. We'll come up with something someday but for now exporting from Audacity is a workaround.
SantaCarl... I need you on MY testing team! 🙂
Bug finders are worth their weight in bananas.
