KejPi
AbracaDABra PTy not exporting to .csv file.
Hi, I’m using Windows 11. On my laptop when exporting Ensemble Information "Export as CSV” file, the PTy info is not always exported to the .csv file. This mainly happens when exporting UK Small Scale Mux’s.
Hi, that is an interesting issue. I assume that you can see PTy in ensemble information but it does not appear in the CVS. Could you please share short IQ recording (30 sec should be fine) of affected ensemble?
You can zip the file or just rename it as zip should work too. Or you can upload it to some cloud and share the link to me privately by email. I think the problem is due to dynamic PTy that is not written to CSV, only static PTy is considered.
At Home in UK, I can receive 14 Multiplexes. 7 are Small Scale (SSDAB) all with dynamic PTy and all 7 don’t export to CSV. the other 7 are “static” and work ok? so you are correct. I am an editor for FMLIST/DABLIST for the UK and I travel around the UK collecting multiplexes to update DABLIST. it’s so time consuming having to fill in the PTy info. Thanks for your replies, much appreciated.
Application also uploads CSV to FMLIST/DABLIST automatically if enabled and in this case also only static PTY is considered. I am not sure if I discussed this topic with Günter specifically, but it is not problem to change the implementation. The question is what to do when both static and dynamic are broadcasted. Furthermore, dynamic PTy is changing in time (in theory), so does is make sense to store current PTy to CVS (FMLIST) considering that it can be different next minute.
In the UK only the BBC have dynamic PTy, all others do not change their PTy. As an editor for DABLIST, I would normally make manual entries.
Only the BBC change the PTy according to the programme being broadcast, on all National Networks. Wales, Scotland & N Ireland are dynamic. BBC locals are all Varied/Talk. All others stay the same and don’t change, in my experience.