build #1456
orchetectbuild.yml
on: schedule
macOS
2m 37s
macOS (Swift 6)
2m 3s
macCatalyst
1m 28s
iOS
1m 59s
tvOS
1m 49s
watchOS
3m 1s
Annotations
36 warnings
|
macCatalyst:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macCatalyst:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macCatalyst:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macCatalyst:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
iOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
iOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
iOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
iOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive xmlString.swift#L235
> TODO: needs coding - add tracks and tempo events
|
|
macOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS:
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive xmlString.swift#L235
> TODO: needs coding - add tracks and tempo events
|
|
macOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
tvOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
tvOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
tvOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
tvOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS (Swift 6):
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macOS (Swift 6):
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macOS (Swift 6):
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
macOS (Swift 6):
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive xmlString.swift#L235
> TODO: needs coding - add tracks and tempo events
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive Helpers.swift#L119
> TODO: This calculation is not accurate, it is merely approximate.
|
|
macOS (Swift 6):
Sources/DAWFileKit/Cubase/TrackArchive/TrackArchive xmlString.swift#L235
> TODO: needs coding - add tracks and tempo events
|
|
watchOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
watchOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|
|
watchOS:
Sources/DAWFileKit/MIDIFile/Conversion/MIDIFile Converting DAWMarkers.swift#L160
> TODO: this may need to factor in marker's original session start timecode against the 'startTimecode' parameter passed into this function. should be an abstracted method that can convert/flatten a marker to a resolved timecode at a certain framerate and start time
|
|
watchOS:
Sources/DAWFileKit/ProTools/SessionInfo/Parse/SessionInfo Parse Sections.swift#L45
> TODO: (Not all PT frame rates have been tested to be recognized from PT text files but in theory they should work. Need to individually test each frame rate by exporting a text file from Pro Tools at each frame rate to ensure they are correct.)
|