User Tools

Site Tools


external:winamp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
external:winamp [2019/12/25 23:19] icke_siegenexternal:winamp [2020/01/17 07:20] (current) – external edit 127.0.0.1
Line 53: Line 53:
 There are some little issues to be aware of: There are some little issues to be aware of:
  
-  * the different framerate - 100 fps - requires converting eisting timestamps when changing the timecode source+  * the different framerate - 100 fps - requires converting existing timestamps when changing the timecode source 
 +  * there is a software issue which wraps frame numbers around when entering timestamps manually in the cuelist playback view as this assumes a framerate of only 25 fps. Hence, if you enter a timestamp with more than 24 frames then this gets wrapped, and a number of seconds being added. E.g. a timestamp of 00:00:01:70 is 'translated' to 00:00:03:20. The workaround is to select all timecode cells and set the framerate to 100 fps as this seems to get stored on a per-cue basis.
   * when patching Winamp in Titan make sure it is patched as first fixture, at universe 1 address 1, and silently make sure the required 19 channels are not used by other fixtures. Else, some features will not funcotion correctly (this is already being investigated)   * when patching Winamp in Titan make sure it is patched as first fixture, at universe 1 address 1, and silently make sure the required 19 channels are not used by other fixtures. Else, some features will not funcotion correctly (this is already being investigated)
-  * if you do not patch it and only rely on the timecode transport controls expect the other channel behave strangely, as they expect some input but don't get it. E.g. the volume or balance can be awkward, or the equalizer has strange settings+  * if you do not patch it and only rely on the timecode transport controls expect the other channels behave strangely, as they expect some input but don't get it. E.g. the volume or balance can be awkward, or the equalizer has strange settings
 +  * timecode is, by definition, designed for values from 00:00:00:00 up to 23:59:59:29 (for 30 fps) - nothing wrong here as there are only 24 hours per day, right? However this limits the transport control for Winamp: you cannot make playlists with more than 23 tracks (well you can - but you cannot start tracks above #23 with this method).
   * one other backdraw is the inherent thing that this works only if Winamp and Titan are on the same machine. On computers running the PC suite you are free to use better sound cards or USB interfaces. On hardware consoles this is not possible, and you are always restricted to the little headphone output - have a DI box and a good sound guy at the ready.   * one other backdraw is the inherent thing that this works only if Winamp and Titan are on the same machine. On computers running the PC suite you are free to use better sound cards or USB interfaces. On hardware consoles this is not possible, and you are always restricted to the little headphone output - have a DI box and a good sound guy at the ready.
 +  * there is a glitch most likely within Winamp itself which manifests in conjunction with this virtual timecode: when playing mp3 files, sometimes the timcode timestamp seems to divert from the Winamp track time by a couple of seconds unless it is paused and restarted. This appears to be due to the encoding method: wav files are okay while mp3 is faulty. If you are encountering these issues then re-encode your files as wav (sampling rate seems to have no effect). See [[https://www.facebook.com/groups/1811437589141428/permalink/2489876031297577/?comment_id=2491793771105803&reply_comment_id=2545827579035755|this facebook post]].
  
external/winamp.1577315949.txt.gz · Last modified: 2019/12/25 23:19 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki