How to dynamically manage a playlist Part 2

[carrzkiss]

Taking off from the script provided by https://github.com/vitoyucepi on my recent thread, 3860.

In reference to the code used in the request.py.
And this

This function creates a single request by extracting the first line from the script output.

What I do know is that I need to create a Python script that reads from my SQL Server database, and I am currently researching this.
I have installed the latest version of Python on my Windows machine.

Reading the quote above, does this mean that it will only generate ONE line each time, and then after that line is played, a new line will be generated?

I am going to stop while I am ahead so vitoyucepi can come in and assist me further.

[vitoyucepi]

I'd like to know what your current needs and capabilities are, and what your overall plans are.
Basically, if you have .net skills, it may be beneficial to drop the Python script altogether and build a JSON API over HTTP.

[vitoyucepi]

Hi @carrzkiss,

Here's my take on getting the next song from the API in jsend format

let jsend = ()

def jsend.handle_http_error(error)
  log.info("Error while doing the http request. #{error.message}", label="http")
end

def jsend.check_response_code(response)
  if response.status_code == 200 then
    response
  else
    log.info("Server response status not OK. #{response.status_code} #{response.status_message}", label="http")
    null()
  end
end

def jsend.parse_response_status(response)
  status =
    try
      let json.parse ({status} : {status : string}) = response
      status
    catch error do
      log.info("Unable to parse the response status. #{error.message}", label="http")
      null()
    end

  if status != null() then
    status = null.get(status)
    if list.mem(status, ["success", "error", "fail"]) then
      status
    else
      log.info("Unknown response status. #{status}", label="http")
      null()
    end
  else
    status
  end
end

def next()
  api_url = "http://web/api/v1/next_song"

  def handle_status_success(response)
    try
      let json.parse ({
        data = {
          url,
          temporary
        }
      } : {
        data : {
          url : string,
          temporary: bool,
        }
      }) = response
      request.create(url, temporary=temporary)
    catch error do
      log.info("Unable to parse the response data. #{error.message}", label="http")
      null()
    end
  end

  def handle_status_error(response)
    try
      let json.parse ({message} : {message : string}) = response
      log.info("Error occurred while processing the request. #{message}", label="http")
    catch error do
      log.info("Unable to parse the response data. #{error.message}", label="http")
    end

    null()
  end

  def handle_status_fail(_)
    log.info("Something is wrong with the request.", label="http")
    null()
  end

  response =
    try
      http.get(api_url)
    catch error do
      jsend.handle_http_error(error)
      null()
    end

  response = null.map(jsend.check_response_code, response)
  status = null.map(jsend.parse_response_status, response)

  result =
    if response != null() and status != null() then
      status = null.get(status)
      response = null.get(response)
      if status == "fail" then
        handle_status_fail(response)
      elsif status == "error" then
        handle_status_error(response)
      else
        handle_status_success(response)
      end
    else
      null()
    end

  if result == null() then
    log.important("Unable to get next song from API.")
  end

  result
end

The API endpoint is /api/v1/next_song.
The response format is

{
  "status": "success",
  "data": {
    "url": "/path/to/the/file",
    "temporary": false
  }
}

I didn't test it thoroughly.

[carrzkiss]

OK, I just saw what you posted.

[carrzkiss]

Is the 'next_song' going to include only ONE song or all the songs with the updated ones added?

[vitoyucepi]

It requests one song at a time.

[carrzkiss]

OK, so the file will only have a single song in it. OK.

I am redesigning the coding of the Upload script.
I have a better component for retrieving the metadata from the files. This will allow for custom tags and more information to be added to the MP3 files, making adding information to the website much faster. Most of it will be added during the upload process.

I considered this before but did not want to do it, and now I am going to do it.
Since the servers do not have live stations, there will be no downtime, so this is the best time to do it.

The Folders with the files are listed as such.

KISS

Asylum

08022023143447200.mp3 (Song is: Who Wants to be Lonely)

What I am going to do now is this.
1 (ArtistID)

21 (AlbumID)

08022023143447200.mp3

This will make it simpler and without any issues, and I will not have to worry about any naming issues.
This way, when I make up the URLs to the files, it will be this.

myradio/media/1/21/08022023143447200.mp3
instead of
myradio/media/KISS/Asylum/08022023143447200.mp3

So, that is what I am working on tonight and Friday,
I will jump on this later on Friday or Saturday and get back to you.
I am really excited about re-coding everything and then getting the Radio going.
It is going to be a sweet setup.