What am I doing wrong? by TheUltimateKoopa at 11:17 AM EDT on August 4, 2012
No, this isn't another complicated thing. Or at least it never used to be.
This is very simple. How do you change the order of GBS files in a playlist? I thought you just changed the number where it says:
"file.gbs::GBS,[x],Title,Length,,Fade

E.g:
Donkey Kong Country [Donkey Kong 2001] (GBC)(2000)(Rare)(Nintendo).gbs::GBS,4,Donkey Kong Country - DK's Treehouse,0:1:02,,0:0:10
Donkey Kong Country [Donkey Kong 2001] (GBC)(2000)(Rare)(Nintendo).gbs::GBS,3,Donkey Kong Country - DK Island Swing,1:46,,0:10
Donkey Kong Country [Donkey Kong 2001] (GBC)(2000)(Rare)(Nintendo).gbs::GBS,10,Donkey Kong Country - Aquatic Ambience,2:21,,0:10
Donkey Kong Country [Donkey Kong 2001] (GBC)(2000)(Rare)(Nintendo).gbs::GBS,15,Donkey Kong Country - Voices of the Temple,1:50,,0:10
Donkey Kong Country [Donkey Kong 2001] (GBC)(2000)(Rare)(Nintendo).gbs::GBS,0,Donkey Kong Country - Fanfare,0:09,,,

and so on....

But not only does the actual playlist remain in the same order, the actual songs are in a completely different order.
The "DK Island Swing" track now plays "Voices of the Temple". DK Island Swing should be the 4th track in the playlist, and Voices of the Temple should be the 16th.
by fridgey at 6:08 PM EDT on August 4, 2012
Without actually looking at a file to check, I thought you changed the order of the lines in the playlist, and those numbers referenced the index in the gbs file.
by TheUltimateKoopa at 6:24 PM EDT on August 4, 2012
Wait, so, you don't just change the numbers? I thought, after creating an M3U with VGMToolbox, you simply changed the index numbers.
by snakemeat at 9:58 PM EDT on August 4, 2012
The numbers represent the song number within the GBS file, not within the playlist. Fridgey is correct that you simply change the line order in the file.

The format specification for nezplug m3u files can be found here: on Sourceforge.



edited 9:59 PM EDT August 4, 2012
by TheUltimateKoopa at 10:17 PM EDT on August 4, 2012
Oh :P

Also, for the loop length, is that specifically the actual length of the loop, or the time that the loop ends? It might be obvious, but, if the song loops from 0:12 to 1:26 for example, do you put 1:26 or 1:14?
by nothingtosay at 10:38 PM EDT on August 4, 2012
You put how long you want it to play before it starts fading. It has no idea whether the music loops or not, it's just playing until the time it's told to stop.
by TheUltimateKoopa at 11:32 PM EDT on August 4, 2012
No...

filename::GBS,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]

let's say I have:
Randomgame.gbs::GBS,5,Level 1,,,,
If I just put this:

Randomgame.gbs::GBS,5,Level 1,2:15,,0:10,

It will play for 2:25 (2:15 followed by a 10 second fade out).

But between those two commas, is the loop, which is where the x is, and the loop count, which is represented by y here:

Randomgame.gbs::GBS,5,Level 1,2:15,x,0:10,y

Now it says this:

loop(h:m:s)
loop length h * 3600 + m * 60 + s (sec)
loop(h:m:s-)
loop start time h * 3600 + m * 60 + s (sec)

If the loop is to start at, for example 0:14, and the loop lasts for 1:25 (i.e. the total length is 1:39), what would I put there?

Would I put 1:25 0:14-? or 0:14-1:25? And what's the point of the play time if the loop start, loop length, and loop count will alone determine the play time?

0:14 start, 1:25 loop length, for 2 loops, is a length of 3:04, right?
by Mouser X at 12:09 PM EDT on August 5, 2012
To my understanding, you've read and interpreted the information correctly. However, in practice, I've never seen the loop count actually work. I think it's only supported by specific formats, or players. You can certainly try it and see what happens (I encourage you to do so. I'd like to be proven wrong here. Try it with a variety of formats though (HES, KSS, GBS, NSF, VGM (if VGM is supported. I can't remember), ect.)). Try with foobar2000, Winamp, and any other player that supports the M3U tags. Experiment, make mistakes, crash the player(s) and computer, and see if there's any situation where the loop start, end, and count actually make a difference. But based on what I've seen so far, I don't think that feature is actually implemented correctly, or it only works with a specific format/player. Knurek might know better.

Good luck! Mouser X over and out.
by TheUltimateKoopa at 6:06 PM EDT on August 5, 2012
I'll wait for Knurek. What I wanted to know is, simply, what would I type?
by nothingtosay at 3:22 PM EDT on August 6, 2012
Oh, now I see what you're talking about. I just tried it out and it seems that the loop time/number overrides the play time. I edited one line in an M3U that said "1:21,,12" to "1:21,0:41,12,5" and now it displays a time of 4:17 in Winamp. Don't know what to do about stuff that has a delayed loop start.
by TheUltimateKoopa at 1:14 AM EDT on August 7, 2012


All I'm guessing is loop start time is when it starts, and loop length is.. how long the loop is.

For example:
Loop: 0:25 - 3:06

loop start time would be 0:25
loop length would be 2:41 (because 3:06 - 0:25 = 2:41 obviously)

Here's the general format:
NEZplug extend M3U playlist format(v0.9) for Winamp

filename::NSF,[1 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::KSS,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::GBR,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::GBS,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::HES,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::AY ,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]
filename::NEZ,[0 based songno|$songno],[title],[time(h:m:s)],[loop(h:m:s)][-],[fade(h:m:s)],[loopcount]

filename song file relative path(*.zip;*.nsf;*.kss;...)

songno 0-based songno(::NSF playlist only has 1-based songno for historical reason.)
$songno 0-based hexadecimal songno

title song title

time song play time h * 3600 + m * 60 + s (sec)
Default time(5min) will be used, if time not specified.

loop(h:m:s)
loop length h * 3600 + m * 60 + s (sec)
loop(h:m:s-)
loop start time h * 3600 + m * 60 + s (sec)
loop(-)
loop length is equal to play time.
Song will not loop, if loop not specified,

fade fadeout length h * 3600 + m * 60 + s (sec)
Default fadeout length(5sec) will be used, if time not specified.

loopcount
loop count
Default LoopCount will be used, if time not specified.

Now what I don't get is the whole [loop(h:m:s)][-]
What is the dash for?

And this part:
loop(h:m:s)
loop length h * 3600 + m * 60 + s (sec)
loop(h:m:s-)
loop start time h * 3600 + m * 60 + s (sec)

It implies that somehow you type the length AND start time of the loop, but ... how? Using the above example, if it was to start at 0:25 and the loop lasted for 2:41, what would I type? 0:25 - 2:41, 2:41 0:25-..... ????


Go to Page 0

Search this thread

Show all threads

Reply to this thread:

User Name Tags:

bold: [b]bold[/b]
italics: [i]italics[/i]
emphasis: [em]emphasis[/em]
underline: [u]underline[/u]
small: [small]small[/small]
Link: [url=http://www.google.com]Link[/url]

[img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message

HCS Forum Index
Halley's Comet Software
forum source