kvanderwende
Forum Replies Created
-
Forum: Plugins
In reply to: [Sermon Browser] You do not have the correct permissions to edit sermons@josephlgrant The links for Delete are being created correctly when the page loads initially but any navigation or filtering renders the content again with incorrect links. To work around this you can go into the Options and set your sermons per page high enough to include the sermon(s) you need to delete. Do not sort or filter. Then change the sermons per page back after you have deleted.
Forum: Plugins
In reply to: [Sermon Browser] You do not have the correct permissions to edit sermonsIf you filter or page the link for delete is missing the nonce from the querystring. Depending on how old the sermon is you need to delete you can set the sermons per page option very high so that it is on the first page when it loads. This is a workaround until the fix for the paging and filtering is uploaded.
Thank you for that information. I was thinking the images were the culprit. I will pass this along.
I thought I’d let you know what I found. My friend uses an ID3 editor to add a variety of metadata to the file before submitting to iTunes. I took the latest episode and tested the location of the data offset. WITH the embedded artwork it is 1982592. If I remove the artwork from the metadata it starts at 3366.
I also created a short Mp3, about 1:30 in length, using Audacity. I exported it with no metadata. The avdataoffset was 0. When I added Artist, Title, Year, Genre the offset was 256.
Don’t know if that will help someone else or not.
Have a friend who uses Power Press. I parse the RSS for a MySql database. A while back the itunes:duration dropped out of the feed. Recently I wrote a script to test the Mp3Info class with a download limit that was higher than the default. In the past he exported at a bit rate of 96 then changed to 112.
I found that if I changed the download limit to 6MB the bitrate and duration would show up. The avdataoffset is pretty far into the file. Around 600,000. So the information is in the file it just requires downloading more of it. Does anyone know if an ID3 tag editor would cause the data to be stored outside the first 1024k of the file?
I’ve tested exporting from Audacity without modifying ID3 tags and the highest offset I found was around 5900.
Thanks,
Kevin