Main > Audio/Jukebox/MP3 Forum
Plugins: Document API for JukePlugSys
loadman:
OK How about a compomise?
Change the list into two groups
Compulsary Options to met the format standard (just the basics):
Then some optionals: :dunno
Barry Barcrest:
--- Quote from: loadman on January 05, 2008, 03:06:19 am ---OK How about a compomise?
Change the list into two groups
Compulsary Options to met the format standard (just the basics):
Then some optionals: :dunno
--- End quote ---
This will sort of work, i thought this thred was to sort out the compulsary options only.... Anything else can then be added individually with any plugin using those will being jukebox specific.
The songstart routine we have in the plugins now should really only need the path/filename passed to it. The plugin author could then read whatever tags, duration, artwork etc from the file they wanted. That way with uncle T not using tags it wouldn't matter because it would be down to the plugin to sort all that out as it would be passed the file location. EDIT: Might need to record if it is random song or user selected so maybe a 1 or 0 flag as a second varible to the pathname.
The song end doesn't need to be passed anything, just tell the plugin the song has ended.
Jukeadd2History, this isn't needed at all. Somebody could code a plugin that records all songs passed with the song start call to a history file. That would be the function of that plugin, so no need to call that as a function in the plugin. Likewise if it records if the song passed is a random song or user selected song the plugin author can record only user songs or random songs or all songs.
Thoughts?
EDIT: actually looking at it, what are we expecting these plugins to do? Most of the options listed here seem like they are pretty pointless for plugin authors to make use of. The song start and end are the real usefull ones. I don't see why plugin authors would need any of the others. Plugins to control lights or whatever would only need to know if music was playing or not. Why does it matter if a song is added to the queue or the queue is cleared? What plugin would do anything on those events?
EDIT2: Also did we find out how visual basic can read info back from the plugin? I didn't think that was working which would also make those command options pretty much useless.
loadman:
--- Quote from: Barcrest on January 05, 2008, 03:48:13 am ---This will sort of work, i thought this thread was to sort out the compulsory options only.... Anything else can then be added individually with any plugin using those will being jukebox specific.
--- End quote ---
Cool ;D I still think the optionals have a place in this thread, we may as well start with them having the same type of format to make it easier for coders
--- Quote ---EDIT: actually looking at it, what are we expecting these plugins to do? Most of the options listed here seem like they are pretty pointless for plugin authors to make use of. The song start and end are the real usefull ones. I don't see why plugin authors would need any of the others. Plugins to control lights or whatever would only need to know if music was playing or not. Why does it matter if a song is added to the queue or the queue is cleared? What plugin would do anything on those events?
--- End quote ---
Yeah :) for what I want to create, LCD and LED drivers and a random wav generator (for fun between songs) I don't need many events. The main thing I need is song info on select/play and a way to display/calculate song remain for LCD Display. A time-out / sceensaver function would be nice but I can also trigger a Led display based on a duration from last song played. I mean you can make plug-ins smart. You don't need to be spoon fed every detail.
--- Quote ---EDIT2: Also did we find out how visual basic can read info back from the plugin? I didn't think that was working which would also make those command options pretty much useless.
--- End quote ---
I thought JukeGetPluginInfo was tyhe only thing that needed that.? Anyway it's existance verified even if it does not pass data is better than nothing.
Yep, that don't work yet but it's no big deal. You could use a separate Plug-in manager written in another language if you wanted to verify, Author, Version etc
Space Fractal:
JukeCommandGet() is also the other functions that have a feed back from the plugins, if they want to make a control based plug in (like over network or such).
Add2History() is usefull if they do NOT want to add the song to plugin's song history. This can caused by song skipping or a song diddent play for other reason.
All Selected type commands is now joined to Add2Queue(). Not all song info might been added to that, so I think this is a comprises?
Also just added JukeSongSuggestion() which is a another feedback command, which can been useful for companies like MusicIP.
Brown marked commands is NOT need to been supported by the software. I guess that is a good comprimes?
Space Fractal:
Hey, Barcrest, you have right about Add2History(), after I saw your post, so it busted.
I have just added a value to JukeSongEnd() instead.
It now up to the plugin writers how the history should been used, if they want that....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version