Welcome to the Rockbox Technical Forums!
Looking at http://taperssection.com/index.php/topic,83004.0.html it seems something is funky with the REP build.... maybe the gui stuff is overloading the cpu during some peak moments?Warning 00000001 is being mentioned in above link
If something is funky with the REP build which it seems to be, esp. for digital in users, I'd suggest mmmm take a look and make sure:1) No threads are being boosted in priority (via thread_set_priority).2) CPU frequency scaling is set to boosted at all times when running S/PDIF. 3) That all code yields very frequently and never starves the codecs of cycles.If I think of any more points to check, I'll post.
I've just looked at the REP patch for the first time and I'm wondering:1) where does the changed dB conversion come from. I once committed changes to that (from Vinylivo), and I wonder it this reverts to the old values or is a new fix that results in more accuracy?
2) I'm thinking of moving the peakmeters below the last line and add a simple if(LCD_HEIGHT > xxx) to double the peakmeter height. That will also leave a nice upper-right corner for a REC/PAUSE symbol.
More recscreen layout changes should wait until after the viewport stuff, and it should go towards a WRS
I've gotten the errors in different recording sessions. My drive is 80% filled and I am using Paulheu's most recent build (mid Feb.) with REP. Analog of course....... I am not sure if any optical issues apply to these errors.....
I will pay closer attention to this thread and not at tapperssection.com, so the people ACTUALLY addressing my problems (rockbox & REP devs) have less steps out of there way.
I've gotten the errors in different recording sessions. Â My drive is 80% filled and I am using Paulheu's most recent build (mid Feb.) with REP. Â Analog of course....... Â I am not sure if any optical issues apply to these errors.....
Ok, a slightly modified version of the REP in my sig (some yields() included)... Needs lots of testing from as many people as possible to find out if I've fixed it or not...This build includes JSMikes recording debug screen which is activated by toggling the remote lcd on and off while you are recording (Vol - key on remote, press stop to exit the debug screen). I think that on this screen you should see the top bar staying on 0. if it changes there could be a problem... This screen is a bit new to me so cant be certain.You can obviously still record as normal....If any errors or dropped samples come up with this build then post here and I'll try something else...
Page created in 0.263 seconds with 18 queries.